The "About This Result" Test is a diagnostic protocol for verifying whether a brand has been reconciled as an Entity in Google's Knowledge Graph. By opening the "Three Dots" menu on a SERP result, you can inspect the "Source" panel. If it shows a description sourced from Wikipedia or the Knowledge Graph, the entity is Reconciled (Trusted). If it shows a generic "First indexed..." date or self-sourced text, the entity is Unreconciled (Guest), indicating no Knowledge Graph ID (KGID) association.
The Problem: The "Guest vs. Host" Dilemma
In the semantic web there are two types of websites. Hosts (Entities): Google knows who they are and trusts their identity because they exist in the Knowledge Graph. Guests (Strings): Google only knows what they say; it indexes their keywords but doesn't recognize their brand authority.
The invisible penalty: you might rank first for a long-tail keyword today, but without entity recognition you're vulnerable. Google's Gemini and SGE preferentially cite "Entities" over "Strings" because entities carry verified trust signals. And if Google doesn't lock your brand to a specific KGID, it's liable to conflate your data with a competitor who has a similar name. Marketing directors often burn budget on backlinks to improve Domain Authority (a third-party metric) while neglecting Entity Authority (Google's native metric). The "About This Result" pane is the only window Google gives us into that native metric.
The Solution: The "Three Dots" Audit
You don't need expensive software. Perform a manual forensic audit of your SERP entry. Search Google for your brand name, click the three vertical dots (⋮) to the right of your homepage URL, and analyze the "Source" description at the top of the panel.
Scenario A (Pass): the panel displays a 2-3 sentence description of your company and explicitly says "Source: Wikipedia" or "Source: Knowledge Graph." Google has mapped your URL to a specific KGID (e.g. /m/045c7b). You're a trusted node. Scenario B (Fail): the panel shows only "First indexed by Google in 2015" or self-sourced text. Google is relying on your own meta description because it has no third-party verification of who you are. You're a "String," not an "Entity."
Technical Implementation: Forcing Reconciliation
If you failed the test, you need to manually connect your "web node" (URL) to your "graph node" (entity).
1. SameAs Schema Injection
Explicitly tell Google where your identity lives. In your Entity Home JSON-LD, use the sameAs array to link to your identity proofs.
2. The Wikidata Bridge
Google relies heavily on Wikidata (not just Wikipedia) to seed the Knowledge Graph. Create a Wikidata item for your organization, and ensure you add the "Official Website" property (P856) pointing to your domain. This creates a bidirectional edge that Google's Knowledge Vault crawler can traverse.
3. Wikipedia Citations (The "Citation" Strategy)
If you can't get a Wikipedia page yet, get cited on one. As covered in the guide on zero-click citations, becoming a reference source builds indirect graph equity that eventually leads to reconciliation.
Domain Authority vs. Entity Authority
Feature | Domain Authority (Moz/Ahrefs) | Entity Authority (Knowledge Graph) |
Source | Backlink profile | Reconciliation & mentions |
Google Impact | Rankings (traditional) | Rich snippets & AI citations |
Verification | Third-party tool estimate | "About This Result" panel |
Optimization | Link building | Schema & Wikidata |
Resilience | Fluctuates with algorithm | Stable (once established) |
Code Example: The Knowledge Graph Search
You can verify whether Google has an ID for you, even if it isn't showing it yet, using the Google Knowledge Graph Search API.
If this script returns an ID but the "About This Result" panel still shows generic text, you have a Confidence Score issue. Google knows you exist but doesn't trust the data enough to display it. You need more consistent sameAs links across the web.
Are you an Entity or just a String?
Free audit. Checks your Knowledge Graph reconciliation, sameAs consistency, and Wikidata bridge so AI engines trust who you are.
Check your entity status →Key Takeaways
- The "Three Dots" never lie. This is the quickest way to audit a client's true standing with Google. If the panel is generic, their SEO foundation is cracked.
- Wikidata is the key. You don't necessarily need a Wikipedia article (hard to get). You do need a Wikidata entry (easier) to generate a KGID.
- Consistency kills doubt. Ensure your Name, Address, and Phone are identical on LinkedIn, Crunchbase, and your footer. Discrepancies lower the Confidence Score.
- Secure your identity. If you don't define your entity, Google might auto-reconcile you to a company with a similar name. Use JSON-LD nesting to lock your product identities to your organization identity.
- Monitor changes. This panel changes dynamically. If you suddenly switch from "Source: Wikipedia" to "Source: YourSite," you may have lost entity trust due to a bad edit or contradictory data.
References & Further Reading
- Google Search Central: About This Result. Official documentation on how Google generates the source panel. https://blog.google/products/search/about-this-result-update/
- Wikidata: Introduction to Linked Data. How to contribute to the structured database that powers the Knowledge Graph. https://www.wikidata.org/wiki/Wikidata:Introduction
- Kalicube: The Brand SERP. Specialized resources on optimizing Knowledge Panels and Brand SERPs. https://kalicube.com/
