seo-content evaluates page content only, leaving technical checks to other skills. It starts with Google’s Who, How and Why test, then scores E-E-A-T across experience, expertise, authoritativeness and trust with the weights of its own model, and reviews word count floors, readability, keyword use, structure, media, links and freshness.
It also assesses AI-generated content patterns and AI citation readiness, checks for hidden text, and runs a cleanup script on your own drafts to strip zero-width characters and swap AI-typical phrases.
What You Get
- A Content Quality Score with an E-E-A-T breakdown across four factors
- An AI Citation Readiness score with quotability and structure findings
- Page-type word count floors presented as coverage guides, not ranking targets
- A hidden-text spam signal from the HTML parser
- A cleaned Markdown draft with a JSON log of removed characters and swapped phrases
Common Use Cases
- Review a blog post for experience and trust signals before publishing
- Find thin or gated pages that need more depth
- Strip zero-width characters and stock AI phrasing from your own draft
- Check a traffic drop against the list of confirmed Google updates
What Makes It Unique
It states its own limits: word counts are coverage floors, readability scores are not ranking factors, its E-E-A-T weights are an internal model that puts trust first, and its scores are heuristics. The cleanup script is limited to editing your own drafts and declines to strip provenance from content you do not own.
Under The Hood
The skill reads shared E-E-A-T reference files from the plugin and runs shell commands that start Python scripts through the claude-seo launcher. One parses a page fetched over the network and reports hidden text, one lists Google updates from a bundled ledger, and one reads a draft from a file or standard input and writes a cleaned copy to disk. Cleanup is two fixed passes, invisible characters and a table of phrase swaps, with nothing paraphrased. It can use DataForSEO tools when present. Fetched content is treated as untrusted data, and the frontmatter does not declare the shell, network or file access.