How Audixa got its users
2,685 template pages, one per language, export target, integration and competitor name, each closing on the same self-serve sign-up, with no other channel present on the site.
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
Choose four entity lists your buyers already type, the way Audixa runs languages (/text-to-speech/hindi/), production tasks (/youtube-shorts-text-to-speech/, /word-document-to-audio-ai/), tool integrations (/zendesk-chatbot-voice-tts/) and model reviews (/xtts-v2-review/) side by side rather than betting on one list.
done whenYour lists produce several hundred distinct slugs, and you can read each one aloud as a phrase you would type into a search box yourself.
- 2
Write one page template with a fixed H2 skeleton and fill it to real length, theirs runs 'What the product currently documents', 'Questions specific to <keyword>', 'Related Pages', 'Test <keyword> with your own acceptance criteria', 'Get Started', at roughly 1,000 words a page.
done whenPick a page at random from your batch: it has no empty section, clears 800 words, and you would leave it up if a person had written it.
- 3
Stamp every generated page with a batch marker and named CTA slots, they ship <meta name="pseo-release" content="...2026-07-24"> plus data-pseo-cta="pricing" and "voices", so you can tell which batch and which button produced the account.
done whenYou can answer 'which batch and which CTA produced this sign-up' from your own logs or dashboard without guessing.
- 4
Ship category hubs at the same time as the leaf pages and link siblings hard: their Hindi page points at 26 internal URLs, almost all other generated pages plus /category/languages/.
done whenEvery new page has 15 or more internal links to siblings, and no generated page sits more than two clicks from a hub.
- 5
Add one comparison page per paid competitor (they have elevenlabs, speechify, murf, playht, lovo, three linked from the homepage) and send all of them to the same self-serve checkout, no demo form, no call, entry priced at a $10 top-up.
done whenSomeone reaches a paid account from a comparison page you never promoted anywhere, with no message from you 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
2,685 URLs in the sitemap, all HTTP 200: 405 guides, 258 language pages, 69 category hubs, 8 comparisons, the rest flat keyword slugs, each around 1,000 to 2,800 words
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.