Profile pages and author identity
Profile page markup is meant for sites where creators share first-hand perspectives. It describes the person or organisation posting, their username, their accounts elsewhere and their activity. Other markup types point to it, notably article markup and discussion markup.
A page describing somebody, not a subject
Profile page markup is designed for any site where creators, people or organisations, share first-hand perspectives; it helps the engine understand who posts in an online community.
officialSource : Google Search Central, “Profile page (ProfilePage) structured data”
The phrasing matches discussion markup: first-hand perspectives. The two are designed together, and the second only makes sense where the first exists — a profile page describes somebody who wrote something somewhere.
Other markup points to profile pages: articles and recipes have authors, and several authors often appear in discussion forum and Q&A page markup.
officialSource : Google Search Central, “Profile page (ProfilePage) structured data”
That is this markup’s real role: to be a destination. An article has an author, a discussion has participants, and those mentions gain from pointing at a page describing the same person the same way everywhere.
What the card contains
The page declares as its main entity the person or organisation described, with a name, an alternate name such as a username, an identifier, a description and an image.
officialSource : Google Search Central, “Profile page (ProfilePage) structured data”
A name, an alternate name, an identifier, a description, an image. The alternate name deserves underlining: the documentation explicitly provides for the username, which matches what the rater guidelines write about forums — a page can reach the highest ratings with participants identified only by a username.
The property provided for other online presences links a profile to the addresses where the same person or organisation is found elsewhere.
officialSource : Google Search Central, “Profile page (ProfilePage) structured data”
That property is the point of contact with another subject on this site: reputation is looked for elsewhere than on the site. Declaring where the same person is found is not a declaration of authority, it is a pointer.
Two families of counters are provided: one describing what the community does towards the profile, follows or likes, and one describing the creator's own activity, such as the number of posts written.
officialSource : Google Search Central, “Profile page (ProfilePage) structured data”
The published example carries a creation date and a modification date for the profile, in timestamped form.
officialSource : Google Search Central, “Profile page (ProfilePage) structured data”
The split between the two counter families is more interesting than it looks. What the community does — following, liking — describes popularity. What the creator produces — posts written — describes activity, and that second figure can be checked on the site itself.
Create marked-up author pages for each of your writers: profile markup passes E-E-A-T on to all your articles.
What this markup does not manufacture
This markup makes legible an identity that already exists in a community; it does not manufacture authority, since the rater guidelines ask that experience be read in the posts themselves rather than in their author's card.
hypothesis
The status is that of a reading, and it crosses two documents. The first describes markup that helps understand who posts; the second asks that experience be judged in the posts themselves. We conclude that a well-filled author card describes a person while adding nothing to what they wrote.
Describing a community's authors with profile pages that gather their publications
hypothesis
- Effort
- moderate
- Time to effect
- months
- Risk
- none
- Durability
- structural
The effort lies in the template and in collecting data the site already holds. The delay is long, because a profile’s value depends on what it accumulates over time. The risk is nil. Durability is good: a contributor’s identity changes less often than content does.
What does not work, or no longer works
Generating one profile page per contributor with nothing gathered on it. The page then describes an absence of publications.
Then presenting this markup as a transfer of authority to the articles. No published source treats it as a signal.
Finally, requiring legal identity to fill the card. The alternate name is explicitly provided for, and the rater guidelines write that a username does not block the highest ratings.
Sources
- Profile page (ProfilePage) structured data — Google Search Centralaccessed on
- General Guidelines, version of 11 September 2025, 182 pages — Googleaccessed on
Block revalidated on
Frequently asked questions
- Is this markup for a single-author blog?
- It is described for sites where creators share first-hand perspectives, and it helps the engine understand who posts in an online community. On a blog signed by one person the author page still serves the reader, but the markup targets multi-voice spaces first.
- Can a username appear in the markup?
- Yes, a property is provided for the alternate name, alongside the name. That matches the rater guidelines, which write that a username does not block the highest ratings: the question is not legal identity but the ability to identify who is speaking and find what they wrote.
- Should accounts on other sites be declared?
- The property exists for exactly that: linking a profile to the addresses where the same person is found elsewhere. It is also the point of contact with reputation, which the rater guidelines ask you to seek off the site rather than in what the site says about itself.
- Are follower counts worth anything?
- Two families are provided, and they do not say the same thing: what the community does towards the profile, and what the creator produces. The second describes activity verifiable on the site itself, which makes it harder to inflate than the first.
- Does this markup improve E-E-A-T?
- Nothing supports that claim, and the rater guidelines ask that experience be read in the posts rather than in their author's card. The markup makes an existing identity legible; it creates neither competence nor reputation, and no published source treats it as a signal.