How to be cited by Gemini and enter the Knowledge Graph
TL;DR
- Gemini and Google's AI features are grounded in Google's index and Knowledge Graph - so being a recognized entity is the lever.
- Entity signals: consistent name and role, Person/Organization markup with a stable @id, and sameAs to authoritative profiles.
- Wikidata is the most actionable path into the Knowledge Graph for people and organizations.
- This is slow, compounding work - not a switch - but it underpins both SEO and GEO.
Unlike Perplexity or Copilot, which lean on Bing, Gemini and Google's AI Overviews are grounded in Google's own index and its Knowledge Graph - the database of entities (people, organizations, places, things) and how they relate. To be cited by Gemini, you have to be something Google recognizes and trusts. That's an entity problem, not a keyword problem.
Why the Knowledge Graph matters
When Google understands that "Miguel Maio" is a specific person - an SEO consultant and trainer, with these credentials and these profiles - it can confidently attribute content to that entity and surface it in AI answers. When you're just a string of text on a page, it can't. The Knowledge Graph is how "a name" becomes "a known thing".
The entity signals that count
- A consistent name, role and description everywhere you appear - no drift between LinkedIn, your site and third parties.
- Person and Organization structured data with a stable, reused <code>@id</code> so every page refers to the same entity.
- <code>sameAs</code> links to authoritative profiles: LinkedIn, university and business-school faculty pages, reputable publications.
- Third-party corroboration: being described consistently by credible sites Google already trusts.
- Where justified, a Wikidata item - the most direct, editable route into the Knowledge Graph.
Wikidata: the actionable path
Wikidata is a structured, open knowledge base that feeds the Knowledge Graph. For a genuinely notable person or organization, a well-sourced Wikidata item - linked via sameAs from your site - is the clearest signal you can create yourself. It must be backed by independent sources; fabricated notability gets removed and can backfire.
Expect it to be slow
Entity authority compounds over months, not days. There's no button. But it's the same foundation that strengthens SEO and GEO at once - which is why I treat it as core infrastructure, not a side tactic.
Key data
| Knowledge Graph — facts (2020) | 500B+ |
|---|---|
| Knowledge Graph — entities (2020) | ~5B |
| Gemini app — MAU (Mar 2025) | 350M |
| Gemini app — MAU (Q4 2025) | 750M |
Knowledge Graph figures are from 2020 (latest public).
Sources: Google / The Keyword · TechCrunch
Common mistakes and how to do it right
Entity work is where good intentions meet inconsistent execution. The recurring mistakes:
| Avoid | Do |
|---|---|
| ✗ Different names/roles across LinkedIn, site and press | ✓ One consistent name, role and description everywhere |
| ✗ Person markup with a different @id on every page | ✓ A single, reused @id so all pages mean the same entity |
| ✗ Inventing a Wikidata item with no real sources | ✓ Building notability first, then a well-sourced item |
| ✗ Expecting Knowledge Graph inclusion in weeks | ✓ Treating entity authority as slow, compounding work |
Tools I use and recommend
- GeminiGoogle's AI assistant, grounded in Search.
- Google Search ConsoleOrganic performance, coverage and field Core Web Vitals.
- Rich Results TestValidate structured data (free, Google).
- ChatGPTAI assistant for research, analysis and quick audits.
Sources
Frequently asked questions
Do I need Wikipedia to be in the Knowledge Graph?
No. Wikipedia helps, but Wikidata, structured data and consistent sameAs signals can get an entity recognized without it. E-E-A-T and entities →
Is this different from getting cited in ChatGPT?
Partly. Gemini leans on Google's Knowledge Graph; ChatGPT and Perplexity lean on Bing. Strong entities help everywhere. Get cited in ChatGPT →