What Google means by “entity”
An entity, in Google’s Knowledge Graph, is a real-world thing — person, place, organization, book, event — that can be identified unambiguously and described with structured facts. A web page is a document. An entity is the subject the document is about. Ranking is about documents. Knowledge Panels are about entities.
“The entity is the thing itself. The page is just one way to talk about it.”
This is why entity SEO doesn’t live in the meta description. It lives in the graph — the network of schema, third-party profiles, Wikidata claims, and citations that let Google build a confident picture of who or what the entity is.
Person schema — the canonical block
Drop this in the <head> of every page that describes the entity (About page, speaker page, book page). It’s the same block everywhere — repetition reinforces the entity, it doesn’t confuse Google.
{
"@context": "https://schema.org",
"@type": "Person",
"@id": "https://example.com/#person",
"name": "Jane Doe",
"givenName": "Jane",
"familyName": "Doe",
"url": "https://example.com",
"image": "https://example.com/jane-doe.jpg",
"jobTitle": "Keynote Speaker on AI Ethics",
"description": "Keynote speaker, author of 'Algorithmic Trust' (Penguin, 2024).",
"worksFor": {
"@type": "Organization",
"name": "Doe Advisory",
"url": "https://doeadvisory.com"
},
"alumniOf": {
"@type": "CollegeOrUniversity",
"name": "Stanford University"
},
"sameAs": [
"https://www.wikidata.org/wiki/Q...",
"https://en.wikipedia.org/wiki/Jane_Doe",
"https://www.linkedin.com/in/janedoe",
"https://twitter.com/janedoe",
"https://www.imdb.com/name/nm..."
]
}The @id is critical — it’s the stable identifier that lets you reference the same entity across multiple schema blocks (Person, Organization, Book, Event) without Google treating them as separate things.
The sameAs graph
sameAs is where Google verifies the entity is real. Each URL must actually describe the same person, and — ideally — link back to your canonical site. Bidirectional verification is the whole point.
Minimum 20 verified profiles for a serious foundation. Group them:
- Authority anchors: Wikidata, Wikipedia (if you have one), LinkedIn, Crunchbase, Bloomberg, Muck Rack.
- Social presence: X/Twitter, Instagram, YouTube, TikTok, Threads, Facebook page.
- Category-specific: IMDB (speakers/authors), Goodreads (authors), speaker-bureau profiles, GitHub, ORCID, ResearchGate.
- Press & media: podcast host pages, Forbes contributor pages, Substack, industry publications.
Wikidata — submission checklist
Wikidata is where the Knowledge Graph is built. A clean, well-cited entry here is the single highest-leverage move for a missing panel. Submit it once, properly, and let the community maintain it.
- Label — full name as commonly used.
- Description — one line, disambiguating (e.g. “American AI ethics researcher and keynote speaker” — not just “speaker”).
- Also known as — every variant of the name in circulation, including pen names and common misspellings.
- Instance of — human (Q5). Always.
- Occupation — as many as apply, each properly linked.
- Country of citizenship — required for disambiguation.
- Notable works — books, talks, papers. Each with citation.
- Educated at — institutions with links, dated.
- Employer — current and notable previous.
- Image — Wikimedia Commons upload only, correctly licensed.
- Official website — links back to your canonical site.
- Identifiers — LinkedIn ID, X handle, IMDB nm-code, VIAF, ORCID as applicable.
Every claim needs a source. “Reference URL” pointing to an independent, verifiable page is the minimum. Self-cited claims get challenged fast.
Claiming the panel
Once a candidate panel appears, the claim flow is:
- Search your name in Google while signed into a Google account tied to an official presence (email at the domain, or YouTube channel authority).
- Click “Claim this knowledge panel” at the bottom of the panel.
- Verify a linked profile — YouTube, Search Console for the official site, or an email at the entity’s domain.
- Submit the ID + photo verification. Government ID plus a selfie holding it. Google reviews manually. Turnaround is typically 3–14 days.
- Once verified, you can suggest edits directly, upload the featured photo, and get notified when changes go live.
“Verified representative” is a persistent status. Once earned it applies to all future edits — you don’t repeat the ID flow.
Disambiguation
Rules for winning a disambiguation fight:
- Every schema block, every social bio, every Wikidata description must include the same disambiguating phrase (occupation + specialty + geography). Repetition is the training signal.
- The other entity’s sameAs graph is what’s pulling — you can’t remove their signals, but you can outweigh them by density and quality of your own.
- Fresh, dated content on your canonical site accelerates the recomputation. Old, static bios stall it.
- Timelines: entity confusion typically clears in 8–16 weeks after the full foundation is in place. It is not fast, and there is no shortcut.
FAQ
Do I need a Wikipedia page to get a Knowledge Panel?
No. A common myth. Google awards Knowledge Panels to entities it can confidently identify and describe from any authoritative source — Wikidata alone is enough if the entry is well-cited. I've seen panels appear for clients with zero Wikipedia presence but a clean Wikidata entry, strong sameAs graph, and consistent Person schema across their properties.
What's the difference between sameAs and mainEntityOfPage?
sameAs is a list of other URLs that describe the same entity — your LinkedIn, X, Wikipedia, IMDB, Crunchbase. It's how Google confirms 'this is the same person as that.' mainEntityOfPage points from a WebPage to the primary entity that page is about — usually itself, as the canonical page for the entity. Both matter; they answer different questions.
How many sameAs entries should I have?
Twenty verified profiles is my baseline for anyone serious. Fewer than ten is thin. What matters more than count is whether each linked profile links back — bidirectional verification is what makes sameAs authoritative. A LinkedIn profile that links to your site while your schema links to the LinkedIn profile is worth more than fifteen unverified directory listings.
Which schema type — Person, Organization, or both?
For a personal brand (speaker, author, executive, coach), Person is primary and any Organization schema references the Person as founder or employee. For a company where the founder is well-known but the brand is the product, Organization is primary and Person schema is nested. If in doubt: build both, mark one as sameAs of the other, and let Google resolve the graph.
Can I edit my own Wikidata entry?
Yes, once claimed. Wikidata is community-editable and welcomes verified subjects contributing to their own entries — the requirement is that every claim cites an independent, verifiable source. Self-created entries without sources get deleted fast. The winning approach is to submit a clean, well-cited entry, then leave ongoing edits to the community while you supply new citations as they arise.
How do I fix a Knowledge Panel showing the wrong information?
Claim the panel first — Google account sign-in plus ID-and-photo verification. Once verified, you can suggest edits directly through the panel interface. For deeper corrections (wrong photo, wrong description, wrong entity entirely), the fix is signal correction upstream: fix your Wikidata entry, correct your sameAs graph, ensure every third-party profile agrees. Google recomputes the panel from those signals.