Editing a Knowledge Panel: Verification & Suggest an Edit

Step 1: claim the panel

Search for your name while signed in. If the panel appears, you'll find a verification prompt underneath it. Google then guides you through an identity check, usually via an official profile you can demonstrably control - such as a verified social media account, a YouTube channel, or Search Console for your own domain.

Once verification succeeds, you become the "verified representative" of the entity. This is not ownership of the panel, but a privileged channel for suggesting changes.

What can be influenced after claiming

• The main image: Google considers suggestions but still chooses which image is shown itself
• Obvious factual errors: wrong founding year, wrong role title, wrong organization assignment
• Linked profiles: missing or incorrect social links, provided the assignment can be substantiated
• The official website, if it's missing or points to an outdated domain

What cannot be edited directly

• The description text: it usually comes from a source such as Wikipedia and can't be freely rewritten
• The selection of facts and modules shown - Google decides what's relevant
• Related searches and "People also search for"
• Third-party ratings and content displayed within the panel
• The existence of the panel itself: claiming it offers no protection against it disappearing again

The Suggest an Edit workflow

Suggested changes only work with evidence. A suggestion without a source is effectively ignored, because Google has no way to confirm it. So this approach makes sense:

• First correct the source the error comes from (Wikidata, a press article, a database, your own website)
• Give the correction time: Google has to re-crawl and re-evaluate the changed source
• Only then submit the change suggestion in the panel, referencing the now-correct source
• Document the date and wording of the suggestion, so you can later tell whether it worked or not
• Observe rather than resubmit: submitting the same identical suggestion multiple times doesn't speed anything up

Typical reasons for rejection

Suggestions rarely fail arbitrarily. The most common patterns are recognizable:

• The evidence is your own website, while the contradicting source is independent - Google follows the independent source
• The change is a matter of opinion ("top expert in...") rather than a verifiable fact
• The source is a press release without editorial processing
• Multiple contradictory data records exist, such as two Wikidata items for the same person
• The suggestion concerns a module that Google doesn't individually control at all

When the correction has to happen at the source

In most cases, the cause of an incorrect panel isn't the panel itself, but one level deeper. A wrong founding year in Wikidata, an outdated role title in a frequently cited article, an old domain in the sameAs graph: as long as the source says the opposite, the panel will keep reproducing the error.

In practice, that means correcting the Wikidata statement with a solid reference, aligning the Entity Home and the JSON-LD, requesting a correction from the outlet if necessary - and then waiting. Changes to sources typically take several weeks before they become visible in the panel.

Why panels change

A panel is not a static data record. If a source goes offline, an article is deleted, or a Wikidata item is changed, the underlying facts shift - and the panel can lose modules, change content, or disappear altogether.

That's why maintenance isn't an upsell, it's part of the deal. Our monitoring watches for exactly these changes. If a panel has already disappeared, it's worth reading Panel disappeared: what cheap panels cause.