CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

seo-audit

When the user wants to audit or diagnose SEO, or asks why traffic dropped, a page won't rank, or whether a setup like canonicals, hreflang, or redirects is right: technical SEO, indexing, Google updates, on-page and titles, Core Web Vitals, local SEO. Start here when someone just says their SEO is bad. For pages at scale, see programmatic-seo. For structured data, see schema. For AI search, see ai-seo.

Quality

80%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/seo-audit/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

67%Weight 40%Scale 1-5

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

A well-structured audit skill with a clear priority-ordered workflow, concrete thresholds and tool guidance, and a genuinely useful reference bundle that keeps evidence and deep detail out of the main file. The main cost is token weight: substantial sections (E-E-A-T, generic on-page and image checklists) restate what Claude already knows and could be trimmed or offloaded to references.

Suggestions

Trim or move the generic on-page/content checklists (E-E-A-T four-pillar breakdown, heading structure, image optimization, internal linking basics) into a reference file, keeping only non-obvious items and error patterns inline.

Compress the inline International SEO section to the error checklist and defer detailed rules (code formats, sitemap limits, Next.js caveat) to international-seo.md, which already exists for that depth.

Add an explicit verification step to the audit workflow — e.g., cross-check each suspected finding with a second method (browser render or Rich Results Test) before reporting it, extending the existing schema-detection guardrail to other findings.

DimensionReasoningScore

Conciseness

Mostly terse checklist format with genuinely non-obvious specifics ("never `en-UK`", 50MB sitemap limit, Next.js `alternates` caveat, `web_fetch` stripping `<script>` tags), but sizable sections restate basics Claude already knows — the E-E-A-T four-pillar breakdown, "One H1 per page", alt-text and meta-description length checklists, and internal-linking basics. Fits "mostly efficient but includes some unnecessary explanation or could be tightened"; not a 2 because there is no padded prose or tutorial-style explanation, and not a 4 because the generic on-page/content checklists occupy a substantial portion that could be trimmed or moved to references.

3 / 5

Actionability

Concrete thresholds (LCP < 2.5s, INP < 200ms, CLS < 0.1), an executable browser command (`document.querySelectorAll('script[type="application/ld+json"]')`), named tools with URL, and a per-issue report format requiring Evidence. Minor gaps: several checklist items say what to check but not how ("Logical hierarchy", "Comprehensive coverage of topic", "Answers search intent"), keeping it below the fully-executable top anchor.

4 / 5

Workflow Clarity

Clear sequence: initial-assessment questions → priority-ordered audit framework (crawlability → technical → on-page → content → authority) → structured report with an Evidence field per finding → prioritized action plan. Checkpoints like the schema-detection limitation warning prevent false findings. Not a 5 because there is no explicit verify/re-check loop for suspected issues (e.g., confirming a finding with a second method), and evidence-checking is embedded in the output format rather than an explicit workflow step.

4 / 5

Progressive Disclosure

Seven reference files exist, are all linked with descriptive signals both inline and in a dedicated References section, and follow a sound split (checklists inline, evidence/sources in references, one level deep). Minor gaps: local-seo.md nests two companion files (two levels deep), and the ~70-line inline International SEO section carries depth that could live in international-seo.md, so structure is good but short of the clean one-level ideal.

4 / 5

Total

15

/

20

Passed

Description

82%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description: it answers both what and when with concrete trigger phrases, covers natural user language for common SEO complaints, and explicitly delegates to sibling skills to avoid triggering the wrong one. The only weakness is that capability verbs are sparse (audit/diagnose) with the bulk of specificity carried by topic-area enumeration.

DimensionReasoningScore

Specificity

Explicit actions are limited to "audit or diagnose SEO", but the description itemizes specific, concrete coverage areas ("canonicals, hreflang, or redirects", "technical SEO, indexing, Google updates, on-page and titles, Core Web Vitals, local SEO") with only minor gaps. Not a 3 because coverage is comprehensive rather than sparse, and not a 5 because it lists topics more than distinct executable actions.

4 / 5

Completeness

Explicitly answers both: what (auditing/diagnosing SEO across technical, indexing, on-page, Core Web Vitals, and local) and when ("When the user wants to audit or diagnose SEO, or asks why traffic dropped, a page won't rank..." and "Start here when someone just says their SEO is bad"). Trigger phrases are concrete and specific, matching the top anchor.

5 / 5

Trigger Term Quality

Includes natural phrases users would actually say — "why traffic dropped", "a page won't rank", "their SEO is bad" — plus specific technical triggers like "canonicals, hreflang, or redirects". Not a 5 because common variations such as "rank higher", "SERP", or "not showing up in Google" are missing.

4 / 5

Distinctiveness Conflict Risk

Clear niche (technical SEO audit/diagnosis) with explicit routing to adjacent skills ("For pages at scale, see programmatic-seo. For structured data, see schema. For AI search, see ai-seo"), which minimizes overlap with closely related skills. This explicit delegation goes beyond the minor-overlap level 4 anchor.

5 / 5

Total

18

/

20

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

coreyhaines31/marketingskills

Path

skills/seo-audit/SKILL.md

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.