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," or "SEO health check." For building pages at scale to target keywords, see programmatic-seo. For adding structured data, see schema-markup.
89
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
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 well-structured description with excellent trigger term coverage and clear differentiation from related skills. The main weakness is the lack of specific concrete actions - it describes the general purpose (audit/review/diagnose) but doesn't enumerate what specific SEO checks or analyses the skill performs.
Suggestions
Add specific concrete actions to improve specificity, e.g., 'Analyzes meta tags, checks page speed issues, reviews heading hierarchy, identifies broken links, evaluates mobile-friendliness'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (SEO) and general actions ('audit, review, or diagnose SEO issues') but doesn't list specific concrete actions like 'analyze meta tags, check page speed, identify broken links, review heading structure.' | 2 / 3 |
Completeness | Clearly answers both what ('audit, review, or diagnose SEO issues') and when ('Use when the user mentions...' with explicit trigger list). Also helpfully distinguishes from related skills (programmatic-seo, schema-markup). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms users would say: 'SEO audit,' 'technical SEO,' 'why am I not ranking,' 'SEO issues,' 'on-page SEO,' 'meta tags review,' 'SEO health check' - these are realistic phrases users would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Explicitly differentiates from related skills (programmatic-seo for building pages, schema-markup for structured data) and has distinct trigger terms focused specifically on SEO auditing/diagnosis rather than implementation. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a strong, comprehensive SEO audit skill with excellent actionability and workflow structure. The priority ordering and output format provide clear guidance for conducting audits. Minor verbosity in some sections (explaining E-E-A-T components, listing common issues that could be inferred) prevents a perfect conciseness score, but overall the skill is well-crafted and immediately usable.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is comprehensive but includes some redundancy and could be tightened. Lists like 'Common issues' repeat patterns, and some sections (e.g., E-E-A-T explanations) explain concepts Claude likely knows. However, it avoids excessive verbosity and stays focused on actionable checklists. | 2 / 3 |
Actionability | Highly actionable with specific checks, concrete metrics (LCP < 2.5s, CLS < 0.1), exact tools to use, and clear output format structure. Each audit area provides specific items to verify rather than vague guidance. | 3 / 3 |
Workflow Clarity | Clear priority order (Crawlability → Technical → On-Page → Content → Authority), structured audit framework, and explicit output format with prioritized action plan. The initial assessment questions establish scope before diving into the audit. | 3 / 3 |
Progressive Disclosure | Well-organized with clear sections, references to external files (ai-writing-detection.md, aeo-geo-patterns.md), and related skills linked at the end. Content is appropriately structured with headers for easy navigation without being monolithic. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- 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.