CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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. For AI search optimization, see ai-seo.

Quality

83%

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

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, actionable audit framework with real progressive disclosure to verified one-level-deep references and smart guards against false findings. Its main cost is token weight: significant portions of the on-page and content-quality checklists restate standard SEO knowledge Claude already has and could be compressed or moved to references.

Suggestions

Compress the On-Page SEO and Content Quality sections to the non-obvious checks only — title tag length, meta description length, one-H1, E-E-A-T definitions, and image alt-text basics are knowledge Claude already has; keep only project-specific thresholds and common-issues patterns.

Move the detailed International SEO checklists (hreflang error catalog, sitemap limits, Next.js caveat) into references/international-seo.md, keeping a short summary plus the reference pointer in the body to cut roughly 50 lines from SKILL.md.

For the highest-frequency checks (robots.txt, sitemap, canonical, site: operator), add the exact fetch command or Search Console report path alongside the check name so every item is copy-paste executable.

DimensionReasoningScore

Conciseness

The checklist format is mostly efficient and the international-SEO section packs non-obvious specifics, but long stretches re-state SEO knowledge Claude already has ("One H1 per page," title tags "50-60 characters," meta descriptions "150-160 characters," E-E-A-T definitions, basic image and internal-linking best practices) — matching anchor 3's 'could be tightened' rather than anchor 4's 'minor instances'.

3 / 5

Actionability

Mostly concrete, executable guidance: an exact browser command (document.querySelectorAll('script[type="application/ld+json"]')), a Rich Results Test URL, specific Core Web Vitals thresholds (LCP < 2.5s, INP < 200ms, CLS < 0.1), named tools per check, and a fully specified report schema (Issue/Impact/Evidence/Fix/Priority). Minor gaps: many checks say what to verify but not the exact command to run.

4 / 5

Workflow Clarity

A clear sequence is present — scoping questions in Initial Assessment, an explicit five-step Priority Order, themed audit sections, then a structured Output Format — and validation is embedded via the mandatory "Evidence: How you found it" field per finding plus the schema-detection false-positive guard. It falls short of anchor 5 only in lacking explicit validate-and-retry loops, which a read-only audit rarely needs.

4 / 5

Progressive Disclosure

Both bundle files (references/international-seo.md, references/ai-writing-detection.md) exist, are linked inline with clear signaling, cataloged in a References section, and are one level deep (only external URLs inside, no nested references). Anchor 4 rather than 5 because the ~490-line body inlines substantial detail — e.g., the ~70-line international section — that a stricter split would move to the reference files.

4 / 5

Total

15

/

20

Passed

Description

90%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.

An exemplary trigger-rich description with explicit what/when guidance and thoughtful boundary routing to sibling skills. The only weakness is that the 'what' states one generic capability (audit/review/diagnose) rather than enumerating the skill's concrete capabilities.

DimensionReasoningScore

Specificity

The description names the domain and audit actions ("audit, review, or diagnose SEO issues on their site"), but the three verbs are near-synonyms for a single capability and no distinct sub-capabilities are enumerated — matching anchor 3 rather than anchor 4's 'several specific actions'.

3 / 5

Completeness

Both questions are explicitly answered: the what ("audit, review, or diagnose SEO issues") and an exceptionally explicit when ("When the user wants to...", "Also use when the user mentions [16 phrases]", "Use this even if the user just says something vague") with concrete trigger phrases, exceeding anchor 4's thinner 'when'.

5 / 5

Trigger Term Quality

Comprehensive natural trigger coverage including synonyms and real user phrasings: "SEO audit," "why am I not ranking," "my traffic dropped," "Google update hit me," "crawl errors," "indexing issues," and even vague cases like "my SEO is bad" — a clear match for anchor 5.

5 / 5

Distinctiveness Conflict Risk

Clear SEO-audit niche with distinct triggers and explicit de-confliction pointers to adjacent skills ("For building pages at scale... see programmatic-seo", "For adding structured data, see schema", "For AI search optimization, see ai-seo"), giving minimal conflict risk per anchor 5.

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

joshmanders/dotfiles

Path

claude/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.