Developer tool playbook
Directory submission for developer tools
Developers find tools on GitHub, Hacker News and inside their stack, and almost all of those links are nofollow. So this splits in two: where to get seen by developers, and the separate, smaller set of directories that actually give you dofollow backlinks.
- 17
- Dev channels
- 10
- Dofollow sources
- 9
- DR 80+ reach
- 17
- Free to submit
Updated 2026-06-14 · DR data: Domain Rating by Ahrefs
If you only do five things
- 01Get a clean README with a demo GIF, since every dev directory judges you by it first.
- 02PR your tool into the relevant awesome-lists, the highest-leverage dev visibility there is.
- 03Post Show HN and launch on DevHunt the same week for the traffic spike.
- 04For backlinks, do the dofollow set: SourceForge, OpenAlternative, LibHunt, SaaSHub and SaaSCity.
- 05Write one honest dev.to build log showing the tool solving a real problem.
What dev-tool directory submission actually does
The nofollow reality changes the math. Here is where the effort really pays.
Genuinely worth it for
- +GitHub stars and real developer traffic (awesome-lists, Show HN)
- +Credibility, since this is where developers expect to find tools
- +Dofollow backlinks from the right, smaller set of directories
- +Language- and stack-scoped discovery (LibHunt, StackShare)
Not a fix for
- -Domain Rating via GitHub or HN, since those links are nofollow
- -A weak README, which directories and devs both bounce off
- -Wrong or missing language tags, which keep you from being found
- -Mass-PRing awesome-lists, since maintainers reject low-effort spam
Prepare once, paste everywhere
Your dev-tool submission kit
Dev directories care about a clean one-liner, an honest install command and the right tags. Write these once, then reuse them across every listing, PR and post.
[Outcome] for developers: [how, in three words].
[Tool] is a [language] [category] that [does what] for [who]. [Key feature]. [License]. Docs at [url].
npm install [tool] # or: brew install [tool] · pip install [tool] · go install [tool]
Show HN: [Tool] - [what it does, no marketing language]
Have ready before you submit
- +README: include a demo GIF in the first screenful, because devs judge in seconds
- +License: state it clearly (MIT, Apache-2.0, and so on) where relevant
- +Language and framework tags: exact, because dev directories are tag-driven
- +Logo: 512x512 PNG, transparent background
- +Screenshots, or a 30 to 60 second demo of the tool running
Track 1 · Visibility (mostly nofollow)
Where developers actually discover tools
High reach and high credibility, and almost entirely nofollow. You are here for stars, traffic and being where developers look, not link equity. For a dev tool, this is the growth engine, so do not skip it just because the links do not count.
- 01DR97GitHub Awesome Listsgithub.comnofollowFree
Where developers actually find tools. The links are nofollow, so you are here for stars, traffic and credibility, not link equity. One accepted awesome-list entry compounds for years.
- Needs
- A polished README with a demo GIF
- How
- Open a PR adding your tool to the relevant awesome-X list
- 02DR91Hacker Newsnews.ycombinator.comnofollowFree
A front-page Show HN is the single biggest dev-traffic event there is. It is nofollow, but the reach earns real dofollow links and press elsewhere.
- Needs
- A working demo and an honest “Show HN:” title
- How
- Post on launch day, reply to every comment
- 03DR90DEV Communitydev.tonofollowFree
A huge developer audience and strong distribution. Profile and post links are nofollow; the value is reach and showing the tool in real use.
- Needs
- A genuine technical post, a build log or how-to that uses your tool
- How
- Publish an article (cross-post with a canonical URL)
- 04DR79StackSharestackshare.ionofollowFree
Developers browse and compare stacks here. Listing links are nofollow (verified), so this is pure visibility in front of a buying-intent dev audience.
- Needs
- A tool profile in the correct stack category
- How
- Add your tool, then list your own stack to seed it
- 05DR70Slantslant.conofollowFree
Ranks for the “best [category] tool” queries developers actually search. Option links are nofollow, but the placement gets you in front of comparison shoppers.
- Needs
- Your tool added as an option with honest pros and cons
- How
- Contribute to the relevant “best X” topics
Track 2 · Dofollow backlinks
Where the dofollow links actually are
A smaller, separate set. These pass real link equity and move your Domain Rating, which the nofollow giants above cannot. Work them top-down by DR, free ones first.
- 01DR92Sourceforgesourceforge.netdofollowFree + Paid
DR-92 dofollow. It is the single highest-authority backlink in the dev set, and indexed everywhere crawlers look.
- Needs
- A project or software listing
- How
- Create a project page
- 02DR62DevHuntdevhunt.orgdofollowFree + Paid
Dofollow, plus a purely developer launch audience with higher signal-to-noise than a general launch board.
- Needs
- Standard launch listing assets
- How
- Launch on DevHunt (the dev-specific Product Hunt)
- 03DR51Open Alternativeopenalternative.codofollowFree
Dofollow, and a fast-growing open-source discovery site. Ideal if your dev tool is open source.
- Needs
- List your open-source tool as an alternative to a proprietary one
- How
- Submit as an OSS alternative
- 04DR62LibHuntlibhunt.comdofollowFree
Dofollow project links (verified) and language-scoped discovery, which is a strong fit for libraries, SDKs and CLI tools.
- Needs
- Your library or SDK added to the right language topic
- How
- Submit to the language-specific list
- 05DR59Console.devconsole.devdofollowFree
A respected curated dev-tools newsletter. A feature drives a high-quality developer audience and a dofollow link.
- Needs
- Submit for the curated review or newsletter
- How
- Submit, then editorial review
- 06DR91G2g2.comdofollowFree + Paid
DR-91 dofollow that both buyers and AI assistants cite, worth it for dev-infra and team tools with a buyer.
- Needs
- Product profile, verified work email, category, then seed reviews
- How
- Claim and verify your listing
- 07DR42SaaSCitysaascity.iodofollowFree + Paid
Full disclosure: this is us. A free permanent dofollow link plus a spot on the live 3D city map. An easy first dofollow win.
- Needs
- Name, logo, one-line pitch (about two minutes)
- How
- Submit free
List your dev tool free, DR 45 dofollow
SaaSCity is one of the dofollow picks above. It is a free, permanent dofollow link plus a spot on the live 3D city map. It takes about two minutes, and gives you a clean first backlink while you work the rest.
The honest version
Why nofollow stars beat a dofollow link here
For most products, a dofollow backlink is the prize. For developer tools, it is often the opposite: a spot on a popular awesome-list or a front-page Show HN sends hundreds of qualified developers, earns GitHub stars, and triggers the organic blog posts and links that are dofollow, none of which the original nofollow link gave you directly.
So run both tracks, but weight by goal. If you are chasing growth and adoption, do Track 1 first. If you are chasing Domain Rating for your own site, do Track 2. The mistake is assuming the GitHub or HN link is doing your SEO. It is not, and a clear-eyed plan puts the dofollow effort where it actually lands.
What to expect
A realistic timeline
- Week 1
PR your tool into the relevant awesome-lists, post Show HN, launch on DevHunt, and write one dev.to build log. Stars, traffic and your first community visibility.
- Weeks 2 to 4
Work the dofollow set: SourceForge, OpenAlternative, LibHunt, SaaSHub and G2. As these get crawled, your Domain Rating starts to move, which is the part GitHub and HN cannot do.
- Month 2 to 3
Awesome-list inclusion compounds, since more stars bring more lists, which bring more stars. Listings index, and a Console.dev feature lands if your submission is accepted. Reach and authority both stack.
Avoid these
Mistakes specific to dev-tool listings
- -Submitting before the README is good
Developers judge in ten seconds. Without a demo GIF, a clear install command and a license, your listing or PR is dead on arrival, however good the tool is.
- -Treating the GitHub or HN link as a backlink
They are nofollow. Chase them for stars and traffic, and get your dofollow links from SourceForge, LibHunt, OpenAlternative and the rest of Track 2.
- -Wrong or missing language or framework tags
Dev directories and their search are tag-driven. “Developer tool” is invisible; “TypeScript CLI for X” gets found.
- -Mass-PRing awesome-lists
Maintainers reject low-effort, self-promotional PRs fast. One well-placed entry in a genuinely relevant list beats ten rejected ones.
Developer tool directory submission FAQ
- Do GitHub and Hacker News links help my SEO?
- No. Links from GitHub READMEs and Hacker News are nofollow (verified), so they pass no ranking authority. They are still among the most valuable places to be, because they drive stars, real developer traffic, and the natural press and links that follow. Treat them as visibility, not link building.
- Where do developer tools actually get dofollow backlinks then?
- From a separate, smaller set: SourceForge (DR-92), DevHunt, OpenAlternative, LibHunt, Console.dev, SaaSHub and G2 all pass dofollow links. There are 10 dofollow sources in the list below. Work those for Domain Rating, and use GitHub, HN and dev.to for reach.
- How do I get my tool into an awesome-list?
- Find the awesome-X repo for your category, read its contributing rules, and open a clean pull request that adds your tool in the right section with a one-line description. Maintainers reject low-effort or self-promotional PRs, so make sure your README and demo are solid first. One accepted entry compounds for years.
- Is StackShare or dev.to worth it if the links are nofollow?
- Yes, for reach. StackShare puts you in front of teams comparing stacks; dev.to and Hashnode give you a large built-in developer audience for a build log or how-to. You are not doing these for link equity. You are doing them to get discovered and to demonstrate the tool.
- Free or paid dev directory listings?
- Almost everything here accepts free submissions, 17 of them. The dev ecosystem rewards good open work over paid placement, so spend your effort on a strong README and genuine community posts before paying for anything.
Full reference: all 17 dev channelsopenclose
| Directory | DR | Link | Price | Submit |
|---|---|---|---|---|
GitHub Awesome Lists github.com | 97 | Nofollow | Free | Visit |
Sourceforge sourceforge.net | 92 | Dofollow | Free + Paid | Visit |
Capterra capterra.com | 91 | Dofollow | Free + Paid | Visit |
G2 g2.com | 91 | Dofollow | Free + Paid | Visit |
Hacker News news.ycombinator.com | 91 | Nofollow | Free | Visit |
Product Hunt producthunt.com | 91 | Nofollow | Free | Visit |
DEV Community dev.to | 90 | Nofollow | Free | Visit |
Hashnode hashnode.com | 83 | Nofollow | Free | Visit |
Indie Hackers indiehackers.com | 81 | Dofollow | Free | Visit |
SaaSHub saashub.com | 79 | Dofollow | Free | Visit |
StackShare stackshare.io | 79 | Nofollow | Free | Visit |
Slant slant.co | 70 | Nofollow | Free | Visit |
DevHunt devhunt.org | 62 | Dofollow | Free + Paid | Visit |
LibHunt libhunt.com | 62 | Dofollow | Free | Visit |
Console.dev console.dev | 59 | Dofollow | Free | Visit |
Open Alternative openalternative.co | 51 | Dofollow | Free | Visit |
SaaSCityThat's us saascity.io | 42 | Dofollow | Free + Paid | Submit free |
Showing 17 of 17. DR = Domain Rating by Ahrefs.
Want general directories too? See the full SaaS directory list.
Get your dev tool listed in two minutes
Claim a free, permanent dofollow listing on SaaSCity, then run both tracks of the playbook.