Listing rules
Every project on SaaSClimb must follow these rules. Last updated 2026-10-19. Plain Markdown version.
1. Your GitHub account is at least 6 months old
- You sign in with GitHub to submit. The account must have been created at least 6 months before you submit.
- This keeps out throwaway accounts made just to collect links.
How we check: Checked when we review your submission.
2. Your domain is at least 30 days old
- Your project's domain must have been registered at least 30 days before you submit.
- Brand-new domains are the most common source of spam. If yours is newer, wait and submit later.
How we check: Checked when we review your submission.
3. It's a working product
- Visitors can sign up, log in, download or buy something from your site today.
- Not accepted: coming-soon pages, waitlist-only pages, parked domains, domains for sale and error pages.
How we check: Checked when we review your submission, and automatically every week.
4. Your site does what your description says
- Describe what your site does today, not what you plan to build.
- Editing your project's name, description, logo or banner sends it back for review, and it's hidden until it's approved again.
How we check: Checked when we review your submission, and automatically every week.
5. No ads
- Your site must not show any ads. That includes display ads, ad networks such as Google AdSense, sponsored ad slots, and pop-up or interstitial ads.
- Sites with ads are rejected, and a listed project is removed as soon as ads are found on it.
How we check: Checked when we review your submission and whenever we revisit listed projects.
6. No gambling, adult, crypto schemes, link farms or get-rich-quick schemes
- Not accepted: gambling and betting, adult content, crypto casinos, token sales and pump schemes, affiliate sites and link farms, and get-rich-quick or make-money-online schemes.
How we check: Checked when we review your submission and whenever we revisit listed projects.
7. Your site is safe and stays on its own domain
- No malware, phishing, deceptive downloads or anything that tricks visitors.
- Your URL must not redirect to a different site. Redirects from http to https, between example.com and www.example.com, and to your own subdomains (app.example.com) are fine.
How we check: Checked when we review your submission and whenever we revisit listed projects.
8. Visitors can contact you
- Your site shows a working way to reach you: an email address, a contact form, or a link to your profile on X, GitHub, LinkedIn or similar.
- If your product collects personal data from users, your site has a privacy policy.
How we check: Checked when we review your submission.
9. Your numbers are real
- Numbers from your own endpoint are labeled "Self-reported". Only Stripe revenue is labeled "Verified".
- Self-reported numbers must reflect your product's real usage. Projects caught faking them are removed.
How we check: Reviewed by hand.
How listing works
- An admin reviews every project before it goes live.
- Your project gets its own page once it's approved. It shows on the homepage only after you connect at least one metric: Stripe, your own endpoint, or both. You can connect them when you submit or later from My projects.
- We check listed projects again every week, and by hand from time to time, to make sure they still follow these rules.
Backlinks
- Every approved project page links to your site. The link is nofollow (rel="ugc nofollow") by default.
- Verified projects (Stripe connected) with at least 30 days of metric history can be reviewed for a dofollow link. We review these by hand, and approval isn't guaranteed.
- A project that breaks a rule or gets suspended goes back to nofollow.
If a project breaks a rule
- A project that breaks a rule is rejected, or suspended if it's already listed. Its page and homepage row are hidden.
- When we give a reason for a rejection, it shows in My projects.
- Rejected: fix the problem and submit the project again.
- Suspended: fix the problem, then update your project's details from its page to send it for review again.
- The weekly check also suspends a project when its site can't be reached two weeks in a row.