eeat-signals

$npx mdskill add kostja94/marketing-skills/eeat-signals

Improve content E-E-A-T signals for SEO and trust.

  • Optimizes content for experience, expertise, authority, and trustworthiness.
  • Relies on content analysis and SEO best practices.
  • Decides based on YMYL topics and missing trust signals.
  • Outputs actionable recommendations for author bios, citations, and structure.

SKILL.md

.github/skills/eeat-signalsView on GitHub ↗
---
name: eeat-signals
description: When the user wants to improve E-E-A-T, add trust signals, or optimize for expertise and authority. Also use when the user mentions "E-E-A-T," "E-E-A-T signals," "experience expertise authority trust," "author bio," "YMYL," "trust signals," "expertise signals," "authority signals," "citations," "references," or "credibility." For headings, use heading-structure.
metadata:
  version: 1.0.1
---

# SEO Content: E-E-A-T Signals

Guides E-E-A-T (Experience, Expertise, Authoritativeness, Trustworthiness) implementation for SEO. E-E-A-T helps search engines and users assess content quality; YMYL topics (health, finance, legal) require higher E-E-A-T.

**When invoking**: On **first use**, if helpful, open with 1–2 sentences on what this skill covers and why it matters, then provide the main output. On **subsequent use** or when the user asks to skip, go directly to the main output.

## What Is E-E-A-T

| Element | Meaning | Implementation |
|---------|---------|-----------------|
| **Experience** | First-hand, real-world experience | Case studies, original research, user testimonials, "we tested" |
| **Expertise** | Subject-matter knowledge | Author credentials, expert quotes, technical depth |
| **Authoritativeness** | Recognition as a source | Backlinks, citations, author page, publisher reputation |
| **Trustworthiness** | Accuracy, transparency | Citations, About page, contact, HTTPS, no misleading content |

**E-A-T** (without Experience) is used in Featured Snippet context—Bing/Google emphasize correctness, document quality, then authority and trust. See **featured-snippet**.

## Author Bio

### Components

| Element | Guideline |
|---------|-----------|
| **Real name** | Full name used consistently across platforms |
| **Photo** | Professional headshot; compress for LCP |
| **Credentials** | Current role, relevant experience tied to article topic |
| **Verifiable links** | LinkedIn, personal site; align `sameAs` in Person schema |
| **Author page** | Dedicated page per author; bio, other articles, social |
| **Lightweight action (optional)** | Newsletter signup, social follow — avoid link stacking |

### Placement

- **End of article** (default): User finishes reading, naturally curious about author; standard for blogs and deep content.
- **Top of article**: Strong expert endorsement; suited for news, YMYL, or short items.
- **Sidebar** (desktop): Compact version. **Mobile fallback required** — sidebar content often disappears on small screens; place author block within the main content column at the bottom on mobile.

### Multi-Author

For co-authored, reviewed, or fact-checked content, list multiple author cards or label roles consistently (e.g. "Written by / Reviewed by").

### Schema

