Person schema generator
Person JSON-LD is the machine-readable layer you fully control, and it quietly does most of what people wrongly hope Wikidata will do. Fill the fields, copy the block, paste it into the head of your entity home. Everything runs in your browser and nothing is sent anywhere.
Exactly as it should appear everywhere. One spelling, forever.
This is the descriptor a machine will reach for. Keep it to the role, not a slogan.
Links the person entity to the company entity. Both should exist separately.
The geographic half of the record. Remote-first people skip this and cannot work out why the record stays soft.
Two letters. GB, US, IN, AE.
The canonical page about you. Not a company About page, and not a link aggregator on somebody else's domain.
The master headshot. The same file everywhere, not a similar one.
Plain, no adjectives. Name is the Role at Organisation, based in City.
Optional. If a scan found one, paste it and it gets wired into sameAs as a Google entity link.
One per line. These become the sameAs array, which is how a machine confirms that four profiles are one person. Three is the floor, more is better.
The whole block, script tags included, inside the <head> of your entity home. One page, not every page. This is the page that is about you.
Run it through the schema validator and the rich results test. Both are free and both are linked above. Fix anything flagged before you move on.
Every value in the block must also be readable on the page itself. Structured data that contradicts the visible content is worse than none, because it looks like an attempt to mislead.
Organization schema on the company site with founder pointing back at your @id. Two connected entities beats one confused one every time.
What schema will and will not do
It will give machines an unambiguous statement of who you are, which profiles are yours, who you work for and where you are. It removes guesswork, and guesswork is the thing that makes systems hedge.
It will not produce a knowledge panel on its own. Schema is a claim in a readable format. It is still your claim about yourself, and no volume of self-description substitutes for independent sources agreeing.
The pattern we see repeatedly: a client ships perfect schema, waits three months, and nothing happens. The schema was not wrong. It was one of five things and the other four were missing. Do this in an afternoon, then spend the next six months on the part that involves other people.
Person JSON-LD belongs on the page that is about the person. Repeating it site-wide dilutes rather than reinforces.
Two profiles is not a pattern. Aim for five or more, and only ones you actually control and keep current.
Image matching is one of the cheapest confirmations a machine can make. Use one file. Not one style, one file.
“Transformational growth catalyst” gives a machine nothing to match against. “Chief Technology Officer” does.
One-way relationships get read as an assertion. Two-way ones get read as a fact.