How AutoContent API got its users
Hundreds of templated pages built on one competitor's brand name and on X-to-Y format queries, with no-signup free tools and an MCP install page as the entry points.
Read from signals. Consistent with what is publicly observable, but nobody confirmed it. Check before you quote it.
You could start this on Monday. No budget, no audience, no permission needed.
- A traffic base that does not collapse when you stop publishing
- Acquisition that owes nothing to any social platform
- A proprietary or painful-to-assemble data source
- A template with a reason to exist page by page
- 6 to 12 months before it compounds
Programmatic SEO in 2026
Still alive, but the bar has moved. Thin pages get deindexed, so you need real data on every single page.
Everything on this channel →The play
5 steps, in the order they ran them.
- 1
Pick the one competitor whose product name your buyers already type, and build the spine around it: a /their-name-api page, a /their-name-alternative page, and one comparison page per rival framed as 'Them vs X', each with the same feature table (starting price, free tier, API access, voice cloning, languages, export formats) and a not-affiliated disclaimer in the footer.
done whenYour competitor-name pages show impressions on brand plus modifier queries in Search Console within 6 weeks, without any link building.
- 2
Build the X-to-Y grid out of the input and output formats your API actually supports, one page per pair (youtube-to-podcast, pdf-to-video, blog-to-slide-deck), each with a hero, a three-step how it works, an FAQ and a 'Get API Key' CTA that lands in the app.
done whenEach format pair page maps to a call you can actually run end to end, and queries you never wrote by hand start landing on those URLs.
- 3
Turn your product database into faceted pages the way they did with 68 voice pages: one URL per record, plus index pages that slice the same records by attribute and by use case, all cross-linked.
done whenEvery record in your database has its own live URL, and the index pages send internal clicks down to the leaf pages in your analytics.
- 4
Ship six to eight no-signup free tools on the same keyword cluster (title generator, outline generator, transcript generator, length calculator), each one a thin call to the paid endpoint, with a named conversion goal on the CTA in a lightweight analytics tool.
done whenTool sessions continue to a pricing view or a key creation, visible as a fired goal rather than a raw pageview count.
- 5
Publish an /mcp page with copy-paste install lines for Claude Code and Codex plus Zapier and Make blocks, so the API can be picked from inside an assistant without anyone visiting a page at all.
done whenAPI keys get created by people whose first recorded touch is the MCP page, with no demo call and no sales reply in between.
Run this against your own product
Carries the play above, and is written to tell you no when this channel is out of reach for you.
The same twelve channels as an agent skill. It reads your repository and eliminates what you cannot run. Open source, MIT.
curl -o ~/.claude/skills/howtodistribute/SKILL.md https://howtodistribute.com/skill.md
How big it got
423 URLs in the sitemap across six templated clusters (123 /content/, 68 /voices/, 44 /convert/, 11 /for/, 9 /compare/, 8 /free-tools/), plus 22 blog posts. The hero claims "600+ businesses" and "2,000,000 assets generated", with nothing on the site backing either number.
What else they ran
Nothing else identified. One channel carried it.
They ran the same play
Want this verdict on your product?
Describe it. You get back the channel I would run in your place, the 30-day plan, and the number at which you stop.