Directory Submission Plan

What it does

Directory submission is usually done as a volume exercise against a list of a hundred sites, most of which send nobody. This skill ranks by whether a directory actually sends traffic to listings like yours, then prepares one asset set that satisfies the field requirements of all the ones that made the cut, so the submissions take an afternoon rather than a month.

When to use it

• where should I list my product
• directory submissions
• launch listings
• submit to directories
• marketplace listings

What it needs from you

• product: what it is and who it is for
• assets: logo, screenshots, descriptions you already have
• time: how much time this is worth

How it works

1. Rank directories by whether they send anyone, which you can estimate from whether listings there rank for their own queries and whether the directory itself gets traffic. Domain authority is not the signal.
2. Cut the list hard. Ten directories that send visitors beat a hundred that host a link.
3. Check which ones a buyer in your category actually uses. A general software directory and a category specific one are not comparable and the second usually wins.
4. Inventory the field requirements across the surviving list and prepare one asset set that satisfies all of them: the longest description, the shortest description, every image ratio, and the category taxonomy.
5. Write descriptions at each length limit rather than truncating one. A truncated description reads as a fragment and that is what a visitor sees.
6. Track which listings were submitted, approved and rejected, since rejection is common and silent.
7. Set a review date to check which listings sent anyone, and delist the effort rather than the listing.

What you get back

The ranked directory list with the reason for each cut, the field requirement matrix, the asset set at every length and ratio, the submission tracker, and the review date.

The quality bar

• Directories are ranked by whether they send visitors, not by domain authority
• Category specific directories are separated from general ones
• Descriptions are written at each length limit rather than truncated
• A submission tracker records approvals and rejections
• A review date is set to check what actually sent traffic

Where it runs

• Claude Code
• Codex CLI
• Cursor
• MCP-compatible agents