what tools are you using for link building and mention outreach?
by•
quick one for anyone doing SEO or growth for clients.
i mean the grind of getting placed in listicles, roundups and comparison pages. finding the pages, digging up who maintains each one, personalized pitches, follow ups, tracking who answered and who actually placed you.
asking because clients started raising the "why doesnt ChatGPT mention us" question, and the answer mostly runs through exactly these pages. AI answers cite listicles and roundups far more than homepages.
so whats your stack? one tool that covers the whole flow, a mix of prospecting and email tools, or a spreadsheet you keep alive by hand? curious what holds up at real volume, hundreds of targets, not ten.
60 views
Replies
No tool here, and I'm at ten targets, not hundreds, so take this as the small-scale version. For a dev tool (an MCP server for an AI chess/Go arena), the pages that mattered weren't blog listicles. They were the official MCP Registry, Glama, and the awesome-mcp-servers lists on GitHub. Those take a PR, not a pitch, so there's no one to dig up and nothing to follow up. One of the PRs sat open until Glama finished scoring the server, and that only happened after I fixed a missing argument in its build spec. Small directories (AI Agents Directory, APITracker, IndieHackers' product database) were forms. The hard part was checking later whether a listing went live. For a couple of them I still can't verify it from outside. If your clients are in a niche with GitHub "awesome" lists, check those first. Same effect on AI answers, much less outreach.
@wwenioaguiar Enio the PR-instead-of-pitch angle is a great flip. in dev niches the gatekeeper is a maintainer or a build check, so prospecting and follow ups mostly vanish. ive been through the MCP directory circuit and it matched your experience exactly.
the verification gap you mention is the underrated part. no clean way to confirm a listing went live from outside, and that pain only grows with volume. how long did the Glama loop take end to end?
@artem_fedorovich About three days. I opened the awesome-mcp-servers PR on Sep 4, the Glama listing went live on the 5th, and the PR merged on the 7th. The holdup was the score. It sat at "?" because the server never had a Glama release: the Dockerfile settings in Glama's admin page were missing the "mcp" subcommand, so the server exited before the MCP handshake. Once I fixed that, the score came back at 3.8 (A) and the PR merged the same day.
One more thing if you're doing this for clients: Glama scores each tool description separately. One of my nine tools got a C for not explaining its parameters or errors. Rewriting that description was the cheapest fix of the whole process.