DEV Community

Alex Spinov
Alex Spinov

Posted on

I Built 130 GitHub Repos in 2 Weeks — Here's What I Learned About Developer SEO

#discuss #github #programming #career

Two weeks ago I had 0 GitHub repos. Today I have 130+. Most are developer tools — API wrappers, security scanners, data extraction scripts.

Here's what I learned about making repos discoverable.

The 80/20 of GitHub SEO

After analyzing which repos get traffic, three factors dominate:

1. README Length Correlates With Stars

Repos with READMEs over 500 words get 4x more traffic than those with short READMEs. GitHub's search heavily weights README content.

Minimum viable README:

  • One-line description
  • Screenshot or code example
  • Installation instructions
  • 3-5 usage examples
  • Related links

2. Repo Name = Keywords

GitHub search matches repo names first. Compare:

  • my-scraper → nobody finds this
  • reddit-data-scraper-python → found by people searching "reddit scraper python"

Name your repos like you'd name a blog post: describe what it does, include the technology.

3. Topics/Tags Are Underused

GitHub lets you add up to 20 topics per repo. Most developers add 0-3. I add 10-15:

python, api, scraper, web-scraping, data-extraction, 
automation, cli-tool, developer-tools, free-api, 
open-source, data-science, security
Enter fullscreen mode Exit fullscreen mode

Each topic is a discovery channel. Someone browsing github.com/topics/web-scraping might find your repo.

The Awesome List Strategy

My highest-traffic repo is awesome-free-apis-2026 — a curated list of 200+ free APIs.

"Awesome lists" work because:

  1. People search for "awesome X" on GitHub
  2. They're shareable on social media
  3. They attract stars just by being useful
  4. Internal links drive traffic to your other repos

Key: Include links to YOUR tools in the awesome list. Not spammy — genuinely useful tools that solve problems the list readers have.

Cross-Linking Is Free SEO

Every repo's README links to 3-5 of my other repos in a "Related" section. This creates an internal link network that:

  • Increases time-on-profile
  • Boosts discovery of less popular repos
  • Builds perceived authority (130 repos looks more credible than 5)

What Didn't Work

  • Too many repos too fast looks spammy
  • Empty READMEs get zero traffic
  • Generic descriptions ("A tool for things") don't attract clicks
  • No topics means zero discovery from GitHub's topic pages

The Compounding Effect

The first repo took hours. By repo #50, I had templates. By #100, I could publish a complete repo in 15 minutes. Each repo links to others, creating compounding discovery.

What's Your GitHub Strategy?

Do you think about SEO when creating repos? Or is it purely for personal/team use?

Check out my 130+ repos or my security toolkit.

Top comments (0)