Person Schema: Connect Real Authors to Their Work

Establish whose record you are describing

Begin with the real person responsible for the work. An author, reviewer and publisher may be different parties, even when a template currently uses one name for all three. Decide the role before writing structured data. If an article is produced by an organisation without an individual byline, do not invent a person to satisfy an assumed SEO requirement. If a real editor takes responsibility for assisted writing, describe that contribution honestly in the visible attribution.

The Schema.org Person definition provides a vocabulary for describing people. It is not a checklist requiring every possible property. A minimal record with an accurate name and public profile can be more useful than a rich record containing guessed affiliations. The visible author biography should explain the person's relevant work in language readers understand. Structured fields should encode that established identity, rather than introduce claims that appear nowhere else on the site.

Use one stable person identifier

A person can author many articles, so avoid generating an unrelated identity record on each page. Choose a stable identifier under a URL you control and reference it consistently. An author profile address with a person fragment can distinguish the person from the page describing them. Keep the identifier stable when the displayed biography changes. A changed job title should update an attribute, not create a different author who happens to have the same name.

In an illustrative library, Maya Chen writes three technical guides. Each article can reference the same person identifier, while the profile contains the fuller description. If another contributor has the same name, give them a separate identity and profile based on their actual participation. Do not merge authors solely because their names match. Entity SEO explains the broader ambiguity problem, including meaningful distinctions such as organisation, role and relevant public work.

Select properties based on evidence and relevance

Name, URL and a suitable image often cover the core public identity. A job title, affiliation or professional identifier may add useful context if it is accurate and appropriate to publish. Confirm the wording with the person and supporting material. Avoid transforming experience into a credential: writing several articles about a subject is not equivalent to holding a professional qualification. A schema property that accepts an award does not make an unsupported award claim legitimate.

Keep privacy proportional to the task. A professional author record rarely needs a home address, birthday or private contact details. Public identity is not an invitation to collect every biographical fact available online. Choose information that helps readers identify the contributor and assess their role. If a person uses a professional name consistently, do not expose a different name merely to make the record appear more complete. The useful record is the one that describes the public contribution accurately and respectfully.

Make identity references genuinely identify the person

External profile links should point to a specific page clearly belonging to the same person. A broad search result, company homepage or article about someone with a similar name is not enough. Check the destination, current affiliation and other identifying details before adding it. A profile can become stale or change ownership, so these links deserve periodic attention alongside ordinary citations. You do not need a long list; one clear reference may be more informative than several ambiguous ones.

Schema.org defines sameAs as an unambiguous identity reference. Use it for that purpose, not as a place to list admired experts, customers or authoritative websites in the author's field. An illustrative programmer's contribution to a project may support a work claim through a contextual link, while the programmer's verified profile can serve as an identity reference. Separating evidence links from identity links keeps the structured record precise and avoids implying that related organisations are the person.

Connect the profile and the article appropriately

A profile page focuses on the person; an article focuses on a subject and identifies its author. Those are different page roles. Google's ProfilePage documentation describes the use of a profile page whose main entity is a person or organisation associated with the site. Do not label every article as a profile simply because it includes a biography. Use the page's main purpose to choose its representation and keep author references consistent across the publication.

The knowledge graph guide explains how separate entities can connect without duplication. In a practical content system, the article record stores an author identifier, and the author record supplies the visible byline and structured identity. This reduces accidental mismatches when a display name changes. It also makes coauthorship manageable: each actual contributor can have their own record and relationship, instead of compressing several names into one fictional Person object.

For coauthored work, keep the visible and structured author lists aligned. An editor who only corrected punctuation should not automatically become a coauthor, while a contributor who supplied substantial analysis should not disappear because the template accepts only one identifier. Resolve the editorial attribution first, then adapt the data model. Technical convenience should not decide whose contribution readers are allowed to see.

Validate truth separately from syntax

Parse the JSON-LD and inspect any available validation output, but do not stop at a clean result. Confirm that the named person exists, the profile is accessible and the article attribution matches the work performed. Look for template defaults that assign every article to the site founder or retain a former contributor's details. These are editorial errors that a syntax validator cannot detect. A valid URL can still identify the wrong person, and a well formed credential can still be false.

Check what the deployed page actually emits. Multiple plugins or components may produce conflicting Person records with different names, images or identifiers. Consolidate the source of truth rather than adding another block to override the others informally. During technical release checks, inspect a representative authored article and its profile together. The pair should tell a coherent story about the person and their contribution, including a clear distinction between authorship and any review that genuinely took place.

Handle career changes without rewriting history

An author's current role can change while their authorship remains a historical fact. Update the profile to describe current information accurately, and retain relevant past experience with dates or clear wording where useful. Do not make every older article imply that the person held their present title at the time of writing. If a contributor leaves the publisher, consider retaining a public profile that explains the historical relationship rather than deleting the identity behind existing bylines.

Agree who owns updates and how contributors can report mistakes. Content governance can assign responsibility for profile facts alongside article maintenance. Remove unverified claims when evidence is unavailable, and keep the biography focused on the subjects the person actually contributes to. Person schema works best as a faithful representation of that modest, inspectable record. Its value is consistency and clarity, with expertise established through real work and evidence rather than through the number of properties supplied.

Start with a truthful minimal Person record

This example describes Vithurs using the public identity and profile already visible on this website. The fragment identifies the person; the profile URL identifies the page about that person. There is no guessed qualification, award, employer or social account. A similarly small record is an appropriate starting point when a publisher has little verified biographical information.

Place the JSON within a script element whose type is application/ld+json. Reference the stable person identifier from an Article author field only when that person actually authored the work. The King of AEO library identifies its organisation as the publisher and article author, while identifying Vithurs as the founder of the project. Those distinct roles should remain accurate even when the brand name is strongly associated with the person.

{
  "@context": "https://schema.org",
  "@type": "Person",
  "@id": "https://thekingofaeo.com/king-of-aeo#person",
  "name": "Vithurs",
  "url": "https://thekingofaeo.com/king-of-aeo"
}

Sources and further reading

• Schema.org PersonDefines properties for describing a person, including name, URL and affiliations.
• Schema.org sameAssameAs identifies an unambiguous reference to the same entity.
• Google ProfilePage structured dataProfilePage describes a page focused on a person or organisation associated with the site.