Directoryz

Request listing corrections clearly

A correction request should tell the contributor what is missing and why it matters. Broad feedback often produces another unusable revision.

Directoryz editorial guide · Updated September 7, 2026

Put it into practice

Name the field, describe the issue, and provide an acceptable example. Keep factual corrections separate from optional style suggestions.

Worked example · illustrative

What this looks like

Please replace the homepage link with the integration documentation URL explains the action more clearly than Improve the link.

Before you move on

Could the contributor make the correction without asking what you meant?

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. Explain the information required before submission.
  2. Review facts separately from presentation.
  3. Give contributors a clear next step.

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 →