ProfilePage schema for an author's public profile
Connect an author profile to the right Person entity and published work. Check affiliation, identity links, and duplicate records before adding ProfilePage markup.
By Crawlito · 5 min read
In short
- Google's ProfilePage feature describes a single person or organization affiliated with the website.
- The profile page and its mainEntity identify different things.
- Stable author identifiers help connect bylines and profiles through name or URL changes.
On this page
Use ProfilePage for a page focused on a single person or organization affiliated with the site, and identify that subject through mainEntity. For an author profile, connect the same person to accurate article bylines and visible biographical information. Verify the relationships in the actual public output before adding more identity links. Google’s ProfilePage documentation
Confirm what the profile page represents
An author page should tell a reader who contributed to the publication and what they did. A staff writer, community contributor, or official organization account can each have an appropriate profile. A general article about a famous person has a different purpose. Google's content guidelines require the profile's subject to be affiliated with the overall website.
Open the public page and identify its primary subject from the heading, biography, portrait, and linked work. A page combining several staff biographies is a team directory. Give each profile a clear individual destination if the publication needs one. The directory can link to those profiles without claiming that the entire page represents one person.
Check the byline role. Writing, reviewing, editing, and conducting an interview are different contributions. A migration that assigns every article to the site's administrator can obscure the actual author even if the visible author name was retained in a paragraph. Resolve authorship using the publisher's records and editorial owner. The author page guide covers the information readers need.
Distinguish the page from the person
The profile page has a URL and page-level metadata. Its main entity is the person or organization it describes. Give the person a consistent identifier within your structured graph so references from articles can point to the same entity. A fragment identifier under the profile URL is one practical convention when it fits the site's existing markup.
{
"@context": "https://schema.org",
"@type": "ProfilePage",
"url": "https://example.com/authors/river-lane",
"mainEntity": {
"@type": "Person",
"@id": "https://example.com/authors/river-lane#person",
"name": "River Lane",
"url": "https://example.com/authors/river-lane"
}
}This fictional example shows the relationship only. Add biographical fields, dates, or activity counts when the publisher has accurate information and the fields describe what is visible or supported. A profile creation date should not be guessed from the latest site deployment. An article count should have a defined meaning and update with the actual publication records.
Inspect existing graph nodes before adding a second person definition. A theme may already create an author node that article templates reference. Extend the appropriate node and preserve useful stable identifiers. The JSON-LD guide helps locate graph arrays and repeated entities.
Connect bylines to the same identity
Choose three articles attributed to the author, including an older one and a recently published one. Follow the visible byline link and inspect the article's author data. Confirm that the name, profile destination, and role match the person described on the profile. A shared display name alone cannot distinguish two contributors with the same name.
If a profile URL changes, keep the old link working through the publication's normal redirect process and update generated references. Decide how stable identifiers are maintained within the existing graph convention. An internal author ID can remain stable even when a person changes their public name or profile slug. Avoid creating a new apparent author merely because a URL or display name changed.
Check imported work for attribution shortcuts. A CMS can assign every imported post to the user who ran the import. The visible text may still credit the original writer, creating a mismatch with the generated data. Repair the record that controls both outputs where possible, and validate the imported subset independently. The article schema guide explains how author information fits into the article entity.
Add identity links with evidence
Use identity references that actually belong to the person or organization. A public professional profile confirmed by the contributor is stronger evidence than a search result with a matching name. Review destination pages for consistent identity and current ownership. Keep a record in the editorial system of who supplied or confirmed each link.
A publisher should respect the contributor's chosen public identity and privacy preferences. A pen name or account handle can be the correct public name when that is how the contributor publishes. The goal is a coherent public profile, supported by the person's own publication relationship. Adding unrelated personal information does not make the article easier to evaluate.
If the profile includes recent work, link to the real items and keep their attribution accurate. A feed that lists every article in the department can make the profile appear to claim work by colleagues. Define whether the list means authored, reviewed, or edited, and label it so a visitor can understand the relationship. Optional activity counts should follow that same definition.
Test a profile update across the publication
Make a representative profile change in a preview or controlled release and inspect the profile, a recent article, an old article, and the author directory. A component may read from cached author data while another reads the current account record. This can leave a changed name or portrait inconsistent across public pages even when the CMS editor looks correct.
Validate the published profile with the current supported structured data tools. Inspect which entity they identify as the main subject, then compare the result with the visible page. Syntax validity cannot confirm that a portrait belongs to the named author or that a linked external account is theirs. Keep those as explicit editorial checks.
Test an anonymous request. A profile page that loads only for logged-in community members has a different public availability from an article byline that anyone can open. If the publication intends a public author profile, ensure the linked destination provides that information without requiring access the reader does not have.
Retain a small acceptance record with the author ID, public profile URL, sampled bylines, and the relationship verified. When the next theme or account migration occurs, use that sample to detect incorrect joins before the whole archive inherits the wrong identity.
Test two contributors who share a display name
Create or select two authorized profile fixtures with the same public name but different internal author IDs and work histories. Generate one article for each and inspect the byline URL and structured identifier. A join based on the display name can silently combine their work even when the author directory lists two separate profiles.
Repeat the test after changing one display name while preserving its internal identity. Existing bylines should continue to credit the right contributor according to the publisher's intended policy. Review the portrait and biography as well as the link. These fields can be cached or joined independently, producing a page with one person's name and another person's image. A stable identity check across those elements is a concrete way to catch the mistake before it reaches a large archive.
Frequently asked questions
Can an organization have a ProfilePage?
Google documents a single affiliated person or organization as the main entity. Use the entity type that accurately represents the public account or profile.
Does a team directory qualify as one person's profile?
A directory describes multiple people. Individual profile pages can provide the focused subject and links needed for each contributor.
Should I include every external account with the same name?
Verify ownership and relevance. A matching name alone is insufficient evidence that two profiles describe the same person.
Check an author profile and a byline
Run the free page check on the public profile, then inspect an article linked to it. Confirm that the visible attribution and structured identity agree.
Filed under Structure and schema. Topics: structured-data, authors, google