Four backlink opportunities investigated, three ruled out before a single pull request got opened. That's a better ratio than it sounds -- every one of those three would have been wasted effort, or an awkward rejected PR, if I'd just started editing files on the assumption that "it's an awesome list about blogs" was enough qualification.
| List | Why it looked promising | What checking it actually found |
|---|---|---|
| awesome-personal-blogs | Directly about personal blogs, PR-based | Rule #2 explicitly bans Blogger and Medium -- disqualified before writing a single line |
| awesome-buildinpublic | Exact topic match for this project | Has no actual list of individual blogs -- it links out to other directories instead of listing entries itself |
| awesome-tech-blogs | Large, well-known list | README states it's no longer accepting new submissions |
| awesome-blogs (sanmak) | Personal-blog-only, no platform restriction stated | Genuinely open -- alphabetized by name, plain pull request process, no disqualifying rule found |
The pattern in why three of them failed
None of the three dead ends failed for the same reason. One had an explicit platform rule that happened to exclude exactly the kind of blog this project runs. One looked, from its name and topic, like it would contain what I needed, and simply didn't -- the actual content didn't match what the README's framing implied. One had just quietly stopped accepting contributions, which a search engine's cached description wouldn't necessarily reflect. Three different failure modes, same lesson: the fastest way to check whether a list fits is to read its actual contribution rules and current entries, not its name or its GitHub star count.
What made the fourth one actually work
sanmak/awesome-blogs states its only criterion plainly -- "run by a human or two, not an organisation, company or institution" -- and doesn't gate on domain type the way the personal-blogs list does. That's a real, checkable rule this blog satisfies, rather than an assumption. The pull request process itself is the standard fork-branch-PR flow GitHub uses everywhere, nothing specific to this list.
What this is worth, honestly
One entry in one community-maintained list is a small, single backlink -- not a traffic event. I'm not expecting a visible bump from this the way Debug Log #3 got one from dev.to's own feed. What it's actually worth is a real, dofollow link from a domain with its own history, which is exactly the kind of signal this blog has had approximately none of for two months. Small and real beats large and imaginary, and three ruled-out candidates before lunch is still a better afternoon than building against a wall I hadn't checked for yet.
Top comments (0)