# How to get a knowledge panel on Google

How to get a knowledge panel: what Google says it controls, what you can influence, how to claim and edit one, and the limits no one can promise past.

---


You cannot apply for a Google knowledge panel. Google's [help pages on knowledge panels](https://support.google.com/knowledgepanel/answer/9163198) describe panels as generated automatically from information across the web, so how to get a knowledge panel comes down to making your name easy to identify and easy to corroborate, then claiming the panel if one appears.

That sounds like a disappointing answer, and it is the honest one. A knowledge panel is the information box that appears beside or above the results when someone searches for a person, company or other entity. It is one of the most visible things search shows about a name, which is why so many pages promise a method. Most of those pages blur two different things: what Google has said in its own documentation, and what practitioners believe works. This guide keeps them apart.

You will find here what Google says a panel is, what you can and cannot change, how claiming works, what Wikipedia and Wikidata do and do not do, and a realistic order of work for someone starting from nothing. No one can promise that a panel will appear for a given person or brand, and neither will this page.

<div class="box"><b>The short version</b>
<ul><li>Google describes no way to request a new knowledge panel. Its automated systems decide when a panel appears or disappears, and the help pages cover claiming and editing existing panels only.</li><li>What you control is the evidence: one clear page that states who you are, consistent profiles, and independent coverage that confirms the same facts.</li><li>Once a panel exists, you can claim it by verifying through a site or profile Google lists, then suggest edits with priority. Some fields cannot be edited at all.</li><li>Wikipedia and Wikidata are separate projects with their own rules. Writing about yourself on Wikipedia is strongly discouraged, and the Google help pages I read mention neither as a requirement or a source.</li><li>Treat a panel as a result of a well-documented identity, never as a deliverable you can buy.</li></ul></div>

Three facts from Google's own pages frame everything that follows.

<figure class="keyfacts">
<div class="keyfacts-grid">
<div><b>None</b><span>application routes for a new panel described in Google's help pages</span></div>
<div><b>A few days</b><span>Google's stated review time for feedback from verified users</span></div>
<div><b>3 business days</b><span>the window an existing owner has to respond in an ownership dispute</span></div>
</div>
<p class="fig-src">From Google's knowledge panel help pages for claiming, updating and understanding panels, read in preparing this article. Policies change, so check the pages before you act.</p>
</figure>

## What a knowledge panel is and who decides when one appears

A knowledge panel is an information box that Google shows when a search is about an entity, and Google's own systems decide when it appears. Google describes panels as boxes that give a quick overview of a topic, built from what it understands about that topic from content across the web.

The word entity matters. Google treats a person, a company, a film, a place or a concept as a distinct thing, not as a string of words. A panel is how that thing is presented. Behind it sits a store of facts about entities, which practitioners call the knowledge graph. A panel is only the visible part: the graph holds data, the panel displays a selection of it.

Google's pages say that the information in a panel is generated automatically from public information on the web. For some subjects, such as film or music, Google may also use data from authoritative partners. Some facts can come from verified subjects who suggested edits to their own panel, and some images come from featured images chosen by people who claimed a panel.

The same pages say something that changes how you plan. Google's page on [updating a panel](https://support.google.com/knowledgepanel/answer/7534842) states that its current policy is not to manually create or delete panels, and that its automated systems determine when they appear and disappear, and the page does not describe a way to ask for one to be added. Two consequences follow. Nothing in the documentation lets you request a panel by contacting staff. Equally, a panel you dislike will not be removed because you ask, which matters for the correction work later in this guide.

### Panels are not Business Profiles

Searches for a local business often show a box that looks similar. That box is a Business Profile, which is specific to businesses that serve customers at a location or in a service area. Google's pages direct those businesses to claim or create a Business Profile instead. If you run a shop, a clinic or a restaurant and want the box that shows your hours and reviews, that is a different process from the one described here. A person, a brand, a firm without a storefront, an artist or an organization is the case a knowledge panel covers.

### Why the same name can get a panel and you do not

In practice, a name clearly tied to one set of facts is easier for a system to represent than a name shared by many people with little distinguishing information. That is reasoning, not a rule Google publishes. A person with a common name may find that a panel, if any, shows someone else. Fixing that is a problem of identity clarity, covered below, not of claiming.

## Why you cannot apply for a panel, and what you can influence

Google's help pages explain how to claim an existing panel, how to suggest edits and how to give feedback. The pages I read describe no form, fee or request route for creating a new one. Any service that claims to submit you for a panel is selling something Google does not describe as available.

