Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
From antigravity-awesome-skills
Analyzes content quality via E-E-A-T framework, readability scores, word count benchmarks, keyword optimization, and structure for SEO audits and AI citation readiness.
npx claudepluginhub sickn33/antigravity-awesome-skills --plugin antigravity-awesome-skillsHow this skill is triggered — by the user, by Claude, or both
Slash command
/antigravity-awesome-skills:seo-content [url][url]This skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
- Use when auditing content quality, readability, thin content risk, or E-E-A-T signals.
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.
Analyzes content quality and E-E-A-T signals (Experience, Expertise, Authoritativeness, Trustworthiness) with word count and readability metrics. Useful for SEO content audits 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.
Share bugs, ideas, or general feedback.
Read 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 launched publicly in May 2025 as a separate tab in Google Search, available in 180+ countries. Unlike AI Overviews (which appear above organic results), AI Mode provides a fully conversational search experience with zero organic blue links, making AI citation the only visibility mechanism.
Key optimization strategies for AI citation:
Generative Engine Optimization (GEO):
GEO is the emerging discipline of optimizing content specifically for AI-generated answers. Key GEO signals include: quotability (clear, concise extractable facts), attribution (source citations within your content), structure (well-organized heading hierarchy), and freshness (regularly updated data). Cross-reference the seo-geo skill for detailed GEO workflows.
| 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. |