ProfilePage structured data for a person: required properties and rules
. Compiled by the People Engine Optimization desk from the sources listed at the end of this page.
ProfilePage markup tells Google that a page is about one creator, a person or an organization. It requires mainEntity, a Person or Organization, with a name. Google lists dateCreated, dateModified, image, description and sameAs as recommended. The page must focus on one person tied to the site, and Google does not guarantee a rich result.
ProfilePage properties as Google lists them
| Property | Where it goes | Status in Google's documentation |
|---|---|---|
| mainEntity | On ProfilePage | Required. A Person or Organization the page is about |
| name | On the Person or Organization | Required. alternateName can stand in if name is missing |
| dateCreated | On ProfilePage | Recommended, in ISO 8601 |
| dateModified | On ProfilePage | Recommended, ideally only for human-made profile edits |
| alternateName | On the Person or Organization | Recommended |
| description | On the Person or Organization | Recommended |
| identifier | On the Person or Organization | Recommended |
| image | On the Person or Organization | Recommended. Crawlable, representative, not a placeholder |
| sameAs | On the Person or Organization | Recommended |
| interactionStatistic | On the Person or Organization | Recommended, for platform-specific counts such as follows or posts |
Download this table (CSV). Free to quote with a link to this page.
What ProfilePage markup is for
Google's documentation says ProfilePage markup is for sites where creators, people or organizations, share first-hand perspectives. It helps Google understand the creators who post in an online community and can surface their content in results, including the Discussions and Forums feature. It is not a Knowledge Panel tool. The documentation does not mention knowledge panels at all.
Which pages qualify
The primary focus of the page must be one person or organization affiliated with the website. Google's valid examples include forum user profiles, news author pages, blog About Me pages and employee pages. Store home pages and organization review sites are not valid. A personal site with a page that is about its owner, and nothing else, fits the description. A home page that sells services does not.
A small example
On a page about one author, the markup holds a ProfilePage with a mainEntity of type Person. The Person carries the name, a short description, an image and a sameAs list of that person's profile pages elsewhere. The ProfilePage carries dateCreated and dateModified. Google asks that dateModified reflect only human-made changes to the profile, so do not let a site tool update it on every build.
Image rules
Images must be crawlable, indexable, representative of the content and in a supported format. Placeholder images are not allowed. Google recommends several high-resolution images in 16x9, 4x3 and 1x1 ratios. A portrait that matches the one used on your other pages also helps the photo on a panel stay consistent.
Recent activity and statistics
Google supports interaction types such as follows, likes, posts, reshares and bi-directional friendships. It says to include only platform-specific statistics. If a profile page shows recent activity, those objects can point back to the profile using the id property and hasPart. A personal site with no community can skip this part.
What it does not do
Google says it does not guarantee that structured data will produce a rich result. The documentation says nothing that connects ProfilePage markup to a knowledge panel or to an entry in the Knowledge Graph. Treat it as a clean statement of who a page is about, readable by Google and by any other system that reads structured data. For a wider look at what feeds a panel see who actually gets a knowledge panel.
Check it before you rely on it
Google provides the Rich Results Test and the structured data reports in Search Console. Run the page through the test, fix missing required properties and watch the report after Google recrawls. Keep the visible text of the page in step with the markup. Markup that says something the page does not say breaks Google's general structured data guidelines.
Where a build fits
A $3,000 build over 60 to 90 days includes one page that states the facts about you, and markup like this is part of making that page easy to read. A panel tends to appear on the bare name 6 to 12 months after, and nobody can guarantee one.
A fact from this site's own records
Our home page reports seven real people, with three where the name already works. A common first job is one page that is plainly about the person, which is exactly what ProfilePage describes.
Questions people ask
What is ProfilePage structured data?
It is markup that tells Google a page is about one creator, a person or an organization, with a mainEntity of type Person or Organization.
What does ProfilePage require?
A mainEntity that is a Person or Organization, and a name on that entity. alternateName can fulfil the name requirement.
Will ProfilePage markup give me a knowledge panel?
Google's documentation does not say so and does not guarantee a rich result. It mentions Discussions and Forums, not knowledge panels.
Can I put it on my home page?
Only if the home page is mainly about one person tied to the site. Google says store home pages are not valid.
What should dateModified contain?
Google says it should ideally reflect only human-made changes to the profile, not automatic updates.
Is this different from Person schema?
ProfilePage describes the page and wraps a Person or Organization as its main subject. The Person carries the facts such as name, image and sameAs.
Read next
- How to change the photo on a Google knowledge panel
- Who actually gets a knowledge panel
- Knowledge graph vs knowledge panel
- How to find your KGMID
- Does AI read my website