Check this page with an assistantOpens a chat asking it to summarise this article and name the evidence behind each claim.
Claude opens with the prompt on your clipboard: Anthropic does not support prefilled prompts on the web, and we would rather copy it than ship a button that drops it.
Start With What Google Has Actually Said
Google's guidance asks you to add accurate authorship information, such as bylines, to content where readers would expect it, and frames the whole area around whether a reader would trust what they are looking at. It does not describe a metric, a score, or a threshold. The instruction is closer to editorial hygiene than to an optimisation target.
It is worth knowing the history, because it inoculates you against most of what is currently being sold. Google launched explicit authorship markup using rel="author" in 2011, showed author photos in results, and then withdrew the whole system in 2014 on the grounds that it was not useful enough. That is a company that tried the strong version of this idea, at scale, and discontinued it.
E-E-A-T sits in a similar category of frequently misread. It comes from the Search Quality Rater Guidelines, a document describing how human raters should assess result quality so that Google can evaluate its own systems. Raters do not rank your site. The concept tells you what Google is aiming at, which is genuinely useful, and it is not a setting you can adjust.
The Numbers Being Quoted at You
Figures circulate claiming that pages without named authors are some exact percentage less likely to be cited, or that E-E-A-T signals correlate with citation probability at a specific coefficient. Treat the precision as the warning sign. None of these come with a published methodology you can inspect, and several describe measurements of things Google does not expose.
This matters more than ordinary statistical scepticism, because the numbers are being used to sell a specific and expensive service category: author authority programmes, entity-building retainers, and reputation packages priced against a correlation nobody can verify. The underlying advice is often fine. The quantified urgency wrapped around it is manufactured.
The defensible version of the claim is qualitative and still worth acting on. Content that names an accountable human, explains why that person would know, and can be corroborated elsewhere is more trustworthy to a reader, to a rater, and to a retrieval system trying to decide whom to quote. You do not need a coefficient to justify putting your name on your work.
The Markup, Kept Modest
Person markup for the author, referenced from Article markup on each piece, with sameAs pointing at profiles that really are theirs. Google separately documents ProfilePage structured data for pages about a single person. That is the whole toolkit, and it describes what your pages already say rather than adding claims.
The failure mode here is well established and worth naming: markup that asserts what the visible page does not. Credentials in JSON-LD that appear nowhere on the author page, a sameAs pointing at a prominent person with the same name, an organisation affiliation nobody has confirmed. Structured data is a labelling system for content that exists, and systems reading it are cross-checking against the rendered page. The general rule and its limits are in schema markup for small businesses.
Keep expectations proportionate too. Author markup does not produce a rich result, does not display a photo in search, and will not move rankings on its own. It makes an entity easier to resolve unambiguously, which is a modest and real benefit, and it is worth the twenty minutes precisely because it is cheap rather than because it is powerful.
Why This Got Louder in the AI Era
When generating plausible text became free, the scarce thing became accountability. A named person who can be checked, contacted, and found elsewhere is expensive to fake at scale, which is exactly the property that makes a signal useful to a system trying to filter an enormous volume of competent-looking content.
That framing also explains why the answer is not to add bylines everywhere as a tactic. A fabricated author with an invented biography is worse than no byline: it converts an absence into a false claim, and it is the specific pattern that scaled-content enforcement looks for. Google's guidance on AI content is explicit that giving AI an author byline is not the way to disclose AI involvement, and the reasoning generalises. A byline asserts that someone stands behind this. Only make the assertion when it is true.
The reason it pays outside your own site is corroboration. The citation research consistently shows assistants leaning on third-party sources over brand-owned pages, and a named expert is the thing that gets quoted, interviewed, and included in someone else's roundup. Your author entity is, in practice, the vehicle for the outreach described in earning third-party citations, and the broader picture is in the AI search visibility playbook.
Questions People Ask About Authors and E-E-A-T
- Is E-E-A-T a ranking factor?
Not directly, and Google has said so repeatedly. E-E-A-T is a concept from the Search Quality Rater Guidelines, used by human raters to evaluate whether the systems are producing good results. Those ratings inform development; they are not a score applied to your pages. The useful framing is that E-E-A-T describes what Google is trying to reward, not a dial you can turn.
- Does Google have an author authority score?
There is no published metric of that kind, and Google has previously built and then abandoned an explicit authorship system. Authorship markup using rel=author launched in 2011 and was retired in 2014, with Google saying it was not useful enough to users. Treat any tool offering you an author authority score as inventing a number, not reporting one.
- Should every blog post have a named author?
Where a reader would expect one, yes. Google's own guidance asks whether content presents information in a way that makes you want to trust it, and specifically encourages accurate authorship information such as bylines where readers would expect them. A product page does not need a byline; an article giving advice on a consequential decision does.
- Can I put an AI as the author?
Google's guidance on AI-generated content says giving AI an author byline is probably not the best way to make clear that AI was part of the content creation process. A byline is an accountability claim, and software cannot be accountable. If AI assisted, the right move is a named human who reviewed and stands behind the work, plus a plain statement of how the content was produced.
- What structured data should an author page use?
Person markup for the author, referenced from the Article markup on each piece they wrote, with a sameAs array pointing to profiles that genuinely belong to them. Google also documents ProfilePage structured data for pages about a single person or organisation. All of it should describe what the page visibly says; markup asserting credentials the page does not show is a liability rather than a shortcut.
Primary Sources
- Google Search Central: Creating helpful, reliable, people-first content
- Google Search Central: Guidance about AI-generated content
- Google Search Central: Profile page structured data
- Google Search Central: Article structured data, including author
- Google: Search Quality Rater Guidelines
- Search Engine Land: The rise and fall of Google authorship
