Listing data
Make every listing useful enough to support a real decision.
Choose required fields for a directory listing
Required fields should support the visitor's first decision.
Read the guide ↗Listing dataWrite unambiguous listing field definitions
A field name alone may not tell contributors what belongs in it.
Read the guide ↗Listing dataRepresent unknown listing information clearly
Unknown, not applicable, and unavailable are different states.
Read the guide ↗Listing dataWrite listing descriptions that add useful context
A description should explain what the listing offers and who can use it.
Read the guide ↗Listing dataTrack where listing facts came from
Source provenance makes future correction possible.
Read the guide ↗Listing dataUse a meaningful last-reviewed date
A review date should indicate that someone checked the listing, not merely that a file was rebuilt.
Read the guide ↗Listing dataChoose a clear contact route for listings
Visitors need to know what happens when they contact a provider.
Read the guide ↗Listing dataChoose informative listing images
An image should identify the listing or show something relevant to the decision.
Read the guide ↗Listing dataModel directory price information without false precision
Pricing often depends on scope, plan, or usage.
Read the guide ↗Listing dataSeparate service areas from office locations
A provider can serve places where it has no office.
Read the guide ↗Listing dataGive each listing a stable identity
A listing needs a stable identifier even when its name or website changes.
Read the guide ↗Listing dataDefine listing status labels people understand
Status labels should describe a real editorial or operational state.
Read the guide ↗Listing dataCreate a model listing for contributors
A completed example can teach contributors more than a long form instruction.
Read the guide ↗No matching guides. Try a shorter phrase or clear your search.