Do your author bio pages identify themselves as profile pages to AI?
Confirms each author or contributor page is tagged as a ProfilePage with the person it represents.
What this signal tests
We check whether your author bio and contributor pages declare themselves as a ProfilePage in structured data, with the main subject being a Person entity that includes a name, image, and links to external profiles. This is the page-level equivalent of identifying an article's author; here, the bio page itself becomes a discoverable profile.
Why it matters for your visibility in AI
AI tools and search engines treat ProfilePage-tagged pages as authoritative biographical sources. When your author Jane Smith is named in another piece of content, an AI agent can follow back to her ProfilePage to verify identity and expertise. Without the markup, the bio page is just another HTML page, indistinguishable from a generic about page. This matters most for sites that publish under named contributors, including news outlets, professional services, and consultancy blogs. Strong author profiles compound: every article your team writes becomes more credible because the author identity is verifiable. Sites that skip ProfilePage markup leave that credibility on the table.
Pass criteria at a glance
| Criterion | Passes when |
|---|---|
| Valid ProfilePage on author pages. |
How we test it
We crawl your author or team URLs, typically under paths like /authors/ or /team/, and look inside their JSON-LD for a type of ProfilePage. We then check that the mainEntity is a Person or Organization with at least a name. Bonus fields like image, sameAs, and interactionStatistic improve the page's discoverability in Google's profile features but are not required to pass.
Show technical detection method
@type ProfilePage with mainEntity Person/Organization with name on author URLs.
If your site fails: how to fix it
- Identify your author bio template. Most CMS platforms have one, sometimes called author archive, team member, or contributor profile.
- Add a JSON-LD block to that template declaring the page as a ProfilePage with mainEntity referencing the person it describes.
- Populate the Person fields: name, alternateName for nicknames, image (a headshot URL), and sameAs links to LinkedIn, ORCID, GitHub, or other authoritative profiles.
- If the author has public engagement metrics such as follower counts, you can include them as interactionStatistic entries. This is optional but helps Google surface the profile in its profile features.
- Validate one URL in Google's Rich Results Test under the Profile Page test type.
Quick facts
| Maturity | ESTABLISHED |
|---|---|
| Weight | medium |
| Category | Structured Data |
Primary sources
Related signals
Frequently asked questions
Do I need a separate bio page for every author?
Yes, ideally. A shared team page is acceptable but weaker. A dedicated profile page per author gives each person their own URL, which AI tools can link to and verify. Even a short bio page with name, photo, and a couple of paragraphs is enough.
What if my authors are pseudonymous or use pen names?
ProfilePage works for pseudonyms. Use the pen name as the name field and the legal name (if disclosed elsewhere) as alternateName. If the pen name is the only public identity, that is fine; the markup helps AI tools attribute content consistently, regardless of whether the name behind it is legal.
Does this help with the EEAT signals Google talks about?
Yes. EEAT (experience, expertise, authority, trust) is heavily author-driven, and ProfilePage is the structured-data way of declaring author identity. Combined with sameAs links to verifiable external profiles, it gives Google and other AI tools a concrete trail to confirm who is behind your content.
Run your own scan
Run a free scan and see how your site grades across all 155 AI-readiness signals.