How AIDesigner got its users
A 57 page library of vs, alternatives and template pages sitting on the tool names buyers already search, all pointing at a free tier that signs up instantly.
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.
- Authority that transfers to the product
- Backlinks that arrive without outreach
- Real expertise and a point of view
- 12 to 24 months of patience
- A writing budget, or a lot of your own time
Editorial SEO in 2026
The channel most damaged by AI answers. It still works if you bring data or an opinion, not a summary.
Everything on this channel →The play
5 steps, in the order they ran them.
- 1
List the eight to ten design tools your buyer is already comparing (their Figma, Canva, v0, Framer, Webflow, Uizard, Bolt set) and publish two pages per tool: a head to head 'you vs them' and an 'alternatives' roundup, each ending on the free tier rather than a contact form.
done whenWithin 6 to 10 weeks, Search Console shows impressions on competitor brand queries for your vs and alternatives pages, and at least one sits on page two or better.
- 2
Add standalone keyword pages outside the blog, one per job your product does, phrased the way people type it: ai landing page builder, brand kit generator, website cloner, image to html. One page, one job, one signup button, no blog wrapper.
done whenEach product-shaped page ranks for its own exact phrase, and your signup source report shows those pages converting at a higher rate than any blog post.
- 3
Turn your own output into a browsable directory: a top level /templates page, category pages, subcategories, then individual template pages, so every example your product can produce becomes its own indexable entry point that shows the thing working before anyone signs up.
done whenYour indexed page count climbs as a cluster rather than one page at a time, and directory pages start sending internal clicks down to individual template pages.
- 4
Ship an MCP server and a public API reference, then give that integration its own landing page, so the product is reachable from inside Claude and picks up traffic from people searching for agent-callable tools.
done whenYou see API calls arriving from agent clients you did not set up yourself, and the MCP page records sessions you never linked to.
- 5
Keep the whole path self-serve: free tier, one paid plan around $25 a month, a recurring affiliate program, and a plain mailto for the rare custom request instead of a demo calendar.
done whenPaid accounts complete checkout with zero conversations in your inbox, and affiliate-tagged signups start appearing in your tracker.
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
87 URLs in the sitemap, 57 of them content (45 blog posts, 20 template pages), 12 standalone keyword landing pages, a Discord at about 435 members with 48 online, a Product Hunt featured badge, and self-reported homepage copy claiming 15,000+ users and 40,000+ designs created
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.