How to update a knowledge panel so the change sticks.

Google is reporting, not deciding

A knowledge panel is an assembled summary. Google reads your official site and its structured data, open databases such as Wikidata and Wikipedia where an entry exists, licensed data feeds, and the general web, then publishes what those sources agree on. When the panel says something odd, a source somewhere is saying it, and that is good news: sources can be edited.

This also explains the most common frustration, where a correction appears for a while and then reverts. The usual cause is simple arithmetic. You updated one page; eleven other pages still carry the old detail. Google went with the majority.

Start by finding where it came from

Before touching anything, work out which source feeds the detail you want changed. A few minutes of searching usually settles it:

• Search the exact wrong value in quotes alongside the entity name. A line like "Managing Director" "Your Company" will surface the pages repeating it.
• Check Wikidata for the entity. Many panel fields map neatly onto Wikidata properties, and the entry is often older than anybody at the company realises.
• Read your own site as a stranger would, including the footer, the author boxes, old press releases and the PDF brochure nobody has opened since 2021.
• Look at the obvious directories and profile sites for your sector, plus LinkedIn, Crunchbase and your industry association listings.

What you end up with is a short list of pages that need the same edit. That list is the actual task.

Fix your own property first

Your website is the source Google treats as closest to the entity, so it goes first and it has to be unambiguous. Put the correct detail in the visible copy, on the page where someone would expect to find it, and mirror it in your structured data. For an organisation that means Organization markup carrying the legal name, logo, founding date, address and the sameAs links to your official profiles. For a person it means Person markup with the current jobTitle, the employing organisation and the same sameAs set.

Two details make a real difference here. Keep the name string identical everywhere, down to the punctuation, because Spire Media FZ-LLC and Spire Media can read as two entities if nothing links them. And date your updates visibly: a page that shows when it changed gives Google a reason to prefer it over an undated page from 2019.

Then update the chorus

Now work through the list you built. Profiles, directories, speaker bios, podcast show notes, conference listings, your co-founders' LinkedIn entries, the About section on every satellite site you own. It is unglamorous work, and it is the part that decides whether the change holds.

Where the detail appears in independent coverage, new coverage is the fix rather than a request to the publisher. One recent article that states the current role or the current headquarters does more for the panel than an email asking a journalist to amend a piece from three years ago. That is one of the quieter arguments for an active PR programme: it keeps a supply of fresh, dated, third-party statements of fact about your entity in circulation.

Only then tell Google

With the sources aligned, raise the correction. Anyone signed in can use the feedback option on a panel to flag something inaccurate. If you have verified yourself as the entity's representative, you get a more direct suggestion route from inside Search, which is one of the reasons claiming the panel is worth doing before you need it.

Keep the suggestion plain and verifiable. Name the field, give the correct value, and point at the public page that confirms it. You are not arguing a case so much as showing Google where to look. Timing varies, so check back rather than resubmitting daily; panels refresh as Google recrawls the sources you changed.

What good maintenance looks like

Teams that keep their panels accurate tend to do the same handful of things. They search their own brand and their executives' names once a quarter and read the panel properly. They treat any rebrand, relocation, funding round or leadership change as a documentation job with a checklist, not just an announcement. They keep structured data in the deployment, so it updates when the site does. And they keep one person responsible for it, which is usually what separates a panel that ages well from one that quietly drifts.

The payoff grows as search changes. AI Overviews and assistant answers lean on the same entity data, so a panel that reflects reality is increasingly what gets repeated back to anyone who asks about you. Our guide on getting cited by AI answers picks up that thread.