Knowledge panel

A knowledge panel is the information box Google shows beside or above search results for an entity it already holds in its Knowledge Graph. Google's own definition: "Knowledge panels are information boxes that appear on Google when you search for entities (people, places, organizations, things) that are in the Knowledge Graph."

The important word is automatically. Google states plainly that panels "are automatically generated, and are updated automatically as information changes on the web." A panel is not a profile you fill in. It is a read-out of what Google's systems have concluded about an entity from many sources at once, rendered as a box.

Where the content comes from

Google says the information "comes from various sources across the web," naming three kinds: data partners, open web sources, and verified entities who have suggested edits to facts on their own panels.

That ordering matters more than it looks. Two of the three inputs are third parties. Only the last is you, and it arrives late — after a panel exists, and as a suggestion rather than an edit. The panel is downstream of the graph, and the graph is downstream of a corroborated web. Google has published that the Knowledge Graph "has amassed over 500 billion facts about five billion entities," which is the scale at which a single self-description carries very little weight against everything else that mentions you.

Claiming versus creating

These are different operations and conflating them wastes months.

Creating is not an available action. There is no form, no submission, no paid route. An entity gets into the Knowledge Graph because enough independent sources describe it consistently enough for Google's systems to resolve it as a distinct thing.

Claiming is available once a panel exists. Google's support documentation: "If you are the subject of or official representative of an entity depicted in a knowledge panel, you can claim this panel and suggest changes." Claiming gets you a verified channel for corrections. It does not get you editorial control, and a suggested change is still adjudicated against the rest of the web.

So the work that produces a panel is not panel work at all. It is entity work: a stable canonical name, one canonical home page, structured data that declares what the entity is and what it is the same as, and consistent descriptions in the places that describe organizations. Contradictory descriptions across your own properties are the common self-inflicted failure — a system reconciling five different self-descriptions may resolve none of them.

Why it matters to anyone trying to be cited by an agent

A knowledge panel is a Google Search feature. An AI assistant answering a question is not reading your panel; it is retrieving documents. Treating the panel as the goal is a category error.

Treating it as an indicator is correct. A panel is public evidence that a large entity-resolution system has successfully mapped a name to a specific thing, with a set of attributes it is confident enough to display. Retrieval systems face the same disambiguation problem. When a model is asked about a company whose name is also a common word, a place, and two other companies, the same signals that let Google resolve the entity — consistent naming, corroboration across independent sources, machine-readable identity claims — are what let a retrieval step return your documents rather than someone else's.

The panel is a symptom of entity clarity. Entity clarity is the thing worth having.

Failure modes

• Chasing the box. Optimising for a panel directly is optimising for an output you cannot write. The input is corroborated entity data; the panel either follows or does not.
• Believing a vendor who sells one. Google documents no paid or submitted path to a panel. An offer to create one is selling either entity cleanup work under a false name, or nothing.
• Assuming a claim is an edit. Verification opens a suggestion channel. Facts still have to be supported elsewhere, and a suggestion contradicted by the open web tends not to stick.
• Inconsistent self-description. Different legal names, founding dates or category labels across your site, your social profiles and your press page give a reconciler no consensus to find.
• Reading a panel error as a Google bug. A wrong fact in a panel is usually a correctly ingested wrong fact from a source. Fixing it means fixing the source, not appealing the panel.
• Confusing the panel with a citation. Appearing in a panel is not the same as being the cited source of an answer, and neither guarantees the other.