Author entity uses `Person` JSON-LD with `name`, `url`, `image`, `jobTitle`, `worksFor`, `knowsAbout`, `sameAs`. Must match visible page content — no exaggeration or fabricated credentials. Validate with [Rich Results Test](https://search.google.com/test/rich-results). See **entity-seo**, **schema-markup**.

## Citations & References

| Scenario | Practice |
|----------|----------|
| **Data or statistics** | Cite source inline or in References section |
| **Expert quotes** | Attribute; link to source or profile |
| **Reference section** | For 5+ citations; list at end before Related posts |
| **Format** | Inline links preferred; numbered refs for academic-style |
| **When to include** | Any claim benefiting from authority (stats, studies, definitions) |
| **External links** | Link to reputable sources; avoid low-quality sites |

## Experience Signals

| Signal | Use |
|--------|-----|
| **Case studies** | Real customer outcomes; Challenge→Solution→Results |
| **Original research** | First-party data, surveys, tests |
| **First-hand testing** | "We tested X"; product reviews with real use |
| **User testimonials** | Authentic quotes; link to full case study when available |

## YMYL (Your Money Your Life)

Topics that can significantly impact health, financial stability, or safety require **higher E-E-A-T**:

- **Health**: Medical, mental health, nutrition advice
- **Finance**: Investment, tax, insurance, loans
- **Legal**: Legal advice, regulations
- **Safety**: Product safety, emergency procedures

**Guidelines**: Author credentials, citations to authoritative sources, clear sourcing, regular updates, avoid speculation.

## AI-Assisted Content

When content is AI-assisted: **human review** before publish; **verify facts** and add citations; **original insights** or data; avoid generic phrasing. Transparency and human refinement support E-E-A-T.

## Output Format

- **E-E-A-T assessment** (gaps, strengths)
- **Author bio** recommendation
- **Citation** plan (where to add, what to cite)
- **Experience** signals (case studies, original data)
- **YMYL** considerations (if applicable)

## Related Skills

- **article-page-generator**: Article page structure; author bio placement
- **article-content**: Article body creation; citations, references format
- **content-optimization**: Original images, content quality; E-E-A-T complements
- **link-building**: Digital PR, E-E-A-T; backlinks signal authority
- **featured-snippet**: E-A-T in snippet algorithm; correctness, authority
- **backlink-analysis**: Authority assessment; E-E-A-T context
- **customer-stories-page-generator**: Case studies as experience signal
- **testimonials-generator**: User quotes as trust signal
- **entity-seo**: Entity signals; Organization, Person schema; Knowledge Panel; E-E-A-T alignment

More from kostja94/marketing-skills

SkillDescription
404-page-generatorWhen the user wants to create, optimize, or audit 404 error pages. Also use when the user mentions "404 page," "404 error," "error page," "page not found," "broken link page," "404 design," "custom 404," "404 redirect," "404 page UX," or "404 recovery." For sitewide page planning, use website-structure.
about-page-generatorWhen the user wants to create, optimize, or audit About page content. Also use when the user mentions "about page," "about us," "company story," "our team," "about section," "company overview," "brand story," "team page," or "who we are." For sitewide page planning, use website-structure.
affiliate-marketingWhen the user wants to plan, implement, or optimize affiliate marketing strategy. Also use when the user mentions "affiliate marketing," "affiliate program strategy," "CPS model," "affiliate recruitment," "commission structure," "affiliate partners," "affiliate network," "affiliate tracking," "affiliate commission," or "partner marketing." For affiliate page, use affiliate-page-generator.
affiliate-page-generatorWhen the user wants to create, optimize, or audit affiliate program page content. Also use when the user mentions "affiliate program," "affiliate page," "partner program," "referral program page," "affiliate landing," "partner landing," "commission page," or "affiliate signup." For affiliate program strategy, use affiliate-marketing.
ai-traffic-trackingWhen the user wants to track AI search traffic in GA4 or GSC. Also use when the user mentions "AI traffic," "ChatGPT referral," "Perplexity traffic," "AI Overviews," "GA4 AI sources," "AI search analytics," "track AI referrals," "AI search traffic," "Claude traffic," or "how to track AI traffic." For AI SEO strategy, use generative-engine-optimization.
alternatives-page-generatorWhen the user wants to create, optimize, or audit alternatives or comparison content (page or blog article). Also use when the user mentions "alternatives page," "alternatives listicle," "X alternatives," "competitor comparison," "vs page," "compare page," "best alternatives to X," "switch from X," "competitor brand traffic," "brand keyword ads," or "intercept competitor search." For competitor research, use competitor-research.
api-page-generatorWhen the user wants to create, optimize, or audit the API introduction/overview page. Also use when the user mentions "API page," "API landing page," "/api page," "API overview," "developer landing," "API marketing," or "API for developers." Note: API documentation (endpoint reference) lives in docs; use docs-page-generator.
app-adsWhen the user wants to run app install ads, user acquisition (UA), or promote mobile apps. Also use when the user mentions "app ads," "app install ads," "UA," "user acquisition," "Google App Campaigns," "Apple Search Ads," "ASA," "UAC," "App Store ads," "Play Store ads," "CPI," or "app promotion." For store listings, use distribution-channels.
article-contentWhen the user wants to write, generate, or create article body content—blog post body, long-form content, how-to guide, listicle. Also use when the user mentions "write article," "article content," "blog post content," "article body," "long-form content creation," "generate article," "article draft," "how-to guide content," "listicle content," "information gain," or "content density." For single post page structure, schema, and SEO metadata, use article-page-generator. For blog index/listing page, use blog-page-generator. For short ad, landing, or email copy, use copywriting.
backlink-analysisWhen the user wants to analyze backlinks, audit link profile, or identify link issues. Also use when the user mentions "backlink analysis," "backlink audit," "referring domains," "toxic links," "link profile," or "disavow file." For acquisition, use link-building.