Schema Markup·3 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 exactly why search engines stopped taking names at face value. Person schema for author pages is the verifiable 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, its relationship to E-E-A-T, and a worked example you can adapt.

Open the tool All insights

Person schema for author pages: 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 genuine expertise, and your author page is a paragraph of prose that a crawler parses no better than any other paragraph. Meanwhile sites with fabricated authors print equally confident bios. From the outside, the two are hard to distinguish.

Person markup breaks the tie with checkable claims. A jobTitle, a worksFor organization, an alumniOf institution, and sameAs links to profiles that actually exist form a web of assertions a machine can follow and confirm. That's the difference between a name and an identity.

A worked Person example for a real author page

Six 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 pulls weight. The jobTitle frames her expertise domain, worksFor anchors her to a confirmable employer, and the sameAs array points at profiles where her history is public. The Person Schema Generator adds the optional layers on top: description, image, alumniOf as a CollegeOrUniversity node, and contact details you can include or withhold field by field.

Author markup and EEAT: what Person schema can and can't do

Honest expectations.

The relationship between author markup and eeat gets oversold, so here's the sober version. E-E-A-T is not a score your markup increments; 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 legible. 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 the most machine-friendly form there is, and after algorithm updates that hit anonymous-feeling sites, that legibility is worth real money to publishers. Think of the markup as the difference between claiming credentials and filing them.

Linking Person to Organization, and articles to both

Small graph, strong signal.

Linking person to organization happens through worksFor: the markup nests an Organization node with your employer's name, and if that company publishes its own Organization block elsewhere, the two entities can be joined. For founders and employees of small firms, this connection lets a modest personal brand borrow confirmability from the company entity and vice versa.

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

Person schema mistakes that blur identity

Ways authors sabotage 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.
Publishing Person blocks on every article page with slightly different data, instead of one canonical block on the author page.
Marking up pen names and real names 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 canonical author page per person and let everything reference it; consolidation is the whole game in entity SEO. Fill sameAs with the two to five profiles where your professional history is genuinely visible, and skip the rest.

And revisit the block when your situation changes. A new employer in worksFor or an updated jobTitle takes a minute to regenerate, and stale professional data reads as neglect to both crawlers and the humans who view source.

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; the inbound byline links give them corroboration, and that combination is what moves a name from ambiguous to established.

Person Schema Generator and the tools around it

Completing the graph.

Your employer or company entity 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 field pointing back at your author page.

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

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