The entity home: The page that shapes how search, AI, and users see your brand
The entity home is the single page that anchors how algorithms, bots, and people understand your brand. It’s usually your About page, and it does far more than most teams realize.
It’s where algorithms resolve your identity, where bots map your footprint, and where humans verify trust before they convert. In one test, improving that page alone lifted conversions by 6% for visitors who reached it. The reason is simple: the human and the algorithm are doing the same job — checking claims, validating evidence, and deciding whether to trust you.
For years, this was overlooked. Most SEOs focused on rankings and traffic while underinvesting in the page that defines what their brand actually is. That’s no longer sustainable. The entity home is the foundation of how your brand is interpreted across search, AI, and what comes next.
What the entity home isn’t
Before going further, here are four misreadings worth pre-empting.
Not a ranking trick
Getting the entity home right doesn’t produce a traffic spike next Tuesday. It builds the confidence prior that compounds through every gate of the pipeline over time.
Not just schema
Schema markup helps the algorithm read what is already there. It isn’t a substitute for the claims, the evidence links, and the consistent positioning that schema describes. Schema without substance is a well-formatted, empty declaration.
Not always the About page
For most companies, it is, and for most individuals, it is a page on someone else’s website. The right URL to use carries the clearest identity statement, the strongest internal link prominence from the rest of the site, and the most stable long-term address (something people often don’t think about).
Not enough without corroboration
The entity home is where you declare your claims. Independent third-party sources confirm and corroborate your claims. The algorithm will only cross the confidence threshold when what you say matches what the weight of evidence supports.
The SEO toolkit you know, plus the AI visibility data you need.
Three audiences, one anchor — and most brands are ignoring two of them
The entity home serves three simultaneously, through three completely different mechanisms. Most brands haven’t yet given them enough thought.
- Bots use the entity home when mapping the digital footprint. They use it to establish what entity they are dealing with and how to interpret every corroborative source they find.
- Algorithms anchor their identity resolution against it, checking confidence at every relevant gate against whatever baseline this page set.
- Humans reach for it when they want to see a resource that feels authoritative precisely because it is structured to inform rather than to sell.
So, the entity home webpage is vital to all three audiences — bots, algorithms, and humans: it sets the tone for the bot in DSCRI, the algorithms in ARGDW, and for the person who converts.
The entity home is just one page, and that isn’t enough
The entity home anchors everything: the canonical URL where the algorithm initializes its model of the brand, where bots orient themselves, and where humans arrive to verify their instinct. One page, doing one critical job. But one page declares. It doesn’t educate.
The entity home website educates. Every facet of the brand structured across pages that give the algorithm a complete picture of:
- Who this entity is.
- What it does.
- Who it works alongside.
- What it has produced.
- Where independent sources confirm what the brand claims about itself.
The difference between the two is the difference between introducing yourself and making your case.
Search built the web around a single assumption — the human acts. The engine organized, the website presented, and the human chose. That model shaped 30 years of architecture decisions because the website’s job was to win the human’s attention and trust once the engine had delivered them to you.
But assistive engines broke that assumption. They took on the evaluation work the human used to do: reading, comparing, synthesizing, and recommending. The human still makes the final call, but the website needs to have made its case to the algorithm before the human ever arrives.
The audience that matters first has shifted, and a website that speaks only to humans is already losing the conversation that determines whether those humans show up at all.
Agents go one step further. The agent researches, decides, and acts. The human receives the outcome. The website that wins in an agentic environment isn’t the one with the most compelling hero section — it’s the one the agent can read, trust, and act on without inferring anything.
All three modes co-exist, and all three always will.
- Search serves the window shopper.
- Assistive engines serve the human who wants a recommendation without doing the research.
- Agents serve the task that can be delegated entirely.
What shifts over the next three years isn’t which mode exists — it’s which mode does the most work, and what your website needs to do to win each one.
This is where I’ll plant a flag, and you can disagree. All three jobs need attention right now — the percentages below describe where the main focus of your effort sits, not permission to ignore the others.
The work on assistive and agential is already overdue. The speed of change will probably make these figures look dated in a few months.
- 2026: Search 60%, Assistive 35%, Agential 5%
- Search still drives most conversions. But the 35% on assistive isn’t optional, it’s late. The brands that started two years ago are already compounding.
- 2027: Search 35%, Assistive 50%, Agential 15%
- Assistive engines will be handling enough upstream evaluation that discovery and correct interpretation become the primary battle. Search remains significant. Agential execution is arriving.
- 2028: Search 20%, Assistive 45%, Agential 35%
- Agents execute. The algorithm’s confidence in your brand determines whether you’re in the consideration set before any human is involved. Search and assistive don’t disappear — they become the infrastructure the agential layer runs on.
The entity home website anchors all three eras. What changes is who it speaks to first, and what that conversation needs to contain.
Each cluster in that diagram declares something: these satellite pages, grouped this way, belong to this entity and describe one specific dimension of what it is.
- /social names the platforms the brand controls.
- /peers places the entity in its professional network.
- /companies closes the relationship loop between person and organization.
The grouping carries meaning — an algorithm that reads the structure learns something the individual pages couldn’t tell it separately.
The entity home website has three jobs
Search, assistive, and agential engines co-exist, which means the entity home website runs three distinct jobs simultaneously.
- The search job is the one 30 years of practice has refined, and it doesn’t change: get the bots through the DSCRI infrastructure gates cleanly, so the ranking engine delivers the right humans to you, and your content draws them through the funnel with clarity, credibility, and a path to conversion.
- The assistive job is the one most brands are ignoring, and where the competitive gap is opening fastest: educate the algorithms. Your entity home website structures your brand’s story so algorithms understand it without guessing, and your content wins the competitive phase (ARGDW) with the highest possible confidence intact. Every explicit link from your entity home website to a satellite property declares a graph edge, carrying higher confidence through the pipeline than any connection the algorithm has to infer for itself.
- Hardest to prepare for, and already arriving: brief the agents. Agentic engines don’t read your website the way a human reads a marketing page — they read it the way an instructed system reads a briefing document, scanning for structured, unambiguous, machine-interpretable facts. Don’t make the machine use imagination it doesn’t have.
Entity pillar pages solve the identity problem keyword cornerstones were never built for
SEO has always known what to do with a topic: build an authoritative page around it, link it well, and earn rankings. That architecture works because the ranking engine evaluates content.
What it can’t do is tell the algorithm who the entity behind that content is, what relationships it has built, what it has demonstrated over time, or why it should be trusted to recommend rather than merely rank.
An entity has facets, and facets aren’t the same thing as topics. A person isn’t “SEO consultant” plus “technical SEO” plus “keynote speaker”: those are keyword clusters, useful for ranking, useless for identity.
What the algorithm actually resolves identity against is the network of dimensions that define what this entity is — the companies it belongs to, the peers it works alongside, the publications it has appeared in, the expertise it has demonstrated over years, the events it speaks at, and the work it has produced.
An entity pillar page is the authoritative page on your own property for one of those dimensions.
- The /expertise page establishes demonstrated knowledge in a specific domain, not as a content topic, but as an identity declaration.
- The /peers page places the entity in a professional network the algorithm already trusts.
- The /companies page closes the loop between person and organization.
- The /press page links to independent coverage that corroborates the entity’s claims, giving the algorithm something to cross-reference rather than take on faith.
These pages aren’t traffic pages in the traditional sense, and that framing matters: SEOs who measure them against keyword rankings will consistently underinvest in them because the return doesn’t show up in rank tracking. The return shows up in what AI assistive engines say about your brand when your prospects ask.
Keyword cornerstone pages and entity pillar pages serve different audiences, and your website needs both
The keyword cornerstone page and the entity pillar page aren’t competing strategies: they’re parallel architectures serving different audiences, which means your website needs both, and the question is how to build them so they compound each other’s value rather than compete for the same resource.
The coincidence between them is real and worth engineering deliberately. The expertise page that ranks for “technical SEO audit” can also function as the entity pillar page that declares this entity’s demonstrated knowledge in that domain if it’s built with that second function in mind:
- Explicit entity statements.
- Schema that names the relationships rather than just the topic.
- Links to corroborating third-party sources stable enough to persist across years.
- A URL structure that commits to the identity dimension rather than the keyword cluster.
When those two requirements align, one page does both jobs, which is a good thing.
When they diverge: when the page that captures search traffic can’t easily carry the identity declaration without sacrificing one function for the other, you face an architectural choice, and making that choice consciously rather than defaulting to the keyword model is the skill the transition requires.
The percentages already told you the weighting: Both layers are required starting today
Earlier in this article, the 2026/2027/2028 split put search at 60%, then 35%, then 20% of focus. What those numbers don’t say, but what the logic demands, is that the other percentage — the assistive and agential share — needs your website to feed them right now. Don’t wait until the balance shifts.
Keyword cornerstone pages feed the search share. Entity Pillar Pages feed the assistive and agential share.
If you build the Entity Pillar Pages in 2027 when assistive engines truly dominate, you’ll be building into a window that has already closed for the brands that started in 2025, because the algorithm’s model of your entity solidifies around whatever you gave it during the period it was actively learning.
The percentages describe where the demonstrable value sits at each stage. Your investment needs to precede the moment your boss sees the results, not follow it.
Both architectures are required today; the balance shifts, but the requirement for both never goes away.
Building for machines and humans simultaneously is cheaper than building for each separately
The risk brands hear when they encounter the machine-optimization argument is a false trade-off: build for machines at the expense of humans, strip the warmth from the copy, replace narrative with structured data fields, and turn the About page into a schema exercise. You can absolutely avoid the trade-off in practice because the best practices are more complementary than they might appear.
Clear entity statements that help the algorithm resolve your identity also help the human visitor understand immediately who they’re dealing with. Explicit links to corroborating third-party sources that build algorithmic confidence also give the human prospect the independent validation they’re quietly looking for. Schema markup that declares relationships for machine consumption gives structured clarity that human scanners doing final due diligence actually appreciate.
For me, this is the reframe that makes the whole project manageable: my approach to the entity home website is your current marketing, restructured to serve three audiences simultaneously, not a technical infrastructure project running alongside it. One investment that has three returns, and (when done right), the requirements pull in the same direction more often than they pull apart.
The funnel is moving inside the assistant.
When an assistive engine names your brand, summarizes it, and links to it in response to a user query, a conversion event has happened that you don’t see in your Analytics dashboard, and the human who arrives at your website has already been half-sold by the algorithm before they clicked. Traffic will decline as more of that evaluation work moves upstream, and the brands that measure only what arrives at the site will systematically underestimate both the value they’re generating and the gaps in their strategy.
Start measuring where your brand appears in assistive engine responses, how consistently it appears, and what the algorithm says about you when it does.
Track, optimize, and win in Google and AI search from one platform.
Getting the entity home right requires definition, proof, and a sustained corroboration campaign
Start with the entity home page itself: choose the single URL that functions as the canonical anchor for your brand’s identity and commit to it. Don’t discover it by asking an AI engine what it thinks your entity home is, because the engine will tell you what it has already learned, and that might be your website homepage, Wikipedia, a press profile, or a LinkedIn page you half-filled in five years ago. You choose it, then you verify the algorithm has learned the lesson you are giving it. You are the adult in the room.
Five criteria determine that choice, in order of weight:
- The most explicit identity statement on the property.
- The strongest internal link prominence from the rest of the site.
- The best-structured schema markup with a stable @id.
- The clearest outbound links to corroborating third-party sources.
- The most stable long-term URL.
If your About page doesn’t hit all five, it isn’t doing the job the algorithm requires.
Invest in your About page. Strengthen it with a clear entity statement, schema with a proper @id, verified links to Wikipedia and Wikidata where they exist, every accurate sameAs declaration you can support, and the claims that define your brand’s positioning.
That single page is the anchor.
The entity home website is the education hub built around it: every entity pillar page you build — /expertise, /peers, /companies, /press — extends the identity declaration outward, giving the algorithm more dimensions to resolve against and more facets to cross-reference with independent sources. Each of those pages does for one identity dimension what the About page does for the whole: declares something specific, verifiable, and machine-readable about who this entity is.
The practical work on the entity home website side is the same audit applied at scale: for each entity pillar page, ask whether it declares a clear facet, links to corroborating evidence, and carries schema that names the relationship rather than just the topic. The pages that answer yes to all three are doing both jobs simultaneously — identity infrastructure and keyword architecture. The ones that don’t need a decision: extend them, or build the pillar function its own dedicated page.
If you’re unsure how much influence you actually have over what AI communicates about you, the answer is more than most people assume — and the channels that give you the most leverage are exactly the ones entity pillar pages are built to activate.
Then force the corroboration loop across the whole footprint: drive independent third-party sources to reference, link to, and echo the claims the entity home makes and the facets the pillar pages declare across enough independent contexts that the algorithm’s confidence crosses from hedged claim to corroborated fact.
That crossing doesn’t happen on a deadline and can’t be engineered in a sprint. The corroboration loop is the curriculum, slow by design, compounding with every cycle, never truly finished. It is the work, and it rewards the brands that start it today over the ones that plan to start it when the percentages shift.
This is the sixth piece in my AI authority series.
- The first, “Rand Fishkin proved AI recommendations are inconsistent – here’s why and how to fix it,” introduced cascading confidence.
- The second, “AAO: Why assistive agent optimization is the next evolution of SEO,” named the discipline.
- The third, “The AI engine pipeline: 10 gates that decide whether you win the recommendation,” mapped the full pipeline.
- The fourth, “The five infrastructure gates behind crawl, render, and index,” walked through the first five gates.
- The fifth, “5 competitive gates hidden inside ‘rank and display’,” covered the last five gates.
- Up next: “The push layer returns.”
Read more at Read More
