E-E-A-T and Author Authority

E-E-A-T and author authority is how Google suggests judging whether content can be trusted. The most important thing to know from the first line: E-E-A-T itself isn't a specific ranking factor. It is a set of aspects by which Google describes helpful content, and trust is the chief of them. The author is often called "a separate signal" and "+15 positions in four months" is promised. Neither is in the documentation. What is there follows: the questions about the author, the definition of YMYL and the rules for author markup.

The basis is the guidance on helpful content, the announcement of the extra E and the page on Article markup. A general introduction is in the lesson on E-E-A-T.

What Google actually says

Google's systems, as the guidance describes them, identify relevant content and aim to prioritize what seems most helpful. To do this they use a mix of factors that can help determine which content demonstrates experience, expertise, authoritativeness and trustworthiness, or E-E-A-T. Three statements carry the lesson:

• Of these aspects, trust is most important; the others contribute to trust, but content doesn't necessarily have to demonstrate all of them. One piece is helpful for the experience it shows, another for the expertise it shares;
• E-E-A-T itself isn't a specific ranking factor, but using a mix of factors that can identify content with good E-E-A-T is useful;
• Raters have no control over how pages rank, and rater data is not used directly in the ranking algorithms; it is like feedback cards at a restaurant. The rater guidelines, Google says, don't directly influence ranking.

Experience, expertise, authoritativeness, trust

The four components are often presented as equals with lists of ways to "demonstrate" each. In the documentation they are not equal: trust is chief. And Google's own example from the announcement of the extra E explains how experience differs from expertise: to fill out your tax returns correctly you want content from an expert in accounting, while for reviews of tax software a discussion among people who have used it may suit. Experience means actual use of a product, having visited a place or relating what a person lived through.

YMYL: defined by harm, not by industry

Google counts as YMYL topics that could significantly impact the health, financial stability or safety of people, or the welfare or well-being of society. For them the systems give even more weight to content that aligns with strong E-E-A-T, and the content must be highly accurate and consistent with established expert consensus. So the example of a medical article is right in substance, while the list "health, finance, law, safety" is an illustration, not a closed list.

Who is the author: Google's questions

The "Who" block of the guidance begins with the thought that E-E-A-T becomes intuitive to people when it is clear who created the content. The questions:

• is it self-evident to your visitors who authored your content?
• do pages carry a byline, where one might be expected?
• do bylines lead to further information about the author, giving background about them and the areas they write about?

Google strongly encourages adding accurate authorship information, such as bylines, where readers might expect it. But it warns about the reverse: fabricating creator profiles, such as with AI-generated headshots, made-up names or false credentials, is a form of deception that makes a page untrustworthy to both users and automated quality systems. For generated content the same logic is in the lesson on AI in content planning: an AI byline instead of an author is not the best route.

Author markup in Article

For the author in Article markup Google gives concrete rules, and they are more precise than the usual "add Article schema with a name and organization":

• all authors shown on the page must be in the markup too; each author gets its own field, not one string with all the names;
• it strongly recommends using type and url (or sameAs): a link to a page that uniquely identifies the author, such as an author page or a social profile;
• in author.name only the name: no job title, honorific, "posted by" or publisher name; those have their own properties: jobTitle, honorificPrefix, publisher;
• use Person for a person and Organization for an organization.

"author": [
  { "@type": "Person", "name": "Willow Lane", "jobTitle": "Journalist",
    "url": "https://www.example.com/staff/willow-lane" }
]

More on markup is in the lesson on structured data. To check that JSON-LD is on the page and parses without errors, use the page analyzer.

What is not in the documentation

• "The author as a separate signal" and "an author page as a strong expertise signal": Google advises showing the author but does not call it a ranking signal;
• Figures such as "+15 positions in 4 months" and timelines for an effect;
• Markup with "name and organization" as a way to improve E-E-A-T: markup helps understand who the author is, it does not prove expertise;
• The claim that algorithms "use E-E-A-T" as a separate score.

How to strengthen trust in a page

1. Go through the expertise questions: clear sourcing, evidence of expertise, background about the author or the publisher through an author page or an About page. These questions are covered in detail in the lesson on content uniqueness.
2. Sign the piece with a real author and link to a page about them. For YMYL topics involve specialists and check the facts.
3. Mark up the authors by the Article rules.
4. Show how the piece was made: for instance how many products were tested and how.
5. Check text quality with text analysis and completeness with entity coverage.

Checklist

1. Pieces carry a byline where readers expect one.
2. The byline leads to an author page with background and topics.
3. Author information is true: no made-up names or false credentials.
4. Author markup follows the Article rules: separate fields, type, url or sameAs.
5. YMYL pieces are accurate and consistent with expert consensus.
6. There are sources, and for reviews a description of how the testing was done.

Mistakes

• Treating E-E-A-T as a separate score you can inflate.
• Inventing authors and credentials.
• Signing everything with a generic name such as "Site Team" where an author is expected.
• Writing a job title or "posted by" in author.name.
• Expecting a specific rise in positions from a single About the author page.

What comes next

Next is structured data: how to describe a page to search engines and which rules apply to markup. The link to choosing a platform is in the lesson on CMS.