howtodistribute
← Back to the index

How Airtable got its users

HARDProgrammatic SEOscale-upb2bruns ads
Visit airtable.com

A page per template and per business use case, plus publicly shared bases that pull collaborators in.

Read from signals. Consistent with what is publicly observable, but nobody confirmed it. Check before you quote it.

Can you run this?
HARD

Reproducible, but it will cost you real money, real months, or a skill you may not have.

Your time
18 months
Your money
A few thousand a month
First signal
9 months
Upside
  • A traffic base that does not collapse when you stop publishing
  • Acquisition that owes nothing to any social platform
Price of entry
  • 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. 1

    Airtable's sitemap.xml carries 2,982 URLs. 291 sit at /templates/[slug]/[expID], 1,411 at /universe/[expID]/[slug]. Same exp base ID, path order flipped. The unit is one base. Bases Airtable builds in-house go on the /templates route; bases users publish land on /universe. No external dataset, no scrape. Your version is the artifact your product already saves. Build the page around one saved object and give that object an ID that outlives a rename.

    done whenName one object your product saves that a stranger would want a copy of. If the honest answer is a settings screen or a dashboard, you have no unit yet and no page to build.

  2. 2

    Open /templates/project-management/expnPwND0WA2x7nhJ. The order: breadcrumb Templates > Category > name, a "Use template" button, a static cover image, a definition of the thing, benefits, key components, 11 related templates each with "Get template", a comparison against Excel and Google Sheets, a five-step build guide, a six-question FAQ. These pages ship Article schema, not Product. The base is one image; everything else is prose answering the query.

    done whenDelete the generated data from your page mockup and read what is left. If under a screen of text remains, you shipped a stub, and search engines will treat 300 of them as one page.

  3. 3

    In the sitemap, 54 of the 291 template slugs end in -template: action-items-template, kanban-board-template, buyer-persona-template, gap-analysis-template. The rest are bare jobs: asset-tracker, alumni-directory, apartment-hunting, assortment-planning. Two slug shapes for two intents, the person typing "[X] template" and the person typing the task. Airtable names the page after the phrase searched, never after its own internal feature name.

    done whenTake your last ten feature names. Count how many a stranger would type into a search box cold. That count is how many pages you can honestly name today.

  4. 4

    Every template page footer links all 19 category hubs: project-management-v2, marketing-v2, hr-and-recruiting-v2, design-and-ux, it-and-operations, forms, interfaces, portals, supply-chain-management and the rest. Nine job functions, six industries, four product features. No leaf page is orphaned, and a new base inherits links the day it joins a category. The -v2 suffix shows hubs were rebuilt in place rather than moved to fresh URLs.

    done whenOpen your newest generated page and count the clicks back to your homepage. More than three means the hub layer is missing and the page will sit unindexed.

  5. 5

    The meta description on /universe/exp0GdColNU1fA33n/comparison-of-35-email-marketing-tools opens in first person: "When I first started sending email newsletters 10 years ago...". Airtable wrote none of it. Someone published a base to share it with collaborators, and the blurb they wrote for humans became that page's unique text. This user-written route outnumbers the curated /templates route roughly five to one in the sitemap.

    done whenCheck your share flow. Does it ask the user for a title and a description? If sharing produces a bare link, you collect no text, and no text means no page.

The product itself

read from airtable.com, live

All your teams, all their workflows, connected in one workspace

free tier~3.0k public pages

Run this against your own product

In your chat

Carries the play above, and is written to tell you no when this channel is out of reach for you.

In your editor

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

Multi-billion valuation

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.