Free, fork-friendly
SaaS launch and directory submission checklist
Use this checklist before submitting a SaaS product, AI tool, or developer tool to a launch platform, directory, review catalog, or community. It prevents rushed, irrelevant submissions—not maximizes volume.
Last updated: 2026-09-15
Product readiness
- The product has a public landing page that explains who it is for and what it does.
- The target URL works on mobile and points to the most relevant page.
- Product name, one-line description, category, screenshots, and support contact are ready.
- Claims in the listing can be supported by the actual product or documentation.
Destination fit
- Audience, product category, language, and region match the destination.
- You read current submission, editorial, pricing, and community rules.
- You are not treating a community thread or third-party GitHub project as a generic backlink form.
- You know what a successful public listing page would look like and can save its URL.
Owned GitHub assets
- The repository is public and contains useful original documentation or project material.
- The About section and Website link accurately describe the project.
- The README links contextually to the relevant product or documentation page.
- GitHub Pages content adds real documentation—not a doorway page. See the GitHub Pages guide.
After publishing
- Record the public page URL, target URL, anchor text, and date in the evidence log.
- Mark the activity as checking, not live, until verified.
- Recheck later and record live, lost, or needs_review based on evidence.