That does not leave you with nothing to do. The decision is automated and the inputs are public, so the inputs are the part you can work on. A system that builds an entity from the web needs three things to go well:

- **Identification.** It must be able to tell who or what you are, and separate you from namesakes.
- **Facts.** It must find stable, specific facts: role, organization, location, links to official profiles.
- **Corroboration.** It must find the same facts repeated by sources that are not you.

None of these guarantees a panel. Google's own structured data documentation for organizations says plainly that features which use structured data are not guaranteed to appear in results. The honest framing is that you can raise the odds that your name is understood correctly, and you cannot set the outcome.

<aside class="callout">
<span class="callout-label">Rule</span>
<h4>Be wary of any promise that a panel will appear</h4>
<p>Google's documentation describes no request route for a new panel. A provider who sells a panel as a fixed deliverable, with a date, is describing something outside their control. Judge providers on the evidence work they do, which you can see and keep, not on the promised result.</p>
</aside>

## The signals that tend to matter, and how sure we can be of each

Google does not publish a checklist of what earns a panel, so any list is a mix of documented points and practitioner judgment. The two are kept apart below, because mixing them is how bad advice spreads.

### Documented by Google

- Panels are generated automatically from public information across the web.
- Descriptions come from various data sources and cannot be edited directly, and Google's page tells you to contact the source of a description you want changed.
- Google checks suggested edits against other public information on the web, which is why a correction needs supporting URLs.

### Practice, not documented

These are the working assumptions most specialists share. They are reasoning, not rules Google has published.

- **One authoritative page about you that you control.** Often called an entity home: an about or profile page on your own domain that states your name, role, organization and links to your official profiles in plain language. It gives a system one place to resolve who you are.
- **Consistent facts across profiles.** The same name form, role, organization and photo across the profiles you own, so nothing contradicts the entity home.
- **Independent coverage.** Interviews, articles, conference listings, awards pages and directories written or maintained by others that confirm the same facts.
- **Machine-readable markup.** Schema.org Person or Organization markup on your own page, including links to your official profiles. Google's structured data documentation that I read covers Organization markup, not Person. It helps a system read the page. It does not create a panel.
- **Time.** Systems revisit pages on their own schedule. A change in one week rarely shows in the next.

The point of separating these is practical. If your entity home is missing, no amount of outside coverage will tell a system which of fifty namesakes you are. If outside coverage is missing, the entity home alone is a claim about you, written by you.

## Which route fits your situation: a decision table

The right starting point depends on what already exists about you. The table compares the main routes on the same criteria. Cost level is relative: low means mostly your own time.

<div class="tablewrap"><table><thead><tr><th>Route</th><th>What it does</th><th>Speed</th><th>Risk</th></tr></thead><tbody>
<tr><td><strong>Entity home plus consistent profiles</strong></td><td>Gives systems one clear source for who you are</td><td>Weeks to build, longer to be reflected</td><td>Low</td></tr>
<tr><td><strong>Independent coverage</strong></td><td>Corroborates your facts with sources that are not you</td><td>Months, depends on what you earn</td><td>Low if real, high if bought</td></tr>
<tr><td><strong>Structured data on your page</strong></td><td>Labels the facts on the entity home for machines</td><td>Days to add, no fixed effect</td><td>Low</td></tr>
<tr><td><strong>Wikidata item</strong></td><td>Adds a structured, open record that others can edit</td><td>Quick to create, may be challenged</td><td>Medium</td></tr>
<tr><td><strong>Wikipedia article</strong></td><td>Only if independent coverage already supports it</td><td>Not in your control</td><td>High if you write it yourself</td></tr>
<tr><td><strong>Claim an existing panel</strong></td><td>Lets you suggest edits with priority and add users</td><td>Google reviews verified feedback in a few days</td><td>Low</td></tr>
<tr><td><strong>Paying for a panel</strong></td><td>Nothing Google describes as available</td><td>Not applicable</td><td>High</td></tr>
</tbody></table></div>

Read the table by sequence, not by row. The first three rows come before the others because they are the evidence on which every later route stands. The last row is there so you can recognize the offer when it arrives.

## The role of Wikipedia and Wikidata, and where each one stops

Wikipedia is not an application route to a panel, and Google's help pages I read do not mention it. Many guides treat a Wikipedia article as the key. The documented position is narrower: Google says panel details come from various sources across the web, and Wikipedia is one of many places an entity may be described. Whether a panel draws on it for a given person is not something Google states.

This matters because Wikipedia has strict rules about who writes what, and ignoring them damages a name faster than having no article.

### What Wikipedia asks of people who write about themselves

