The "Three Dots" Audit: Why Google Doesn't Trust Your Brand

Validating Your Knowledge Graph: The Google "About This Result" Test

Definition

The "About This Result" Test is a diagnostic protocol for verifying if a brand has been successfully reconciled as an Entity in Google's Knowledge Graph. By accessing the "Three Dots" menu on a SERP result, SEOs can inspect the "Source" panel. If this panel displays a description sourced from Wikipedia or the Knowledge Graph, the entity is Reconciled (Trusted). If it displays a generic "First indexed..." date or self-sourced text, the entity is Unreconciled (Guest), indicating a lack of "Knowledge Graph ID" (KGID) association.

The Problem: The "Guest vs. Host" Dilemma

In the Semantic Web, there are two types of websites:

1. Hosts (Entities): Google knows who they are. It trusts their identity essentially because they exist in the Knowledge Graph (KG).
2. Guests (Strings): Google only knows what they say. It indexes their keywords but does not recognize their brand authority.

The Invisible Penalty:

You might rank #1 for a long-tail keyword today, but without Entity Recognition, you are vulnerable.

• AI Overview Exclusion: Google's Gemini and SGE (Search Generative Experience) preferentially cite "Entities" over "Strings" because Entities have verified trust signals.
• Hallucination Risk: If Google doesn't lock your brand to a specific Knowledge Graph ID, it is liable to conflate your data with a competitor who has a similar name.

The Consequence:

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 this native metric.

The Solution: The "Three Dots" Audit

To check your status, you do not need expensive software. You need to perform a manual forensic audit of your SERP entry.

The Protocol

1. Search: Go to Google and search for your Brand Name.
2. Click: Locate your homepage result and click the Three Vertical Dots (⋮) to the right of the URL.
3. Analyze: Look at the "Source" description at the top of the panel.

Scenario A: The Verified Entity (Pass)

• Visual: The panel displays a 2-3 sentence description of your company.
• Attribution: It explicitly says "Source: Wikipedia" or "Source: Knowledge Graph."
• Meaning: Google has mapped your URL to a specific KGID (e.g., /m/045c7b). You are a trusted node in the graph.

Scenario B: The Unreconciled Site (Fail)

• Visual: The panel displays "Source: [[suspicious link removed]]" or just "First indexed by Google in 2015."
• Meaning: Google is relying on your own meta description because it has no third-party verification of who you are. You are a "String," not an "Entity."

Technical Implementation: Forcing Reconciliation

If you failed the test (Scenario B), you need to manually force Google to connect your "Web Node" (URL) to your "Graph Node" (Entity).

1. SameAs Schema Injection

You must explicitly tell Google where your identity lives. In your Entity Home (About Page) JSON-LD, use the sameAs array to link to your "Identity Proofs."

JSON

<script type="application/ld+json">

{

  "@context": "https://schema.org",

  "@type": "Organization",

  "name": "Website AI Score",

  "url": "https://websiteaiscore.com",

  "sameAs": [

    "https://www.wikidata.org/wiki/Q123456",

    "https://en.wikipedia.org/wiki/Website_AI_Score",

    "https://www.linkedin.com/company/websiteaiscore",

    "https://crunchbase.com/organization/websiteaiscore"

  ]

}

</script>

2. The Wikidata Bridge

Google relies heavily on Wikidata (not just Wikipedia) to seed the Knowledge Graph.

• Action: Create a Wikidata item for your organization.
• Property: 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 cannot get a Wikipedia page yet, get cited on one. As we discussed in our guide on Zero-Click Citations, becoming a reference source builds indirect graph equity that eventually leads to reconciliation.

Comparison: Domain Authority vs. Entity Authority

Code Example: The "Knowledge Graph" Search

You can verify if Google has an ID for you, even if it isn't showing it yet, by using the Google Knowledge Graph Search API.

Python Script for Entity Lookup:

Python

import requests

import json

def check_entity_status(query, api_key):

    url = f"https://kgsearch.googleapis.com/v1/entities:search?query={query}&key={api_key}&limit=1&indent=True"

    response = requests.get(url)

    data = response.json()

    if 'itemListElement' in data and len(data['itemListElement']) > 0:

        result = data['itemListElement'][0]['result']

        print(f"✅ Entity Found: {result['name']}")

        print(f"   KGID: {result['@id']}")

        print(f"   Description: {result.get('description', 'N/A')}")

        print(f"   Score: {data['itemListElement'][0]['resultScore']}")

    else:

        print(f"❌ Entity Not Found. You are likely an 'Unreconciled String'.")

# Replace with your actual Google Cloud API Key

# check_entity_status("Website AI Score", "YOUR_API_KEY")

Developer Note:

If this script returns an ID (e.g., kg:/g/11h5...) 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.

Key Takeaways

1. 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.
2. Wikidata is the Key: You do not necessarily need a Wikipedia article (which is hard to get). You do need a Wikidata entry (which is easier) to generate a KGID.
3. Consistency Kills Doubt: Ensure your Name, Address, and Phone (NAP) are identical on LinkedIn, Crunchbase, and your Footer. Discrepancies lower the Confidence Score.
4. 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.
5. 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

1. Google Search Central: About This Result. Official documentation on how Google generates the source panel.
   • Link: https://blog.google/products/search/about-this-result-update/
2. Wikidata: Introduction to Linked Data. How to contribute to the structured database that powers the Knowledge Graph.
   • Link: https://www.wikidata.org/wiki/Wikidata:Introduction
3. Kalicube: The Brand SERP. Specialized resources on optimizing Knowledge Panels and Brand SERPs.
   • Link: https://kalicube.com/