How Calendesk got its users
231 competitor comparison pages and 22 alternative pages, plus one booking page per profession, catch buyers who are already typing a rival scheduling tool's name.
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
List every scheduling tool your buyers already shortlist (Calendly, Acuity, Setmore, Booksy, Microsoft Bookings, SavvyCal) and publish one /compare/you-vs-them page each, with real pricing and feature detail so the page stands on its own instead of reading as a stub.
done whenEvery comparison URL returns 200 with its own title, and Search Console shows impressions on '<rival> vs' queries within 8 to 12 weeks.
- 2
Build a second, separate /alternatives/<competitor> directory: 'Calendly alternative' is a different search from 'Calendesk vs Calendly', and Calendesk treats it as its own 22-page set rather than folding it into the compare pages.
done whenThe alternatives URLs collect their own impressions in Search Console, distinct from the compare set, instead of cannibalising them.
- 3
Publish one landing page per trade you already serve (psychologists, lawyers, hairdressers, beauty salons, tutors, personal trainers, therapists), each describing the booking flow that trade actually runs, and link them from the homepage.
done whenVertical pages start a higher share of trials than the homepage does, measured on trial starts per session.
- 4
Back every claim with proof a stranger can check: one case study post per named customer, plus listings on Capterra and GetApp wired into your sameAs structured data and a review badge on the page.
done whenProspects mention the case study or the directory listing in sales calls before you send it to them.
- 5
Feed the answer engines: serve /llms.txt and /llms-full.txt, add a glossary for the terms your buyers ask about (what is an API, what is Zapier), and ship one small free tool like a QR code generator for booking links.
done whenAsking ChatGPT or Perplexity for scheduling tools for your vertical returns your product by name.
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
1,158 URLs in the sitemap: 231 competitor comparison pages, 137 blog posts, 77 help pages, 42 glossary entries and 22 alternative pages, with listings on Capterra and GetApp referenced in the site's structured data
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.