Person schema and ProfilePage schema: which one an author page needs

Person describes a human; ProfilePage says a page is about that human. What Google requires for each, how sameAs works, and a full JSON-LD author page example.

· Updated 7 min read

Person schema describes a human. ProfilePage schema says that a page is about one person or one organization. An author page needs both: a ProfilePage whose mainEntity is a Person. An article needs only the Person, inside its author property.

What is the difference between Person and ProfilePage?

They are different kinds of thing. Person is an entity: a name, a description, a photo, links to that person's other profiles. ProfilePage is a type of web page, and its job is to point at the entity the page is about.

PersonProfilePage
DescribesA humanA page about a human or an organization
Used onAuthor pages, and inside author on every articleAuthor pages, "About me" pages, user profiles
Required by GooglenamemainEntity (a Person or an Organization)
On its ownValid inside an ArticleSays nothing without a mainEntity

The common mistake is to treat them as interchangeable. A ProfilePage with no Person inside it describes a page about nobody. A bare Person on an author page does not say the page is a profile.

When does Google use ProfilePage markup?

Google's documentation says ProfilePage markup is for sites where creators, people or organizations, share first-hand perspectives. It lists author pages on news sites, "About me" pages on blogs, employee pages on company sites and user profiles on forums and social sites as valid uses. A store's home page is not one, and neither is a review site's page about an organization that does not own that page (Google Search Central).

Google says it uses the markup to understand and highlight creator information and to tell creators with similar names apart, in features such as Perspectives and Discussions and Forums. That is recognition, not ranking. Nothing in the documentation says the markup moves a page up, and correct markup does not earn an AI citation by itself.

Which properties does Google require?

Very few. Checked against Google's documentation on 17 November 2026:

TypePropertyStatusWhat it holds
ProfilePagemainEntityRequiredThe Person or Organization the page is about
ProfilePagedateCreated, dateModifiedRecommendedWhen the profile was created and last edited by a human
PersonnameRequiredThe name the creator is known by
PersonalternateNameRecommendedA public handle
PersonidentifierRecommendedThe profile's unique ID on your site
PersondescriptionRecommendedA byline or credential
PersonimageRecommendedA profile photo
PersonsameAsRecommendedLinks to the person's profiles elsewhere
PersoninteractionStatistic, agentInteractionStatisticRecommendedFollower counts and the profile's own activity, on platforms that have them

If you do not know whether an account belongs to a person or an organization, Google's guidance is to use Person.

What does sameAs do?

sameAs lists URLs of other pages that are about the same person: a LinkedIn profile, a profile on another publication, a personal site. It is how a name on your site is tied to the same human elsewhere, which matters most for a common name.

Link only profiles that belong to that person and that say so themselves. A sameAs link to a profile that does not mention your site, or that belongs to someone else with the same name, weakens the claim it was meant to support.

What does a complete author page look like?

One ProfilePage, one Person inside it, with an @id the rest of the site can refer to:

{
  "@context": "https://schema.org",
  "@type": "ProfilePage",
  "dateCreated": "2025-03-10T09:00:00Z",
  "dateModified": "2026-11-17T09:00:00Z",
  "mainEntity": {
    "@type": "Person",
    "@id": "https://example.com/authors/jane-doe#person",
    "name": "Jane Doe",
    "alternateName": "janedoe",
    "description": "Structured data engineer. Writes about schema markup and search.",
    "image": "https://example.com/images/jane-doe.jpg",
    "url": "https://example.com/authors/jane-doe",
    "sameAs": [
      "https://www.linkedin.com/in/janedoe-example",
      "https://github.com/janedoe-example"
    ]
  }
}

Everything in the markup must also be visible on the page. A job title, a photo or a profile link that appears only in the JSON-LD describes a page that does not exist.

How does the Person go inside an article?

Set the article's author to a Person object, not a plain string, and point it at the author page:

{
  "@context": "https://schema.org",
  "@type": "Article",
  "headline": "How structured data is read",
  "datePublished": "2026-11-17",
  "author": {
    "@type": "Person",
    "@id": "https://example.com/authors/jane-doe#person",
    "name": "Jane Doe",
    "url": "https://example.com/authors/jane-doe"
  }
}

The shared @id tells a parser that the author of the article and the subject of the profile page are one entity. Google's own example links an article's author to a profile this way. The article side is covered in our Article schema guide.

How do you check it?

  1. Run the author page through Google's Rich Results Test. It reports whether the ProfilePage was parsed and which properties are missing.
  2. Run it through the Schema Markup Validator for errors against the schema.org vocabulary that Google's test does not report.
  3. After release, use URL Inspection in Search Console on one author page to see the markup Google read from the live page.

Or paste the URL into our free schema check, which reads the JSON-LD on a page and lists what is missing.

Why we wrote this page

In Search Console for citelity.com, in the 28 days to 14 November 2026, "author schema" had 47 impressions at an average position of 24.9, "person schema" 26 at 33.3, "person schema guide" 15 at 14.2 and "schema profilepage" 13 at 11.3. Google showed all of them our general Article schema guide, which covers authors in one section. None had a page that answered it directly. This is that page; whether it changes those positions is something we will measure, not something we promise.

Do I need both Person and ProfilePage schema?
On an author or profile page, yes: a ProfilePage whose mainEntity is a Person. Inside an article you need only the Person, as the value of the author property.
What properties does ProfilePage schema require?
Google requires one: mainEntity, set to a Person or an Organization. dateCreated and dateModified are recommended. The Person inside it requires a name; alternateName, identifier, description, image and sameAs are recommended.
What is sameAs used for in Person schema?
It lists URLs of the same person's profiles elsewhere, such as LinkedIn or a profile on another publication. It ties the name on your site to the same human on other sites. Link only profiles that belong to that person.
Does ProfilePage schema improve rankings?
Google's documentation does not say so. It says the markup helps Google understand and highlight creator information and tell creators apart. Treat it as making identity readable, not as a ranking change.
Can ProfilePage be used for a company?
Yes. mainEntity accepts an Organization as well as a Person. Google's examples include employee pages and organization profiles, but not a store's home page.
Should the author in Article schema be a string or a Person?
A Person object, with at least a name and ideally a url pointing to the author page. A shared @id between the article's author and the profile page's mainEntity says they are the same entity.

Sources