Stats
Actions
Tags
From claude-seo
Evaluates content quality and E-E-A-T for SEO with AI citation readiness. Useful for content audits, readability checks, and thin content analysis.
How this skill is triggered — by the user, by Claude, or both
Slash command
/claude-seo:seo-content [url][url]The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Before scoring E-E-A-T sub-factors, every page audit should pass Google's
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).
Read skills/seo/references/eeat-framework.md for full criteria.
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.
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.
Google's raters now formally assess whether content appears AI-generated.
Helpful Content System (March 2024): The Helpful Content System was merged into Google's core ranking algorithm during the March 2024 core update. It no longer operates as a standalone classifier. Helpfulness signals are now weighted within every core update. The same principles apply (people-first content, demonstrating E-E-A-T, satisfying user intent), but enforcement is continuous rather than through separate HCU updates.
Optimize for AI search engines (ChatGPT, Perplexity, Google AI Overviews):
Google AI Mode is Google's conversational AI search surface — powered by Gemini 3.5 Flash since I/O 2026 (May 2026) and now past 1 billion monthly users globally. Unlike AI Overviews (which appear above organic results), AI Mode is a fully conversational experience with zero organic blue links, making AI citation the only visibility mechanism. It is a distinct citation engine from AI Overviews — the two share only ~14% of cited URLs — so optimize for both surfaces, not one (see the seo-geo skill).
Key optimization strategies for AI citation:
Generative Engine Optimization (GEO):
Per Google's AI optimization guide, "AEO" and "GEO" are rebranded labels for SEO — AI Overviews and AI Mode are grounded in the same ranking and quality systems as classic Search. The optimization signals that matter (quotability, attribution, heading hierarchy, freshness) are SEO fundamentals applied to AI-search surfaces, not a separate discipline. Cross-reference the seo-geo skill for detailed workflows; both surfaces share the primary-source synthesis in skills/seo-geo/references/google-ai-optimization-guide.md.
| Factor | Score | Key Signals |
|---|---|---|
| Experience | XX/25 | ... |
| Expertise | XX/25 | ... |
| Authoritativeness | XX/25 | ... |
| Trustworthiness | XX/25 | ... |
If DataForSEO MCP tools are available, use kw_data_google_ads_search_volume for real keyword volume data, dataforseo_labs_bulk_keyword_difficulty for difficulty scores, dataforseo_labs_search_intent for intent classification, and content_analysis_summary for content quality analysis.
| Scenario | Action |
|---|---|
| URL unreachable (DNS failure, connection refused) | Report the error clearly. Do not guess page content. Suggest the user verify the URL and try again. |
| Content behind paywall (402/403, login wall) | Report that the content is not publicly accessible. Analyze only the visible portion (meta tags, headers) and note the limitation. |
| Thin content (fewer than 100 words retrievable) | Report the findings as-is rather than guessing. Flag the page as potentially JavaScript-rendered or gated, and suggest the user provide the full text directly. |
For prompt-guided content optimization, use /seo flow optimize <url> and /seo flow win <url> — FLOW's optimize and win prompts provide structured E-E-A-T improvement and BOFU conversion workflows.
npx claudepluginhub agricidaniel/claude-seo --plugin claude-seoEvaluates web page content quality using Google E-E-A-T criteria, readability scoring, and word count analysis. Useful for content audits, SEO reviews, and AI citation readiness checks.
Analyzes content for E-E-A-T compliance, quality metrics including readability, word count, keyword optimization, structure, and SEO best practices.
Analyzes content quality, readability, thin content risk, and E-E-A-T signals for SEO. Useful for content-focused audits and AI citation readiness checks.