Wikipedia's [conflict of interest guideline](https://en.wikipedia.org/wiki/Wikipedia:Conflict_of_interest) says you should not create or edit articles about yourself, your family or friends. It does allow fixing defamation or a serious error quickly, then following up through the volunteer response team or the living persons noticeboard. It also says that once an article exists you have no right to control its content or to delete it outside the normal channels.

Paid editing is covered separately. The guideline very strongly discourages paid advocates from editing articles directly, and tells them to propose changes on the article's talk page. Under Wikimedia's terms of use, anyone paid for a contribution must disclose their employer, client and affiliation.

For a founder or executive, that means three things. Do not write your own article. Do not hire someone to do it quietly. If an article already exists and contains an error, the route is a disclosed request on its talk page, with a reliable source attached.

### Notability: why many people will not have an article

Wikipedia's [notability guideline for people](https://en.wikipedia.org/wiki/Wikipedia:Notability_(people)) is the second barrier. It states that trivial coverage of a subject by secondary sources is not usually sufficient to establish notability, that autobiography and self-promotion are not the routes to having an encyclopedia article, and that primary sources do not contribute toward proving notability. It also says that "notable" is not a synonym for "famous". I could not read the general notability guideline itself in preparing this guide, so read it before drafting anything.

Practically, your own website and profiles are primary sources, and the guideline says primary sources do not contribute toward proving notability, while trivial coverage is not usually enough. Without substantial coverage by others, a draft is unlikely to succeed. This is also why an article about you is a consequence of a public record, not a lever for building one.

### What Wikidata is, and what it is not

Wikidata describes itself as a free and open knowledge base that humans and machines can read and edit, and its main page says anyone can edit it. According to Wikipedia's article on the project, its data is released under a public domain dedication, organized as items with identifiers and statements, and Google announced in 2014 that it would shut down Freebase in favor of Wikidata.

What that does not tell you is whether a Wikidata item feeds a panel for a particular person. Google's help pages do not say so, and I could not read Wikidata's own notability page in preparing this article, so the inclusion rules should be read before you create anything. Three cautions apply. An item about you is open to editing by others. An item with no reliable references can be challenged. And an item you create does not oblige any system to use it.

Where an item for a person already exists, it is worth checking that its statements are accurate and carry references. Where it does not, creating one is a lighter step than a Wikipedia article, but it should rest on the same independent sources.

## Building the entity home and the profiles that point to it

The most controllable piece of the work is one page on your own domain that says who you are. Everything else is judged against it, so it needs to be specific and boring. The aim is clarity for a reader and for a system, not persuasion.

A workable entity home contains:

- Your full name as you use it professionally, once, as the page heading, and the same form everywhere else.
- A first sentence that states what you do and for whom, in plain words, with your current role and organization.
- Verifiable facts: where you are based, what you have published or built, and links to the sources that confirm them.
- Links to the official profiles you control, using the same name form, so each profile can be traced back to the page.
- A photo and a short bio that match your other profiles.

Then add markup that states the same facts for machines. A Person or Organization record in JSON-LD on the page, with the name, role, URL and a list of official profile links, is the common practice. For organizations, Google's structured data documentation defines the sameAs property as the URL of a page on another website with additional information about your organization. The same idea carries over to a person's page. It tells systems which other pages are you, which is the problem with common names.

Our [personal brand](/personal-brand) work builds this owned page one for people who need a stable source of truth about their name. It is the right first step whether or not a panel follows, since search engines and AI assistants read it too.

### Make the profiles agree

Each profile you control should state the same name form, role and organization as the entity home and link back to it. Contradictions are where identity breaks: an old job title on one profile, a different spelling on another, a company page that still lists a former founder. A system resolving an entity reads all of them. Audit them before you add new ones.

### Scenario: a founder with press but no owned page

This is an illustration, not a real case. Assume a founder named in several trade articles and a handful of conference listings, with a social profile and nothing on their own domain. Search shows scattered results and a namesake's profile ranking above theirs.

In that situation the missing piece is the entity home, not more coverage. The order of work is: publish the page; align the social profile to it; add the markup; ask the publications that already mention the founder only for corrections where something is wrong, and for a link to the page where the publication would normally add one. Nothing in this sequence promises a panel. It removes the ambiguity that makes one less likely, and it improves the results people see in the meantime.

## Independent coverage: what corroboration looks like and what to avoid

Corroboration means other sources saying the same things about you, in their own words. The useful kinds are ordinary: a conference page that lists your talk, an interview in a trade publication, a company page that names you as a director, a directory run by a professional body, an awards page, a podcast episode page with your name and role.

Three rules keep this work honest and durable.

