The homepage tries to name every persona
Marketing is proud of the list. Sales still pastes a PDF. We split roles onto URLs a champion can forward.
B2B SEO
B2B SEO from senior consultants who turn search demand into rankings, traffic and revenue for your business. We start with a free audit and a 90-day plan built around your goals.
Our process
We agree the target accounts and segments for this period, and the job titles involved in real deals.
We decide which roles get their own page and which are covered in a section of a broader page.
We list the claims sales already makes and check whether your website backs each one.
Sales gets live page links to share instead of outdated decks, with a short guide on when to use each.
Position
A committee does not read one homepage and agree. A champion forwards a page. A finance title wants proof. An operator wants the job to be obvious. Search intent has to show on the URL that title opens: who this is for, what you will stand behind, and what happens next. A hero that lists every persona is not a role page. This page owns that set.
The object is buying-group HTML. Account map. Role URLs. Evidence packs. Sales enablement so the live page matches the deck. Software vendors still need this when the deal is a committee even if they also need vs and docs on SaaS SEO. A professional-services firm, a manufacturer, or a logistics vendor needs this without a comparison grid. Enterprise SEO still owns many sites and launch trains. Those are not this H1.
We will not write one brochure for every title. We will not treat paid as the organic program. If the real job is comparison and docs for a product, open SaaS SEO. If the real job is many brands shipping at once, open enterprise SEO. If the real job is hand-briefed articles, open content SEO. If the real job is ads to a committee, open B2B PPC.
Compare packages if a published retainer already fits. Use SaaS SEO when a related service is the real job. If this page is still a guess, start with a free AI + SEO audit.
When this fits
This page fits when more than one title must agree, and the site still speaks as if one visitor will buy.
Marketing is proud of the list. Sales still pastes a PDF. We split roles onto URLs a champion can forward.
Security, implementation, or ROI claims never appear in fetchable HTML. We pack evidence onto pages sales may send.
The product needs vs pages on SaaS SEO. The committee still needs role URLs here. We name which object is missing instead of blending both H1s.
The site speaks to a generic market. The map of named accounts and segments is missing.
Process
Four committee jobs in this order. We do not start with a blog calendar because the homepage listed personas. The point is pages sales will actually send.
Outcome A dated account and title map sales will recognize.
Outcome A role URL list with owners and a refuse list.
Outcome An evidence pack list: live URL, PDF-only, or do not claim.
Outcome An enablement note: which URL for which title, and who updates it.
Deliverables
You leave with an account map, a role URL list, an evidence pack list, and an enablement note. You do not leave with a vs farm, an estate launch plan, or a ranking date.
Who is in the deal this period. Dated. Last year's persona poster is not this map.
Which titles get a page, which share a parent, and which we refuse. Navigation should match.
Claims with a live URL versus claims that still live in a deck. Invented metrics are named.
What sales sends for each title. A second intranet copy of the homepage is not enablement.
When a vs grid is still missing, that line points at SaaS SEO. When paid must cover a gap, that line points at B2B PPC.
Benefits
Each title has a URL. The homepage stops pretending it is everyone.
Claims sales already makes become fetchable or get retired. Committees stop asking for a PDF that search never saw.
The committee map does not swallow the comparison set. Both can exist. They do not blend.
Enablement is a path. New hires stop linking the homepage to every title.
Methodology
This works when sales can name the titles in a deal, and someone can ship a role URL. If both are missing, we are touring personas. We are not enabling a committee.
We start with two titles from a live opportunity, the homepage, and any PDF sales already sends. If any of those is missing, we name it first.
We fetch published HTML. We do not trust the brand deck. Can this title open a page that is for them? Is the proof on the page?
You may rename the roles below. You may not leave the title map implied. An implied everyone-hero is how the only URL stays the homepage.
First working session
The first hour is one buying title that only sees the homepage. It is not a tour of SaaS vs templates.
We pick a live deal. We list the titles in it. We fetch the URL each title would open today. If they all land on the homepage, that is the job. If the real question is a vs grid and docs, that is SaaS SEO. If the real question is many brands and launches, that is enterprise SEO. If the real question is ads while pages are missing, that is B2B PPC.
Then we open the PDF sales already sends. We mark which claims have no HTML. Those rows are usually the job. A persona workshop without pipeline titles is not evidence.
We leave with a first map or a stop. A map names accounts, titles, and which URL must exist. A stop names what is missing: sales access, a publisher, or a product that actually needed evaluation templates first. Both are outcomes. A thought-leadership calendar is not.
AI search
Honest committee HTML can help later extraction. This page cannot sell AI Overviews, a chat mention, or LLM visibility as a score.
People ask whether pages for every title will land the vendor in Google AI Overviews (AIO). If the only fetchable page is a homepage, generative search has a vague noun to lift, or a claim sales will not sign. That is ours to split into role and evidence URLs. A program across search UIs is AI SEO.
AI search needs a page it can fetch. A gated deck that never published does not help. Nobody can guarantee a spot in AI Overviews, but clear pages improve your chances.
We check whether the URL uses the same titles as the pipeline. That is entity optimization as a committee input.
LLM visibility needs a sentence a model can quote, then measurement on LLM SEO. A role page can make a claim look real. Semantic keywords belong in a pack only when the objection is still that title's job.
Schema
JSON-LD helps a machine read a vendor the page already states. This work stops fake FAQ on a homepage that lists every title. Schema supports the work; it is not the whole job.
If schema boasts a result the HTML does not state, extractors guess. We name the mismatch. We do not add Review spam.
We refuse question blocks that exist only to host more titles. A real objection lives on the role URL.
Markup will not force generative search to cite the pack. Good markup makes you eligible; it cannot buy a mention.
Who we work with
Someone has to refuse a fake persona. We work with that person. We do not replace them with a second brand retainer.
Names titles. Holds the map when marketing wants one homepage for everyone.
Ships role URLs and ungates proof. Rechecks after a brand redesign.
Can keep going once role URLs exist. If they try to run this as a vs farm, two jobs collide. Comparison stays on SaaS SEO.
FAQ
SaaS SEO owns software evaluation HTML: comparison, alternatives, integrations, crawlable docs, and trial or demo IA. This page owns committee buying for software and non-software vendors: account map, role pages, evidence packs, and sales enablement. A vs grid is that H1. A page a CFO can forward inside a buying group is this H1.
Enterprise SEO owns several sites, several publishers, and launches that change templates across an estate. This page owns the buying-group URL set even when you have one site. A large company can need both. A release train is not a role map. A role map is not a portfolio gate.
No. A homepage that tries to speak to every buyer at once is a brochure. Committee work needs a URL each role can open without translating. We map accounts and titles first. We do not hide the map behind a hero that says everyone.
Paid can cover a query while a role page is missing. It does not replace the page sales has to send when the committee asks for proof. B2B PPC stays on its own URL for ads. This page stays on organic role and evidence URLs. Shared landing pages can serve both. The mix is not this H1.
No. Honest role and evidence HTML can help later extraction. This work does not buy a place in Google AI Overviews (AIO), a generative-search mention, or an LLM visibility score. If the packs already tell the truth and models still invent a claim sales will not stand behind, that measurement sits on an AI search audit and on LLM SEO.
Roles, not one homepage
Send the homepage, two titles that sit in a real deal, and any one-pager sales already emails. We will name whether role URLs are missing, whether evidence is trapped in a PDF, or whether the work is actually SaaS evaluation pages or an enterprise estate.