How Beno got its users
A library of templated articles, one page per hyper-specific trade (sometimes trade plus city), sits outside the sitemap and funnels every reader into the same single CTA block.
Best guess. A working hypothesis. Useful to think with, not to repeat as fact.
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 entity axis the way Beno did: one page per named business type ('Man with a Van', 'Veterinary Practice', 'ATM Business'), then multiply by city or region wherever local intent exists. Write 150 to 300 rows in a sheet before producing a single page.
done whenYour list holds at least 100 rows, each one a phrase a real owner would type into Google, and no two rows would produce a page that reads the same.
- 2
Build one article skeleton and never vary it. Beno's is a strategy table, a 'How Beno One Helps' section, and 'Key Takeaways'. Yours needs the same three-part shape so a page can be generated by filling slots, not by writing.
done whenYou can produce a finished page in under 10 minutes by filling slots, and a reader who lands on two of your pages sees the identical section order.
- 3
Put one identical CTA block on every page, the way all 172 fetched pages carry 'Try Beno AI in action' with the same proof line. Do not personalise the offer per page: the page does the targeting, the CTA does the selling.
done whenEvery published page shows the same CTA text when you view source, and your analytics can attribute signups to the article path rather than the homepage.
- 4
Ship complete ranking metadata on each page (meta description, meta keywords, og:title, og:url, twitter:card) and decide deliberately what goes in the sitemap. Beno's articles are absent from a 4 URL sitemap and are found only through internal links, so discovery has to be built on purpose.
done whenView source on any live page returns a unique meta description and og:url, and Search Console reports the page as discovered within two weeks of publishing.
- 5
Copy the 'More You Might Like' pattern: every page links 3 further pages, and the homepage links 3 entry points into the library. Then publish in bursts of several posts a day over a few weeks, stop, and measure, rather than dripping one page per week.
done whenStarting from your homepage and clicking internal links only, you can reach every page you published, and a crawler run over your own site returns zero orphans.
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
A crawl starting from the three articles linked on the homepage reached 172 pages under /a/, none of which appear in the 4 URL sitemap.
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.