usdigitalmarketingindex.com SEO
When should an author profile page use ProfilePage structured data?
Updated November 15, 2026
When the page is about one person or one organization connected with the site, and that subject is the main thing on the page. Google’s documentation describes the markup as “designed for any site where creators (either people or organizations) share first-hand perspectives” (Google’s profile page structured data documentation). An author page on a publication fits: it presents a single writer, and the writer’s articles link to it. A team page listing twelve people does not, and neither does a page whose real subject is the company. The markup states who the page is about. It adds no credentials and creates no authority that the page itself does not show.
Profile-page purpose
A profile page answers the question of who someone is. For an author, that means a name, a short biography, perhaps a photograph, and the work they have published on the site.
The documentation sets the condition that the cases below turn on: “The primary focus of the page must be a single person or organization that is affiliated with the overall website”.
| Page | Fits ProfilePage? | Reason |
|---|---|---|
| A staff writer's author page | Yes | One person, affiliated with the site |
| A contributor's page on a multi-author blog | Yes | One person, affiliated as a contributor |
| An "about the company" page for the publisher | Yes, with an Organization as the subject | One organization, the site's own |
| A team page listing every author | No | No single subject |
| A page about a public figure the site writes about | No | The subject is not affiliated with the site |
| An article with an author box at the foot | No | The article is the main content; the author box is secondary |
| A tag archive that happens to show an author name | No | An archive, not a profile |
Person and profile relationship
Two entities are involved, and the markup keeps them apart: the page, and the person the page describes. ProfilePage is the page. Its required property, mainEntity, holds the Person or Organization the page is about.
A small example. The name, addresses, and dates are placeholders.
{
"@context": "https://schema.org",
"@type": "ProfilePage",
"dateCreated": "2024-02-10T09:00:00+00:00",
"dateModified": "2026-09-01T11:20:00+00:00",
"mainEntity": {
"@type": "Person",
"@id": "https://www.example.com/authors/jordan-ellis#person",
"name": "Jordan Ellis",
"description": "Staff writer covering home heating.",
"image": "https://www.example.com/images/jordan-ellis.jpg",
"sameAs": [
"https://social.example.net/jordanellis"
]
}
}
The documentation lists mainEntity as the one required property of the page and recommends the two dates. For the person it asks for a name and suggests further properties such as a description, an image, and sameAs links to the person’s other profiles.
The connection to articles runs through the author property. Google’s Article documentation says of the author’s URL: “If the URL is an internal profile page, we recommend marking up that author using profile page structured data” (Google’s Article structured data documentation). So the pattern is:
- each article names its author and gives the author page as the author’s URL;
- the author page carries ProfilePage markup whose mainEntity is that same person.
Using one @id for the person in both places states that they are the same individual.
Content and identity requirements
The markup describes the visible page. Google’s structured data guidelines say “Don’t mark up content that is not visible to readers of the page” (Google’s structured data general guidelines).
| Property | Condition |
|---|---|
| name | The name shown on the page |
| description | Matches the visible biography |
| image | The photograph shown on the page |
| sameAs | Profiles that belong to this person and that the person or publisher can confirm |
| jobTitle, credentials, affiliations | Only what is true and stated on the page |
| dateCreated, dateModified | Real dates for the profile |
What not to do:
- Do not add a qualification, title, or employer to the markup that the person does not hold.
- Do not link sameAs to a profile belonging to someone else with the same name.
- Do not mark up a pen name as though it were a verified individual with invented details.
- Do not put ProfilePage on every page of the site through a template.
A pseudonymous or house byline can have a profile page if the site is open about what it is. The markup then says what the page says, and no more.
Meeting these requirements makes a page eligible and no more. Why correct markup can still produce nothing in the results is covered in the guide to why valid structured data might fail to produce a rich result.
Validation and maintenance
- Test the page in the Rich Results Test and confirm that profile page markup is detected without errors.
- Check that mainEntity is present and holds a single Person or Organization.
- Compare each property with the visible page.
- Open an article by the author and confirm that its author URL is this page.
- In Search Console, review the profile page report, where one is shown for the property, for errors across author pages.
Maintain it as people change.
| Event | Action |
|---|---|
| Biography updated | Markup description and dateModified follow |
| Author changes name | Page, markup, and article bylines updated together |
| Author leaves | Keep the page if their articles remain, with accurate status; do not delete the identity behind published work without redirecting or reassigning |
| Profile on another site closed | Remove it from sameAs |
| Template change | Retest a sample of author pages |
As with every structured data type, correct markup makes the page eligible for the ways Google may use it and does not promise a particular display.
Decision summary:
| Situation | Use ProfilePage? |
|---|---|
| One author, own page, affiliated with the site | Yes |
| Publisher's own organization page | Yes, with Organization as mainEntity |
| Several people on one page | No |
| Subject not connected to the site | No |
| Author information inside an article | No; that is the article's author property |
The article side of the relationship, including which properties Google recommends for bylines and dates, is set out in the guide to when a publisher should add Article structured data.
The test: one page, one affiliated person or organization as its main subject, and markup that repeats only what the page shows.
Add your comment to this answer