Manypages
All page types
Persona/x-for-persona

USE-CASE PAGES

A real estate agent doesn't search for "crm" — she searches for "crm for real estate agents". Use-case pages meet every industry and role at that exact query, re-framing one product around each persona's workflow, vocabulary, and objections. It's the play Notion and Airtable made famous: a horizontal tool with a page for every audience that searches for it.

GET /crm-for-real-estate-agents

GET /notion-for-students

made famous by Notion, Airtable

When to use it

The right play when

  • Your product is horizontal — a CRM, a form builder, a scheduler — and every vertical searches for it with their industry attached.
  • Sales calls keep opening with "does this work for real estate / clinics / agencies?" Search demand mirrors that question.
  • Your homepage ranks for the head term but loses every long-tail "for X" query to niche competitors built for one vertical.
  • You already have persona-level proof — templates, testimonials, workflows — that one generic landing page can't fit.

Your sheet

The columns you bring

personaslugtop_painwinning_featureexample_workflow
real estate agentscrm-for-real-estate-agentsleads go cold between showingsautomated follow-up after every showingone pipeline from first call to closing

every row becomes a page — add an AI-filled column for per-row unique copy

Build it

Three steps to live use-case pages

01

List every persona that searches

One row per industry and role: real estate agents, students, freelancers, clinics. Add columns for each persona's top pain, the feature that lands, and a workflow example. Paste rows or import the CSV — every row becomes a product-for-persona page.

02

AI-fill copy in their language

Point the AI column at each row's pain and workflow and it writes copy the persona recognizes — an agent's cold-lead problem, a student's semester chaos. Grounded in that row's facts, so pages differ in substance, not just a swapped job title.

03

Generate one page per persona

Hit generate. Each persona page ships as cached, SEO-first HTML — titles from the row ("CRM for real estate agents"), canonicals, sitemap and robots handled. Spot-check a few personas on the free subdomain, then attach your domain to index.

SEO notes

Make it rank

  • "crm for realtors" and "crm for real estate agents" are one intent — pick one URL and fold variants into it, or your persona pages cannibalize each other before they rank.
  • Cross-link each persona page to that persona's templates, integrations, and comparisons — a realtor should never have to route through your generic homepage.
  • Answer "is [product] good for [role]" concretely on the page — name the workflow, not adjectives. That's the sentence LLMs lift when someone asks the same question in chat.

FAQ

Use-Case Pages, answered

Isn't this just the same page with the job title swapped?

It is if your dataset is thin — and Google treats it that way. The pages earn their place when each row carries persona-specific substance: the pain point, the workflow, the feature that role actually cares about. That's why the dataset asks for more than a persona name, and why the AI fill grounds itself in your row's facts instead of writing generic filler.

How many personas deserve a page?

Start with the ones already showing up in signups and sales calls — if a vertical keeps asking "does this work for us", people are searching it too. Ten personas with real pains and workflows beat a hundred guessed ones. You can always paste more rows and regenerate later.

Should the URL use my product name or the category?

Match how people search. Nobody types "yourstartup for students" until you have brand demand — they type "note app for students". Lead with the category, like /crm-for-real-estate-agents. Notion-scale brands earn the name-first version; most products get there later, not first.

Related patterns

Pairs well with

Ship your first use-case pages

Bring your dataset, pick this pattern, and Manypages generates and hosts the pages — sitemap, robots and canonicals handled.