How Askr got its users
One page per integration, industry and use case, named after platforms buyers already search, with the free tier as the entry point, while every canonical points at a domain that does not resolve.
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
Ship the widget as a one script tag install and put a $0 tier next to the paid one (Askr prices Premium at $5.99/month), so every template page has a free thing to send a reader into and a working signup form behind it.
done whenA visitor can go from a template page to a created free account without you touching anything.
- 2
Pick the entity sets your buyers actually type: the platforms you integrate with (wordpress, shopify, webflow, framer, nextjs, react, slack, zapier), the industries you sell into, and the jobs the widget does. One template, entity name swapped into title, H1 and body.
done whenYou can list 15 to 25 entities where a real buyer would search the entity name next to your category.
- 3
Write real copy per entity before publishing. Askr published 500 unfilled pages that still read 'Why Use Askr with 001', and /integrations/platform-001 and /integrations/platform-250 are byte identical at 56,411 bytes.
done whenDiff any two of your pages: if the only differing tokens are the entity name, they are not ready to publish.
- 4
Give every published page a crawl path from inside the site and a canonical on the host you actually serve. Askr's 500 placeholders are linked from nowhere, and /integrations/wordpress canonicalises to askr.io, which resolves to nothing.
done whenEvery published page is reachable in two clicks from your homepage, and the canonical host matches the host serving the page.
- 5
Add robots.txt and exactly one analytics tag before scaling page count, so you can see which entity pages earn signups. Askr has no robots.txt (404) and zero third party scripts on any page.
done whenYou can pull per URL sessions and signups for each entity page and rank them.
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
19 filled template pages live and returning 200 (5 /use-cases, 6 /industries, 8 named /integrations), one blog post, and a sitemap declaring 522 URLs, all on askr.io, a domain with no DNS records
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.