seo-audit
When the user wants to audit, review, or diagnose SEO issues on their site. Also use when the user mentions "SEO audit," "technical SEO," "why am I not ranking," "SEO issues," "on-page SEO," "meta tags review," "SEO health check," "my traffic dropped," "lost rankings," "not showing up in Google," "site isn't ranking," "Google update hit me," "page speed," "core web vitals," "crawl errors," or "indexing issues." Use this even if the user just says something vague like "my SEO is bad" or "help with SEO" — start with an audit. For building pages at scale to target keywords, see programmatic-seo. For adding structured data, see schema-markup. For AI search optimization, see ai-seo.
86
80%
Does it follow best practices?
Impact
96%
1.12xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/seo-audit/SKILL.mdQuality
Discovery
89%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a strong skill description with excellent trigger term coverage and clear differentiation from related skills. The main weakness is that it focuses heavily on when to use the skill but provides limited detail on the specific actions or capabilities the skill offers. Adding concrete actions like 'analyzes meta tags, checks crawl errors, evaluates page speed' would strengthen it.
Suggestions
Add specific concrete actions at the beginning (e.g., 'Analyzes meta tags, checks crawl errors, evaluates page speed, reviews on-page SEO factors, and identifies indexing issues')
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (SEO audit/diagnosis) and mentions some actions like 'audit, review, or diagnose SEO issues,' but doesn't list specific concrete actions like 'analyze meta tags, check crawl errors, evaluate page speed metrics.' The description focuses more on when to use it than what it actually does. | 2 / 3 |
Completeness | Clearly answers both what (audit, review, diagnose SEO issues) and when (extensive list of trigger phrases plus explicit guidance to 'start with an audit' for vague requests). The 'Use when' guidance is explicit and comprehensive. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural user phrases including 'why am I not ranking,' 'my traffic dropped,' 'lost rankings,' 'not showing up in Google,' 'site isn't ranking,' 'Google update hit me,' plus technical terms like 'core web vitals,' 'crawl errors,' 'indexing issues.' Also handles vague requests like 'my SEO is bad.' | 3 / 3 |
Distinctiveness Conflict Risk | Explicitly distinguishes itself from related skills by referencing 'programmatic-seo' for building pages at scale, 'schema-markup' for structured data, and 'ai-seo' for AI search optimization. Clear niche as the diagnostic/audit skill versus other SEO-related skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
70%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured SEO audit skill with excellent workflow clarity and progressive disclosure. The priority framework and output format provide clear guidance. However, it leans toward descriptive checklists rather than executable commands, and has some redundancy that could be tightened.
Suggestions
Add executable examples for common checks (e.g., curl commands for robots.txt, specific Search Console API queries, or browser console snippets for quick audits)
Consolidate the schema detection limitation into a single location rather than repeating it in both the Audit Framework and Tools sections
Convert some 'Check for' lists into actionable commands or specific tool workflows (e.g., 'Run site:domain.com | expected: X pages' rather than just 'site:domain.com check')
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is comprehensive but includes some redundancy (e.g., schema detection limitation explained twice, once in detail and again in Tools section). Some sections like 'Common Issues by Site Type' could be more condensed, though most content earns its place. | 2 / 3 |
Actionability | Provides good checklists and criteria but lacks executable code examples. The audit framework is thorough but mostly descriptive ('Check for X') rather than providing specific commands or copy-paste ready solutions for detection. | 2 / 3 |
Workflow Clarity | Clear priority order (Crawlability → Technical → On-Page → Content → Authority), well-structured output format with explicit report structure, and logical progression from initial assessment through findings to prioritized action plan. | 3 / 3 |
Progressive Disclosure | Well-organized with clear sections, appropriate references to related skills (ai-seo, programmatic-seo, schema-markup), and one external reference file. Content is appropriately structured for an overview skill with clear navigation to related topics. | 3 / 3 |
Total | 10 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- coreyhaines31/marketingskills
- Commit
9d4d29a
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.