Directoryz

Explain a rejected directory submission

A rejection should refer to the directory's stated scope or requirements. A short reason helps contributors understand whether revision is possible.

Directoryz editorial guide · Updated September 7, 2026

Put it into practice

Use a specific policy reason and explain whether a corrected submission is welcome. Avoid implying a quality judgment you did not make.

Worked example · illustrative

What this looks like

A general agency submission can be declined from a product-integration directory because it is outside scope.

Before you move on

Does the reason match the criteria contributors saw before submitting?

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 →