skillboardUpdated every 6 hours
skillboardWhen 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.
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.
| 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.
| 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 |
For co-authored, reviewed, or fact-checked content, list multiple author cards or label roles consistently (e.g. "Written by / Reviewed by").
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. See entity-seo, schema-markup.
| 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 |
| 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 |
Topics that can significantly impact health, financial stability, or safety require higher E-E-A-T:
Guidelines: Author credentials, citations to authoritative sources, clear sourcing, regular updates, avoid speculation.
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.
Copy a source-pinned command for your client. You run it yourself.
Destination: .claude/skills/eeat-signals · pinned to the source commit
git clone https://github.com/kostja94/marketing-skills.git
cd marketing-skills
git checkout 70987bad4ebe9dce1f74858c1c64f3f8810f18e4
mkdir -p ".claude/skills/eeat-signals"
cp -r "skills/seo/content/eeat-signals" ".claude/skills/eeat-signals"Review the source before running. This copies files into your project; it is not a one-click install and does not verify runtime safety.
Scanner static-checks@0.1.0 · commit 70987bad4ebe. Static checks cannot prove runtime safety – review the source and the exact diff before installing. How checks work.
No static rules matched. This is not a safety guarantee.