Schema Markup·4 min read

Person Schema for Author Pages: Markup That Builds Trust

Bylines are cheap. Any site can print a name above an article, which is why search engines don't take names at face value. Person markup is the checkable layer underneath the byline: structured data declaring who the author is, what they do, where they work and which profiles confirm it. For writers, consultants and anyone whose name is part of their product, this guide covers the markup, the ProfilePage wrapper for author pages, its relationship to E-E-A-T, and a worked example you can adapt.

Open the free Person Schema Generator All insights

Why the byline needs backup

The verification gap.

The scenario is familiar to anyone publishing under their own name. You've written for years, built real expertise, and your author page is a paragraph of prose that a crawler reads like any other paragraph. Meanwhile sites with invented authors print equally confident bios. From the outside, the two are hard to tell apart.

Person markup narrows the gap with checkable claims. A jobTitle, a worksFor organization, an alumniOf institution and sameAs links to profiles that actually exist form a set of statements a machine can follow and compare. That's the difference between a name and an identity.

Person or ProfilePage?

The wrapper for author pages.

Google documents ProfilePage markup for pages that focus on one person, such as an author page on a news site or an about me page on a blog. Its mainEntity is the Person. In the Person Schema Generator, tick Wrap in ProfilePage (for an author or profile page), then enter the profile page URL and its created and last modified dates.

Leave the box unticked when the Person markup sits on a page about something else, such as a speaker listed on an event page. Either way, put the full block on one page only, the page that represents the person, not on every post.

A worked Person example for an author page

A few properties that establish a professional.

For a privacy consultant who writes about compliance, the core block looks like: {"@type": "Person", "name": "Maria Chen", "jobTitle": "Data Privacy Consultant", "worksFor": {"@type": "Organization", "name": "Clearform Advisory"}, "sameAs": ["https://linkedin.com/in/mariachen", "https://github.com/mariachen"]}.

Each property does work. The jobTitle frames her area, worksFor ties her to an employer that can be checked, and the sameAs array points at profiles where her history is public. The generator adds optional layers on top: description, image, alumniOf as a CollegeOrUniversity, and knowsAbout topics typed as a comma-separated list. Only fields you fill are written, so birth date, gender, email and phone can stay out, and most people should leave them out.

Author markup and E-E-A-T: what it can and can't do

Honest expectations.

The relationship gets oversold, so here's the sober version. E-E-A-T is not a score your markup raises; it's a quality framework Google's systems and raters apply to content and its sources. Person markup doesn't add expertise you lack.

What it does is make existing expertise easier to read. Google's own guidance asks whether content clearly shows who created it and whether background about the author is available. Structured author data answers both questions in a machine-friendly form, and knowsAbout lets you name the topics your published work supports. Think of the markup as filing your credentials rather than claiming them.

Linking Person to Organization, and articles to both

Small graph, strong signal.

The Works for field writes a worksFor property with an Organization holding your employer's name, and if that company publishes its own Organization block, search engines can connect the two. For founders and employees of small firms, this link lets a modest personal profile and the company support each other.

The third corner of the triangle is your articles. Article markup carries an author property; point it at the same name and author page URL where your Person block lives, and every piece you publish points to the same identity instead of scattering weak signals.

Person schema mistakes that blur identity

Ways authors undercut their own markup.

The common failures are worth a checklist:

sameAs links to abandoned profiles or accounts under a different name, which weaken rather than confirm the identity.
A jobTitle that changes with every redesign, leaving Google several conflicting professional claims.
Person or ProfilePage blocks on every article page with slightly different data, instead of one block on the author page.
Pen names and real names marked up as separate, unlinked people when they share a body of work.

Tips that make Person markup pull its weight

Three moves for authors.

Keep one author page per person and let everything reference it; consolidation matters more than volume. Fill Same as with the two to five profiles where your professional history is genuinely visible, and skip the rest.

Revisit the block when your situation changes. A new employer or an updated job title takes a minute to regenerate, and if you use the ProfilePage wrapper, update the last modified date at the same time. Stale professional data reads as neglect to crawlers and people alike.

One more move for people who write across platforms: ask editors to link your guest bylines back to your author page. The markup gives machines the identity claims, and the links from elsewhere back them up.

Person Schema Generator and the tools around it

Completing the graph.

Your employer or company comes from the Organization Schema Generator, and the names should match across both blocks exactly. The articles carrying your byline get their markup from the Article Schema Generator, with the author url pointing back at your author page.

If your about page represents you rather than a company, the About Page Schema Generator can wrap that page around the same person, keeping every signal aimed at one identity.

Try it now

Open Person Schema Generator

The tool is one click away. No sign up, no upload, no payment.

Open Person Schema Generator

Write a review