There is no way to request a Google knowledge panel. Google generates panels automatically for entities it holds in its Knowledge Graph and judges a query to be about, so the work available to a publisher is making an entity unambiguous, well described and independently corroborated. That work has a sensible order, and this page gives it. Nothing in it is a guarantee, and any source promising one is selling something Google does not offer.
What the goal actually is
A knowledge panel requires two separate things: Google holding an entity for the subject, and Search deciding a given query resolves to it. The steps below aim at the first. The second follows from name distinctiveness and query volume, both largely outside direct control.
One distinction changes everything about the approach. If the subject is a business with a physical location or a service area, the route is a Google Business Profile, which is a product with a dashboard, a verification process and fast edits. That is a different mechanism from the graph-derived panels covered here, and it should be completed first for any local business. Everything below applies to organizations, brands, people, publications and other non-local entities.
The checklist
1. Confirm there is a real entity to describe
Google represents things that exist independently of their own marketing. A company with a registration, employees, customers and press coverage is an entity. A campaign name, a tagline, a product line with no independent coverage, or a personal brand with no third-party mentions is not, and no amount of markup makes it one. If a subject has no coverage in sources it does not control, the honest first step is producing some, not writing schema.
2. Establish an entity home
An entity home is the single page that a search engine should treat as authoritative for the entity, and the page every other reference points at. Conventionally this is the site’s home page for an organization, or a dedicated bio page for a person, on a domain the entity controls.
The requirements are simple and often violated. One page, not several. A stable URL that will not change. Content that describes the entity itself, including what it is, where it operates, when it started, and who is involved, rather than only what it sells. And a page that is indexable, canonical to itself, and reachable in one click from the home page.
The term comes from entity SEO practice rather than from Google documentation, and the underlying idea is the linked data principle that a thing should have one address that returns useful information about it.
3. Fix name and description consistency
Pick one name form and use it everywhere: the website, social profiles, directory listings, press releases, conference bios, business registrations. “Acme Analytics”, “Acme Analytics, Inc.” and “AcmeAnalytics” are three strings, and reconciling them is work a search engine may or may not do correctly.
Do the same for the description. Write one short factual sentence of the form “X is a Y that does Z”, and use that same sentence wherever a bio or boilerplate is required. When independent sources describe an entity the same way the entity describes itself, there is something to corroborate. When every source says something different, there is not.
4. Publish structured data at the entity home
Mark up the entity with JSON-LD on its home page, using a stable @id and pointing sameAs at external records that describe the same entity. This is the one step Google documents directly: it reads structured data and lists it among its sources.
{
"@context": "https://schema.org",
"@type": "Organization",
"@id": "https://acmeanalytics.com/#organization",
"name": "Acme Analytics",
"url": "https://acmeanalytics.com/",
"logo": "https://acmeanalytics.com/logo.png",
"description": "Acme Analytics is a data analytics company serving logistics operators.",
"foundingDate": "2014-03-01",
"founder": { "@type": "Person", "name": "Jane Doe" },
"address": {
"@type": "PostalAddress",
"streetAddress": "100 Main Street",
"addressLocality": "Gainesville",
"addressRegion": "FL",
"postalCode": "32601",
"addressCountry": "US"
},
"sameAs": [
"https://www.wikidata.org/wiki/Q00000",
"https://www.linkedin.com/company/acme-analytics/",
"https://www.crunchbase.com/organization/acme-analytics"
]
}
For a person, use Person with jobTitle, worksFor, alumniOf and sameAs links to an ORCID, an author page, or verified profiles. Property-level detail is at organization schema and person schema.
Two rules on sameAs matter more than the property list. Every URL must describe the same entity, not a related one; linking a company to its founder’s profile asserts that the company and the person are one thing. And the @id should be a URI on a domain the entity controls, reused unchanged on every page and in every block that mentions the entity.
5. Claim the profiles that count as official presence
Google’s panel verification requires an official presence it can check, and its documentation lists routes including a website verified in Search Console, an official YouTube channel, and official profiles on supported social platforms. Set those up and name them identically before a panel exists, because they are also the profiles sameAs should point at, and because verification later depends on them.
6. Build corroborating third-party sources
This is the step that takes longest and does most. Independent sources repeating the same facts is the pattern that distinguishes represented entities from unrepresented ones. Useful categories:
- Press and trade publication coverage that names the entity and states facts about it.
- Industry databases and registries appropriate to the sector.
- Author bios, speaker pages, podcast appearances and course listings for people.
- Professional association and accreditation listings.
- Company registers and filings, which are structured, dated and independent.
The test for each is whether it states checkable facts about the entity and whether the entity controls it. A guest post byline on a site the entity does not own counts. A syndicated press release republished on twenty low-quality domains supplies twenty copies of one source, and Google’s systems are built to notice that.
7. Consider Wikidata, honestly
A Wikidata item is one of the sources Google names, it is free to create, and it gives the entity a public identifier that sameAs can point at. It is also governed by notability guidelines that require a serious and publicly available reference, or a clear structural role in the data, and items for subjects that fail those tests are deleted. Creating an item is a reasonable step after step 6 has produced real references. Creating one before is usually wasted effort, and self-created items for marginal subjects are a well-known pattern that reviewers watch for.
A Wikipedia article works differently again, because Wikipedia’s notability standard is higher and its conflict-of-interest rules discourage subjects from writing about themselves. An article is a result of coverage, not a route to it.
8. Wait, then claim and correct
Nothing here produces a same-week result. Google’s graph updates on its own schedule, and it does not notify anyone when an entity changes. Once a panel does appear, two mechanisms open up: the “Claim this knowledge panel” flow, which marks an account as a verified representative and lets it suggest changes, and the feedback link, which anyone can use to report a factual error. Neither grants editing rights. Both are covered in detail on the knowledge panel page.
What does not work
Markup alone. No schema.org type or property guarantees a panel. Structured data makes claims legible and consistent; it does not create entities. This is the single most common misunderstanding in the area, and it survives because markup is the part of the process a practitioner can finish in an afternoon.
Buying a panel. Google states that it does not accept payment to create or change knowledge panels. Services selling panels are selling either the steps above or nothing.
Mass directory submissions. Bulk citation building produces many low-value copies of the same assertion and adds no independent corroboration.
Editing Wikipedia about oneself. It conflicts with Wikipedia’s guidelines and often ends in reversion and a documented conflict-of-interest note.
Waiting for markup to be crawled as a strategy. The bottleneck is almost never crawling. The entity has too little independent evidence for anything to corroborate.
Related pages
FAQ
How long does it take to get a knowledge panel?
There is no documented timeframe, and Google publishes no thresholds. The graph updates on its own schedule and gives no notification when an entity is added, so the honest answer is that it depends on how much independent coverage the entity accumulates and how distinctive its name is. Practitioners generally describe timelines in months rather than weeks.
Can a person get a knowledge panel without a Wikipedia page?
Yes. People appear with panels on the basis of author records, catalog metadata, professional listings, and press coverage, without any Wikipedia article. Successful cases share independent third-party sources stating consistent facts, plus one clear entity home page the person controls with matching structured data.
Does schema markup guarantee a knowledge panel?
No. No markup guarantees a panel. Structured data is a documented input that makes an entity’s claims legible and consistent, and Google lists it among its sources, but Google decides what enters its graph and when a panel renders. Markup with no independent corroboration behind it produces no panel.
What is an entity home?
An entity home is the single authoritative page for an entity on a domain it controls, and the page every other reference and sameAs link points to. For an organization, it is usually the home page; for a person, a dedicated bio page. The term comes from entity SEO practice rather than from Google documentation.
Sources and further reading
- Google. Knowledge panel help center (claiming, verification and suggesting changes). https://support.google.com/knowledgepanel
- Google. A reintroduction to Google’s Knowledge Graph (May 2020). https://blog.google/products/search/about-knowledge-graph-and-knowledge-panels/
- Google Search Central. Introduction to structured data markup. https://developers.google.com/search/docs/appearance/structured-data/intro-structured-data
- Google Business Profile Help. https://support.google.com/business
- Wikidata. Notability. https://www.wikidata.org/wiki/Wikidata:Notability
- schema.org. Organization. https://schema.org/Organization