- **Earn it.** Real coverage comes from doing things worth covering and from being available to the people who cover them. A coverage plan is a list of real opportunities, not a list of placements to buy.
- **Match the facts.** The value of a mention is that it agrees with your entity home. When a mention is wrong, ask the publisher to correct it, politely, with a source.
- **Do not manufacture it.** Paid placements disguised as editorial, fake profiles, networks of invented sites and edits made in your own favor on open projects are the shortcuts that backfire. Platforms and open projects do detect and reverse them, and a reversed edit can become the next thing someone finds about you.

If you also need to deal with results that are already negative, coverage and an entity home help push accurate, better content up the page. That is a separate discipline with its own limits, and a knowledge panel is not a way around it.

## How to claim a knowledge panel and what verified users can change

If a panel about you or your organization already exists, claiming it is the point at which you gain real, documented control. Google's [claiming instructions](https://support.google.com/knowledgepanel/answer/7534902) describe the process in steps. You need a Google Account, then you search for yourself or the entity you represent and click "Claim this knowledge panel" at the bottom of the panel, which may be in the About section. After reviewing the information, you sign in to one of the official sites or profiles Google lists, such as YouTube or Search Console.

<figure class="fig">
<figcaption><b>Claiming an existing knowledge panel</b></figcaption>
<ol class="fig-steps">
<li><b>Create or choose a Google Account</b>Use an account you intend to keep for this role, since the panel's users are tied to Google Accounts.</li>
<li><b>Find the panel and the claim option</b>Search for the name, and look for the claim button at the bottom of the panel. If it is missing, the panel may not be claimable yet.</li>
<li><b>Verify through a listed site or profile</b>Sign in to one of the official sites or profiles Google lists. If Google cannot find associated sites, it may ask for more information to verify you.</li>
<li><b>Suggest edits with the verified account</b>Use the feedback or suggest-edits option while signed in with the verifying account, so that Google treats the feedback as coming from a verified user.</li>
<li><b>Add the people who need access</b>Managers, owners and contributors have different permissions, and managers can add or remove users.</li>
</ol>
</figure>

Several points in Google's pages are worth knowing before you start.

- Not every panel can be claimed. The page says plainly that not all knowledge panels are claimable and to check periodically for the claim option.
- Roles differ. A manager can suggest changes and add or remove users, an owner is the primary user with the same permissions, and a contributor can suggest changes only.
- If a panel is already claimed by someone else, Google describes an account recovery route through Knowledge Panel Support. Current owners are emailed and have three business days to respond. If they do not, the panel becomes claimable again.
- Local businesses are directed to a Business Profile, not to this process.

### What you can change, and what you cannot

Google says it reviews feedback from verified users within a few days, though it can sometimes take longer. A review is not an approval. Google checks each suggestion against other public information on the web, so an edit with no public support is unlikely to succeed.

Google's page separates the fields clearly:

- **Social profiles:** You can suggest new ones or edit existing ones, but you cannot reorder them.
- **Title:** Changes are considered only with substantial evidence that the automated selection was not the most representative.
- **Subtitle:** Generated automatically. Google says it does not accept or create custom subtitles, though you can ask for relationship-related subtitles to be removed.
- **Description:** It comes from various data sources and cannot be edited. You can contact the source, or submit strong evidence for removal. Google does not write a custom one.
- **Featured image:** It can be replaced only where one already exists, using a direct public image address, not a web page address.
- **Personal information:** You can opt out of showing items such as date of birth, relationships or marital status.
- **People also search for:** It cannot be customized, only removed where it breaks Google's policies.

The practical lesson is that a description you dislike is usually fixed at its source. If it is pulled from a page you or someone else can change, change that page. Google's page points you to the source for exactly this reason.

When you submit feedback, describe the problem, say what should change and give the public URLs that support it, as Google's page asks. In practice, keeping each request to one issue makes it easier to assess.

<aside class="callout">
<span class="callout-label">Limit</span>
<h4>You cannot ask Google to delete a whole panel</h4>
<p>Google states that its policy is not to manually create or delete panels. You can correct facts, opt out of some personal fields and ask for removal of items that break its policies, but not remove the panel because you would rather not have one.</p>
</aside>

## A realistic timeline from nothing to a claimable panel

No schedule is promised by anyone, including Google, which only gives a review time for feedback from verified users. What follows is the order our team usually works in and the ranges we usually see, as experience and never as a guarantee. A panel may not appear at the end of it.

