{"slug":"knowledge-panel-strategy","title":"Knowledge Panel Strategy Workflow","tags":["seo","entity-seo","knowledge-panel","wikidata"],"agent_summary":"Explains a structured workflow for acquiring and optimizing Knowledge Panels for brand entities.","trigger_phrases":["optimize knowledge panel","claim google knowledge panel","fix my knowledge panel","Wikidata entry setup","entity Google panel","schema sameAs for knowledge","knowledge disambiguation","entity resolution Google"],"runnable":true,"markdown":"### Knowledge Panel Acquisition Path:\n1. **Wikidata first** -- Create or complete a Wikidata entry (label, description, aliases in relevant languages). This is the single most influential editable knowledge base for triggering a Knowledge Panel.\n2. **Add key Wikidata statements:** `instance of` (P31), `official website` (P856), `social media` IDs, `inception` (P571), `founded by` (P112), `industry` (P452). Every statement needs a reference to an authoritative third-party source.\n3. **Claim Google panel** -- Search for the entity, click \"Claim this knowledge panel\", complete Google's verification. Bing panels are driven by Wikidata + LinkedIn -- update those sources directly.\n4. **Schema.org sameAs** -- Add `sameAs` links in Organization/Person schema pointing to Wikidata URL, Wikipedia article, LinkedIn, YouTube, and all verified profiles. `sameAs` is the single most powerful Schema.org property for entity resolution.\n\n### Common Knowledge Panel Fixes:\n| Issue | Root Cause | Fix |\n|-------|-----------|-----|\n| No panel appears | Entity not in Knowledge Graph | Build Wikidata entry + structured data + authoritative mentions |\n| Wrong image | Sourced from incorrect page | Update Wikidata image; set preferred image on About page and social profiles |\n| Wrong description | Pulled from wrong source | Edit Wikidata description; ensure About page first paragraph defines the entity clearly |\n| Wrong entity shown | Disambiguation failure | Strengthen unique signals, add Wikidata qualifiers, resolve disambiguation |\n\n### Entity Disambiguation Workflow:\n1. Search the entity name across Google, Wikidata, and AI platforms to identify conflicting entities\n2. Add disambiguation qualifiers to Wikidata (industry, location, founding date)\n3. Use identical entity name + description consistently across all 10+ platforms\n4. Build contextual co-occurrence signals -- content that explicitly connects the entity to its unique topic/industry associations\n5. Verify resolution quarterly by querying ChatGPT, Perplexity, and Google AI Overviews with \"What is [entity name]?\"\n\n### Wikipedia COI Rule:\nNever create or edit Wikipedia articles about your own entity. Build notability through independent reliable sources (press, industry publications, academic citations) and use the Requested Articles process if warranted.\n","html":"

Knowledge Panel Acquisition Path:

\n
    \n
  1. Wikidata first -- Create or complete a Wikidata entry (label, description, aliases in relevant languages). This is the single most influential editable knowledge base for triggering a Knowledge Panel.
    2. \n
  2. Add key Wikidata statements: instance of (P31), official website (P856), social media IDs, inception (P571), founded by (P112), industry (P452). Every statement needs a reference to an authoritative third-party source.
    3. \n
  3. Claim Google panel -- Search for the entity, click \"Claim this knowledge panel\", complete Google's verification. Bing panels are driven by Wikidata + LinkedIn -- update those sources directly.
    4. \n
  4. Schema.org sameAs -- Add sameAs links in Organization/Person schema pointing to Wikidata URL, Wikipedia article, LinkedIn, YouTube, and all verified profiles. sameAs is the single most powerful Schema.org property for entity resolution.
    5. \n
\n

Common Knowledge Panel Fixes:

\n

| Issue | Root Cause | Fix |\n|-------|-----------|-----|\n| No panel appears | Entity not in Knowledge Graph | Build Wikidata entry + structured data + authoritative mentions |\n| Wrong image | Sourced from incorrect page | Update Wikidata image; set preferred image on About page and social profiles |\n| Wrong description | Pulled from wrong source | Edit Wikidata description; ensure About page first paragraph defines the entity clearly |\n| Wrong entity shown | Disambiguation failure | Strengthen unique signals, add Wikidata qualifiers, resolve disambiguation |

\n

Entity Disambiguation Workflow:

\n
    \n
  1. Search the entity name across Google, Wikidata, and AI platforms to identify conflicting entities
    2. \n
  2. Add disambiguation qualifiers to Wikidata (industry, location, founding date)
    3. \n
  3. Use identical entity name + description consistently across all 10+ platforms
    4. \n
  4. Build contextual co-occurrence signals -- content that explicitly connects the entity to its unique topic/industry associations
    5. \n
  5. Verify resolution quarterly by querying ChatGPT, Perplexity, and Google AI Overviews with \"What is [entity name]?\"
    6. \n
\n

Wikipedia COI Rule:

\n

Never create or edit Wikipedia articles about your own entity. Build notability through independent reliable sources (press, industry publications, academic citations) and use the Requested Articles process if warranted.

\n"}