What the letters mean
After this lesson you can describe E-E-A-T correctly and make a page show real authorship and sourcing. Mistakes about E-E-A-T are some of the most common in the whole field.
E-E-A-T stands for experience, expertise, authoritativeness and trust. It comes from Google's Search Quality Rater Guidelines, which tell human raters how to evaluate results, and from Google Search Central's guidance on creating helpful, reliable, people-first content. The guidance describes trust as the most important element, and the others as feeding into it. This is documented, as of 2026-11.
What it is not (documented and widely clarified)
Google has said E-E-A-T is not a single ranking factor and not a score attached to your page. It is a way of thinking about quality that Google's systems aim to align with. Therefore:
- There is no "E-E-A-T schema" or checkbox.
- You cannot "optimise the number".
- The raters' guidelines are a description for evaluators, not a checklist that guarantees any placement.
If a tool sells you an "E-E-A-T score", treat it as that vendor's opinion.
The four ideas in plain words
- Experience: have you actually done or used the thing you write about?
- Expertise: do you have the knowledge or skill for this subject?
- Authoritativeness: do others recognise you or your site as a go-to source?
- Trust: is the page accurate, honest about who is behind it, safe, and clear about its sources?
You cannot fake the third; you earn it. You can make the first, second and fourth visible.
Show who is behind the page (established practice)
Readers, and sensible systems, look for:
- A named author with a short, true bio and a link to a profile page.
- How they know: a sentence about relevant experience that you can back up.
- Sources for factual claims, linked to primary or authoritative pages.
- Dates: published and updated, with the update dates reflecting real changes.
- Contact details and an About page naming the organisation.
- Corrections policy: how a reader reports an error.
- Reviewer information where the topic needs it, true and dated.
<article>
<h1>Choosing a sourdough flour</h1>
<p class="byline">By <a href="/about/">Asha Rao</a>, baker at Greenfield Bakery (fictional). Updated 2026-11-14.</p>
<p>I tested four flours over six weeks in my own kitchen; the notes are below.</p>
<p class="note">Sources and method are listed at the end. Spotted a mistake? Email the address on the contact page.</p>
</article>All the people and details there are fictional. In real use every statement must be true and checkable.
High-stakes topics
Google's guidance refers to topics that could affect health, financial stability or safety as needing particular care. On these topics, claims about expertise and sourcing carry more weight. Practical consequences:
- Link to official bodies and primary sources rather than blogs.
- Say what you are not: "This is general information, not medical advice."
- Do not give a reviewer credit unless a qualified person reviewed it.
- Prefer ranges and caveats over certainty.
Authorship pages and Person markup
A short author page is better than a fake team of experts. Structured data can restate the facts (see lesson Schema.org JSON-LD basics), but markup is not evidence. A schema block claiming a doctorate does not make it true, and claims in markup must match visible text.
On this site
Lesson pages here show an author and a status. This course is status review with no reviewedBy line: the repository's quality gate requires a human technical review before publishing, and that is Himanshu's to do. Nothing in this course states his qualifications; those have to be confirmed by him.
Does it affect AI answers?
Google's guide says generative features build on its core ranking and quality systems, which is consistent with trust mattering. Beyond that, how much authorship signals change which page an assistant cites is unknown. Hypothesis, but harmless: being honest helps readers.
Common mistakes
- Inventing a "Dr" or a team of reviewers.
- Listing credentials that do not relate to the topic.
- Updating the date without changing the content.
- Anonymous articles on topics where authorship matters.
- Treating E-E-A-T as a plugin or a checklist item.
Exercise
- Pick a page and add a true byline, a one-sentence bio, a last-reviewed date reflecting real review, and links to two primary sources.
- List every claim of expertise on the page and mark each: provable, or remove.
- Decide whether the topic is high stakes. If yes, add a plain limitation sentence.
Show a sample answer
Example limitation sentence for a finance page: "This explains how the calculation works; it is not personalised advice, and rates and rules change, so check your lender or an official source." Mark any claim you cannot prove for deletion.
Previous: Entities, brand mentions and consistency. Next: Schema.org JSON-LD basics.
Key points
- E-E-A-T stands for experience, expertise, authoritativeness and trust, with trust the most important; it comes from Google's search quality guidance.
- Google has said E-E-A-T is not a direct ranking factor or a score; it is a framework its quality evaluators and systems align with.
- Show who wrote a page, why they are qualified, how you know, and when it was last reviewed.
- Do not invent credentials, reviewers or dates.
- Higher-stakes topics (health, money, safety) deserve stronger sourcing and caution.