--- title: "Person entity SEO | sameAs and author schema | Len P. van der Hof" description: "Person entity SEO reduces identity ambiguity: one visible author profile, one stable Person @id, Article author markup that points at it, and sameAs links…" image: "https://lenvanderhof.com/media/generated/blog-hero-person-entity-seo-v1.d13cebcc9af0.wide.webp" --- [SEO, GEO and AEO](https://lenvanderhof.com/en/blog/category/seo-geo-aeo/) Research guide # Person entity SEO: a name an engine can attach A byline gives an engine a string. A coherent author graph gives that string somewhere to resolve. Len P. van der HofPublished 23 September 20265 min read The useful graph is small enough to inspect and coherent enough to follow. Direct answer Person entity SEO is the work of making a public identity consistent and unambiguous across pages and references. Build one visible author profile, give its Person entity a stable @id, point every Article's author markup at that same @id, and use sameAs only for URLs that unambiguously identify the same person. Schema.org defines sameAs that way, with a Wikipedia page, a Wikidata entry, or an official website as examples; owning the destination is not required. Google supports Person as the main entity of a ProfilePage and recommends sameAs for external profiles or home pages, but structured data does not guarantee a knowledge panel, a citation, or a ranking benefit. The markup must agree with what readers can see. ## Key takeaways - Use one stable Person @id across the profile page and every Article's author markup. - sameAs means a page that unambiguously identifies the same person, not merely a URL you control. - A book product page, an employer homepage, or a generic publisher page usually does not identify one person. - Structured data creates eligibility and clarity. It cannot guarantee rankings, citations, or a knowledge panel. A byline gives an engine a string. An author profile gives that string a home. A coherent graph lets every article point back to the same person. **Person entity SEO is the work of making a public identity consistent and unambiguous across pages and references.** Build one visible author profile. Give its Person entity a stable `@id`. Point every Article’s author markup at that same `@id`. Use `sameAs` only for URLs that unambiguously identify the same person. That is the whole discipline. It reduces avoidable ambiguity. It does not create authority, and it cannot reserve a knowledge panel. This page is about identity resolution. [How to get cited by ChatGPT](https://lenvanderhof.com/en/blog/how-to-get-cited-2026/) is about whether a page is useful enough to become a source, and the [citation-readiness audit](https://lenvanderhof.com/en/blog/citation-readiness-audit/) tests that page. A clean identity graph supports both jobs without replacing either. ## One Person node that every page can share Give the public author profile a stable Person `@id`. The identifier does not have to be a page a reader visits. A fragment URL is a common implementation: ``` { "@context": "https://schema.org", "@type": "ProfilePage", "url": "https://example.com/authors/mira-chen/", "mainEntity": { "@type": "Person", "@id": "https://example.com/#mira-chen", "name": "Mira Chen", "url": "https://example.com/authors/mira-chen/", "sameAs": [ "https://www.wikidata.org/wiki/Q123456", "https://orcid.org/0000-0000-0000-0000" ] } } ``` Then let every article refer to that identifier instead of minting a slightly different Person on each page: ``` { "@type": "Article", "headline": "A worked example", "author": { "@type": "Person", "@id": "https://example.com/#mira-chen" } } ``` The stable `@id` is the join. The profile page describes the person; the article says who wrote the work. On a bilingual site, the English and Dutch profile URLs can describe the same Person node. Forcing every locale through one visible URL is unnecessary when the graph already supplies a shared identity. This is an implementation pattern, not a declared Google ranking factor. ## What sameAs actually says Schema.org defines `sameAs` as the URL of a reference page that unambiguously indicates the item’s identity, and gives a Wikipedia page, a Wikidata entry, or an official website as examples. The test is stricter than “related to this person” and broader than “controlled by this person.” Good candidates include: - an accurate Wikidata or Wikipedia entry; - an ORCID record for the author; - an author page at a publisher or bookseller that is devoted to that one person; - an official profile on another platform. A book product page identifies a product. A company homepage identifies an organization. A conference programme merely mentions a name. Those URLs may belong elsewhere in the graph, attached to the book, the organization, or the event. They do not belong in `sameAs`, because `sameAs` is appropriate only when the destination resolves the person without guesswork. Control still matters operationally. A profile you maintain is less likely to go stale. But control is not part of the definition, and a controlled page with the wrong name or a dead redirect is still a poor identity reference. ## Author schema must agree with the page Google’s ProfilePage guidance expects a page focused on one person or organization, named in `mainEntity`, and it recommends `sameAs` for external profiles or home pages. The visible profile should therefore carry the same public name, description, image, and role that the markup describes. A crawler should not have to reconcile: - “Mira L. Chen” in the page heading with “Mira Chen” in the schema and “M. Chen” on every external profile; - a Person `url` that opens an About page listing three team members; - Article markup that alternates between several author URLs for the same writer; - `sameAs` targets that redirect to a platform homepage, return 404, or now belong to somebody else. Name variation is sometimes legitimate. Pen names, diacritics, locale variants, and changed surnames need an editorial decision, not mechanical uniformity. Use `alternateName` for a real public variant. Do not erase useful distinctions to make a spreadsheet look tidy. ## A compact person-entity audit Start with the reader-facing profile, then inspect the graph. 1. **Resolve the subject.** Does the page clearly describe one person, in visible HTML? 2. **Inspect the Person node.** Is the `@id` stable, and do `name`, `url`, image, and description match the page? 3. **Follow every author edge.** Does each Article node use the same Person `@id`? 4. **Open every sameAs URL.** Does each destination still resolve this person unambiguously? 5. **Remove category errors.** Move product, employer, publisher, and generic social URLs to the properties where they belong. 6. **Check locales and redirects.** Do language variants and old profile paths converge without loops, accidental duplicates, or lost meaning? 7. **Re-test after migrations.** A handle change or a platform redirect can break an otherwise sound graph. This site’s [author profile](https://lenvanderhof.com/en/authors/len-p-van-der-hof/) follows the shared-node pattern: ProfilePage names the person, and every article’s author markup refers to the same identifier. ## Keep the promise narrow Google says it does not guarantee that features consuming structured data will appear in results, and its guide to generative Search says no special schema is needed for those features. Valid markup is an eligibility and interpretation aid. It is not a search treatment you can book. The narrow promise is the useful one. It stops a clean identity graph from being sold as a reputation machine, and it keeps the fakery out: no FAQPage theatre, no invented ratings, no shop markup on an author page. Person entity SEO makes authorship easier to resolve. Authority still has to come from the work, the evidence, and references that deserve to exist. [The Findability Engine](https://lenvanderhof.com/books/the-findability-engine/) owns the longer treatment. The book is in production and not for sale. Cite this:Person entity SEO: a name an engine can attach.Len P. van der Hof. [https://lenvanderhof.com/en/blog/person-entity-seo/](https://lenvanderhof.com/en/blog/person-entity-seo/) · Published 23 September 2026. ## Sources 1. [Len P. van der Hof author profile](https://lenvanderhof.com/en/authors/len-p-van-der-hof/) 2. [How to get cited by ChatGPT](https://lenvanderhof.com/en/blog/how-to-get-cited-2026/) 3. [Citation-readiness audit](https://lenvanderhof.com/en/blog/citation-readiness-audit/) 4. [The Findability Engine](https://lenvanderhof.com/books/the-findability-engine/) 5. [ProfilePage structured data](https://developers.google.com/search/docs/appearance/structured-data/profile-page) · Google Search Central 6. [sameAs](https://schema.org/sameAs) · Schema.org 7. [Optimizing your website for generative AI features on Google Search](https://developers.google.com/search/docs/fundamentals/ai-optimization-guide) · Google Search Central ## Further reading - [Len P. van der Hof](https://lenvanderhof.com/en/authors/len-p-van-der-hof/) - [How to get cited by ChatGPT](https://lenvanderhof.com/en/blog/how-to-get-cited-2026/) - [Citation-readiness audit](https://lenvanderhof.com/en/blog/citation-readiness-audit/) - [The Findability Engine](https://lenvanderhof.com/books/the-findability-engine/) About the author ## [Len P. van der Hof](https://lenvanderhof.com/en/authors/len-p-van-der-hof/) Entrepreneur, AI Innovator and Venture Builder Len P. van der Hof builds practical AI systems, digital ventures and evidence-informed tools for founders. ```json { "@context": "https://schema.org", "@graph": [ { "@type": "Person", "@id": "https://lenvanderhof.com/#person", "name": "Len P. van der Hof", "alternateName": [ "Len van der Hof", "L.P. van der Hof", "Leendert Pieter van der Hof" ], "honorificSuffix": "MSc", "url": "https://lenvanderhof.com/", "image": [ "https://lenvanderhof.com/photos/len-portrait-1.jpg", "https://lenvanderhof.com/photos/len-portrait-2.jpg", "https://lenvanderhof.com/photos/len-portrait-3.jpg", "https://lenvanderhof.com/photos/len-portrait-4.jpg", "https://lenvanderhof.com/photos/len-speaking.jpg", "https://lenvanderhof.com/photos/len-hero.jpg" ], "jobTitle": "Entrepreneur, AI Innovator and Venture Builder", "description": "Len P. van der Hof, MSc, is a Dutch entrepreneur and AI innovator in Zwijndrecht. He builds ReasonKit, MindSesh, Undominated.ai, books under his name, the fiction imprint LPH98.lifestyle, and technology ventures through LPH98.ventures. Eleven titles in Systems for the Strategic Self are available now, in English and Dutch.", "address": { "@type": "PostalAddress", "addressLocality": "Zwijndrecht", "addressCountry": "NL" }, "alumniOf": { "@type": "CollegeOrUniversity", "name": "Rotterdam School of Management, Erasmus University" }, "knowsAbout": [ "Artificial intelligence", "AI agents", "Agentic AI systems", "LLM routing", "SEO", "Generative engine optimization", "Answer engine optimization", "Venture building", "Founder performance", "Founder psychology", "Evidence-based decision-making" ], "sameAs": [ "https://www.linkedin.com/in/lenvanderhof/", "https://x.com/LenvanderHof", "https://www.youtube.com/channel/UCTG20buKqYYbitqqf7l3zJA", "https://www.instagram.com/Lenvanderhof/", "https://www.threads.com/@lenvanderhof", "https://github.com/Lenvanderhof", "https://huggingface.co/LPH98", "https://www.npmjs.com/~lenvanderhof", "https://www.goodreads.com/author/show/70983905.Len_P_van_der_Hof", "https://www.amazon.com/author/lenvanderhof", "https://www.bol.com/nl/nl/b/len-p-van-der-hof-msc/609879394/", "https://bsky.app/profile/lenvanderhof.com", "https://mastodon.social/@Lenvanderhof", "https://crates.io/users/Lenvanderhof", "https://cursor.com/@Lenvanderhof", "https://medium.com/@Lenvanderhof", "https://gitlab.com/Lenvanderhof", "https://hub.docker.com/u/lenvanderhof/", "https://dev.to/lenvanderhof", "https://www.facebook.com/Lenvanderhof", "https://soundcloud.com/Lenvanderhof" ], "affiliation": [ { "@id": "https://lenvanderhof.com/#publisher" }, { "@id": "https://lenvanderhof.com/#mindsesh" }, { "@id": "https://lenvanderhof.com/#lifestyle" } ] }, { "@type": "WebSite", "@id": "https://lenvanderhof.com/#website", "url": "https://lenvanderhof.com/", "name": "Len P. van der Hof", "description": "Len P. van der Hof, MSc, is a Dutch entrepreneur and AI innovator in Zwijndrecht. He builds ReasonKit, MindSesh, Undominated.ai, books under his name, the fiction imprint LPH98.lifestyle, and technology ventures through LPH98.ventures. Eleven titles in Systems for the Strategic Self are available now, in English and Dutch.", "inLanguage": [ "en", "nl" ], "publisher": { "@id": "https://lenvanderhof.com/#person" } }, { "@type": "Organization", "@id": "https://lenvanderhof.com/#publisher", "name": "LPH98.ventures", "url": "https://lph98.ventures", "founder": { "@id": "https://lenvanderhof.com/#person" } }, { "@type": "Organization", "@id": "https://lenvanderhof.com/#mindsesh", "name": "MindSesh", "url": "https://mindsesh.net", "founder": { "@id": "https://lenvanderhof.com/#person" } }, { "@type": "SoftwareApplication", "@id": "https://lenvanderhof.com/#reasonkit", "name": "ReasonKit", "url": "https://reasonkit.sh", "creator": { "@id": "https://lenvanderhof.com/#person" } }, { "@type": "SoftwareApplication", "@id": "https://lenvanderhof.com/#undominated", "name": "Undominated.ai", "url": "https://undominated.ai", "creator": { "@id": "https://lenvanderhof.com/#person" } }, { "@type": "Organization", "@id": "https://lenvanderhof.com/#lifestyle", "name": "LPH98.lifestyle", "url": "https://lph98.lifestyle", "founder": { "@id": "https://lenvanderhof.com/#person" } }, { "@type": "ImageObject", "@id": "https://lenvanderhof.com/en/blog/person-entity-seo/#primaryimage", "url": "https://lenvanderhof.com/media/generated/blog-hero-person-entity-seo-v1.d13cebcc9af0.wide.webp", "contentUrl": "https://lenvanderhof.com/media/generated/blog-hero-person-entity-seo-v1.d13cebcc9af0.wide.webp", "representativeOfPage": true }, { "@type": "BreadcrumbList", "@id": "https://lenvanderhof.com/en/blog/person-entity-seo/#breadcrumb", "itemListElement": [ { "@type": "ListItem", "position": 1, "name": "Home", "item": "https://lenvanderhof.com/" }, { "@type": "ListItem", "position": 2, "name": "Blog", "item": "https://lenvanderhof.com/en/blog/" }, { "@type": "ListItem", "position": 3, "name": "SEO, GEO and AEO", "item": "https://lenvanderhof.com/en/blog/category/seo-geo-aeo/" }, { "@type": "ListItem", "position": 4, "name": "Person entity SEO: a name an engine can attach", "item": "https://lenvanderhof.com/en/blog/person-entity-seo/" } ] }, { "@type": "WebPage", "@id": "https://lenvanderhof.com/en/blog/person-entity-seo/#webpage", "url": "https://lenvanderhof.com/en/blog/person-entity-seo/", "name": "Person entity SEO: a name an engine can attach", "description": "Person entity SEO reduces identity ambiguity: one visible author profile, one stable Person @id, Article author markup that points at it, and sameAs links that unambiguously identify the same person. It improves machine-readable consistency. It does not buy a knowledge panel.", "isPartOf": { "@id": "https://lenvanderhof.com/#website" }, "primaryImageOfPage": { "@id": "https://lenvanderhof.com/en/blog/person-entity-seo/#primaryimage" }, "breadcrumb": { "@id": "https://lenvanderhof.com/en/blog/person-entity-seo/#breadcrumb" }, "inLanguage": "en-GB" }, { "@type": "BlogPosting", "@id": "https://lenvanderhof.com/en/blog/person-entity-seo/#article", "mainEntityOfPage": { "@id": "https://lenvanderhof.com/en/blog/person-entity-seo/#webpage" }, "headline": "Person entity SEO: a name an engine can attach", "description": "Person entity SEO reduces identity ambiguity: one visible author profile, one stable Person @id, Article author markup that points at it, and sameAs links that unambiguously identify the same person. It improves machine-readable consistency. It does not buy a knowledge panel.", "datePublished": "2026-09-23T07:00:00.000Z", "author": { "@id": "https://lenvanderhof.com/#person" }, "publisher": { "@id": "https://lenvanderhof.com/#person" }, "image": [ "https://lenvanderhof.com/media/generated/blog-hero-person-entity-seo-v1.d13cebcc9af0.square.webp", "https://lenvanderhof.com/media/generated/blog-hero-person-entity-seo-v1.d13cebcc9af0.landscape.webp", "https://lenvanderhof.com/media/generated/blog-hero-person-entity-seo-v1.d13cebcc9af0.wide.webp" ], "articleSection": "SEO, GEO and AEO", "inLanguage": "en-GB" } ] } ```