Entity & Knowledge Panel Checker
Check if your brand is a recognized entity in Wikidata & Wikipedia — the backbone of Google Knowledge Panels and AI recognition. Free, no API key.
Knowledge Panel Checker: find out which of four things is actually wrong
Type in your brand name and we check the thing you're actually asking about: not just whether Google's Knowledge Graph has a record of you, but whether that record ever became a rendered panel, and whether the facts inside it are yours. Most tools stop at the API record and treat its resultScore as a confidence meter — it isn't one. If you run a local business, the honest answer might be that a panel was never the right target for you at all.
Built and reviewed by Sayed Hasan, founder of SEOs Hut · Updated 28 September 2026 · Free, no signup
Am I in Google's Knowledge Graph?
Possibly, and it may not matter yet. Google's Knowledge Graph Search API can return a record for your brand with no panel ever appearing in search results — the API and the rendered panel run on separate thresholds. A panel appears only when Google's own algorithm decides there's enough information about you across the open web, automatically, with no application involved.
Being in the API is not having a panel
Query the Knowledge Graph Search API for your brand and you'll get back a record with a resultScore, and it's tempting to read that number as a confidence score. It isn't. resultScore ranks how well that record matched the specific query you searched — not how strong or established your entity is. Google's own documentation warns the API 'is not suitable for use as a production-critical service' and quietly points you elsewhere: 'we recommend using data dumps from Wikidata instead.' A record in the API and a panel on the results page are two separate systems with two separate thresholds. You can have either one without the other.
Which of the four states are you actually in?
Entity status isn't a score out of a hundred. It's one of four states, and each one needs a completely different fix — chasing the wrong one wastes months.
Search your exact brand name in Google. What actually shows on the results page?
Are you a local business — a plumber, a dentist, a shop with a physical location or a defined service area?
Panels are automatic, and Google never mentions Wikipedia
“Knowledge Panels are created automatically by Google Search Algorithm when there is enough information available on the open web”
<b>Google Search Help, Knowledge Panel documentation</b> — Google Knowledge Panel Help
No, you don't need a Wikipedia page
This one survives because two different documents keep getting conflated.
Wikidata's actual notability policy needs only one of three things to be true: a valid sitelink to Wikipedia, Wikivoyage or Commons; being 'an instance of a clearly identifiable conceptual or material entity that can be described using serious and publicly available references'; or that it 'fulfills a structural need.' Nowhere in that policy does the word 'independent' appear. (Wikidata is currently running an open RfC proposing to rewrite all three criteria, so treat this as current only as of 28 September 2026.)
That word comes from a different document entirely — Wikidata:Self-promotion, an essay, not a policy — which states that 'personal websites, social-media pages, personal blogs, press releases, native advertising, and marketing materials do not meet this requirement' and that 'paid promotion is still self-promotion.' It's the standard serious editors hold you to in practice, but it isn't the policy itself, and the gap between the two is where most of the confusion lives.
Google, separately, never makes Wikipedia or Wikidata a requirement for a panel at all. Its own description is that a panel forms when information is available on the open web, and that 'information that appears in a knowledge panel comes from various sources across the web.' The lever that's actually documented is independent coverage repeating the same facts about you consistently — which is mechanically what the Citation Finder is built to surface.
What a Knowledge Graph API record actually tells you
A real-shaped record, annotated. Note what it doesn't say anywhere: nothing here confirms a panel exists.
The six terms this topic keeps confusing
- QID
- Wikidata's unique item identifier — the letter 'Q' followed by digits. Per Wikidata's own glossary, a label 'does not uniquely identify the page; this function is served by its QID (title) only.'
- KGMID
- Google's own identifier for an entity in its Knowledge Graph, in the form /m/xxxx or /g/xxxx. A separate identifier space from a QID, though the two are frequently mapped to each other.
- /m/ vs /g/
- /m/ = a legacy identifier issued under Freebase before Google retired it (Wikidata property P646). /g/ = minted after Freebase, for entities Google has identified since (Wikidata property P2671). g.co/kg/<mid> currently 302-redirects.
- resultScore
- A relevance number the Knowledge Graph Search API returns for how well a record matched your specific query. Not a measure of how strong or well-established your entity is.
- Panel vs Business Profile
- A knowledge panel is Google's general-purpose entity box. A Google Business Profile is the local-business equivalent, and Google's own guidance routes location- and service-area businesses there instead of toward a panel.
- sameAs
- A schema.org property pointing at pages that 'unambiguously indicate the item's identity' — a Wikipedia page, Wikidata entry, or official profile. Google documents it as supporting information, not as one of the properties it actually names for disambiguation (that's iso6523 and naics).
Four ways people chase the wrong fix
All four come from treating entity resolution as a form you fill in, rather than a set of facts that has to agree with itself.
Looking for an application form
What happens: There isn't one, for a panel or for Knowledge Graph inclusion. People spend weeks looking for a submission page that doesn't exist.
Do this instead: Panels form automatically once your facts are consistent and corroborated enough. The work is in the facts, not in a form.
Assuming sameAs is Google's disambiguation signal
What happens: Google never actually calls sameAs a disambiguation property. Its own Organization documentation names different fields for that job: 'Some properties are used behind the scenes to disambiguate your organization from other organizations (like iso6523 and naics).'
Do this instead: Keep sameAs for identity, and add iso6523Code (prefixed 0060: for a DUNS number, 0199: for an LEI) or naics where it genuinely applies. Verify the block is actually live on the page with the Schema Markup Analyzer.
Ignoring a domain that changed hands or names
What happens: A rebrand, a bought domain, or an old redirect chain is one of the most common causes of a name collision, and it's rarely investigated because it looks unrelated to 'SEO.'
Do this instead: Check the domain's registration and ownership history with the Domain Age Checker before assuming Google simply made a mistake — often it's repeating a fact that used to be true.
Assuming AI Overviews run on the Knowledge Graph
What happens: The word 'entity' appears zero times in Google's dedicated AI Overviews and AI Mode optimisation guide, as do Wikidata, Wikipedia, Knowledge Graph, and sameAs. Google actively warns against the adjacent tactic: 'seeking inauthentic mentions across the web isn't as helpful as it might seem.'
Do this instead: Treat entity resolution and AI citation as related but separate problems, each worth checking on its own terms.
What the policies actually require
Once the entity resolves, ask the next question
Fixing your entity is table stakes, not the finish line. Once Google — and separately, the AI engines — can resolve who you are without ambiguity, the question that actually affects traffic is whether they choose to cite you. Run that check with the AI Visibility Checker once your facts genuinely agree.
Entity & Knowledge Panel Checker FAQ
Why is getting a Google Knowledge Panel so confusing?
Our logo is showing up in the knowledge panel for a company with similar name
Lost my Google Knowledge Panel after changing Person Schema. Need advice
Google's priority on Google My Business Panel vs Structured Data/Knowledge Graph
How much does Google Knowledge Panel cost?
Is the Knowledge Panel going extinct? I'm seeing it less and less for brands
Primary sources used on this page
- Wikidata Glossary — QID definition and why labels aren't unique identifiers — www.wikidata.org
- Wikidata:Notability — the actual policy, one of three criteria required — www.wikidata.org
- Wikidata:Self-promotion — the essay (not policy) where "independent" sourcing comes from — www.wikidata.org
- Google: Organization structured data — disambiguation properties (iso6523, naics), sameAs as supporting info — developers.google.com
- Google Knowledge Panel Help — panels created automatically from open-web information — support.google.com
- Google Knowledge Panel Help — claiming via four surfaces; not all panels claimable; local businesses routed to Business Profile — support.google.com
- Google Knowledge Graph Search API docs — not production-critical, recommends Wikidata dumps instead — developers.google.com
- Google Search Central: AI optimisation guide — no entity/Wikidata/sameAs mentions, warns against inauthentic mentions — developers.google.com
Fix the entity, then check whether it pays off
Entity resolution is plumbing, not a destination. These build the facts underneath it, and the last one tells you whether it actually changes who gets cited.
Read the guide: Local Business Schema: How to Add LocalBusiness Markup and Benefits of Google Business Profile for Local Businesses. Want it handled for you? See our AI SEO (GEO) services.