Eeat Signals
Implement Experience, Expertise, Authoritativeness, and Trustworthiness on landing pages, blogs, and YMYL content so Google and AI search surfaces treat the site as credible.
Overview
E-E-A-T Signals is an agent skill most often used in Launch (also Grow content, Validate landing) that guides implementation of experience, expertise, authority, and trust markers for SEO and YMYL pages.
Install
npx skills add https://github.com/kostja94/marketing-skills --skill eeat-signalsWhat is this skill?
- Four-pillar E-E-A-T table: Experience, Expertise, Authoritativeness, Trustworthiness with concrete implementation rows
- YMYL guidance for health, finance, and legal topics requiring stronger proof and transparency
- Author bio, credentials, case studies, and citation patterns called out as repeatable signals
- Pairs with heading-structure skill for on-page SEO depth
- First-use framing: optional 1–2 sentence overview then actionable E-E-A-T checklist output
- 4 E-E-A-T elements defined in the implementation table
- Skill metadata version 1.0.1
Adoption & trust: 785 installs on skills.sh; 586 GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
Your pages rank poorly or feel thin because search engines and users cannot see who wrote them, what real experience backs the claims, or where facts are cited.
Who is it for?
Solo founders publishing blog, docs, or landing content in competitive or YMYL-adjacent niches who need a repeatable trust checklist from an agent.
Skip if: Pure B2B apps with no public marketing site, or teams that only need technical sitemap/robots work without content credibility rewrites.
When should I use this skill?
User mentions E-E-A-T, trust signals, YMYL, author bio, expertise or authority signals, citations, references, or credibility—or asks to improve perceived expertise for SEO.
What do I get? / Deliverables
You get a structured E-E-A-T implementation plan—author, citations, trust pages, and experience proof—ready to edit into live URLs before or after publish.
- E-E-A-T gap list mapped to the four pillars
- Concrete on-page edits (author, citations, experience proof)
- Trust transparency recommendations (About, contact, accuracy)
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Launch → seo is the canonical shelf because the skill maps E-E-A-T elements to on-page and site-level SEO signals aimed at ranking and snippet quality, not day-one product coding. SEO subphase covers trust copy, author entities, citations, and YMYL rigor—the same work solo founders do when pages go public and compete in SERPs.
Where it fits
Add author credentials and transparent pricing claims on a pre-launch landing page before ad spend.
Audit a launch blog post for experience statements, expert quotes, and outbound citations to authoritative sources.
Refresh top traffic articles with stronger About-page linkage and trustworthiness fixes (HTTPS, contact, no misleading hooks).
How it compares
On-page trust and expertise playbook—not a backlink outreach tool or paid-ads creative generator.
Common Questions / FAQ
Who is eeat-signals for?
Indie builders and small teams optimizing marketing or editorial sites who want agent-guided E-E-A-T without hiring an SEO agency.
When should I use eeat-signals?
Use it at Launch when polishing SEO before go-live, during Grow when upgrading older posts with author bios and citations, or at Validate when stress-testing landing page trust before you spend on distribution.
Is eeat-signals safe to install?
The skill is editorial guidance only; confirm upstream package integrity via the Security Audits panel on this Prism page before enabling it in production agents.
SKILL.md
READMESKILL.md - Eeat Signals
# 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) To