Google documents how to claim a panel and stays quiet on who qualifies for one, which is where the disagreement lives.
What Google’s documentation covers
Google’s “Get verified on Google” help page lays out the claiming path. You need a Google Account, plus sign-in to one of YouTube, Search Console, Twitter or Facebook as an official site or profile, and a “Claim this knowledge panel” option showing below the panel.
If Google cannot find sites associated with you, the page says you are prompted to provide more information to help verify you.
Once verified, three roles exist. Owner is the primary user and can transfer ownership. Manager can suggest changes and add or remove users. Contributor can suggest changes.
The sentence that does the most work
One line on that page sets the boundary: “Not all knowledge panels are claimable as of now.”
Read it carefully and it tells you something about claiming, and nothing about qualifying. A panel has to exist before the sentence applies to you at all.
What Google does not publish
Google’s verification documentation does not contain an eligibility list for who receives a personal knowledge panel. There is no stated follower count, no media threshold, no job title that qualifies.
That gap is the reason the practitioner literature exists.
The practitioner position
Jason Barnard, writing in Search Engine Journal, states that the Knowledge Graph has no notability guidelines and that anyone can get a place in it.
His mechanism is procedural rather than reputational: an Entity Home you own, schema.org markup on it, then corroboration from authoritative first and third party sources that link back, producing what he calls an “infinite, self-confirming loop”.
On timing he distinguishes well-understood entities, which move in days to weeks, from ambiguous or confused ones, which take longer.
Where the two views line up
Semrush’s account of panel generation sits between them. Google matches the query to an entity, judges confidence and usefulness, picks a template by entity type, fills it with facts and images, then displays it.
The data sources Semrush names are the ones Barnard’s method targets: Wikipedia, Wikidata, official websites, social profiles, news and industry directories.
Both accounts put corroborated facts across independent sources at the center. The disagreement is about whether fame is a precondition.
The encyclopedia gate is a separate gate
Semrush notes Wikipedia requires notability via significant coverage in reliable independent sources, while Wikidata’s bar is lower, though entries still need references.
Those are Wikimedia standards, applied by volunteer editors. Barnard’s claim is about the Knowledge Graph, which is Google’s. Conflating the two is how founders conclude they are ineligible for something they were not tested for.
If you serve customers at a location
Google’s documentation includes a routing rule worth knowing. Local businesses serving customers at a location or a service area should use a Business Profile instead of a knowledge panel.
If you are the named face of a local practice, that rule applies to the business, and your personal entity remains a separate question.
The honest answer, and what to do with it
Semrush states the limit in writing: panels may take weeks or months to appear, can change or disappear, and come with no guarantee. Anyone promising you a panel is promising something the documentation declines to promise.
The pattern I see running visibility work at Subscribe PR is founders treating eligibility as the question when the input quality is the question they can act on.
Google’s page also notes that without verification you can still submit suggestions through the Feedback option, which is worth using while the rest develops.
To see what the input work looks like in practice, the write-ups at calebhellinger.com/insights show the shape of it.
Caleb Hellinger runs Subscribe PR, an answer engine optimization and digital PR agency in Phoenix.
