Nobody can promise you a knowledge panel. Google builds the entity on its own schedule, from sources it trusts, and it shows the panel when it is confident. What you can do is make it easy for Google to build the entity, and remove every reason it has to hesitate. Done properly, that takes a few weeks of work and then a few months of waiting. Here is the order that works.
-
Pick one exact name and use it everywhere.
Decide the form of your name that will appear on every profile, every bio and every byline. Full name with middle name or without, maiden name or not, credentials after the name and never inside it. From now on there are no variants. Half of Google's hesitation about a person comes from the same human appearing under three slightly different names. 2. Build a home page that states the facts plainly.
You need one page on a domain you control that is unmistakably about you and says, in ordinary sentences, who you are: your name, what you do, where you work, where you were born, where you studied, where you live, what you have written or built. Google cannot cite what your site only implies. If the facts are not written down somewhere canonical, the later steps have nothing to point at.
Keep it to one bio. Two pages on the same site that both read as biographies confuse the picture; a second page should be a media kit or a press page, not another bio. 3. Add Person schema with sameAs links.
Underneath the visible page sits a block of structured data, written in JSON-LD, that says in machine terms what the page says in prose. For a person it names a single Person entity with a stable identifier, lists the job title, employer, education and birthplace, and, most importantly, carries a sameAs list pointing at every profile you control: LinkedIn, X, YouTube, Crunchbase, your author page, your podcast host page. That list is how Google learns that all of those profiles are one person. Person schema, explained with an example you can copy, covers the markup in detail. 4. Make every profile agree.
Go through every editable profile and make the name, the headshot, the title and the website field match the home page. The website field should point at your own domain, not your employer's. Report duplicate LinkedIn profiles. Retire old handles where you can and accept the ones you cannot. One photo everywhere; it is the photo Google will eventually use. 5. Collect corroboration from other people's pages.
Google weighs what others say about you more than what you say about yourself. Interviews on podcasts, articles that quote you, a speaker listing, a press release about something you launched, a profile on a company site: each is a dated page by a third party that repeats your facts. Ask hosts to use your exact name and link to your home page in their show notes. The more of these that agree, the sooner the entity forms. 6. Wikidata, but only if you qualify.
Wikidata is the open database Google reads directly. An entry there, with references to your home page and to third party sources, is a strong signal. It also has a notability bar: at least one independent, named source about you, such as an article in a real outlet. If you add yourself without that, the entry gets deleted and you have wasted the effort. If you qualify, keep the entry minimal and reference every statement. 7. Search Console and indexing.
Add your domain to Google Search Console as a domain property, then use URL inspection to request indexing on your home page and media kit. This gets the pages read sooner, shows you whether Google parsed your schema, and later lets you watch how many people search your name and see your site. It is also one of the ways Google verifies that you are the person behind the domain when you claim the panel. 8. Wait, and check monthly.
Entities form in weeks or months, not days. Once a month, in a private browsing window, search your plain name and your name plus company. When the panel appears, you will see a "Claim this knowledge panel" link. 9. Claim it.
Signed in to a Google account on your own domain, click the claim link and verify through the Search Console property or a linked social profile. After the claim you can suggest edits to the photo, the subtitle and the links, and report errors through the feedback link under the panel. The next post walks through the claim step by step.
How long each step takes
People give up because they expect the panel in a fortnight. The honest timeline, for someone starting with a LinkedIn and a few mentions:
| Step | Your time | Calendar time before it has an effect |
|---|---|---|
| Pick one name form | An hour to decide, a week to apply everywhere | Immediate once applied |
| Canonical home page | A day to write if the facts are to hand; two to three if you have to dig | Indexed in days; weighed over weeks |
| Person schema | Two hours with a template | Read on the next crawl |
| Profiles agreeing | An afternoon for the quick fields; a week for the ones that need support tickets | Days to weeks |
| Corroboration | Ongoing; aim for one new third party page a month | Each one lands within days of indexing |
| Wikidata | An hour, if you qualify | Often the fastest to show in Google, inside a week or two |
| Search Console and indexing | Thirty minutes | Indexing in hours to days |
| Entity forms, panel appears | None | Four to sixteen weeks is typical; longer for a contested name |
The pattern is that your work is front loaded into the first fortnight and the rest is waiting while the sources agree. The monthly check keeps you from fiddling.
If you share your name with someone better known
A footballer, a judge, a dentist with three hundred reviews. The machine resolves a name to the best documented person, and that is them. You will not out shout them, and you should not try. You become unambiguous instead.
State the disambiguating facts in the first sentence of your home page: city, company, field, middle name if you use it. Put the same details in the description property of your schema. Use the longer form of your name consistently if the short form is the contested one; "Sarah Walling Lockwood" is a different string from "Sarah Lockwood", and schema can declare both so the machine knows they are one person. Then collect corroboration that mentions you alongside those disambiguating details, because every interview that says "founder of Northwind Analytics" is a vote for your entity and not theirs. Expect the longer end of the timeline, and expect the panel to appear on name plus company well before it appears on the plain name.
What to tell anyone who helps you
If an assistant, an agency or a friend who knows WordPress is doing some of this, give them a one page brief so they do not undo each other's work. It should contain: the one exact name form, the identifier (https://yourdomain.com/#person), the headshot file they must use everywhere, the website address every profile points at, and the rule that no page other than the home page describes you. Most damage to a person's entity is done by well meaning people adding a second bio, a variant name or a different photo.
What to look for each month
Open a private window. Search the plain name, then name plus company, then name plus city. Note whether a panel appears, which image it uses, and what the subtitle says. Search your name in Google Images and count how many of the first twenty faces are you. Open Search Console and look at impressions for queries containing your name; a rising line means the machine is connecting searches for you to your site. Run the AI answer check quarterly. Write the results in a dated note so you can see movement, because the changes are gradual and memory is unreliable about gradual things.
The mistakes that stop it working
Buying a panel. Services that promise one for a few hundred dollars feed Google thin sources, and a panel built that way tends to vanish, taking your real entity with it.
Automated feeds on the home page. A JavaScript widget pulling your latest posts gives Google nothing to read and can drown the Person signal in article noise. Static links with dates, refreshed by hand, work better.
Changing your name form halfway through. Every variant restarts the clock.
Stale third party bios. One old conference page listing a role you left in 2019 can feed a duplicate entity that competes with your real one. Email the outlet and ask for an update with a link to your home page.