Directory submission checklist: review the form before you send it

To review a directory submission form, run the same directory submission checklist of 12 fields before you press send: account, product name, URL, tagline, description, category, pricing, logo, screenshots, links, social proof and the confirmation trail. The form belongs to the directory, not to you. Autofill moves values from one form to the next; it does not know that this directory limits the tagline to 60 characters or rejects a pricing field that says “contact us”.

This chapter is for the moment after the extension has filled the form and before you click submit. It takes one pass per directory, and it produces a record you can reuse when the next directory asks for the same facts in a different order.

Why an autofilled directory submission form still needs a review

A directory form is a set of decisions made by someone else. The field order, the character limits, the category tree and the review rules belong to the directory. Autofill can copy your product profile into those fields, but it cannot tell whether the result still means what you intended. That is the gap this checklist closes.

The first four layers you can verify inside the form. The fifth one you cannot. Read the directory’s submission rules on a separate tab, because the form will not repeat them and the reviewer will apply them after you leave.

The 12-field directory submission checklist

The checklist below has 12 rows, and it is a review order, not a score; we use this order as of 29 October 2026. Each row has one pass condition, so a second person can run the same check without asking what “looks fine” means.

The links row is the one people treat as automatic. Google’s documentation on crawlable links, checked 29 October 2026, says a link is crawlable when it is an <a> element with an href, and that the words between the tags tell the crawler what the destination is. A directory may render your URL as plain text, as a button, or as a redirect. Check the live result, not the field preview.

How to review the form in six steps

Run the steps in order. The first three protect the record, the last three protect the reader. Stop at the first step that fails and fix it before moving on, because a later field can hide an earlier mistake.

1. Open the directory’s rules in a second tab. Find the submission requirements, the character limits and the category definitions. Finish when you can name the one rule most likely to reject this listing.
2. Check the account and the product identity. Confirm the signed-in account, the product name and the canonical URL. Finish when all three match your product profile.
3. Read every filled field aloud. Autofill is fast and literal. Finish when no field contains a sentence that starts in one form and ends in another.
4. Test the two links a reader will click. Open the main URL and the secondary link in a private window. Finish when both land on the page you meant and neither carries a tracking parameter.
5. Look at the preview at the size a reader sees it. Check the logo, the screenshot crop and the tagline on a phone-width preview. Finish when the product is still identifiable without reading the description.
6. Save the confirmation before you close the tab. Record the date, the status and the listing URL or ticket in your tracker. Finish when the row exists, even if the status is still “submitted”.

Step three is the one that catches the most errors, and it costs almost nothing. Reading a field aloud forces you to parse it as a sentence rather than recognize it as a value.

What to do when a field does not fit

Most form problems are not errors; they are compression. You have three honest options, and one dishonest one. The honest options are to shorten the text, move the detail into the description, or skip the directory. The dishonest option is to leave a field that says something you cannot support.

Do not invent a number to fill a required field. A listing with an empty optional field is recoverable; a listing with a false claim is a support ticket waiting to happen.

Three ways this review goes wrong

All three are shortcuts taken at the end of a launch week. None of them looks broken in the form preview.

1. Reviewing the preview instead of the live page. The preview shows your input; the live page shows what the directory did with it. Open the published listing after it goes live.
2. Reusing one description everywhere. A description written for a launch platform reads like an ad on a niche directory. Rewrite the first sentence for the reader who is already in the category.
3. Treating “submitted” as “done”. The tracker row is not the result. Add the live URL and the date you verified it, or the row will lie to you in a month.

What this checklist cannot do

A directory submission checklist cannot tell you whether the directory will approve the listing. We do not know how long a reviewer will take, what queue your form lands in, or which internal rule will decide the outcome. No checklist can promise approval, and a directory that guarantees one is telling you something about its review process.

It also cannot tell you whether the listing will send traffic or conversions. A live listing proves that a page exists. It does not prove that anyone clicked it, and it does not prove that a click became a customer. Those are separate measurements, taken later, with their own limits.

And it cannot replace the directory’s own instructions. If the form and the help page disagree, the help page wins; if the help page and the reviewer disagree, the reviewer wins. Keep the confirmation so you can show which version you followed.

Common questions

Do I need a different description for every directory?

Usually yes, at least the first sentence. The facts can stay the same, but the reader’s context changes: a launch platform reader is browsing new products, while a niche directory reader is already looking for a tool in that category. Lead with the reason that reader is there.

What if no category fits my product?

Choose the nearest parent category and explain the fit in the first line of the description. Do not choose a wrong specific category to look more relevant. The reviewer will see the mismatch, and a later correction is harder than a clear parent category.

Should I put UTM parameters in the directory link?

Not in the main website field. Many directories treat that field as the canonical listing URL, and a tracking parameter makes the same product look like two pages. If the form has a separate campaign or source field, use that. If it does not, record the directory name in your own tracker instead.

How long should the review take?

Long enough to open the rules, read each field aloud and test both links. The number of fields matters less than the number of fields that autofill guessed. Count the guesses, not the rows.

Where does this fit in the workflow?

After you have chosen which directories to submit to and before you record the result in the directory submission tracker. The selection decides where to go; this review decides whether the form is ready; the tracker keeps the evidence. The channel distribution workflow is built around that order: profile, fill, confirm, record.

A directory submission form is a small contract. You supply the facts, the directory supplies the rules, and the review is where you check that both sides still agree. Do it once per form, keep the confirmation, and the next listing starts from a record instead of a memory.