Leaving your content anonymous now has a measurable cost. In January, Semrush analyzed 304,805 URLs that ChatGPT, Google AI Mode and Perplexity actually cited, and content with clear author information got cited 1.8x more often than anonymous content. Taken as a cluster, EEAT signals predicted citation better than anything except clarity itself. That moves EEAT in AI search out of metaphor territory and into a selection bias you can measure. Below I'll go through what the evidence really shows, how each pillar maps onto AI retrieval, and how to rebuild author pages as the infrastructure that carries the signal.
The skeptics are half right
Start an EEAT conversation anywhere and two camps form within minutes. The skeptics quote Google: you can't sprinkle EEAT onto a page like a meta tag, because it's a framework for human quality raters rather than an algorithmic input anyone can detect. The believers point out that the sites winning AI citations all seem to have real names and real entity footprints behind them. Every SEO forum has some version of this fight:
Does an Author Profile Page Boost SEO?
It's been suggested to me to create an author profile page to boost Google's EEAT signals. This page would list out all the experts who write blogs of our site, including those that wrote one-off guest posts. I would create a short bio to p...
I think both camps are right, as long as each gives something up. There is no EEAT score. Google's helpful content guidance describes the qualities its systems reward, and its AI Overviews documentation says outright that no special optimizations exist for AI features. The signals underneath the framework are a different story. Named authors, machine-readable credentials and consistent entity presence across the web are all crawlable, and in the citation data they're what separates cited pages from pages that rank and get ignored. What you can add is everything an engine uses to infer trustworthiness.
That distinction matters even more for AI engines than for Google. A system assembling an answer needs sources it can defend, and an answer engine that cites a faceless content farm can't stay credible for long.
EEAT Is No Longer Just for Google — AI Search Changed Everything in 2026
What the citation data actually shows
Semrush's January 2026 analysis is the strongest dataset anyone has published on this so far. It set the 304,805 cited URLs against 921,614 URLs that ranked in Google's top 20 for related queries and never got cited, then measured how each signal correlated with citation:
Content with 1 very specific characteristic gets cited by AI platforms 1.8x more often. If you want to know exactly what ChatGPT, Claude and broader AI search platforms are looking for when they decide which content to cite, the data is now specific enough to act on. According https://t.co/yLa0hORyEl
Alex Groberman@alexgrobermanJun 3, 2026
Clarity and summarization came first at +32.8%, and EEAT signals were close behind at +30.6%, ahead of Q&A format, section structure and structured data. The number I find most useful is the only negative one. Promotional tone correlated with citation at -26.2%, which means the engines actively deselect content that tries to sell.
The AI Overviews data points the same way, including a Wellows study of 15,847 AI Overview results. The gate for a citation is being identifiable, which ranking well never guaranteed.
You're getting AI traffic. But do you know where it comes from?
RankControl credits every visit to the assistant that sent it: ChatGPT, Perplexity, Claude, Gemini, Copilot, or Grok. Full source attribution, next to your Google traffic.
How each pillar translates to retrieval
The rater-guideline version of EEAT was written for humans to apply. In retrieval, each pillar turns into something a system can actually observe:
| Pillar | What it looks like to a retrieval system |
|---|---|
| Experience | Firsthand markers a model can detect: "we tested", "our data", screenshots, specific numbers from real usage |
| Expertise | Machine-readable credentials: a named author whose role, history and qualifications exist in structured data and resolve across the web |
| Authoritativeness | Entity presence: the author and brand exist in the knowledge graph engines consult, corroborated by profiles and mentions beyond your own domain |
| Trustworthiness | Consistency plus restraint: claims that match across your site and your profiles, and the non-promotional tone the citation data rewards |
Experience is where generic content falls down hardest. Synthesis without firsthand markers reads as re-summarized training data, because that's what it is. None of the four pillars is a score, but each is an input a retrieval system can weigh when it decides which of twenty candidate pages earns the citation, and that decision is the whole game we covered in writing content AI agents cite.
Rick Steves shows what the compounding version looks like. After a recent core update, SEO analysts watching AI Overview citations noticed a surge from his travel site, a brand that spent two decades building exactly this signal cluster: a named expert, long-running community forums, deep topical coverage, and active YouTube and TikTok channels. The lift showed up in organic rankings and AI citations at the same time, and the video channels got cited too, so entity presence built across channels paid out across channels.
The author page, rebuilt as infrastructure
Most SaaS author pages hold a name, a stock photo and one adjective-heavy sentence, and nothing on them gives an engine something to resolve. Rebuilt as trust infrastructure, the page has five jobs.
The bio comes first, and it has to be specific. Verifiable claims beat adjectives (years in the field, companies, launches, numbers), so "Led lifecycle marketing at two B2B startups through Series B" leaves an entity trail while "passionate about growth" is filler. Credentials and role come next: what this person does at your company and why they're qualified to write about your category. Third is the full body of work, every post they've authored on your site linked from the page, which is what makes authorship a sitewide signal instead of a decoration on individual posts.
The fourth job is sameAs, with links out to LinkedIn, X and GitHub, and to conference bios or anywhere else the same human verifiably exists. That property is the connective tissue that lets an engine resolve your author page and their LinkedIn into one entity. The fifth is the markup itself. Google documents ProfilePage structured data for exactly this page type, wrapping a Person entity with name and jobTitle, a description and image, and the sameAs array, and it pairs well with the sitewide patterns in our schema blueprint.
None of the pages currently ranking for EEAT-and-AI queries shows the actual markup, so this is the complete pattern for an author page:
{
"@context": "https://schema.org",
"@type": "ProfilePage",
"mainEntity": {
"@type": "Person",
"name": "Jane Rivera",
"jobTitle": "Head of Lifecycle Marketing",
"description": "Led lifecycle marketing at two B2B startups through Series B. Writes about AI search measurement.",
"image": "https://yourdomain.com/authors/jane-rivera.jpg",
"url": "https://yourdomain.com/authors/jane-rivera",
"sameAs": [
"https://www.linkedin.com/in/janerivera",
"https://x.com/janerivera",
"https://github.com/janerivera"
]
}
}
Then reference that same Person entity, by its url, in the author field of the Article schema on every post she writes. That repetition is what turns twenty scattered bylines into one resolvable expert.
One trap quietly undoes all of this, and it's your SEO plugin. Yoast and Rank Math both noindex author archive pages by default, so teams build beautiful author infrastructure that no engine ever retrieves, and practitioners keep rediscovering this the hard way. Flip the noindex, add the schema and request indexing. It's a ten-minute fix, and it decides whether the page works as a signal or just sits there as decoration.
We'll show you exactly where your brand stands in AI search.
No commitment. $0 due today, cancel anytime. See how ChatGPT, Perplexity, Claude, Gemini, Grok, and Google AI Mode talk about your brand today.
The fake author trap
The tempting shortcut is to invent authors: an AI headshot, a plausible bio, made-up credentials, instant EEAT. A major sports publisher got caught doing exactly this in a widely reported 2023 incident, AI-generated author photos and biographies included, and the reputational damage outlived every article those "authors" produced.
In AI search the risk is worse, because a fabricated author fails in a way engines can detect. An invented person has no entity trail. There's no LinkedIn profile older than your blog, no conference talks or co-authors, and the name never co-occurs with anything in the places engines look. A retrieval system that checks sameAs links against reality finds nothing, and a brand caught faking identity signals has poisoned the very trust inference it was trying to buy.
So use real people. On a small team, a founder plus one or two genuine subject-matter contributors beats a masthead of ghosts every time. That's why RankControl's brand control settings keep author profiles for real team members: the Forge Agent adds Person markup for the byline to every article automatically, but the humans have to exist. Once they do, our guide to building expert bylines AI actually trusts covers turning a real person into a recognized entity.
Measure whether authorship moves citations
You can test author infrastructure, and I'd run the test, because it settles the skeptic debate for your own site:
- Take a baseline first. Run your standard prompt panel across ChatGPT, Perplexity, Claude and Gemini, and log citation rates for your pages before you touch anything.
- Ship the infrastructure in one batch: author pages, schema and sameAs, the indexing fixes, and bylines wired to the pages. One batch gives you one before/after line instead of noise.
- Compare authored pages against unauthored ones, and if you can, leave one content section without bylines for a quarter. seoClarity's authorship analysis documents the paradox well, since authorship isn't a direct ranking factor and yet properly attributed content keeps outperforming, with metadata-rich pages cited about 40% more according to Search Engine Journal's reporting.
- Re-sweep on your normal cadence and watch whether the authored pages enter candidate sets faster.
One data point on effort versus impact is encouraging. A practitioner who implemented author signals purely through schema, without rewriting a single visible bio, reported pages moving from around position 50 into the top 6, so the structured data did the work the prose was supposed to do. Your mileage will vary, but the experiment cost him an afternoon.
On time, real author pages take 2 to 3 hours each and the markup another hour. The indexing cleanup is an afternoon, and the measurement rides on sweeps you should already be running. The other route is letting the Forge Agent generate the author schemas from your content engine, with the citation tracking catching the before/after automatically.
Know exactly what AI says about your competitors.
RankControl's Recon Agent monitors competitor citations across ChatGPT, Perplexity, Claude, Gemini, Grok, and Google AI Mode. See where they show up and you don't.
The anonymous blog was a viable strategy for fifteen years, but the engines are getting pickier about who they quote, and every study so far says they resolve "who" before they decide "whether." Teams that give their experts a verifiable, machine-readable identity now are buying a selection bias that compounds with every answer.
