E-E-A-T

E-E-A-T stands for Experience, Expertise, Authoritativeness, and Trust. Google uses the concept in its Search Quality Rater Guidelines to describe qualities that help people decide whether a result is useful and reliable. Google added the extra E for experience in December 2022.

The important boundary is often missed: E-E-A-T is not a single score, schema property, or direct ranking factor. Google says its automated ranking systems use many factors that can identify content demonstrating E-E-A-T qualities. Human quality raters use the guidelines to evaluate whether search systems are producing good results; an individual rating does not directly change a page’s ranking.

What the four qualities mean

Quality	Question to ask	Useful evidence
Experience	Has the creator actually used, visited, built, tested, or lived through the subject?	Original photos, test conditions, dated observations, screenshots, limitations, and first-hand examples
Expertise	Does the creator have the knowledge needed for this task?	Qualifications where relevant, technically accurate explanations, methods, calculations, and subject-matter review
Authoritativeness	Is the creator or site recognized as a dependable source on this topic?	Independent citations, relevant references, a consistent body of work, and clear organizational identity
Trust	Is the page accurate, honest, safe, and accountable?	Sources, corrections, author and publisher details, contact and policy pages, secure transactions, and transparent commercial relationships

Google’s people-first content guidance says trust is the most important member of the group. The other qualities contribute to trust, but they are not interchangeable. A product review may depend heavily on first-hand use. Tax advice may require professional expertise. A checkout page needs accurate pricing, secure handling, and accountable business information.

E-E-A-T and YMYL

YMYL means topics that can significantly affect health, financial stability, safety, or societal welfare. Google says signals aligned with strong E-E-A-T receive more weight for these topics.

That does not mean adding a doctor’s byline to unrelated content or placing a generic disclaimer at the top of every page. Match the safeguard to the risk:

• Medical or legal guidance should identify the qualified author or reviewer, cite current primary guidance, and state important limits.
• Financial content should disclose assumptions, dates, risks, and commercial relationships.
• Product reviews should show what was actually tested, the test period, comparison criteria, and who paid for or supplied the product.
• Low-risk tutorials can demonstrate trust with reproducible steps, expected outputs, failure cases, and an update history.

Where E-E-A-T fits in a Google SEO workflow

E-E-A-T matters most after you have confirmed that Google can discover, crawl, render, and index the page. It does not replace technical eligibility, and it is not a shortcut around search intent or page usefulness.

Use this wiki page to keep the concept precise, then move to the page that matches the real job:

• Start with the Google SEO guide if you need the full workflow from discovery and indexing to ranking, clicks, and conversion.
• Use the Google SEO audit checklist when you need URL-level evidence instead of writing “low E-E-A-T” with no supporting issue, source gap, or missing proof.
• Review helpful content guidance when the problem is originality, scope, stale claims, or weak sourcing rather than authorship alone.
• Run SEO Audit first if you need to rule out noindex, canonical, rendering, or internal-link blockers before spending time rewriting a page for trust.
• Check GSC Management after release so URL Inspection, impressions, clicks, and page-query-language routing confirm whether the revised evidence changed search behavior.

A practical E-E-A-T audit

1. Define the page’s claim and risk

Write down the decision the page helps a reader make. A definition, a personal review, and professional advice require different evidence. Flag claims that can cause financial, health, safety, or legal harm if wrong.

2. Make the creator and method visible

Identify who produced the content and how. Add a relevant author profile, but do not treat a bio as proof by itself. For tests and comparisons, document inputs, tools, dates, excluded cases, and limitations. For AI-assisted work, review facts and explain the production method when that context would help readers judge reliability.

3. Support factual claims

Use primary sources for standards, product behavior, regulations, and scientific or official claims. Link citations close to the claim they support. Remove references that merely repeat another publisher’s summary without adding evidence.

4. Check page and site trust

Verify the visible author or publisher, contact route, editorial or correction policy, privacy terms, and commercial disclosures. Test that prices, availability, forms, downloads, and calls to action match what the page promises. Technical polish cannot rescue misleading content, but broken or unsafe experiences can undermine trust.

5. Record maintenance

Show a meaningful updated date when the substance changes, not when a script touches the file. Assign an owner and review interval for time-sensitive sections. Keep a short change log for high-risk or operational guidance.

Evidence matched to common page types

Page type	Strong evidence	Weak substitute
How-to guide	Reproducible steps, tested output, failure modes	Generic checklist with no test
Product review	Original use, comparison method, disclosure	Manufacturer claims rewritten as experience
Definition	Primary documentation, scope, status, examples	Unsourced claim that the term is a ranking signal
Case study	Baseline, dates, method, measured outcome, caveats	Outcome claim with no denominator or time period
YMYL advice	Qualified review, current sources, risk limits	Author photo plus a broad disclaimer

Common mistakes

• Selling an “E-E-A-T score” as if Google exposes one official metric.
• Treating backlinks, author schema, word count, or an updated date as sufficient proof.
• Claiming that quality rater feedback directly changes a specific page’s position.
• Using an expert byline when the named person did not create or review the work.
• Calling stock photos, invented examples, or unverified AI output first-hand experience.
• Publishing YMYL advice without current sources, review ownership, or risk boundaries.

Validation checklist

• The page states who created or reviewed it when identity matters.
• Experience claims include observable evidence and test conditions.
• High-impact claims link to current primary sources.
• Commercial relationships and conflicts are disclosed near the recommendation.
• The page explains limitations, uncertainty, and when professional help is appropriate.
• Contact, correction, privacy, and transaction details work as described.
• The update date reflects a substantive review.

How to validate an E-E-A-T update

1. Confirm the visible page changed in the way your claim requires: byline, reviewer, sourcing, test notes, limits, or disclosure.
2. Re-check the rendered page so canonical tags, internal links, and any bilingual hreflang setup still match the intended URL pair.
3. Use GSC Management or Search Console to confirm the page remains indexed and that query-to-page routing did not shift to the wrong language or weaker URL.
4. Compare impressions, clicks, and the visible query mix after re-crawling. Do not claim that an E-E-A-T edit worked if Google has not reprocessed the page yet.

Primary sources

• Google Search Central: Creating helpful, reliable, people-first content — explains how E-E-A-T relates to automated systems, quality raters, YMYL, and the “Who, How, and Why” self-assessment.
• Google Search Central: E-A-T gets an extra E for Experience — announces the 2022 change and clarifies the role of quality raters.
• Google Search Quality Rater Guidelines — the detailed evaluator framework, including page quality, E-E-A-T, and YMYL guidance.

Related concepts

• YMYL (Your Money or Your Life)
• Helpful content
• Content quality
• Schema markup
• Google SEO guide
• Google SEO audit checklist