Structured Data for Personal Brands: Person vs. ProfilePage vs. Article

Why the choice matters

Schema markup tells search engines and AI crawlers what kind of thing a page fundamentally is. Marking a biography page as a generic Article, or a blog post as a ProfilePage, doesn't just miss out on rich results — it actively mis-describes the content to every system trying to understand it, including the LLM-based answer engines this site's robots.txt explicitly welcomes.

Person schema — the entity itself

Person schema describes the individual as an entity independent of any single page: name, jobTitle, credentials, sameAs links to verified profiles, knowsAbout. It should have one stable @id used consistently across every page that references the person, so search engines resolve all those references back to the same entity rather than treating each page as describing someone slightly different.

ProfilePage — when a page is about the person

A page whose primary purpose is describing a specific person — a bio, an authority page, an "about" page — is more accurately typed as ProfilePage than a bare Article, with mainEntity pointing at the Person node. Google's own guidance treats these as a distinct pattern from editorial content, and getting this right is part of why this site's own /authority page uses ProfilePage rather than Article.

Article / BlogPosting — when a page is a piece of writing

A page whose primary purpose is delivering a standalone piece of writing — like this one — is correctly typed as Article or BlogPosting, with author pointing at the Person node and publisher pointing at the Organization node. The distinction that trips people up: the Article is about a topic, authored by a person; the ProfilePage is about the person, who happens to have written things. This post is both an Article in its own right and a supporting reference for the ProfilePage.

How this site's graph is actually structured

Every page on this site emits a single linked @graph rather than isolated schema blocks: a stable Person node, an Organization node for Arcetis, a page-specific WebPage node, and — depending on the page — a ProfilePage or Article node pointing back to Person via mainEntity or author. Stable @id anchors mean a crawler encountering this post and the /authority page separately can still resolve them as describing the same underlying person and organization.

The practical takeaway

If a personal-brand site only has Article schema and no Person or Organization entity behind it, every piece of content is an island. The schema type isn't a formality — it's the mechanism that lets a body of separate pages accumulate into one recognized entity. See Entity SEO: What It Actually Means Beyond Schema Markup for what has to happen beyond markup for that recognition to actually occur.

Related reading