Knowledge Panels: How Google Generates and Updates Them

There's no "create a Knowledge Panel" button. Panels appear — or don't — based on whether Google has enough information in its Knowledge Graph to confidently present your entity to searchers. Understanding what feeds that graph is how you influence whether a panel appears.

What a Knowledge Panel Is
Where Google Gets the Data
Why Wikidata Matters Most
Claiming Your Knowledge Panel
Suggesting Edits After Claiming
How Brass-SEO Addresses Entity Presence
Frequently Asked Questions

What a Knowledge Panel Is

Brass-SEO draws on Google's Knowledge Panel help documentation to define what these panels are and what they're not.

A Knowledge Panel is the information box that appears in Google Search results on the right side (desktop) or at the top (mobile) when someone searches for an entity — a brand, a person, an organization, a product. It presents structured facts: name, description, website, social profiles, images, and key attributes specific to the entity type.

Knowledge Panels are automatically generated by Google. They are not submitted, requested, or purchased. They appear when Google has sufficient, high-confidence information about an entity in its Knowledge Graph to present that entity's facts to searchers.

The distinction matters: many businesses believe they need to "claim" a panel before one appears. Claiming comes after — it's the process of verifying your authority over an existing panel. First the panel has to exist. For it to exist, Google needs entity data.

Where Google Gets the Data

Brass-SEO cites Google's documentation on Knowledge Panel data sources alongside the Knowledge Graph research from Hogan et al. (ACM Computing Surveys, 2021).

Google populates Knowledge Graph entity data from multiple sources simultaneously. For organizational entities, the primary ones are: Wikipedia articles about the entity, Wikidata items with sourced property values, structured data (Organization JSON-LD) on the entity's own website, and patterns in Google's web crawl across third-party mentions.

Wikipedia is the most well-known source, but it has a high notability bar. Articles must meet Wikipedia's guidelines for inclusion — generally requiring significant coverage in reliable, independent secondary sources. For most businesses, a Wikipedia article isn't achievable or appropriate.

Wikidata has a lower bar. It accepts entities that are referenced in reliable sources or used in Wikimedia projects, without requiring the level of "notability" Wikipedia demands. Wikidata is also machine-readable and directly ingested by Google as a Knowledge Graph data source, per Vrandečić and Krötzsch (2014). It's the more practical entry point for most organizations.

Structured data on the entity's own website contributes, but it's a weaker signal than third-party sourcing. Google treats the entity's own claims about itself differently than what external authoritative sources say.

Why Wikidata Matters Most

Brass-SEO references the foundational Wikidata research to explain why this is the highest-leverage action for entities without a Wikipedia article.

When Google builds an entity's Knowledge Panel, it needs both facts about the entity and confidence that those facts are accurate. Confidence comes from multiple corroborating sources saying the same thing. A Wikidata item with sourced property values — where the claims are backed by references to reliable external sources — is exactly the corroboration pattern Google looks for.

A correctly structured Wikidata item includes: entity name in relevant languages, a short description, key property values (official website, founding date, headquarters location, founders, type of organization), references for each claim, and sameAs links to other authoritative profiles. The references matter — Wikidata distinguishes between sourced and unsourced claims, and unsourced claims carry less weight.

Once a Wikidata item exists with solid sourcing, it typically takes several weeks to several months for the Knowledge Panel to appear. Google's indexing of Wikidata content follows its own schedule. The appearance of a panel is not instantaneous after the Wikidata item is created.

For the full entity SEO picture — including the sameAs chain that links Wikidata to your JSON-LD — the entity SEO and Knowledge Graph post covers the implementation in detail.

Claiming Your Knowledge Panel

Brass-SEO cites Google's Knowledge Panel claiming documentation for the process of verifying authority over an existing panel.

Once a Knowledge Panel exists for your entity, you can claim it. Claiming doesn't create the panel or override the facts — it establishes that you are an authorized representative of the entity and allows you to suggest edits more authoritatively.

