How Webflow got its users
A template marketplace plus customer sites carrying a badge. The SEO is fed by the users themselves.
Read from signals. Consistent with what is publicly observable, but nobody confirmed it. Check before you quote it.
Reproducible, but it will cost you real money, real months, or a skill you may not have.
- 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
Start with the teardown. webflow.com/robots.txt points to webflow.com/sitemap.xml, and every child file sits on a CDN path literally named growth-seo/live/. Six files: showcase_projects (split in two), profiles, tags, manual_sitemap_entries, apps. Counting <loc> entries today, the showcase files hold 50,000 and 45,115 URLs, profiles 13,605, tags 8,658, manual entries 8,552, apps 345. The pages Webflow wrote by hand are the smallest file in the set.
done whenRun the same count on your own sitemap. If the URLs you wrote by hand outnumber the ones your users wrote, you have a blog, not an engine.
- 2
The entity list is a text box. Every distinct tag a submitter types becomes /made-in-webflow/{tag}. Fetch /made-in-webflow/skincare: title "Best Skincare Websites | Free Examples & Designs", H1 "Discover Skincare websites built by the Webflow community", meta description "Discover the best skincare websites created by professional designers." Nobody curated that list. /made-in-webflow/osmo, /evilgoodies and /dennis%20snellenberg (space and all) are live pages beside it.
done whenOpen your own submission form. Is there a free-text field whose values already map to a URL? If tags render only as grey pills inside a record, you are discarding your entity list.
- 3
The unit is one submission and it fans out. The button on /made-in-webflow says "Showcase your site". One submission mints a project page at /made-in-webflow/website/{slug} whose meta description is the submitter's own blurb verbatim, emoji and outbound links included, feeds the author's /@handle profile page, and adds a row to every tag page it touches. The reason people bother is the "Cloneable sites only" filter: submitting earns them a one-click clone link to hand around.
done whenName the selfish reason a user submits. If the only answer is exposure on your site, volume stops the week you stop asking people one by one.
- 4
Second engine, different source: the marketplace search box. /templates/search/{query} carries 1,482 URLs in the manual sitemap and the slug is the raw search string pasted in unedited. /templates/search/accounting returns title "accounting Website Templates & Page Designs" and an H1 with a leading space and no capital letter. Hand-cut tiers sit above it: /templates/category (28 URLs), /templates/subcategory (108), /templates/style (9), /templates/languages (4).
done whenExport your site-search log and count queries that returned at least one real result. That number, not a keyword tool, is how many search pages you can publish without shipping empty ones.
- 5
Copy the restraint. That robots.txt disallows /template/ and /design/, the editor itself, while explicitly allowing /api/v1/marketplace/made-in-webflow/, so crawlers get the catalogue and never the app. The curated tiers stay deliberately small: nine style pages, four language pages, 21 hand-written /vs/{competitor} pages. Generated pages carry the volume, written pages carry the pitch, and they live on separate URL paths.
done whenList every URL path a crawler can reach on your product. Anything behind a login, or with no stable content, gets disallowed before you publish a single generated page.
The product itself
read from webflow.com, live“Make your website a growth engine”
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
Multi-billion valuation
What else they ran
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.