<figure class="fig">
<figcaption><b>Typical order of work for someone starting from nothing</b></figcaption>
<ol class="fig-steps">
<li><b>Weeks 1 to 2: audit what exists</b>Search the name in private browsing, list every profile and mention, note contradictions and namesakes, and decide the one name form to use everywhere.</li>
<li><b>Weeks 2 to 4: publish the entity home</b>Build the page on your own domain with plain facts and links to official profiles, then add markup that states the same facts.</li>
<li><b>Weeks 3 to 6: align the profiles</b>Correct each owned profile to match, link back to the entity home and remove abandoned ones that now contradict it.</li>
<li><b>Months 2 to 6: earn independent coverage</b>Pursue real interviews, speaking slots, directory listings and contributions, and ask publishers to fix errors where they appear.</li>
<li><b>Months 3 to 9: check and claim</b>Search the name periodically from several devices. If a panel appears, claim it. If it does not, keep the evidence current and continue.</li>
</ol>
</figure>

Two things stretch the schedule more than anything else. One is the lack of independent coverage, which cannot be hurried honestly. The other is a name shared with several other people, where the work is disambiguation first. If you start from months of existing press and an outdated or missing owned page, the first stages can move quickly and the rest depends on what the systems choose to do.

A reasonable expectation is that visible results from the entity home and profiles can come before any panel, because search engines and AI assistants read those pages too. If a panel never appears, the work still leaves you with a more accurate set of results for your name.

## Mistakes that cost the most, and why

Most failed attempts fail in the same few ways. Knowing them is more useful than another tactic.

- **Starting with Wikipedia.** An article written by the subject, or by someone paid and undisclosed, is likely to be flagged and can be deleted. The guidelines above explain why. Without independent coverage, there is nothing to cite.
- **Several versions of the name.** A different spelling or title on each profile makes the entity harder to resolve. Pick one form.
- **An entity home that sells.** A page full of claims and no verifiable facts reads as advertising. State facts and link to proof.
- **Buying coverage.** Disguised paid placements and invented profiles risk platform penalties, reversals and a damaging story about the attempt itself.

### When a panel shows someone else, or the wrong facts

If search shows a panel for a namesake when you search your name, you can use the feedback link on the panel, which Google's page offers to people who are not the entity's representatives, or claim the panel if it is yours. The longer fix is the same as everything else: make your own identity clearer than theirs. If a fact on a panel is simply wrong, submit it with the public URL that shows the right fact, and correct the source if you control it.

Search engines and AI assistants summarize a name from different sources, and a correct entity home helps with both. If what an assistant says worries you more than a panel, our page on [what AI assistants say about you](/ai-search-reputation) explains how we assess it.

## The next step: audit before you build

Start with a read of what exists, because that decides whether your first job is identification, evidence or correction. Search your name in a private window, list the first twenty results, note which are you, which are namesakes and which carry an error, and check whether a panel already shows.

<div class="box hot"><b>If this is happening to you now</b>
<p>If a panel shows wrong facts, or someone with your name has taken the space you want, an audit sorts the cause before any work begins. Reputation Partners can run a private review of what search shows for your name and what to do first. <a href="/audit">Request a private audit</a>.</p></div>

If you are building from scratch, spend your first week on the audit, your second on the name form and the entity home, and only then think about coverage. The sequence matters more than the speed.

## Questions people ask

### Is a Google knowledge panel free?

Yes. The help pages I read mention no fee for claiming or suggesting edits, and they describe no paid route to create a panel. Anyone who sells a panel as a product is selling services around the evidence, such as writing a page or seeking coverage, and cannot sell the panel itself. Judge them on the work you can see and keep.

### Can I get a knowledge panel without a Wikipedia page?

Google's help pages do not list a Wikipedia article as a requirement, and they describe panel information as coming from various sources across the web. Plenty of entities are described without one, though what a given person's panel draws on is not something Google spells out. Do not create an article for yourself to try to trigger a panel.

### How long does it take for a knowledge panel to appear?

No one can say, and Google gives no timeline for panels to appear. It only states a few days for reviewing feedback from verified users. Our experience is that months of consistent work come before any visible change, and that for many people, especially those with common names or little coverage, a panel may never appear.

### What if someone else has already claimed my panel?

Google describes an account recovery route through Knowledge Panel Support. Current owners receive an email and have three business days to respond. If they do not, the panel becomes claimable again. Prepare proof of your link to the entity, since Google decides whether to proceed.

### Do I need a website to get a knowledge panel?

Google's help pages do not set a website as a requirement. A site you control still gives systems one reliable page that states who you are, and verification options such as Search Console depend on it. Without one, you rely entirely on profiles and coverage controlled by others, which makes inconsistencies harder to fix.
