Persona template for role-based landing pages
Scale a directory of role-based pages — one per buyer role — so a CMO, a VP Marketing, and a Founder each land on a page that speaks to them.
- Sanity / CMS
- Airtable
- GitHub
- Vercel
- Notion
Build persona pages for our top 6 buyer roles.
- Pulled the personas6 roles from GTM docs and sales calls
- Generated pages6 role-based pages from the template
- Tuned the top 3CMO, VP Marketing, Founder hand-tuned
- Shipped the directoryHub + 6 pages, all crawlable
Six role-based pages shipped, with the top three hand-tuned. The CMO page matches "ai marketing agent for enterprise teams" exactly, where the generic page matched approximately. The directory is the role-based asset now.
A persona template scales the role-based landing page play: one page per buyer role, each tuned to the pains and the language that role uses. A CMO searching "ai marketing agent for enterprise teams" and a founder searching "ai marketing agent for solo founders" want different pages, and the persona template is what makes both cheap to ship.
What is a persona template for landing pages?
A reusable page shape for role-based landing pages, where each page targets a buyer role and the role-specific query. The template fixes the shape — the role, the pains, the language, the proof — so a directory of personas scales without hand-authoring each.
Build the directory
- Hub that targets the category query
- One page per buyer role
- Role-specific pains, language, and proof per page
Scale without generic copy
- Generate pages from the persona catalog
- Tune the top roles by hand; templatize the long tail
- Add FAQPage schema per page for citation lift
How does a buyer persona template differ from an ICP?
An ICP is the company you sell to; a persona is the person inside the company who buys. The page targets the persona — their role, their pains, their language — because the search is done by the person, not the company.
Why do role-based landing pages earn intent?
Because the buyer searches with their role implied — "for CMOs", "for solo founders", "for enterprise teams". A page that names the role and speaks to its pains matches the query exactly, where a generic page matches approximately.
How is a persona directory structured?
A hub that ranks for the category query plus a page per role that ranks for the role-specific query. The hub links to every persona page; each persona page links back and to adjacent roles.
How the persona template fits your stack
The agent reads your persona catalog from your GTM docs or a sheet, generates a page per role using the template, and flags generic copy for enrichment. It pairs with the directory and use-case page patterns.
- Sanity / CMS
- Airtable
- GitHub
- Vercel
- Notion
Who uses this persona template
- SEO teams
- Win the role-specific queries a generic page cannot.
- GTM leads
- Give every buyer role a dedicated page.
- Founders
- Speak to each buyer in their own language.
How to run this persona template in Metaflow
List the personas
From your GTM docs, ICP work, or sales calls.
Generate the pages
Agent fills the template per role.
Tune the top roles
Hand-tune the high-traffic personas.
Ship and verify
Export to CMS and confirm the directory is crawlable.
What you provide
- Persona catalog
- Role-specific pains and language
- Proof per role
What you get back
- Hub page
- One page per persona
- Role-specific copy
- FAQPage schema per page
Why use this persona template?
Wins the role-specific queries a generic page cannot
Scales with the persona catalog, not the writing
Tunes the top roles by hand; templatizes the long tail
Pairs with the directory and use-case patterns
Persona template FAQs
What is a persona template?
A reusable page shape for role-based landing pages, where each page targets a buyer role and the role-specific query. The template fixes the shape so a directory of personas scales without hand-authoring each.
How is a persona different from an ICP?
An ICP is the company you sell to; a persona is the person inside the company who buys. The page targets the persona — their role, pains, and language — because the search is done by the person, not the company.
Why do role-based landing pages work?
Because the buyer searches with their role implied — "for CMOs", "for solo founders". A page that names the role and speaks to its pains matches the query exactly, where a generic page matches approximately.
How many personas should you build pages for?
Three to eight — the roles that actually buy. More than that and the pages compete for the same query; fewer and you miss the roles that search with their title. The top roles get hand-tuned; the long tail gets the template.
Similar programmatic SEO templates
Key takeaways
- A persona page matches the role-specific query exactly
- An ICP is the company; a persona is the person who buys
- Tune the top roles by hand; templatize the long tail