Directoryz

Track where listing facts came from

Source provenance makes future correction possible. Without it, an editor cannot distinguish a verified detail from an old assumption.

Directoryz editorial guide · Updated September 7, 2026

Put it into practice

Keep a source URL, checked date, and editor note alongside important facts. Revisit the source when the listing changes.

Worked example · illustrative

What this looks like

A provider's service area may come from its contact page, while a product integration's status may come from documentation.

Before you move on

Could another editor find the evidence for the published claim?

Write down the evidence for your answer. If you cannot point to a concrete example, revise the work before treating it as ready.

A repeatable workflow

  1. Choose a representative set of listings.
  2. Record the source and meaning of each field.
  3. Review the public result before applying changes widely.

Your working notes

Apply this guide to one real project. Notes stay in this page until you download them; they are not saved to your account.

Where Directoryz fits

Directoryz supports directory publishing, listings and custom fields, CSV imports, submission review, and workspace operations. These guides include editorial workflows you can carry out with a worksheet or your own tools. They do not imply that every audit, reminder, verification, or integration is automated by Directoryz.

Foundations and templates →