TL;DR
Your brand is an entity, and in 2026 Google and the AI engines need one canonical page to anchor everything they believe about it. That page is your entity home — usually your About page — and it is the single highest-leverage, lowest-cost piece of entity SEO most UK brands are still getting wrong. This guide gives you the ANCHOR blueprint (Anchor URL, Name discipline, Core facts, Hooked-up schema, Outbound identity, Reinforce internally), a build-it-today checklist, an illustrative Organization schema block, and a UK worked example. Get it right and you give every other authority signal you earn a clean place to land.
Here’s a question most brands can’t answer cleanly: which single page on your site your brand? Not your homepage, necessarily. Not a product page. The one URL you’d point Google to and say “this is who we are — the founders, the founding date, what we do, where we operate, and every other place on the web that’s officially us.”
If you don’t have a confident answer, neither does Google. And in 2026 that’s no longer a tidy-house problem — it’s a visibility problem. Whether you get named in an AI Overview, whether you trigger a Knowledge Panel, whether an AI assistant recommends your product over a competitor’s — all of it leans on whether the systems can resolve “your brand” to a clear, consistent entity. The page that does that resolving is your entity home.
The good news: building one is cheap, fast, and almost entirely within your control. The catch is that almost nobody does it properly. Let’s fix that — UK-specific, step by step.
What an entity home actually is (and why 2026 made it urgent)
An entity home is the one canonical URL that anchors how algorithms, bots and people understand your brand. The term was formalised by Jason Barnard of Kalicube and popularised through Search Engine Land in early 2026, but the idea is older than the label: Google has always needed a primary, trusted source for “what is this thing,” and for a brand, the cleanest source is a page you own and control. For most businesses, that page is your About page. For larger organisations, it might be a dedicated brand or company page. Either way, there should be exactly one.
Why does this matter so much more now than it did two years ago? Because the entire search surface shifted underneath us. Google’s Knowledge Graph spans billions of entities, and Gemini — the model behind Google’s AI Overviews and AI Mode — is trained on it. So entity clarity stopped being a back-office concern for big brands with PR teams and became the thing that decides whether you appear in AI-generated answers at all. Industry analyses suggest the large majority of AI Overview citations go to pages already ranking in the top 10 — but among those pages, entity clarity is part of what tells Google which one is the authoritative source to name.
There’s a second 2026 wrinkle that makes the entity home directly valuable. Google’s Knowledge Panel description used to be pulled almost entirely from Wikipedia’s first sentence. Increasingly it’s a Gemini-generated, multi-source description — and when there’s no Wikipedia article, or your About page is simply a better source, Google draws from your own entity home. In other words: the text you write on that page can become the text Google shows the world about you. That’s an unusual amount of influence over your own brand SERP, and it’s sitting there unclaimed on most UK sites.
It helps to be clear about what an “entity” even is here, because it’s the whole reason this works. To a modern search engine, your brand isn’t a string of characters to be matched against a query — it’s a thing with attributes and relationships: a founding date, founders, a location, products, a category, competitors. The engines extract those entities from text, link them to a canonical identifier, and then build trust when the same entity shows up consistently across independent sources. Your entity home is the page that hands them the canonical version of all of that in one place, so the linking step stops being guesswork. Get it right and a brand with an ambiguous, common-word name becomes unmistakable; get it wrong and even a distinctive brand can fragment into several half-versions of itself.
First, check what Google already believes about you
Before you build, find out what the systems currently think. Entity recognition isn’t announced — Google never emails to say “we’ve understood you.” You discover it by reading the signals. Spend twenty minutes running these checks and you’ll know exactly how confused your current picture is, which tells you how much the entity home has to fix.
- Search your brand name. Does a Knowledge Panel appear on the right (or at the top on mobile)? Is the description accurate? Is it even you — or a similarly named company, person, or product? A missing or wrong panel is the clearest sign your entity is unresolved.
- Read the brand SERP as an audit. What sits in the top results for your name? Your own properties, or aggregators and namesakes? The brand SERP is Google showing you, in public, what it believes about you.
- Run the Rich Results Test and Schema validator. Point them at your current About page. Does Google recognise an Organization at all? Most brands discover here that they have no valid entity schema live.
- Ask the AI engines directly. Type “What is [your brand]?” into ChatGPT, Gemini and Perplexity. Are the answers right, vague, or confidently wrong? This is the fastest read on whether the entity layer has you straight.
- Query the Knowledge Graph directly. Google’s Knowledge Graph Search API lets you look up whether your brand or founder exists as a recognised entity and what type Google has assigned. It’s a more technical check, but it’s the closest you’ll get to reading Google’s mind about whether you’re in the graph at all.
Write down what you find. Those checks become your before-and-after baseline, and re-running them a few weeks after you ship the entity home is the cleanest way to see it working. If everything already looks perfect, brilliant — you can spend your time elsewhere. For almost everyone, at least one of those checks reveals a gap, and that gap is the business case for the next thirty minutes of work.
And the surfaces that read your entity are multiplying. It’s not just the classic Knowledge Panel anymore — it’s AI Overviews, Google’s AI Mode, Gemini’s answers, and increasingly the AI assistants people use to shortlist products and suppliers before they ever click a link. Each of those leans on a clean entity to decide whether to name you, and each of them is becoming a bigger share of how UK buyers actually discover brands. The entity home is upstream of all of it: one page that, done well, feeds every one of those surfaces the same confident answer.
The ANCHOR blueprint for a brand entity home
Before the detail, here’s the whole method on one screen. Work through these six in order and you’ll have an entity home that does its job. Everything after this section just expands each letter.
The ANCHOR blueprint
A — Anchor URL. Pick one canonical page (usually /about/) and commit to it as the entity home. One page, one job.
N — Name discipline. Choose one canonical brand name and use it identically everywhere — your site, your socials, every directory, every byline.
C — Core facts. Put the entity facts on the page in plain English: what you do, when you were founded, who founded it, where you’re based, who you serve.
H — Hooked-up schema. Add an Organization JSON-LD block with an @id pointing to your canonical domain, plus Person schema for your founders.
O — Outbound identity. Use the sameAs property to connect the page to every other official profile — Wikidata, Companies House, LinkedIn, your socials.
R — Reinforce internally. Make the entity home the most-linked-to internal page on your site, so it reads as the centre of your brand.
A — Pick the one URL that anchors your brand
Start by choosing the page. For the overwhelming majority of UK businesses, your About page is the natural entity home — it’s where a human goes to find out who you are, and that’s exactly what you want the machines reading too. Don’t scatter the job across five pages. If you currently have a thin “About” stub, a separate “Our Story,” a “Meet the Team,” and a “Company” page in the footer, you’ve split your entity signal four ways. Consolidate.
Pick the URL, make sure it’s clean and permanent (no /about-us-new-2024/ that you’ll migrate next year), and confirm it’s indexable — not blocked in robots.txt, not noindexed, returning a clean 200, with a self-referencing canonical tag. This is the page you’re going to point everything at, so it needs to be rock solid before you build on it. If you only do one thing from this guide today, decide which URL is your entity home and write it down.
One more thing while you’re choosing: if you’ve got old, redirected, or duplicate “about” URLs floating around from past redesigns, clean them up now. Make sure they 301 to your chosen entity home rather than sitting there as competing soft-duplicates. Every alternative version of the page is a small invitation for Google to anchor on the wrong one, and the whole point of this exercise is to remove that ambiguity. A single, canonical, permanently-linked URL is worth more than a beautifully written page that exists in three slightly different places.
N — Lock down one canonical name (the consistency problem)
This is the cheapest fix with the biggest payoff, and it’s where most brands quietly leak entity confidence. Pick one canonical form of your name and use it identically everywhere. “Three Putt” versus “Three Putt Golf” versus “ThreePutt” fragments recognition — every variant is a slightly different string the systems have to reconcile back to one thing, and reconciliation is exactly what you’re trying to make unnecessary.
Run a quick name audit. Open your homepage, your About page, your LinkedIn company page, your Companies House record, your Google Business Profile, your X/Twitter and Instagram handles, and the byline on your blog. Are they all the same name, in the same form? In the UK there’s a specific trap here: your registered name at Companies House is often a Ltd entity (“Acme Digital Ltd”) while your trading name is shorter (“Acme”). Decide which is your public brand entity, use it consistently in your branding, and let the legal name live only where it legally must. The systems can handle the legal-name-versus-trading-name relationship — but only if you’re consistent enough for them to learn it.
Naming consistency is also the part that travels worst across markets, so if you operate internationally, settle it before you scale. The same discipline underpins cross-border authority work, where a brand name rendered inconsistently across languages quietly splits the entity in two.
Watch the edge cases that quietly cause UK brands the most trouble: a rebrand where the old name still lingers on half your profiles; an acquisition where two legacy names compete; or a personal-brand founder whose name is doing double duty with the company’s. In each case the systems are trying to work out whether they’re looking at one entity or several, and every inconsistency tips them toward “several.” Pick the canonical form, update everything you control in one pass, and request corrections where you can on the things you don’t. Consistency isn’t a polish step here — it’s the signal.
C — Put the core facts on the page in plain English
Your entity home has to actually say the things you want Google to know — in clear, human language, not buried in a brand-story essay about your “journey.” The systems are reading this page to extract facts, so make the facts extractable. Here’s the build-it-today checklist for the page content itself:
- A one-line definition: “[Brand] is a [what you are] that [what you do] for [who you serve], based in [place].” Put it near the top, in plain text.
- Founding date: the year (and ideally month) you started — matched to your Companies House incorporation date where relevant.
- Founders and key people: named, with their roles, each linked to a bio page.
- Location and scope: where you’re based and the geographic markets you serve (e.g. “UK-wide, with clients across the EU”).
- What you do, specifically: your products, services or categories named with the words real people use — not internal jargon.
- Proof of existence: logo, contact details, and a registered office or company number for UK trust signals.
Write it so a stranger — or a language model — could read the page once and correctly answer “who are they, what do they do, and where?” If the page can’t pass that test for a human, it won’t pass it for Gemini either. And remember the Knowledge Panel point from earlier: this plain-English description is a strong candidate for the text Google ends up showing about you, so make the first sentence one you’d be happy to see in your brand SERP.
A quick contrast makes the point. “Founded in 2019, we set out on a mission to reimagine how modern teams work together, driven by a passion for simplicity” tells Google almost nothing extractable — it’s atmosphere, not fact. “Acme is a UK project-management software company, founded in 2019 in Bristol, that helps professional-services firms plan and bill client work” hands over the type, the place, the founding date, the category, and the audience in one sentence. Both can live on the page, but the second one is the sentence that does the entity work — and the one Google can lift into your Knowledge Panel. Lead with the facts; save the mission statement for after.
H — Hook up the schema (Organization + Person)
Now you make the same facts machine-readable. Schema markup is the most direct signal you can send about what your entity is — and sites without Organization schema are effectively invisible to the entity layer of search. You want an Organization JSON-LD block on your entity home, with an @id that points to your canonical domain (this is the unique anchor that ties every mention of your entity together), plus the core properties and your sameAs array. Here’s an illustrative block for a UK brand — adapt it, don’t paste it verbatim:
{
“@context”: “https://schema.org”,
“@type”: “Organization”,
“@id”: “https://yourbrand.co.uk/#organization”,
“name”: “Your Brand”,
“url”: “https://yourbrand.co.uk”,
“logo”: “https://yourbrand.co.uk/logo.png”,
“description”: “UK software company helping…”,
“foundingDate”: “2019-04”,
“founder”: { “@type”: “Person”, “name”: “Jane Smith” },
“sameAs”: [
“https://www.wikidata.org/wiki/Q00000000”,
“https://www.linkedin.com/company/yourbrand”,
“https://find-and-update.company-information.service.gov.uk/company/00000000”,
“https://x.com/yourbrand”
]
}
Then add Person schema on each founder’s bio page, with a worksFor property pointing back to your Organization @id. That closes the loop between the people and the brand — Google can now see that Jane Smith founded and works for this specific entity, not some other Jane Smith.
Where this trips people up. A few failure modes account for most broken implementations. Mismatched facts: your schema says you were founded in 2018 but your About text says 2019 — pick one truth and make every source agree. Multiple conflicting Organization blocks across the site, each with a different @id, so nothing consolidates. Schema that validates but describes a different entity than the visible page (Google cross-checks the two). And the classic: shipping the markup, never testing it. Run the page through Google’s Rich Results Test and the Schema.org validator before you call it done, and re-test after any site redesign — a theme update silently dropping your JSON-LD is one of the most common ways an entity home quietly breaks.
O — Wire up your sameAs identity graph
The sameAs array is where the entity home stops being an island. Each URL you list is you telling the systems “this other profile is also officially us” — and the more independent, authoritative confirmations you stack up, the more confidently Google can resolve your entity. Think of it as the identity backbone of the whole exercise. Prioritise these:
- Wikidata: your QID is the single most valuable sameAs target, because it’s the structured node Google’s Knowledge Graph reads directly.
- Companies House: for UK entities, your official register record is a high-trust, low-controversy identity confirmation that most brands forget to include.
- LinkedIn company page: widely used as an entity signal and almost always already live.
- Your verified social profiles: X, Instagram, YouTube, Facebook — the official ones, not fan or duplicate accounts.
- Crunchbase, industry registers, and an ISNI where you have one: additional authoritative corroboration, especially for B2B and funded companies.
The rule is reciprocity: every profile in your sameAs array should, where it can, point back at your canonical domain. When your entity home points to your Wikidata item and your Wikidata item points back to your site, each one corroborates the other and the entity hardens. One discipline above all — only list profiles that are genuinely, officially yours and accurate. A sameAs link to a half-abandoned account with the wrong details actively confuses the picture you’re trying to clarify.
A practical UK note on sequencing: don’t wait for a Wikidata item to exist before you ship the rest. Build the entity home, the schema, and the sameAs links you can confirm today — Companies House, LinkedIn, your socials — and add the Wikidata QID to the array once it’s live. The identity graph is additive; you strengthen it over time rather than needing every node in place on day one. Just keep it accurate as you go, because a sameAs array is a promise, and a broken or wrong promise costs you more confidence than the extra link earns.
R — Make it the most-linked-to page on your site
Here’s the step almost everyone skips. Your entity home should be the most internally linked page on your whole site. That’s how you tell Google, through your own architecture, “this is the centre of gravity for our brand.” In practice that means linking to it from your main navigation or footer (site-wide), from author bios, and contextually from your most-trafficked pages wherever your brand identity is relevant.
This is also where internal link equity does real work. The pages on your site that earn external backlinks pass authority through your internal links — so routing some of that flow toward your entity home strengthens it as a ranking entity, not just a semantic one. If you want the mechanics of how that equity actually moves (and the myths that waste people’s time), our breakdown of how internal link equity flows in 2026 covers it. The quick win most UK sites are missing: run an internal link audit, find your ten highest-traffic pages, and check whether any of them link to your entity home. Adding those links costs nothing and frequently moves things within a single crawl cycle — the same free lever that drives internal-linking wins for featured snippets.
Be deliberate about the anchor text, too. When you link to your entity home, use your brand name as the anchor most of the time — “about Acme,” “the Acme team,” “Acme” — because branded anchors pointing at your canonical page are another consistency signal reinforcing which entity that page represents. You don’t need exact-match keyword anchors here; the job isn’t to rank the About page for a commercial term, it’s to make unmistakably clear that this page is the brand. A footer link site-wide, a line in every author bio, and a handful of contextual links from your best content is usually all it takes to make the entity home the most-linked node on the site.
Build your entity map first (the spreadsheet that makes this systematic)
If you manage more than a handful of pages, do this before you touch the schema. An entity map is a simple sheet that ties every important URL to the entity it represents — your semantic source of truth. It turns “entity SEO” from a vague aspiration into a checklist you can actually work through, and it stops you accidentally creating two pages that both claim to be about the same thing.
| URL | Primary entity | Related entities | External ID | Notes |
| /about/ | Your Brand (Organization) | Founders; HQ city; sector | Wikidata QID; Companies House no. | This is the entity home. @id lives here. |
| /team/jane-smith/ | Jane Smith (Person) | Your Brand; her prior roles | LinkedIn; ORCID if any | worksFor → entity home @id. |
| /product/[name]/ | Product (the offering) | Brand; category; competitors | — | Product schema; links up to brand. |
| /london/ | Your Brand in London (place) | Brand; London; service area | Google Business Profile | Only if you have a real local presence. |
Columns: URL, primary entity, related entities, external identifier, and relationship notes. Fill it in for your top pages, then implement against it. Over time this sheet becomes your internal map of how your brand connects to the wider web of entities in your niche — founders, products, locations, categories, even the competitors you’re benchmarked against when you run a check on which pages AI Overviews actually cite.
A UK worked example: an entity home that fixed a confused brand
Take a composite drawn from UK brands we’ve analysed — we’ll call them a Bristol-based B2B fintech with a common-word name it shared with an American app and a defunct UK consultancy. Their problem wasn’t content or links; by classic metrics they were doing fine. The problem was that their branded search showed a messy, half-wrong picture, no Knowledge Panel appeared, and two AI assistants confidently described them as the American product. The systems simply couldn’t tell which “thing” they were.
The fix was an entity home, built straight off the ANCHOR blueprint. They consolidated three overlapping About-style pages into one canonical /about/ URL. They locked the name to a single form and corrected it on their LinkedIn page, their Companies House public record display, and every byline. They rewrote the page to lead with a plain one-line definition and the core facts — founded, founders, Bristol HQ, the specific fintech category they serve. They added a clean Organization schema block with a stable @id, Person schema for both founders with worksFor pointing back, and a sameAs array tying the page to a freshly created Wikidata item, Companies House, LinkedIn and their verified socials. Finally, they made the entity home the most-linked page on the site, including from the footer and their ten top-traffic articles.
The outcome was the kind that makes the case on its own. Within roughly two months their branded-query Knowledge Panel appeared and stabilised, the description Google showed matched the first line they’d written, and the two AI assistants stopped confusing them with the American app. None of it required a single new backlink — it was pure entity hygiene, done in the right order. That’s the recurring lesson: for a brand the web already discusses, the entity home is often the missing piece that lets all the existing signals finally consolidate.
Why did it work so fast? Because the brand had been generating the right signals all along — the coverage, the search demand, the content — but those signals had nowhere clean to land. Google was receiving evidence about three different “things” that happened to share a name and couldn’t confidently merge them. The entity home gave it an unambiguous anchor: one canonical page, one consistent name, one @id, and a sameAs graph that said “all of this is the same entity, and here’s the proof.” Once that anchor existed, the consolidation the brand needed could finally happen. That’s the mechanism worth internalising — an entity home doesn’t manufacture authority, it gives existing authority somewhere to attach.
How the entity home plugs into the rest of your authority work
Be honest about what the entity home can and can’t do. It makes your brand legible — it cannot, on its own, make the web care about you. A brand that no independent source discusses won’t be rescued by a tidy About page and a QID. The entity home is the foundation that lets your earned signals land cleanly; the earned signals are still the thing that builds the authority. So the two have to run together.
Here’s the division of labour. The entity home and your schema are what you about your brand. The corroboration — the part the AI engines weight most heavily — comes from independent sources describing you, and that’s classic earned-media work: editorial guest contributions on relevant publications, expert commentary via HARO, and reactive PR that puts your brand name in front of journalists. Every one of those produces the third-party mentions that confirm what your entity home claims — and the more your name is used consistently across the web, the more those signals consolidate onto the entity you’ve just defined.
The pattern also shifts by sector, which is where the UK specifics bite. A recruitment or HR-tech brand earns corroboration through trade titles like People Management and Personnel Today; a wedding or hospitality supplier builds it through hyper-local press, county magazines and venue associations whose mentions feed brand-search demand. The entity home is the same discipline for both — one canonical page, consistent name, clean schema — but the sources that corroborate it are wherever your buyers and their journalists actually are.
There’s a data point worth carrying through all of this. When you look at what actually predicts AI-search visibility, brand mentions across the web tend to out-predict raw backlink counts — the corroboration layer matters more than the link tally alone. That’s not an argument against links; it’s an argument that links and mentions are doing slightly different jobs, and your entity home is what lets both of them attach to a single, well-defined brand instead of scattering. Build the page, then go earn the coverage that points at it, and measure the result where it now shows up: in whether the AI surfaces start naming you for the questions your buyers actually ask.
Quick answers to the questions people always ask
Should my entity home be my homepage or my About page? Either can work, but for most brands the About page is the cleaner choice — it exists to describe who you are, which is exactly the entity home’s job, whereas the homepage is doing ten other jobs at once. Whichever you pick, the Organization @id and the consolidated facts live there, and you commit to it.
How long until I see a Knowledge Panel? There’s no guaranteed timeline, and not every entity earns a panel — Google shows them only when it has enough validated, corroborated information. Clean entity hygiene plus genuine third-party mentions is what moves it; in practice brands that already have some independent coverage often see a panel firm up within weeks of fixing their entity home, while brands the web barely discusses may need to earn the coverage first.
Do I need Wikidata and Wikipedia as well? They’re different layers of the same stack. Your entity home is what you declare on your own site; Wikidata is the external structured record that helps verify it; Wikipedia is a separate, higher bar earned through notability. Start with the entity home because it’s entirely in your control, then add a Wikidata item when you can, and treat Wikipedia as a possible long-term consequence of real coverage rather than a near-term task.
Is this just for big brands? The opposite. Big brands usually already have a resolved entity; it’s small and mid-sized UK businesses — especially those with common-word or shared names — that gain the most, because they’re the ones the systems most often confuse. The entity home is the single fastest way for a smaller brand to stop being mistaken for something else.
The mistakes that keep brands invisible
A handful of errors account for most failed entity homes. Avoid these and you’re ahead of the large majority of your competitors:
- Spreading the entity across pages. Five thin “about” variations instead of one definitive page. Consolidate to one canonical URL.
- Name drift. Different forms of your brand name across your site, socials and register. Pick one and enforce it.
- Schema that no human could verify. Markup describing facts the visible page doesn’t state. Keep the page and the schema in perfect agreement.
- An orphaned entity home. A beautiful About page that nothing internally links to. Make it your most-linked page.
- Keyword-stuffing it. Cramming entity-flavoured phrases in for density. Entity SEO is about signalling which thing the page is about, not repeating a phrase — write for clarity, not density.
- Set-and-forget. Facts change; rebrands happen; themes drop schema. Re-check the page, the markup and the sameAs links every quarter.
None of this is complicated, and that’s rather the point. The entity home is the rare piece of 2026 SEO that’s almost entirely in your hands, costs close to nothing, and compounds quietly underneath everything else you do. Decide on the URL, lock the name, state the facts, wire up the schema and the sameAs graph, and make it the centre of your internal links. Do that, and when the systems go looking for “who is this brand,” they’ll find one clear, confident answer — the one you wrote.
