You can’t create a knowledge panel yourself. Google generates one when it is confident about which entity a search refers to and holds enough reliable information to describe it. That changes the question behind how to get a knowledge panel: it becomes what Google already knows about you, and what is stopping it from showing that knowledge.
If you searched your brand or name and saw no panel, or saw the wrong one, the useful next step is working out which of three situations you are in. Each calls for different work, and applying the steps for the wrong one costs weeks. This guide is built around that decision.
What can I influence, and what is Google’s decision?
I can influence what information Google has about an entity and how consistently that information appears across sources. I can’t influence whether, when, or for which queries Google chooses to show a panel. That decision belongs to Google, and it publishes no thresholds, so any article on how to get a knowledge panel that promises a fixed list of steps or a fixed timeline is claiming more than anyone outside Google knows.
It helps to separate two layers. The first is the entity record: whether Google holds a distinct, well-described entity for you. This layer responds to evidence such as an entity homepage, aligned profiles, structured data, and independent sources that describe you the same way. It lives in the knowledge graph, which is related to the panel but not the same thing, as the knowledge graph vs knowledge panel guide explains. The second layer is display: whether, for one particular query, Google decides a panel is warranted. You can only affect that indirectly.
There is no application form and no fee. The conditions Google tends to weigh are laid out in the eligibility framework on the knowledge panel guide, and the eligibility signals article goes through them one at a time. I won’t repeat them here, because for most people the order of the work matters more than the list.
Which starting point am I in?
There are three common starting points: Google has no entity record for you, Google has a record but shows no panel for your main query, or a panel appears but it is wrong. A handful of searches usually tells you which applies, and that decides which of the sections below you need.
Run the searches in a private browser window, and note your location and language, because results vary. Search the exact name, then the name plus a descriptor of what you do, then the name plus a city, and for a company, the founder’s name as well. Write down what you see for each: a panel, no panel, someone else’s panel, or a panel only in a related-search box. Tools that query Google’s public knowledge graph data can also show whether an entity record exists under your name, but they reflect only part of what Google holds, so an empty result is a hint and not proof.
Then match what you saw to a state. If no variation produces a panel and no entity record turns up, you are at the start. If some variations produce one but the plain name doesn’t, an entity exists and display is the issue. If a panel appears for the wrong person or company, or carries wrong facts, the problem is accuracy and not acquisition. Finding out why a specific gap exists is a longer job, and the knowledge graph audit covers the diagnostic tests. Here I only use the searches to choose a route.
To make the three cases concrete, take a hypothetical four-person engineering consultancy called Halden Structural Partners, based in Leeds. A search for its exact name returns its website, a LinkedIn page, and a few directory listings, but no panel. Adding “structural engineers Leeds” changes nothing. Halden is at the start. I will come back to it twice.
No entity yet: what should come first?
Start by deciding on one correct description of the entity, then publish it in one authoritative place before spreading it anywhere else. Order matters because Google compares sources against each other, and many sources that disagree can do less for recognition than a few that match.
The sequence I follow is short. First, write the canonical record: name, entity type, a one-sentence description, founding date, key people, and official URL. Second, publish it on your own site through an entity homepage with matching Organization or Person schema. Third, add an independent structured reference such as a Wikidata entry that points back to the site. Fourth, bring existing profiles into line with the record. Fifth, let independent corroboration build, which is the slow part. The step-by-step build guide lays out each phase with decision points, so I won’t reproduce it here.
What is specific to panels is how the work fits together. A panel is the last visible output of a chain that begins with the record, so effort spent on the visible end before the record is correct tends to be wasted. Halden’s first job, for example, has nothing to do with panels. It is deciding whether the company is “Halden Structural Partners” or “Halden Structural” and using that single name everywhere.
If the entity is a person as well as a company, the two are separate targets with separate paths, and the personal vs brand knowledge panels guide covers how they differ.
Google has me, so why is there no panel?
A panel is triggered per query, not per entity. An entity can exist in Google’s records and still produce no panel for the query you care about, usually because the query is ambiguous, because Google is more confident the searcher means a different entity, or because the available information is too thin to display. Google doesn’t publish the trigger, so working this out is a process of elimination.
Query type is the first thing to look at. The bare name, the name with a descriptor, the name with a location, and the name of a founder are four different queries, and they can behave differently. Back to Halden: some months after fixing its naming and publishing the record, the plain name still shows nothing, but “Halden Structural Partners Leeds” now produces a small panel. That is an entity with display on some queries and not others, which is a normal in-between stage and not a failure.
Ambiguity is the second thing. Names shared with other companies, with common surnames, or with a famous entity compete for the same query, and Google tends to resolve that competition toward the entity it knows best. The guide to how search engines disambiguate entities explains the signals involved. In practice I make the descriptor query the first realistic target and the bare name the later one: pair the name with the same short descriptor in your schema, your profiles, and your own copy, so the combined query points to one entity.
The third factor is how much there is to show. A panel with only a name and a link is possible, but Google may hold back when the record is sparse. Adding verifiable attributes, such as founding date, location, and a clear description, in the places Google already reads gives it more to work with. None of this guarantees a panel. It removes reasons for Google to hesitate, which is all that can honestly be claimed.
A panel shows, but it’s wrong or isn’t mine
If a panel appears for the wrong entity or carries wrong facts, acquisition is no longer the problem. The problem is conflicting sources, and it is fixed by correcting those sources, not by asking Google to remove or reassign the panel.
The guide on why Google shows wrong information about your brand explains how Google resolves conflicting signals and the order in which to fix them. If the cause is name overlap and not outdated facts, the disambiguation material above applies instead.
If the panel is correct and belongs to you, the next step is claiming it. The claiming guide and the verification explainer cover that process. Claiming and verification let you suggest changes, but Google still decides what the panel shows, so they don’t replace the groundwork above.
Does a Google Business Profile count as a knowledge panel?
No. A Google Business Profile and a knowledge panel are separate things, even though both can appear as an information box on a brand search. For a local business, the box shown for its name is often driven by the Business Profile, which is managed inside that product and not through the knowledge panel route.
Businesses asking how to get a knowledge panel often start with their Business Profile, and a complete, consistent profile is one more source that agrees with the rest of the record. It isn’t a shortcut to an entity-level panel, and a thin or inconsistent profile can add conflicting details. How small and local businesses should think about this, including which route fits which goal, is covered in the small business knowledge panel guide.
When should I stop making changes and wait?
Stop when the entity record is correct and identical everywhere you control, and the remaining gap is external. Past that point extra edits mostly create new inconsistencies, and what remains is corroboration, which builds slowly and on a schedule you don’t set.
In practice I settle on a monthly check. Repeat the same set of search variations, log the result for each in a simple sheet, and change something only when a monitored result changes or when a real fact about the entity changes. When a fact does change, update the sources in order of authority, as the entity consistency guide describes, so that a fresh inconsistency doesn’t appear halfway through the update.
Two habits cost time without helping. One is checking daily, which invites reactive edits to results that naturally fluctuate. The other is sending repeated feedback asking Google to create a panel. The feedback option on an existing panel exists to correct displayed information, and there is no request channel for a panel that doesn’t exist yet. The realistic horizon is months, not days, and the build guide sets out progress signals worth watching in the meantime.
What should I do first this week?
Run the searches, name your starting state, and do only the work that state calls for. Doing everything at once is how consistent records turn into contradictory ones.
If you are at the start, write the canonical record and settle the name. Everything else depends on it, and the entity homepage is where it should live first. If Google already has you but shows no panel, choose one descriptor query as your target, align the descriptor across your sources, and check whether a shared name is competing with yours. If a wrong panel is showing, find the conflicting source before changing anything, using the reconciliation guide linked above.
That is the practical answer to how to get a knowledge panel: find your state, fix the record before the display, and then wait with a monitoring routine instead of constant edits. The knowledge panel pillar guide gives the wider framework behind all three routes, and the specific guides linked in each section go deeper where your situation needs it.
What else do people ask when no panel appears?
Why does a competitor with a weaker website have a panel when I don’t?
A panel depends on how well Google recognizes an entity, not on how strong the website is. A competitor may have a longer public record, an independent reference such as a Wikidata item, or simply a less ambiguous name. I can’t see their inputs, but comparing their publicly visible sources, such as their schema, their external profiles, and where they are mentioned, is more informative than comparing site metrics.
Will the panel appear for every search of my name?
No. Panels are triggered query by query, and they can vary with location, language, and device. That is why logging several variations over time says more than a single check.
Can I get a panel if my name is shared with someone well known?
It is possible, though harder, because the established entity usually wins the plain-name query. The realistic route is qualified queries first, with a consistent descriptor, and the disambiguation guide linked earlier explains how competition between similar names is resolved.
Do I need a website to get a panel?
A website isn’t a stated requirement, but it is the one place where you control the full record. Without one, the record depends on third-party sources you don’t control, which makes it slower to keep consistent.