Everyone in SEO talks about author schema, and almost nobody implements it correctly. Half the sites that have it stuff a job title into author.name. The other half mark up an Organization on posts a human obviously wrote. And a surprising number never add sameAs at all, even though that's the property doing the entity-resolution work AI engines lean on.
Ahrefs tested this in May 2026, and the result is worth knowing before you touch any markup: adding schema by itself didn't lift AI citations. What the markup does is make your author's identity readable to systems that are already trying to weigh expertise. The lift comes from being someone an AI engine can verify, and schema is the layer that lets it check.
What "author trust" actually means to an AI engine
Before an AI engine cites your article, it does two things. It reads the visible content, and it looks for signals about who wrote it. The content decides whether your page is a candidate at all. The author signals decide whether it's a candidate the engine can trust.
Google's E-E-A-T framework is the public version of what every AI engine is trying to model in miniature. Google added the second "E", for Experience, in December 2022, per its official announcement. The September 11, 2025 Quality Rater Guidelines went further, adding evaluation criteria written specifically for AI Overviews and naming Trustworthiness the most important part of E-E-A-T.
Nobody really disputes that a named author with verifiable expertise gets more weight than an anonymous or generic byline. The part people miss is where the checking happens. It runs through your entity graph, and the byline itself is only the starting point.
Lily Ray spotted the mechanical side of this when Google started showing author names right inside News and Discover carousels:
Ooo! This is super cool. More evidence that authorship (and personal branding) are helpful for SEO/Discover. At the very least, they can potentially impact CTR! (I’ve seen the same treatment of author names on news articles in Search too)
Lily Ray 😏@lilyraynycSep 2, 2025That makes authorship a live CTR signal you can watch, which is a long way from an abstract E-E-A-T idea. Marie Haynes has run a matching diagnostic for years, asking Gemini what Google's systems already know about you:
New blog post: Using Gemini to get insight into your E-E-A-T. https://t.co/pvTBD14TJc
Marie Haynes@Marie_HaynesJan 13, 2025Both lead to the same lesson. If Gemini can't say what you're an expert in, no amount of Person markup will build that reputation from nothing. The markup only makes the authority you already have readable by machines.
The full Person schema field map
Schema.org's Person type has dozens of properties, but for author markup the useful ones fall into three groups:
| Field | Group | What goes in it |
|---|---|---|
name | Identity core, always include | Just the name. Not "Dr. Jane Smith, VP of Content." |
url | Identity core | The author's landing page on your site (recommended) |
sameAs | Identity core | An array of URLs pointing to unambiguous identity references (LinkedIn, Wikidata, ORCID, employer bio, personal site); the entity-graph anchor |
jobTitle | Expertise, include what applies | For example "Senior Product Marketer" |
worksFor | Expertise | The Organization node for the author's employer |
knowsAbout | Expertise | An array of topics or entity URLs the author covers; underused, so do use it |
alumniOf | Expertise | Educational institutions |
hasCredential | Expertise | Professional credentials, if verifiable |
image | Presentation | A real photo (min 50K pixels for ProfilePage); Gravatar works |
description | Presentation | A short bio |
honorificPrefix / honorificSuffix | Presentation | Dr., PhD and so on, never inside name |
Keep name clean. Google's wording is blunt: "In the author.name property, only specify the name of the author." Point url at the author's page on your own site, and mark that page up with ProfilePage schema, which Google updated on Dec 10, 2025.
The setup that works is to embed the Person inline in your Article schema's author property and set author.url to a /author/[slug] landing page with ProfilePage markup. An AI engine can then follow that identity anchor to one canonical profile, and from there out to your external sameAs targets. Ahrefs' companion study of 6M URLs found AI-cited pages about 3x more likely to carry JSON-LD, which suggests it's worth doing even without a direct causal lift.
The sameAs property is the whole game
If you only fix one property, fix sameAs. It does the entity-resolution work, and most sites either skip it or misuse it.
Per schema.org, sameAs is the "URL of a reference Web page that unambiguously indicates the item's identity." For a working professional, these are the links that count, from most authority to least:
| Rank | Link | Why it counts |
|---|---|---|
| 1 | Wikidata QID URL | The entity-graph gold standard and the single strongest anchor if the author has an entry. If not, creating one (with valid external references) is worth the effort for high-authority authors |
| 2 | ORCID | For researchers, and useful for anyone with published papers. Format: https://orcid.org/0000-0002-XXXX-XXXX |
| 3 | The strongest single external anchor for most SaaS authors: a public, name-consistent profile | |
| 4 | Employer bio page | The author's page on their company site, which should mark the person up with ProfilePage schema too |
| 5 | Personal site | A matching bio, credentials and publications list |
| 6 | X/Twitter, GitHub, Google Scholar, Crunchbase | Supporting signals |
How many should you add? Practitioners generally settle on 2-3 links for basic disambiguation and 8+ for strong entity resolution. The count matters less than two other things. Every link has to resolve, because a broken URL is worse than none. And every profile has to name the same person the same way.
Picture a sameAs array with a LinkedIn URL for "Jane A. Smith", a Wikidata entry for "Jane Andrea Smith" and a bio page for "J. Smith." With those three, your entity graph gets fuzzier instead of sharper.
AI search traffic grew 835% this year. Is your content ready?
RankControl generates 26 content formats optimized for ChatGPT, Claude, and Perplexity. Published on your domain, matched to your brand.
Where Ahrefs' experiment actually points
Ahrefs' schema study is the cleanest test anyone has published on this. Here's how it was built and what came out:
| Part of the study | Detail |
|---|---|
| Pages tested | 1,885 pages that added JSON-LD schema between August 2025 and March 2026 |
| Control | 4,000 pages, compared by difference-in-differences using Ahrefs' Brand Radar citation tracker |
| Google AI Mode | Citations +2.4%, not statistically distinguishable from zero |
| ChatGPT | Citations +2.2%, not statistically distinguishable from zero |
| Google AI Overviews | Citations -4.6%, significant and negative |
Search Engine Journal's coverage said it plainly: schema markup didn't move AI citations in this test, so schema alone isn't a multiplier. Yet the same team's 6M-URL correlation study found AI-cited pages about 3x more likely to have JSON-LD than uncited ones. Schema and citations show up together, while the cause runs through what the schema signals.
For your author markup, that means adding Person schema won't buy you citations on its own. It makes the author entity readable, so the signals that do count can be counted: external mentions, credible sameAs targets and consistent bylines over time. It works the other way too. An author with real expertise and no schema can still be found, just parsed less easily.
Someone on r/TechSEO asked straight out whether author schema does anything:
Does author schema help with anything?
Looking for real results/experience, not theory. We’re being asked by a content partner to add author schema to our site. - have you done this? - what results did you see (if any)? - would you recommend for/against? I do some research in th...
Several of the practitioners who answered had shipped it for clients. They saw no ranking lift, but they did see consistent gains in how Google understood authorship and expertise attribution. One commenter put it as "in theory, Schema helps LLMs, so in the long run, I would do it," which lines up with the Ahrefs numbers.
The author landing page pattern
Here's the version that works end to end. You need three pieces, and they have to agree with each other:
| Where | What it needs |
|---|---|
| Every article page | A visible byline linking to /author/[slug], plus Article schema with author set to a full Person object (never a bare string name) that includes sameAs |
| The author landing page | An H1 with the author's name; visible bio, photo and credentials; a list of published articles that updates automatically; links to the external profiles in the schema's sameAs; ProfilePage schema wrapping a mainEntity Person with that same sameAs |
| Reciprocal links | Every byline points to the landing page, the landing page links to at least one external sameAs target, and the external profiles (LinkedIn "About" section, personal site bio) link back to the landing page |
The Contently and Yoast implementations both converge on this, and it's what Google's ProfilePage documentation describes. On WordPress, Yoast generates Person schema from each user profile and pulls in social links as sameAs. On a custom stack you'll build it yourself, which is about a day's work.
Built by the team that got cited in 48 hours.
Content generation, backlink building, AI visibility tracking, and Google rankings. One platform, zero guesswork.
The traps
Sites get author schema wrong in seven ways. Here they are, from most common to least.
The most common is a polluted author.name: "Dr. Jane Smith, Senior Editor at Acme" where it should just say "Jane Smith." Google's Article structured data guidance wants the name only, so move the title into jobTitle, honorifics into honorificPrefix and the publisher into the publisher property.
Next comes an Organization listed as the author of a post a person wrote, which is often just a CMS default. Google's rule is simple: "Use the Person type for people, and the Organization type for organizations." In practice, Organization belongs on wire copy.
A byline can also show on the page and be missing from the schema. Google asks you to "Make sure that all the authors that are presented as authors on the web page are also included in markup," and a mismatch invalidates the whole author signal.
Then there's sameAs that's missing or broken. A Person with no external anchors reads as an unknown entity, and one whose sameAs points at a 404 reads worse, so check every link on a schedule.
On fake or AI-generated bylines, Google's guidance is direct: "Giving AI an author byline is probably not the best approach." The August 2025 Core Spam Update goes after scaled content abuse, and abrupt byline shifts are one of the signals it flags. YMYL amplifies the risk.
Generic bylines like "Admin," "editorial staff" and "team" are a problem too. Practitioner reports suggest they fail Perplexity's author confidence check no matter how good the content is. That's harder to verify from Perplexity directly, though it's consistent across GEO writeups, so use real names.
The last trap is an author page with no reciprocal links. A post links to /author/jane, but Jane's page links nowhere and her LinkedIn doesn't link back to the site. The entity graph never closes, and closing it was the whole point of the schema.
An r/SEO thread with 52 comments recently reached the same place from hands-on experience. Nobody there claimed a direct ranking boost from author profile pages, but several practitioners described them as a trust-signal foundation that pays off over months rather than weeks.
What to ship this week
Starting from zero, this is about three days of work:
- Add
Personauthor schema to every published article. Cutauthor.namedown to just the name, and addjobTitle,worksFor,sameAs,imageanddescription. - Build an author landing page at
/author/[slug]for every named byline, with ProfilePage schema wrapping a Person that repeats the samesameAs. - Wire up
sameAswith at least three external profiles. Start with Wikidata if the author has an entry, then LinkedIn and a personal or employer bio, plus ORCID for researchers. - Update every external profile to link back to the author landing page: the LinkedIn "Featured" section, the employer bio hyperlink, the personal site.
Already have author schema? Then your job is an audit. Run every sameAs URL through a validator and check every author.name for job titles. Make sure no post uses Organization where a human wrote it, and hold every visible byline up against the schema. Half the sites doing author markup have at least one of these broken.
Our content engine adds the author markup to each post automatically once you set up your author roster. Our AI visibility tracking shows which of your pages ChatGPT, Perplexity and AI Mode cite each week, so you can see whose articles are earning the citations. For the wider schema picture, our structured data blueprint for AI search covers Article, Organization and Product schema in the same spirit.
The usual mistake is treating author schema as a checkbox. It's the machine-readable version of your reputation, and it only works when there's a reputation to read, so do the entity work first and let the schema follow.
See your first AI citation report in under 5 minutes.
No setup calls. No onboarding meetings. Connect your domain and see where AI mentions your brand right now.
