Seo Content
Audit a URL or draft for Google helpful-content signals, E-E-A-T, readability, thin-content risk, and AI-citation readiness before you ship or refresh pages.
Overview
seo-content is an agent skill most often used in Launch (also Grow) that audits pages for helpful-content signals, E-E-A-T, readability, thin content, and AI citation readiness.
Install
npx skills add https://github.com/agricidaniel/claude-seo --skill seo-contentWhat is this skill?
- Runs Google’s Who / How / Why helpful-content heuristic before E-E-A-T sub-factor scoring
- E-E-A-T framework with YMYL-aware author and expertise checks
- AI citation readiness assessment alongside readability and thin-content flags
- User-invokable with optional URL argument for live page audits
- v2.0.0 MIT skill under agricidaniel/claude-seo with SEO category metadata
- Three-question Who / How / Why heuristic table before E-E-A-T sub-factor scoring
- Skill metadata version 2.0.0
Adoption & trust: 2.1k installs on skills.sh; 8.5k GitHub stars; 2/3 security scanners passed (skills.sh audits).
What problem does it solve?
You have published or draft pages but no structured way to tell if they pass Google’s helpful-content bar, E-E-A-T, and citation-friendly quality before you invest in distribution.
Who is it for?
Solo builders shipping blogs, docs, or marketing pages who want an agent-driven E-E-A-T and content audit on a specific URL or draft.
Skip if: Teams that only need keyword rank tracking or technical crawl audits without editorial E-E-A-T judgment, or pages already signed off with no URL or text to analyze.
When should I use this skill?
User says "content quality", "E-E-A-T", "content analysis", "readability check", "thin content", or "content audit".
What do I get? / Deliverables
You get a Who/How/Why-grounded content quality assessment with E-E-A-T and readability findings you can use to revise copy, author bios, and disclosure before republishing or scaling SEO.
- E-E-A-T and helpful-content assessment
- Readability and thin-content findings
- AI citation readiness notes
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Canonical shelf is Launch because the skill is framed around search visibility, helpful-content heuristics, and page-level SEO content quality—not generic writing alone. SEO subphase matches explicit triggers (content audit, E-E-A-T, thin content) and the Who/How/Why helpful-content checklist from Google’s guidance.
Where it fits
Run a Who/How/Why pass on a new pricing page before you turn on distribution and backlinks.
Refresh older tutorial posts that read thin after competitors added first-hand examples.
Stress-test a waitlist landing page for credibility signals before you drive paid traffic.
Pre-flight editorial review on release notes and changelog pages tied to a product launch.
How it compares
Editorial E-E-A-T and helpful-content checker—not a sitemap generator or pure technical SEO crawler.
Common Questions / FAQ
Who is seo-content for?
Indie founders, content marketers, and dev-rel writers using Claude Code or Cursor who publish SEO-sensitive pages and need structured quality and E-E-A-T feedback.
When should I use seo-content?
At Launch when polishing landing and blog URLs for search and AI citations; at Grow when refreshing lifecycle or support content; whenever you say “content audit”, “E-E-A-T”, “thin content”, or “readability check”.
Is seo-content safe to install?
It is user-invokable MIT metadata from the catalog entry; review the Security Audits panel on this Prism page before pointing it at production URLs or pasted confidential drafts.
SKILL.md
READMESKILL.md - Seo Content
# Content Quality & E-E-A-T Analysis ## Google's "Who / How / Why" Test (canonical heuristic) Before scoring E-E-A-T sub-factors, every page audit should pass Google's own three-question heuristic from the helpful-content guide: | Question | What to look for | |---|---| | **Who** created it? | Visible byline, author bio page, professional credentials. Required where readers expect it; non-negotiable for YMYL. | | **How** was it created? | Process disclosure where readers would reasonably ask — especially for AI-assisted content. Original research / first-hand evidence / lived experience. | | **Why** does it exist? | "To help people" rather than "to attract search clicks." Watch for niche entry without expertise, content churn for freshness signals, content written to a word-count target. | Primary source: https://developers.google.com/search/docs/fundamentals/creating-helpful-content When all three answers are weak, the page is at risk under the core ranking system's helpfulness signals (formerly the standalone Helpful Content System, merged into core during the March 2024 update). ## E-E-A-T Framework (updated Sept 2025 QRG) Read `skills/seo/references/eeat-framework.md` for full criteria. ### Experience (first-hand signals) - Original research, case studies, before/after results - Personal anecdotes, process documentation - Unique data, proprietary insights - Photos/videos from direct experience ### Expertise - Author credentials, certifications, bio - Professional background relevant to topic - Technical depth appropriate for audience - Accurate, well-sourced claims ### Authoritativeness - External citations, backlinks from authoritative sources - Brand mentions, industry recognition - Published in recognized outlets - Cited by other experts ### Trustworthiness - Contact information, physical address - Privacy policy, terms of service - Customer testimonials, reviews - Date stamps, transparent corrections - Secure site (HTTPS) ## Content Metrics ### Word Count Analysis Compare against page type minimums: | Page Type | Minimum | |-----------|---------| | Homepage | 500 | | Service page | 800 | | Blog post | 1,500 | | Product page | 300+ (400+ for complex products) | | Location page | 500-600 | > **Important:** These are **topical coverage floors**, not targets. Google has confirmed word count is NOT a direct ranking factor. The goal is comprehensive topical coverage; a 500-word page that thoroughly answers the query will outrank a 2,000-word page that doesn't. Use these as guidelines for adequate coverage depth, not rigid requirements. ### Readability - Flesch Reading Ease: target 60-70 for general audience > **Note:** Flesch Reading Ease is a useful proxy for content accessibility but is NOT a direct Google ranking factor. John Mueller has confirmed Google does not use basic readability scores for ranking. Yoast deprioritized Flesch scores in v19.3. Use readability analysis as a content quality indicator, not as an SEO metric to optimize directly. - Grade level: match target audience - Sentence length: average 15-20 words - Paragraph length: 2-4 sentences ### Keyword Optimization - Primary keyword in title, H1, first 100 words - Natural density (1-3%) - Semantic variations present - No keyword stuffing ### Content Structure - Logical heading hierarchy (H1 -> H2 -> H3) - Scannable sections with descriptive headings - Bullet/numbered lists where appropriate - Table of contents for long-form content ### Multimedia - Relevant images with proper alt text - Videos where appropriate - Infographics for complex data - Charts/graphs for statistics