Directoryz
The Directoryz field guide

Listing data

Make every listing useful enough to support a real decision.

13 practical guides1 topic
Listing data

Choose required fields for a directory listing

Required fields should support the visitor's first decision.

Read the guide ↗
Listing data

Write unambiguous listing field definitions

A field name alone may not tell contributors what belongs in it.

Read the guide ↗
Listing data

Represent unknown listing information clearly

Unknown, not applicable, and unavailable are different states.

Read the guide ↗
Listing data

Write listing descriptions that add useful context

A description should explain what the listing offers and who can use it.

Read the guide ↗
Listing data

Track where listing facts came from

Source provenance makes future correction possible.

Read the guide ↗
Listing data

Use 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 data

Choose a clear contact route for listings

Visitors need to know what happens when they contact a provider.

Read the guide ↗
Listing data

Choose informative listing images

An image should identify the listing or show something relevant to the decision.

Read the guide ↗
Listing data

Model directory price information without false precision

Pricing often depends on scope, plan, or usage.

Read the guide ↗
Listing data

Separate service areas from office locations

A provider can serve places where it has no office.

Read the guide ↗
Listing data

Give each listing a stable identity

A listing needs a stable identifier even when its name or website changes.

Read the guide ↗
Listing data

Define listing status labels people understand

Status labels should describe a real editorial or operational state.

Read the guide ↗
Listing data

Create a model listing for contributors

A completed example can teach contributors more than a long form instruction.

Read the guide ↗