Ask an assistant about your company and watch what happens. Some of it will be right. Some of it will be a competitor’s achievement attributed to you, a founder who left in 2023, an old address, or a confident sentence about what you do that nobody at your company would recognise.
That is not a hallucination problem. It is a sourcing problem. The machine assembled an answer from whatever it could find, and what it could find was scattered, stale and contradictory.
The fix is unglamorous and it works: give the web one page that is unambiguously the authority on who you are, make every other profile point at it, and make the facts on it machine readable. That page is your entity home.
This is the Understandability layer of assistive agent optimization, and it is the first thing we fix in any engagement (Kalicube, Search Engine Land). An agent cannot trust you or choose you until it is confident it knows who you are. For the full framework, see our assistive agent optimization guide.
What Is an Entity Home?
An entity home is the single page you nominate as the authoritative source about a brand, person or organization: it states every core fact in plain text, carries the structured data that describes the entity, and is the page that every other profile you control links back to.
Three things make it work, and all three are required.
- It is singular. One page per entity. Not an About page, a Company page, a Founders page and a Press kit all half telling the story.
- It is authoritative. It lives on your own domain, which you control, rather than on a profile you rent from a platform.
- It is corroborated. Everything it claims is confirmed somewhere independent, and your own profiles all point back to it.
For most businesses the entity home is the About page, upgraded. For a founder or executive it is a personal bio page. Larger organizations may need one per major entity: the company, the founder, perhaps a flagship product.
Why One Page Changes the Answer?
Machines resolve entities before they describe them. The question “which company is this” has to be settled before “what do they do” can be answered. Ambiguity at that first step produces confident nonsense at the second.
Four common ambiguity traps, all of which we have seen cause real misattribution:
- Name collisions. Another company, a person, a product or a band shares your name. Without a strong signal, the systems merge you or pick the wrong one.
- Scattered facts. Founding year on the About page, leadership on LinkedIn, services on a sales page, address only in the footer. Nothing to anchor to.
- Stale duplicates. An old site, a dormant profile, a directory listing from two pivots ago, each asserting something different.
- Unverifiable claims. Statements that appear nowhere except on your own marketing, which a cautious system will not repeat.
A single, clear, well linked page collapses all four. It gives every system one place to resolve to and one version of the facts to carry forward.
What Belongs on the Page?
Think of it as a reference entry that happens to be well written, not a brand story that happens to contain facts.
| Section | What it must contain | Why an agent needs it |
|---|---|---|
| Identity | Legal and trading name, any former names, what category of business you are in | Resolves which entity this is and prevents name collisions |
| What you do | Plain description of services or products, and who they are for | Matches you to a need without guesswork |
| Provenance | Founding date, founders, location, company size, registration if public | Establishes you are real and currently operating |
| People | Named leadership with roles, linked to their own profiles | Agents check for accountable humans behind a brand |
| Proof | Clients, case studies, credentials, awards, press, each linked to a source | Converts claims into verifiable statements |
| Reach | Markets and languages served, and any limits | Avoids being recommended where you cannot deliver, and vice versa |
| Contact | Address if you have one, phone, email, booking link | Lets an agent complete the next step |
| Profiles | Links to every official profile you control | Ties the scattered web back to this page |
Two rules that matter more than the list itself. Every fact belongs in real text, never only inside an image, a logo lockup or a PDF. And every fact here must match what your other profiles say, because a contradiction is worse than an omission: an omission leaves a gap, a contradiction destroys confidence in everything nearby.
The Schema Layer
Structured data does not create authority. It removes ambiguity about facts that already exist on the page. Google’s guidance is explicit that structured data is not a requirement for appearing in its AI features, and that there is no special optimization for them (Google, Google). Add it because it makes your facts unambiguous to a machine, not because someone told you AI requires it.
Use Organization for the company and Person for a founder or executive (schema.org). The minimum worth shipping:
{
"@context": "https://schema.org",
"@type": "Organization",
"@id": "https://example.com/about/#organization",
"name": "Example Company",
"legalName": "Example Company Ltd",
"url": "https://example.com/",
"logo": "https://example.com/logo.png",
"foundingDate": "2019-03-01",
"description": "One sentence on what you do and for whom.",
"founder": { "@type": "Person", "name": "Jane Doe" },
"address": { "@type": "PostalAddress", "addressLocality": "City", "addressCountry": "GB" },
"sameAs": [
"https://www.linkedin.com/company/example",
"https://www.crunchbase.com/organization/example"
]
}Three implementation notes that catch people out. Use a stable @id so the entity can be referenced consistently from other markup on your site. Make sure the markup matches what a visitor can actually see on the page, which is a stated requirement in Google’s structured data policies (Google). And follow the logo guidance rather than pointing at whatever image was nearest (Google).
For the wider schema picture, including which types earn you what, see our guide to schema markup for AI Mode.
sameAs: The Part Everyone Gets Wrong
The sameAs array is how you tell a machine “these profiles are also me”. It is the cheapest entity work available and most sites either skip it or stuff it.
Include, in roughly this order of value:
- Your LinkedIn company page
- Authoritative business databases where you have a real entry
- Your primary social profiles, the ones you actually post on
- Industry directories and review platforms where you have a genuine listing
- Wikidata, if you genuinely meet its notability requirements, and only then
On that last point: do not create a Wikidata item for a company that does not meet the notability criteria. It will be deleted, and the attempt is visible (Wikidata).
Leave out:
- Dormant profiles you abandoned
- Directory listings you never claimed and cannot edit
- Anything with a different name, address or description from your entity home
- Profiles belonging to a former entity or a prior brand, unless you also handle the name change explicitly
Then close the loop.
Every profile in that list should, where the platform allows it, link back to the entity home URL rather than to your homepage. A reciprocal set of links between a page and the profiles it claims is a far stronger signal than a one way list.
The Claim, Frame, Prove Pattern
Marketing pages assert. Reference pages substantiate. An entity home has to do the second while still reading like a human wrote it. The pattern we use on every one:
- Claim. A short, specific, checkable statement. “We have run paid media for retail brands since 2019.”
- Frame. The context that makes it meaningful. “Mostly mid market retailers spending between X and Y a month.”
- Prove. A link to something outside your control. A case study with a named client, a press mention, a verified review, a public registration, a conference listing.
Compare the two versions below, which carry the same information:
| Assertion only | Claim, frame, prove |
|---|---|
| We are a leading digital marketing agency trusted by brands worldwide. | We have run paid media for retail brands since 2019, mostly mid market retailers in two markets. Our work for [Client] is documented in this case study and was covered by [Publication]. |
| Our team are industry experts. | The team is led by [Name], who previously led acquisition at [Company] and speaks regularly at [Event]. Profiles and talks are linked below. |
The second column is what a machine can repeat without risk. The first column is what it will quietly decline to repeat, because nothing in it can be checked.
This is also why the entity home cannot be written by someone who does not know the business. The facts have to be true and sourced, and somebody has to be willing to stand behind each one.
The Founder’s Entity Home
If a named person is part of why clients choose you, that person needs their own entity home too. Agencies, consultancies, professional services and personal brands all fall into this category, and the page is not the same as the company one.
A person’s entity home answers a different set of questions:
- Who they are professionally. Current role, organization, and the field they work in, stated plainly in the first paragraph.
- What they are credibly expert in. Specific areas rather than a list of adjectives. “Paid media for retail” beats “growth leader”.
- The record. Previous roles, years active, qualifications, anything publicly verifiable.
- The public trail. Talks, podcasts, published articles, quotes in press, each linked out.
- The relationship to the company. Explicitly stated, and mirrored in the company’s own markup so the two entities connect.
Mark it up as a Person, give it its own stable identifier, and connect it to the organization from both directions. The company page names the founder, the founder page names the company, and the structured data on each references the other. That reciprocity is what stops a machine treating them as two unrelated things that happen to share a surname.
One judgement call worth making deliberately: do not create a personal entity home for someone who has no public trail at all. An empty profile page with nothing to link to adds an entity for a machine to be uncertain about, which is the opposite of the goal. Build the trail first, then the page.
Common Mistakes
- Several competing About pages. Pick one. Redirect or consolidate the rest. Two half authoritative pages are worse than one.
- Facts that exist only in images. Team photos with names baked in, an infographic timeline, a logo that contains the founding year. Machines read none of it.
- Schema that contradicts the page. Markup claiming an address or a founding date the visible page does not state breaks structured data policy and undermines trust.
- Inconsistent naming. “Example Co”, “Example Company Ltd” and “example” across profiles. Choose one public form, state the legal name once, and be consistent.
- No named humans. Anonymous brands are harder to verify. A named, linked leadership team is a credibility signal that costs nothing.
- A press page with no press. Empty proof sections are worse than absent ones. They invite the question and answer it badly.
- Set and forget. A stale entity home is an actively misleading one. Review it when anything material changes, and at least twice a year regardless.
How to Verify It Worked?
Entity work is slow and mostly invisible, so measure it deliberately rather than waiting for a feeling.
- Write a fixed list of ten questions about your brand: who are they, what do they do, who runs it, where are they, who do they serve, how much do they cost, how long have they existed.
- Ask those questions across the assistants your buyers use, before you make any changes. Save the answers verbatim with a date.
- Make the changes: consolidate, publish the facts in text, add the markup, fix the profile links.
- Wait. Entity signals propagate slowly and unevenly, and nobody publishes a timeline for it. Re ask at 30, 60 and 90 days (Google has background on how brand information surfaces).
- Score the change on accuracy, not flattery. The win is “the facts are now correct and consistent”, not “it said something nice”.
Expect partial results. Assistants also draw heavily on third party sources, and citation studies consistently show community and professional platforms among the most cited domains (Search Engine Land). Your entity home makes the facts available and unambiguous; it does not override what the rest of the web says about you. That is the next piece of work.
A 30 Day Plan
Week 1: decide and inventory.
- Pick the one URL that will be the entity home. Usually your About page.
- List every profile you control, and note what each one currently says about name, description, address and founding date.
- Capture the baseline answers from assistants and save them with the date.
Week 2: write the page.
- Cover every section in the table above, in real text.
- Apply the claim, frame, prove pattern to each substantive statement.
- Remove or soften anything you cannot support with a source.
Week 3: mark it up and link it.
- Add Organization markup, with Person for the founder, matching the visible page exactly.
- Build the sameAs list from profiles you actually control and maintain.
- Update each of those profiles to point back at the entity home URL.
Week 4: consolidate and schedule.
- Redirect or rewrite competing pages so only one remains authoritative.
- Fix contradictions found in the week 1 inventory.
- Diarise a review at 30, 60 and 90 days against the saved baseline.
Where YuvGro Fits?
We build entity homes as a fixed scope piece of work: a profile and contradiction audit across everything that mentions you, the page itself written with the claim, frame, prove pattern, the Organization and Person markup, a cleaned sameAs set with reciprocal links, and a before and after record of what assistants say about you.
It is usually the first thing we do, because the rest of the AI visibility work depends on machines knowing which company they are describing. See our AEO services and AI optimization services.
Frequently Asked Questions
What is an entity home page?
An entity home is the single page you nominate as the authoritative source about a brand, person or organization. It states every core fact in plain text, carries structured data describing the entity, and is the page that all your other official profiles link back to. For most businesses it is the About page upgraded into a reference entry: identity, what you do, provenance, named people, verifiable proof, markets served and contact details.
How do I make AI understand my brand?
Give it one unambiguous source and make everything else agree with it. Publish your core facts as real text on a single authoritative page, add Organization and Person structured data that matches what is visible, list your official profiles in a sameAs array, and update those profiles to link back to that page. Then fix contradictions between sources, because conflicting information damages confidence more than a missing fact does.
What is sameAs schema and why does it matter?
sameAs is a property in your structured data that lists other web pages representing the same entity, such as your LinkedIn company page, business databases and genuine review platform listings. It matters because it ties your scattered presence back to one identity, which helps machines resolve who you are. Include only profiles you control and maintain, make sure each says the same name and description, and have them link back to your entity home where the platform allows it.
Does structured data help AI search?
It helps machines confirm facts quickly and unambiguously, but it is not a requirement. Google’s guidance states plainly that structured data is not required to appear in its AI features and that there is no special optimization for them. Add Organization and Person markup because it removes ambiguity about facts already visible on the page, not because you were told AI systems demand it. Markup that contradicts the visible page also breaks Google’s structured data policies.
Should my entity home be my About page or my homepage?
Usually the About page. A homepage has to sell, which means it changes often and rarely states provenance clearly. An About page can carry the full reference set, founding date, leadership, markets, proof and contact, without fighting a conversion goal. What matters more than the choice is that there is only one such page, that it is on a domain you control, and that every profile you own points back to it.
How long does it take for AI assistants to update what they say about my brand?
There is no published timeline, and propagation is slow and uneven across systems. Capture a dated baseline of what assistants say before you change anything, then re ask the same fixed questions at 30, 60 and 90 days. Judge the result on accuracy rather than flattery. Expect partial improvement, because assistants also draw heavily on third party sources that your own page cannot override.
Should I create a Wikidata entry for my company?
Only if you genuinely meet Wikidata’s notability requirements. Items created for companies that do not meet them get deleted, and the attempt is publicly visible, which is a poor look for a brand trying to establish credibility. If you do qualify, a well maintained item is a useful corroborating source. If you do not, spend the effort on review platforms, genuine press and industry listings instead.
What is the claim, frame, prove pattern?
It is a way of writing entity facts so machines can repeat them safely. Make a short, specific claim; add the context that makes it meaningful; then link to evidence outside your own control such as a named case study, a press mention, a verified review or a public registration. Unsupported superlatives like “leading” or “trusted worldwide” cannot be checked, so cautious systems tend not to repeat them.
How many entity home pages should a company have?
One per distinct entity. A single company with one brand needs exactly one. If a founder has a meaningful public profile of their own, they warrant a second page as a Person entity, linked to the organization. Large organizations may add one for a flagship product. What you must avoid is several pages competing to describe the same entity, which recreates the ambiguity the entity home exists to remove.