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.

Quality

66%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/seo-audit/SKILL.md

Quality

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 completeness. Its main weakness is that the 'what it does' portion is somewhat high-level — it says 'audit, review, or diagnose' but doesn't enumerate the specific concrete actions or outputs the skill produces. The cross-references to related skills are a notable strength for disambiguation.

Suggestions

Add specific concrete actions the skill performs, e.g., 'Checks meta tags, analyzes page speed, identifies crawl errors, reviews heading hierarchy, audits internal linking structure, and evaluates mobile-friendliness.'

Dimension	Reasoning	Score
Specificity	The description names the domain (SEO) and some actions like 'audit, review, or diagnose SEO issues,' but doesn't list specific concrete actions the skill performs (e.g., check meta tags, analyze page speed scores, identify broken links, review heading structure). The actions remain at a high level.	2 / 3
Completeness	Clearly answers both 'what' (audit, review, diagnose SEO issues) and 'when' with an extensive explicit trigger list including a 'Use when' equivalent and even guidance for vague requests. Also includes cross-references to related skills for disambiguation.	3 / 3
Trigger Term Quality	Excellent coverage of natural trigger terms users would actually say, including both technical terms ('core web vitals,' 'crawl errors,' 'indexing issues,' 'meta tags review') and casual/natural language ('why am I not ranking,' 'my traffic dropped,' 'my SEO is bad,' 'not showing up in Google'). This is comprehensive and well-thought-out.	3 / 3
Distinctiveness Conflict Risk	Explicitly distinguishes itself from related skills (programmatic-seo, schema-markup, ai-seo) with clear cross-references, and the trigger terms are specific to SEO auditing rather than general web development. This makes it highly unlikely to conflict with other skills.	3 / 3
	Total	11 / 12 Passed

Implementation

42%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The skill is well-organized with good progressive disclosure and cross-references to related skills, and contains some genuinely valuable non-obvious guidance (schema markup detection limitations, international SEO nuances). However, it is significantly too verbose — the majority of content restates standard SEO knowledge that Claude already knows (title tag best practices, meta description lengths, E-E-A-T definitions, basic HTTPS checks). The lack of executable code examples or concrete commands reduces actionability.

Suggestions

Cut the on-page SEO, content quality, and E-E-A-T sections down to brief reminders of non-obvious points only — Claude already knows what title tags and meta descriptions are, what good heading structure looks like, etc.

Add executable code/command examples where possible — e.g., a curl command to check robots.txt, a Python snippet to validate sitemap XML, or a browser console script to audit heading hierarchy.

Add explicit validation checkpoints to the workflow — e.g., 'After fixing crawlability issues, re-run site:domain.com to verify indexation improved before moving to on-page audit.'

Move the 'Common Issues by Site Type' section to a reference file — it's useful but adds significant length to the main skill for content Claude can largely infer.

Dimension	Reasoning	Score
Conciseness	This is extremely verbose at ~400+ lines. Much of the content is checklist-style knowledge Claude already possesses (what title tags should look like, what meta descriptions are, E-E-A-T definitions, basic HTTPS checks). The international SEO section is detailed and valuable, but the on-page SEO, content quality, and common issues sections largely restate SEO fundamentals that don't need to be spelled out.	1 / 3
Actionability	The skill provides structured checklists and specific thresholds (LCP < 2.5s, INP < 200ms, etc.) which are useful, and the schema markup detection limitation is a genuinely actionable insight. However, there are no executable code examples, no concrete commands to run, and most guidance is descriptive checklist items rather than copy-paste-ready instructions.	2 / 3
Workflow Clarity	The audit framework establishes a clear priority order (crawlability → technical → on-page → content → authority) and the output format section provides good structure. However, there are no explicit validation checkpoints or feedback loops — for instance, no step saying 'verify fixes resolved the issue before moving on' or iterative checking processes.	2 / 3
Progressive Disclosure	The skill effectively references external files (references/international-seo.md, references/ai-writing-detection.md) and related skills (ai-seo, programmatic-seo, schema-markup, etc.) with clear one-level-deep navigation. Content is organized into logical sections with a clear hierarchy.	3 / 3
	Total	8 / 12 Passed

Validation

100%

Warnings & errors only

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: 1bcff9f

Reviewed: 6 days ago

Table of Contents

Discovery Implementation Validation

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.