SaaS directory submission checklist

1. Create a dated source of truth

Directory pages drift when each form is completed from memory. Start with a short, dated record that one person owns. Every claim should be visible on the live product, supported by an internal source the owner can verify, or deliberately omitted.

• Exact product and company names, including capitalization.
• Canonical public URL and preferred landing page.
• Current availability, platform, pricing model, and trial or free-plan status.
• Primary audience, problem solved, and product category.
• Monitored support or founder contact and record owner.
• Date facts were checked and event that should trigger another review.

2. Prepare copy for different field jobs

One paragraph rarely fits every form. Keep a factual base, then write variants for common jobs. Character limits differ, so verify the live form rather than assuming a universal number.

• One-line tagline: audience plus outcome, without an unsupported superlative.
• Short description: what the product does, who it is for, and one meaningful distinction.
• Long description: problem, workflow, important boundaries, pricing state, and availability.
• Category and tags: the smallest set a real buyer would use to find the product.

Adapt wording to the directory's taxonomy and readers. Do not rotate keywords or claims merely to make submissions look unique.

3. Inspect media at the sizes people will see

Keep a square logo, a wide social image when accepted, and a small set of current interface screenshots. Use real product states. Remove customer records, emails, tokens, private repository names, and unrelated browser UI.

• Logo remains legible on light and dark backgrounds.
• Screenshots show distinct, current parts of the product.
• Each file meets the live form's type, dimension, and size limits.
• Image owner has permission to publish every visible element.

4. Choose stable links

Use the canonical product URL requested by the directory. Keep campaign tracking in your own records when a form prohibits tracking parameters. Check pricing, documentation, demo, privacy, and support links in a signed-out browser.

5. Qualify the directory before completing it

A large list of targets is not the same as a useful list. Check whether the directory serves your audience, accepts your product type, has current editorial activity, and publishes rules you can follow. Avoid targets whose main pitch is manipulating rankings or selling a promised outcome.

• Inspect recent listings and the categories buyers actually browse.
• Confirm paid, open-source, regional, maturity, or launch-date requirements.
• Record fees, recurring obligations, badge requirements, review rules, and correction routes.
• Skip forms that demand unnecessary secrets, broad account access, or misleading reciprocal claims.

6. Protect accounts and contacts

Use a monitored business address when appropriate and a password manager for any new credentials. Grant only the access needed for the current workflow. Never paste API keys, recovery codes, private repository content, or customer data into a listing form.

7. Review and record each decision

Before the final action, compare the preview with your source record. Afterward, save exactly what happened; do not equate a confirmation screen with publication.

• Product facts and pricing match the current live site.
• Category, tags, and description fit this directory's readers.
• Required disclosures and relationship to the product are clear.
• Submitted URL and media are correct.
• Log records target, date, owner, exact state, and any follow-up date.
• Status distinguishes drafted, submitted, acknowledged, approved, published, rejected, and removed.

8. Refresh the facts, not the promises

Review published pages when pricing, positioning, ownership, availability, or major screenshots change. Correct stale facts through the directory's supported route. Measure referral visits and conversions separately from whether a page exists.