Knowledge Panel

The Knowledge Panel is the boxed information card that Google surfaces on the right side of the SERP (or at the top on mobile) when a search query resolves to a specific entity — usually a business, but also a person, place, product, or organization. The card aggregates data from multiple sources: the entity’s Google Business Profile, Wikipedia, the Google Knowledge Graph, and structured data on the business’s own website.

For a local business, the Knowledge Panel typically shows the name, primary category, address, phone, hours, star rating with review count, a hero photo, the business website, and direct action buttons (directions, call, save). It is the most visually dominant single block Google can hand a brand — when it shows, your branding occupies the entire right rail of the SERP.

Knowledge Panels appear when the query is specific enough to resolve to a single entity. The clearest trigger is an exact business name (“Thomas W. Loeb, MD”, “Acme Plumbing San Francisco”) — Google’s entity-resolution layer matches the query to a Knowledge Graph node and short-circuits the usual Local Pack + organic combo for a panel-anchored view.

Broader category-shaped queries (“plumber near me”, “best dentist”) almost never trigger a panel — Google returns the Local Pack instead, because there’s no single entity to feature. The line between “branded” and “generic” queries is exactly where this flip happens.

Our geo-grid pipeline detects Knowledge Panel ownership on every cell scan. The detector in backend/app/core/etl/audit/knowledge_panel.py (P-13) handles both maps-provider response shapes — hasdata returns a top-level placeResults dict, DataForSEO returns a knowledge_graph block — and pulls the panel’s place_id out of either shape.

If that place_id matches your linked Google Business Profile, the cell is flagged as “panel owned” and gets a crown overlay on the heatmap, distinct from the normal rank color band. That distinction matters: ranking #1 in the Local Pack and owning the entire Knowledge Panel are different outcomes for the searcher, and the heatmap shouldn’t collapse them into one number.

Knowledge Panels and Local Packs are mostly mutually exclusive at the per-query level. For branded-entity queries, Google returns a panel and often suppresses the Pack — the searcher already resolved to your business, so the comparative listing block isn’t useful. For category queries, Google returns the Pack and no panel.

Across a service area, both surfaces matter. A geo-grid scan of a category query measures Pack rank per cell; a geo-grid scan of a branded query measures panel ownership per cell. The two scans answer different questions: “where do I rank when searchers ask for what I sell?” vs. “where am I the default answer when searchers ask for me by name?” Both feed the same heatmap UI; only the metric on the cell changes.

The panel is curated by Google, not the business owner, but the inputs are mostly knowable. The Google Business Profile is the dominant source for local-business panels — name, category, hours, address, phone, hero photo, star rating, and the linked website all flow directly from GBP into the card. Curated facts (founding date, executives, social profiles, brand description) can flow from Wikipedia, the business website’s structured data (Organization / LocalBusiness schema), and Knowledge Graph entries Google maintains for larger entities.

Owners can suggest edits to the panel directly from search (“Suggest an edit” link in the card) and via the Google Business Profile dashboard for the GBP-derived fields. Wikipedia-sourced content has to be corrected at the Wikipedia article level; Knowledge Graph claims are corrected via Google’s feedback form. None of this guarantees a change — Google decides what to surface — but consistent NAP across GBP, the business website, and citation directories is the single biggest lever a business owner controls.