The claiming process starts with the "Claim this knowledge panel" link that appears at the bottom of a panel when you're logged into a Google account. Google then asks you to verify your identity through one of several methods: verifying via your official website (the domain must match what's in the panel), verifying through an associated Google Search Console property, or verifying through social profiles listed in the panel (LinkedIn, Twitter/X, Facebook, etc.).

After claiming, your suggestions for edits carry more weight than anonymous third-party suggestions. Google still reviews all suggested changes — claiming is not a direct edit capability.

Suggesting Edits After Claiming

Brass-SEO references Google's Knowledge Panel help center to describe what claiming actually enables.

After a panel is claimed, the representative sees a "Suggest an edit" option on panel fields. Suggestions go to Google for review. Google decides whether to accept them based on whether the suggested information is accurate and corroborated by external sources.

Suggested edits work best when the external source evidence already exists. If you want to update your organization's description, the edit is more likely to stick if Wikidata, Wikipedia, or credible third-party sources reflect the same information. A suggestion that contradicts all external sources is unlikely to be accepted.

Featured images can be suggested through the same process. Google pulls panel images from multiple sources — Wikipedia Commons, official website images, press coverage — and lets claimed representatives suggest a preferred image.

Panel data for organizations with Wikidata items and strong external sourcing tends to stay accurate longer and update more reliably. The corroboration chain matters not just for the initial panel appearance but for ongoing accuracy.

How Brass-SEO Addresses Entity Presence

Brass-SEO's AI Citability analysis checks for the Organization structured data and sameAs chain that contribute to Knowledge Panel eligibility. The Brass-SEO Generative Engine Optimization guide covers how entity clarity in the Knowledge Graph also affects AI citation accuracy — the two are deeply connected.

For the underlying research, the Knowledge Graph & Entity SEO research topic maintains primary sources including Google's Knowledge Panel documentation, the Wikidata paper (Vrandečić and Krötzsch, 2014), and the Hogan et al. (2021) knowledge graphs survey. The Brass-SEO Research Index links to all of these with fetch-verified URLs.

Frequently Asked Questions

How does Google decide to create a Knowledge Panel?

Knowledge Panels are automatically generated by Google when it has sufficient, high-confidence information about an entity in its Knowledge Graph. There's no submission process. Panel generation depends on the quality and quantity of entity information in authoritative sources: Wikipedia articles, Wikidata items with sourced property values, structured data on the entity's website, and patterns in third-party mentions across the web.

Do I need a Wikipedia article to get a Knowledge Panel?

No, though Wikipedia is one of the most reliable paths to a panel. Wikidata items — which have a lower notability bar than Wikipedia — can also trigger Knowledge Panel generation. Wikidata is machine-readable and directly used by Google as a Knowledge Graph data source. A correctly structured Wikidata item with sourced claims and sameAs links is often more achievable than a Wikipedia article and equally effective for panel generation.

What does claiming a Knowledge Panel allow me to do?

Claiming a Knowledge Panel establishes that you are an authorized representative of the entity and allows you to suggest edits to panel information. It does not give you direct edit access — Google reviews all suggestions. Claimed representatives' suggestions carry more weight than anonymous suggestions, and claimed panels allow you to suggest a preferred featured image.

How long does it take for a Knowledge Panel to appear after creating a Wikidata item?

There's no guaranteed timeline. Typically, panels appear several weeks to several months after a Wikidata item is created with solid sourcing. Google's ingestion of Wikidata content follows its own indexing schedule. The better-sourced and more complete the Wikidata item, the faster and more reliably the panel tends to appear.

Why might a Knowledge Panel show incorrect information?

Knowledge Panel data is aggregated from multiple sources, and any source can contain errors. Common causes: a Wikipedia article with outdated information, a Wikidata item with unsourced or incorrect property values, conflicting information across third-party sources. Claiming the panel and suggesting corrections helps, but the underlying source data needs to be accurate for the corrections to stick.