Author e e a t requirements skill
- Named Author Attribution
by AgriciDaniel·MIT license·★ 2,219 Stars on the repo·GitHub ↗
Files of Author e e a t requirements
AgriciDaniel/
Show the full text332 lines
Author E-E-A-T Requirements
Contents
- Named Author Attribution
- Author Bio Structure
- Author Page Requirements
- Person Schema Properties
- Experience Signal Markers
- Trust Indicators
- September 2025 QRG Key Principle
- E-E-A-T Scoring Rubric
- E-E-A-T Framing by Topic Risk
- E-E-A-T Signals by Content Type
Named Author Attribution
A named accountable author or editor is strongly preferred for every blog post. Organization attribution is acceptable when the organization is the accountable publisher and the page also exposes clear editorial ownership.
Never Use
| Attribution | Problem |
|---|---|
| "Admin" | No person, no trust |
| "Staff" | Indistinguishable from auto-generated |
| "Team" | No individual accountability |
| "Editor" | Not an author signal |
| No byline | Worst case: page appears authorless |
Preferred
- Full real name (first + last)
- Crawlable author or profile page with a stable URL
- Same name used on social profiles linked via
sameAs - One author per post (co-authors acceptable with both named)
Author Bio Structure
2-3 sentences. The bio establishes E-E-A-T credentials, not a sales pitch.
Formula
Sentence 1: [Name] is a [role/title] with [N years] experience in [domain]. Sentence 2: [Credential, employer, or notable achievement relevant to the topic]. Sentence 3 (optional): [Specific focus area or what they write about].
Good Examples
Sarah Chen is a content strategist with 8 years of experience in B2B SaaS. She's led content programs at HubSpot and Drift, specializing in data-driven blog optimization.
Marcus Rivera is a senior frontend engineer at Vercel. He maintains two open-source React component libraries with 12K+ combined GitHub stars and writes about performance patterns for production applications.
Dr. Elena Vasquez is a clinical psychologist and researcher at Stanford Medical Center. She has published 23 peer-reviewed papers on cognitive behavioral therapy and digital mental health interventions.
Bad Examples (Anti-Patterns)
"John is passionate about helping businesses grow through innovative digital solutions.": Vague, no credentials, sounds like marketing copy.
"Our team of experts delivers world-class content marketing services." : Not a person, promotional, no specific expertise.
"Jane is the CEO of GrowthMax Inc., the leading AI-powered marketing platform.": Sales pitch disguised as bio.
Author Page Requirements
Every named author should have a crawlable author or profile page. The URL path can follow the site's existing information architecture.
Page Must Include
| Element | Details |
|---|---|
| Full name (H1) | Same name used in bylines |
| Professional photo | Real photo, not avatar or stock |
| Extended bio | 100-200 words with credentials |
| Social links | LinkedIn, Twitter/X, personal site, GitHub (as relevant) |
| Article list | All published posts by this author, newest first |
| ProfilePage schema | JSON-LD with Person entity |
ProfilePage Schema Example
{
"@context": "https://schema.org",
"@type": "ProfilePage",
"mainEntity": {
"@type": "Person",
"@id": "https://example.com/author/sarah-chen#person",
"name": "Sarah Chen",
"jobTitle": "Content Strategist",
"description": "Content strategist with 8 years of experience in B2B SaaS, specializing in data-driven blog optimization.",
"url": "https://example.com/author/sarah-chen",
"image": "https://example.com/images/authors/sarah-chen.jpg",
"sameAs": [
"https://linkedin.com/in/sarahchen",
"https://twitter.com/sarahchen",
"https://sarahchen.com"
],
"worksFor": {
"@type": "Organization",
"name": "Example Corp"
},
"alumniOf": {
"@type": "CollegeOrUniversity",
"name": "UC Berkeley"
}
}
}
Person Schema Properties
The Person schema embedded in BlogPosting and on author pages.
| Property | Required | Description | Example |
|---|---|---|---|
@type |
Yes | Always "Person" | "Person" |
@id |
Yes | Stable URI with fragment | "https://example.com/author/sarah-chen#person" |
name |
Yes | Full name | "Sarah Chen" |
jobTitle |
Yes | Current role | "Content Strategist" |
url |
Yes | Author page URL | "https://example.com/author/sarah-chen" |
image |
Yes | Headshot URL | "https://example.com/images/authors/sarah-chen.jpg" |
sameAs |
Yes | Array of social/profile URLs | ["https://linkedin.com/in/sarahchen"] |
worksFor |
Recommended | Organization entity | {"@type": "Organization", "name": "Example Corp"} |
alumniOf |
Optional | Educational institution | {"@type": "CollegeOrUniversity", "name": "UC Berkeley"} |
description |
Recommended | Brief professional summary | "B2B SaaS content strategist..." |
knowsAbout |
Optional | Array of expertise topics | ["SEO", "content strategy", "B2B marketing"] |
Complete Person JSON-LD
{
"@type": "Person",
"@id": "https://example.com/author/sarah-chen#person",
"name": "Sarah Chen",
"jobTitle": "Content Strategist",
"url": "https://example.com/author/sarah-chen",
"image": "https://example.com/images/authors/sarah-chen.jpg",
"description": "Content strategist with 8 years of experience in B2B SaaS, specializing in data-driven blog optimization.",
"sameAs": [
"https://linkedin.com/in/sarahchen",
"https://twitter.com/sarahchen",
"https://sarahchen.com"
],
"worksFor": {
"@type": "Organization",
"name": "Example Corp",
"url": "https://example.com"
},
"alumniOf": {
"@type": "CollegeOrUniversity",
"name": "UC Berkeley"
},
"knowsAbout": ["SEO", "Content Strategy", "B2B SaaS Marketing"]
}
Experience Signal Markers
Phrases that demonstrate first-hand experience. Use these naturally throughout content to signal genuine expertise to both human readers and quality raters. In AI citation selection, demonstrated Experience is the tie-breaker when two sources are similarly authoritative: original testing, named workflows, direct observations, and proprietary data win over generic summaries.
Use These Patterns
| Pattern | When to Use |
|---|---|
| "When we tested..." | Describing an experiment or A/B test |
| "In our experience..." | Sharing practitioner insight |
| "After implementing this for [client]..." | Case study context |
| "Over the past [N] years, I've found..." | Long-term observation |
| "Here's what our data shows..." | Introducing proprietary findings |
| "I've personally seen..." | Direct observation |
| "We ran this experiment across [N] sites..." | Multi-site testing |
| "What surprised us was..." | Counterintuitive findings |
| "The mistake most teams make is..." | Practitioner wisdom |
| "When I worked at [Company]..." | Named employer context |
Signals to AVOID
| Anti-Pattern | Problem |
|---|---|
| "As an expert in..." | Self-proclaimed authority, no evidence |
| "It is well known that..." | Vague consensus claim |
| "Studies show..." (no citation) | Unsourced authority claim |
| "Everyone agrees..." | Unfalsifiable |
| "Trust us when we say..." | Demands trust rather than earning it |
| Generic "top tips" language | Could have been written by anyone |
| No first-person perspective | Reads like encyclopedia, not experience |
| "In this article, we will..." | Filler, not experience signal |
Trust Indicators
Trust is the most important member of the E-E-A-T family (September 2025 QRG). Trust encompasses and validates all other signals.
Site-Level Trust Signals
| Signal | Priority | Implementation |
|---|---|---|
| Contact page | Critical | Real email, phone, or contact form |
| About page | Critical | Company/author info, mission, team |
| Privacy policy | Critical | Required depending on jurisdiction, tracking, and data collection |
| Terms of service | High | Legal framework for content use |
| Editorial policy | High | How content is created, reviewed, updated |
| Physical address | High (local) | Required for LocalBusiness, helpful for all |
| Author social profiles | High | Verifiable external presence |
| HTTPS | Critical | Non-negotiable baseline |
| Clear ownership | High | Who publishes this site and why |
Content-Level Trust Signals
| Signal | Implementation |
|---|---|
| Source attribution | Every claim backed by named source |
| Transparent methodology | How data was collected, sample size |
| Conflict of interest disclosure | Affiliate links, sponsorships |
| Correction/update notes | "Updated [date]: corrected [what]" |
| Expert review | "Reviewed by [Expert Name], [credentials]" |
| Date transparency | Publish date AND last updated date visible |
Trustworthiness requires the FLOW evidence triple. Experience and authority signals only land when the underlying claims are verifiable: year anchor in prose, inline citation with publisher and title, URL with retrieval date in compact retrieval notes, footnotes, or a bibliography. See flow-alignment.md.
September 2025 QRG Key Principle
Google's Quality Rater Guidelines (September 11, 2025 revision) remain the current QRG in mid-2026 as of 2026-07-07. That 182-page version renamed "YMYL Society" to "YMYL Government, Civics & Society," added AI Overview evaluation examples, and assigned lowest ratings to value-less auto or AI content.
The E-E-A-T framing is stable. Google's September 2025 revision established:
"Trust is the most important member of the E-E-A-T family because untrustworthy pages have low E-E-A-T no matter how Experienced, Expert, or Authoritative they may seem."
This means a page with brilliant expert content but missing trust signals (no author attribution, no contact info, no source citations) will score low overall. Trust is the foundation; the other three factors build on it.
E-E-A-T Scoring Rubric
These are internal scoring weights for the claude-blog quality rubric. Google does not publish numeric E-E-A-T weights.
| Factor | Internal Weight | Key Signals |
|---|---|---|
| Experience | 20% | First-hand knowledge, original content, case studies, personal testing, process documentation |
| Expertise | 25% | Credentials, technical depth, accuracy, comprehensiveness, professional background |
| Authoritativeness | 25% | Industry recognition, external citations, backlinks, reputation, speaking/publication history |
| Trustworthiness | 30% | Contact info, transparency, security, source attribution, editorial policy, corrections |
Scoring Flow
Trust is evaluated FIRST. If trust is low, the overall E-E-A-T score is capped regardless of how strong the other three signals are.
Trust Assessment → If Low → Cap at "Low E-E-A-T"
→ If Adequate → Evaluate E + E + A → Combined Score
E-E-A-T Framing by Topic Risk
Helpful, trustworthy content matters broadly, but evidence expectations scale with topic risk and likely user harm. YMYL topics still carry the highest scrutiny.
- Highest risk: health, finance, legal, safety, elections, civics, and other YMYL topics need strong credentials, sourcing, review, and harm-prevention language.
- Medium risk: technical, business, and product guidance needs first-hand testing, transparent methodology, and current sources.
- Lower risk: hobby and entertainment topics still benefit from experience signals, but they do not need the same proof burden as health or finance.
Practical Impact
A blog post about "best mechanical keyboards" should show first-hand testing and transparent recommendations. A post about "best health insurance plans" needs a much higher bar for credentials, review, sourcing, and legal or financial caveats.
E-E-A-T Signals by Content Type
| Content Type | Experience | Expertise | Authoritativeness | Trustworthiness |
|---|---|---|---|---|
| Blog Post | Author tested/used what they write about; personal anecdotes | Deep topic knowledge; technical accuracy | Links from other sites; author published elsewhere | Sourced claims; editorial policy; contact page |
| Product Review | Hands-on testing; original photos/video; owns the product | Technical specs knowledge; comparison framework | Known reviewer; multiple reviews published | Disclosure of affiliates; transparent scoring method |
| How-To Guide | Author has done the process; screenshots of their work | Step accuracy; edge cases covered; troubleshooting | Recognized practitioner; cited by others | Tested instructions; warnings included; updated dates |
| News Article | Reporter was present or interviewed sources directly | Subject matter knowledge; context provided | Established publication; editorial oversight | Multiple sources; corrections policy; byline |
| Opinion/Editorial | Author has relevant professional experience | Informed perspective backed by evidence | Published track record; industry standing | Clearly labeled as opinion; counterpoints acknowledged |
Minimum Requirements by Content Type
| Content Type | Must Have |
|---|---|
| Blog Post | Named author, 2+ sourced stats, author bio with credentials |
| Product Review | Original photos, hands-on testing evidence, disclosure |
| How-To Guide | Author's own screenshots, tested steps, last-updated date |
| News Article | Named journalist, 2+ sources, publication editorial policy |
| Opinion/Editorial | Author credentials for topic, "Opinion" label, evidence |
| 1 | # Author E-E-A-T Requirements |
| 2 | |
| 3 | ## Contents |
| 4 | |
| 5 | [Named Author Attribution] |
| 6 | [Author Bio Structure] |
| 7 | [Author Page Requirements] |
| 8 | [Person Schema Properties] |
| 9 | [Experience Signal Markers] |
| 10 | [Trust Indicators] |
| 11 | [September 2025 QRG Key Principle] |
| 12 | [E-E-A-T Scoring Rubric] |
| 13 | [E-E-A-T Framing by Topic Risk] |
| 14 | [E-E-A-T Signals by Content Type] |
| 15 | |
| 16 | ## Named Author Attribution |
| 17 | |
| 18 | A named accountable author or editor is strongly preferred for every blog post. |
| 19 | Organization attribution is acceptable when the organization is the accountable |
| 20 | publisher and the page also exposes clear editorial ownership. |
| 21 | |
| 22 | ### Never Use |
| 23 | |
| 24 | | Attribution | Problem | |
| 25 | |-------------|---------| |
| 26 | | "Admin" | No person, no trust | |
| 27 | | "Staff" | Indistinguishable from auto-generated | |
| 28 | | "Team" | No individual accountability | |
| 29 | | "Editor" | Not an author signal | |
| 30 | | No byline | Worst case: page appears authorless | |
| 31 | |
| 32 | ### Preferred |
| 33 | |
| 34 | Full real name (first + last) |
| 35 | Crawlable author or profile page with a stable URL |
| 36 | Same name used on social profiles linked via `sameAs` |
| 37 | One author per post (co-authors acceptable with both named) |
| 38 | |
| 39 | |
| 40 | |
| 41 | ## Author Bio Structure |
| 42 | |
| 43 | 2-3 sentences. The bio establishes E-E-A-T credentials, not a sales pitch. |
| 44 | |
| 45 | ### Formula |
| 46 | |
| 47 | **Sentence 1**: [Name] is a [role/title] with [N years] experience in [domain]. |
| 48 | **Sentence 2**: [Credential, employer, or notable achievement relevant to the topic]. |
| 49 | **Sentence 3** (optional): [Specific focus area or what they write about]. |
| 50 | |
| 51 | ### Good Examples |
| 52 | |
| 53 | > Sarah Chen is a content strategist with 8 years of experience in B2B SaaS. |
| 54 | > She's led content programs at HubSpot and Drift, specializing in data-driven |
| 55 | > blog optimization. |
| 56 | |
| 57 | > Marcus Rivera is a senior frontend engineer at Vercel. He maintains two |
| 58 | > open-source React component libraries with 12K+ combined GitHub stars and |
| 59 | > writes about performance patterns for production applications. |
| 60 | |
| 61 | > Dr. Elena Vasquez is a clinical psychologist and researcher at Stanford |
| 62 | > Medical Center. She has published 23 peer-reviewed papers on cognitive |
| 63 | > behavioral therapy and digital mental health interventions. |
| 64 | |
| 65 | ### Bad Examples (Anti-Patterns) |
| 66 | |
| 67 | > "John is passionate about helping businesses grow through innovative digital |
| 68 | > solutions.": Vague, no credentials, sounds like marketing copy. |
| 69 | |
| 70 | > "Our team of experts delivers world-class content marketing services." |
| 71 | >: Not a person, promotional, no specific expertise. |
| 72 | |
| 73 | > "Jane is the CEO of GrowthMax Inc., the leading AI-powered marketing |
| 74 | > platform.": Sales pitch disguised as bio. |
| 75 | |
| 76 | |
| 77 | |
| 78 | ## Author Page Requirements |
| 79 | |
| 80 | Every named author should have a crawlable author or profile page. The URL path |
| 81 | can follow the site's existing information architecture. |
| 82 | |
| 83 | ### Page Must Include |
| 84 | |
| 85 | | Element | Details | |
| 86 | |---------|---------| |
| 87 | | Full name (H1) | Same name used in bylines | |
| 88 | | Professional photo | Real photo, not avatar or stock | |
| 89 | | Extended bio | 100-200 words with credentials | |
| 90 | | Social links | LinkedIn, Twitter/X, personal site, GitHub (as relevant) | |
| 91 | | Article list | All published posts by this author, newest first | |
| 92 | | ProfilePage schema | JSON-LD with Person entity | |
| 93 | |
| 94 | ### ProfilePage Schema Example |
| 95 | |
| 96 | |
| 97 | { |
| 98 | "@context": "https://schema.org", |
| 99 | "@type": "ProfilePage", |
| 100 | "mainEntity": { |
| 101 | "@type": "Person", |
| 102 | "@id": "https://example.com/author/sarah-chen#person", |
| 103 | "name": "Sarah Chen", |
| 104 | "jobTitle": "Content Strategist", |
| 105 | "description": "Content strategist with 8 years of experience in B2B SaaS, specializing in data-driven blog optimization.", |
| 106 | "url": "https://example.com/author/sarah-chen", |
| 107 | "image": "https://example.com/images/authors/sarah-chen.jpg", |
| 108 | "sameAs": [ |
| 109 | "https://linkedin.com/in/sarahchen", |
| 110 | "https://twitter.com/sarahchen", |
| 111 | "https://sarahchen.com" |
| 112 | ], |
| 113 | "worksFor": { |
| 114 | "@type": "Organization", |
| 115 | "name": "Example Corp" |
| 116 | }, |
| 117 | "alumniOf": { |
| 118 | "@type": "CollegeOrUniversity", |
| 119 | "name": "UC Berkeley" |
| 120 | } |
| 121 | } |
| 122 | } |
| 123 | |
| 124 | |
| 125 | |
| 126 | |
| 127 | ## Person Schema Properties |
| 128 | |
| 129 | The Person schema embedded in BlogPosting and on author pages. |
| 130 | |
| 131 | | Property | Required | Description | Example | |
| 132 | |----------|----------|-------------|---------| |
| 133 | | `@type` | Yes | Always "Person" | `"Person"` | |
| 134 | | `@id` | Yes | Stable URI with fragment | `"https://example.com/author/sarah-chen#person"` | |
| 135 | | `name` | Yes | Full name | `"Sarah Chen"` | |
| 136 | | `jobTitle` | Yes | Current role | `"Content Strategist"` | |
| 137 | | `url` | Yes | Author page URL | `"https://example.com/author/sarah-chen"` | |
| 138 | | `image` | Yes | Headshot URL | `"https://example.com/images/authors/sarah-chen.jpg"` | |
| 139 | | `sameAs` | Yes | Array of social/profile URLs | `["https://linkedin.com/in/sarahchen"]` | |
| 140 | | `worksFor` | Recommended | Organization entity | `{"@type": "Organization", "name": "Example Corp"}` | |
| 141 | | `alumniOf` | Optional | Educational institution | `{"@type": "CollegeOrUniversity", "name": "UC Berkeley"}` | |
| 142 | | `description` | Recommended | Brief professional summary | `"B2B SaaS content strategist..."` | |
| 143 | | `knowsAbout` | Optional | Array of expertise topics | `["SEO", "content strategy", "B2B marketing"]` | |
| 144 | |
| 145 | ### Complete Person JSON-LD |
| 146 | |
| 147 | |
| 148 | { |
| 149 | "@type": "Person", |
| 150 | "@id": "https://example.com/author/sarah-chen#person", |
| 151 | "name": "Sarah Chen", |
| 152 | "jobTitle": "Content Strategist", |
| 153 | "url": "https://example.com/author/sarah-chen", |
| 154 | "image": "https://example.com/images/authors/sarah-chen.jpg", |
| 155 | "description": "Content strategist with 8 years of experience in B2B SaaS, specializing in data-driven blog optimization.", |
| 156 | "sameAs": [ |
| 157 | "https://linkedin.com/in/sarahchen", |
| 158 | "https://twitter.com/sarahchen", |
| 159 | "https://sarahchen.com" |
| 160 | ], |
| 161 | "worksFor": { |
| 162 | "@type": "Organization", |
| 163 | "name": "Example Corp", |
| 164 | "url": "https://example.com" |
| 165 | }, |
| 166 | "alumniOf": { |
| 167 | "@type": "CollegeOrUniversity", |
| 168 | "name": "UC Berkeley" |
| 169 | }, |
| 170 | "knowsAbout": ["SEO", "Content Strategy", "B2B SaaS Marketing"] |
| 171 | } |
| 172 | |
| 173 | |
| 174 | |
| 175 | |
| 176 | ## Experience Signal Markers |
| 177 | |
| 178 | Phrases that demonstrate first-hand experience. Use these naturally throughout |
| 179 | content to signal genuine expertise to both human readers and quality raters. |
| 180 | In AI citation selection, demonstrated Experience is the tie-breaker when two |
| 181 | sources are similarly authoritative: original testing, named workflows, direct |
| 182 | observations, and proprietary data win over generic summaries. |
| 183 | |
| 184 | ### Use These Patterns |
| 185 | |
| 186 | | Pattern | When to Use | |
| 187 | |---------|-------------| |
| 188 | | "When we tested..." | Describing an experiment or A/B test | |
| 189 | | "In our experience..." | Sharing practitioner insight | |
| 190 | | "After implementing this for [client]..." | Case study context | |
| 191 | | "Over the past [N] years, I've found..." | Long-term observation | |
| 192 | | "Here's what our data shows..." | Introducing proprietary findings | |
| 193 | | "I've personally seen..." | Direct observation | |
| 194 | | "We ran this experiment across [N] sites..." | Multi-site testing | |
| 195 | | "What surprised us was..." | Counterintuitive findings | |
| 196 | | "The mistake most teams make is..." | Practitioner wisdom | |
| 197 | | "When I worked at [Company]..." | Named employer context | |
| 198 | |
| 199 | ### Signals to AVOID |
| 200 | |
| 201 | | Anti-Pattern | Problem | |
| 202 | |-------------|---------| |
| 203 | | "As an expert in..." | Self-proclaimed authority, no evidence | |
| 204 | | "It is well known that..." | Vague consensus claim | |
| 205 | | "Studies show..." (no citation) | Unsourced authority claim | |
| 206 | | "Everyone agrees..." | Unfalsifiable | |
| 207 | | "Trust us when we say..." | Demands trust rather than earning it | |
| 208 | | Generic "top tips" language | Could have been written by anyone | |
| 209 | | No first-person perspective | Reads like encyclopedia, not experience | |
| 210 | | "In this article, we will..." | Filler, not experience signal | |
| 211 | |
| 212 | |
| 213 | |
| 214 | ## Trust Indicators |
| 215 | |
| 216 | Trust is the most important member of the E-E-A-T family (September 2025 QRG). |
| 217 | Trust encompasses and validates all other signals. |
| 218 | |
| 219 | ### Site-Level Trust Signals |
| 220 | |
| 221 | | Signal | Priority | Implementation | |
| 222 | |--------|----------|----------------| |
| 223 | | Contact page | Critical | Real email, phone, or contact form | |
| 224 | | About page | Critical | Company/author info, mission, team | |
| 225 | | Privacy policy | Critical | Required depending on jurisdiction, tracking, and data collection | |
| 226 | | Terms of service | High | Legal framework for content use | |
| 227 | | Editorial policy | High | How content is created, reviewed, updated | |
| 228 | | Physical address | High (local) | Required for LocalBusiness, helpful for all | |
| 229 | | Author social profiles | High | Verifiable external presence | |
| 230 | | HTTPS | Critical | Non-negotiable baseline | |
| 231 | | Clear ownership | High | Who publishes this site and why | |
| 232 | |
| 233 | ### Content-Level Trust Signals |
| 234 | |
| 235 | | Signal | Implementation | |
| 236 | |--------|----------------| |
| 237 | | Source attribution | Every claim backed by named source | |
| 238 | | Transparent methodology | How data was collected, sample size | |
| 239 | | Conflict of interest disclosure | Affiliate links, sponsorships | |
| 240 | | Correction/update notes | "Updated [date]: corrected [what]" | |
| 241 | | Expert review | "Reviewed by [Expert Name], [credentials]" | |
| 242 | | Date transparency | Publish date AND last updated date visible | |
| 243 | |
| 244 | **Trustworthiness requires the FLOW evidence triple.** Experience and authority signals only land when the underlying claims are verifiable: year anchor in prose, inline citation with publisher and title, URL with retrieval date in compact retrieval notes, footnotes, or a bibliography. See `flow-alignment.md`. |
| 245 | |
| 246 | |
| 247 | |
| 248 | ## September 2025 QRG Key Principle |
| 249 | |
| 250 | Google's Quality Rater Guidelines (September 11, 2025 revision) remain the |
| 251 | current QRG in mid-2026 as of 2026-07-07. That 182-page version renamed "YMYL |
| 252 | Society" to "YMYL Government, Civics & Society," added AI Overview evaluation |
| 253 | examples, and assigned lowest ratings to value-less auto or AI content. |
| 254 | |
| 255 | The E-E-A-T framing is stable. Google's September 2025 revision established: |
| 256 | |
| 257 | > "Trust is the most important member of the E-E-A-T family because untrustworthy |
| 258 | > pages have low E-E-A-T no matter how Experienced, Expert, or Authoritative they |
| 259 | > may seem." |
| 260 | |
| 261 | This means a page with brilliant expert content but missing trust signals (no |
| 262 | author attribution, no contact info, no source citations) will score low overall. |
| 263 | Trust is the foundation; the other three factors build on it. |
| 264 | |
| 265 | |
| 266 | |
| 267 | ## E-E-A-T Scoring Rubric |
| 268 | |
| 269 | These are internal scoring weights for the claude-blog quality rubric. Google |
| 270 | does not publish numeric E-E-A-T weights. |
| 271 | |
| 272 | | Factor | Internal Weight | Key Signals | |
| 273 | |--------|-----------------|-------------| |
| 274 | | Experience | 20% | First-hand knowledge, original content, case studies, personal testing, process documentation | |
| 275 | | Expertise | 25% | Credentials, technical depth, accuracy, comprehensiveness, professional background | |
| 276 | | Authoritativeness | 25% | Industry recognition, external citations, backlinks, reputation, speaking/publication history | |
| 277 | | Trustworthiness | 30% | Contact info, transparency, security, source attribution, editorial policy, corrections | |
| 278 | |
| 279 | ### Scoring Flow |
| 280 | |
| 281 | Trust is evaluated FIRST. If trust is low, the overall E-E-A-T score is capped |
| 282 | regardless of how strong the other three signals are. |
| 283 | |
| 284 | |
| 285 | Trust Assessment → If Low → Cap at "Low E-E-A-T" |
| 286 | → If Adequate → Evaluate E + E + A → Combined Score |
| 287 | |
| 288 | |
| 289 | |
| 290 | |
| 291 | ## E-E-A-T Framing by Topic Risk |
| 292 | |
| 293 | Helpful, trustworthy content matters broadly, but evidence expectations scale |
| 294 | with topic risk and likely user harm. YMYL topics still carry the highest |
| 295 | scrutiny. |
| 296 | |
| 297 | **Highest risk**: health, finance, legal, safety, elections, civics, and other |
| 298 | YMYL topics need strong credentials, sourcing, review, and harm-prevention |
| 299 | language. |
| 300 | **Medium risk**: technical, business, and product guidance needs first-hand |
| 301 | testing, transparent methodology, and current sources. |
| 302 | **Lower risk**: hobby and entertainment topics still benefit from experience |
| 303 | signals, but they do not need the same proof burden as health or finance. |
| 304 | |
| 305 | ### Practical Impact |
| 306 | |
| 307 | A blog post about "best mechanical keyboards" should show first-hand testing and |
| 308 | transparent recommendations. A post about "best health insurance plans" needs a |
| 309 | much higher bar for credentials, review, sourcing, and legal or financial caveats. |
| 310 | |
| 311 | |
| 312 | |
| 313 | ## E-E-A-T Signals by Content Type |
| 314 | |
| 315 | | Content Type | Experience | Expertise | Authoritativeness | Trustworthiness | |
| 316 | |-------------|------------|-----------|-------------------|-----------------| |
| 317 | | **Blog Post** | Author tested/used what they write about; personal anecdotes | Deep topic knowledge; technical accuracy | Links from other sites; author published elsewhere | Sourced claims; editorial policy; contact page | |
| 318 | | **Product Review** | Hands-on testing; original photos/video; owns the product | Technical specs knowledge; comparison framework | Known reviewer; multiple reviews published | Disclosure of affiliates; transparent scoring method | |
| 319 | | **How-To Guide** | Author has done the process; screenshots of their work | Step accuracy; edge cases covered; troubleshooting | Recognized practitioner; cited by others | Tested instructions; warnings included; updated dates | |
| 320 | | **News Article** | Reporter was present or interviewed sources directly | Subject matter knowledge; context provided | Established publication; editorial oversight | Multiple sources; corrections policy; byline | |
| 321 | | **Opinion/Editorial** | Author has relevant professional experience | Informed perspective backed by evidence | Published track record; industry standing | Clearly labeled as opinion; counterpoints acknowledged | |
| 322 | |
| 323 | ### Minimum Requirements by Content Type |
| 324 | |
| 325 | | Content Type | Must Have | |
| 326 | |-------------|-----------| |
| 327 | | Blog Post | Named author, 2+ sourced stats, author bio with credentials | |
| 328 | | Product Review | Original photos, hands-on testing evidence, disclosure | |
| 329 | | How-To Guide | Author's own screenshots, tested steps, last-updated date | |
| 330 | | News Article | Named journalist, 2+ sources, publication editorial policy | |
| 331 | | Opinion/Editorial | Author credentials for topic, "Opinion" label, evidence | |
| 332 |
Discussion
Browse more free Claude skills.