Most schema advice is written for e-commerce stores and recipe blogs. Almost nobody explains structured data for the asset that matters most to consultants, founders, and creators: your own name. I have spent years building search presence around "Pierre Subeh," and structured data is the least glamorous, most load-bearing part of that work.
This is the practical setup. No JSON-LD theory lectures, just what goes where and why.
Why Person Schema Matters More in 2026 Than It Did in 2020
Search engines and AI assistants have both moved from indexing pages to modeling entities. When someone asks Google or ChatGPT about you, the system is consulting its internal picture of you as an entity: name, roles, organizations, locations, notable work. Schema is your chance to author that picture instead of letting it be assembled from scraps.
Two shifts raised the stakes:
1. Knowledge panels and AI answers describe you in one sentence. You want to write that sentence, not inherit it.
2. Disambiguation is brutal for common names. If you share a name with anyone notable, the machines will merge or confuse you without strong entity signals. I cover the broader discipline in personal SEO and owning your name; schema is the technical backbone of it.
The Core Setup: One Canonical Person Entity
The biggest mistake I see is scattered, contradictory Person markup: one version on the homepage, another on the about page, a third auto-generated by a WordPress plugin. Pick one canonical definition and reference it everywhere.
Where the canonical entity lives
I put the full Person object on my about page and give it a stable @id. Every other page that mentions me as author references that @id instead of redeclaring everything. One source of truth, many pointers.
What goes in the Person object
The fields that pull real weight in my experience:
- name exactly as you want to be known, spelled one way, forever.
- jobTitle and worksFor pointing at your Organization entity. Mine connects to X Network, which has its own Organization markup with its own @id.
- sameAs as a curated list of profiles you control or that verifiably describe you: LinkedIn, X, Wikidata if you have an item, author pages on publications, speaker pages.
- knowsAbout for your topical territory. I keep this honest and narrow: SEO, digital marketing, brand strategy. A list of forty topics reads as noise.
- description written as the one-liner you want machines to repeat.
- Validate quarterly with the Schema.org validator and Google's rich results test. Plugins update, themes change, markup silently breaks.
- Search your own name monthly and read how Google and the AI assistants describe you. Drift in those descriptions usually traces back to a contradiction somewhere in the cluster.
- Update the moment facts change. New role, new company, new book. Stale schema teaches machines outdated facts that take months to correct.
- Keep copy and markup in agreement. If your about page says one title and your JSON-LD says another, you have told the machines you are an unreliable narrator.
The sameAs discipline
sameAs is not a link dump. Every URL should pass this test: does this page unambiguously describe the same person, with matching name and facts? A dead profile, a mismatched bio, or a shared account weakens the cluster. I audit mine twice a year and prune.
Connecting Person, Organization, and Content
The entity graph only works when the pieces reference each other. My structure:
1. Person (me) worksFor Organization (X Network).
2. Organization has founder pointing back to the Person @id.
3. Every article on my site carries author referencing the Person @id, plus publisher referencing the Organization.
4. WebSite and WebPage markup tie it all to the domain.
This circular referencing sounds pedantic. It is also exactly how machines confirm they are looking at one coherent entity rather than four coincidentally similar ones. It is the same consistency logic that drives getting cited by LLMs: agreement across sources is the trust signal.
The Off-Site Half Nobody Does
Schema on your own site is a claim. The claim gets weight when off-site sources agree. Three moves worth the effort:
Wikidata, if you qualify
A Wikidata item is the closest thing to a public entity registry the web has. If you have genuine notability signals (press coverage, published work, verifiable roles), a properly sourced item becomes the anchor that knowledge panels and AI systems lean on. Do not fabricate notability; sloppy self-promotional items get deleted and the deletion itself becomes a signal.
Author pages on publications
My author page on Entrepreneur at https://www.entrepreneur.com/author/pierre-subeh does more entity work than almost anything on my own domain, because it is a third party stating my name, my role, and my topics. If you contribute anywhere, make sure your author bio is accurate and consistent with your canonical description, then put that URL in sameAs.
Speaker and organization pages
Event sites, association pages, board listings. During my time leading AMA Orlando, the association's own pages describing my role were corroboration I could never manufacture on my own domain.
Testing and Maintenance
Schema is not fire-and-forget. My maintenance routine:
Start Here This Week
If you do nothing else: write your one-sentence description, build a single canonical Person object on your about page with five to eight strong sameAs links, and reference it from your articles as author. That alone puts you ahead of most personal brands, and it lays the foundation for the E-E-A-T signals that everything else in modern search rests on.
Your name is the one keyword nobody can outrank you for, unless you leave it undefined. Define it.