seo-technical

Technical SEO audit across 9 categories: crawlability, indexability, security, URL structure, mobile, Core Web Vitals, structured data, JavaScript rendering, and IndexNow protocol. Use when user says "technical SEO", "crawl issues", "robots.txt", "Core Web Vitals", "site speed", or "security headers".

Quality

75%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Critical

Do not install without reviewing

Fix and improve this skill with Tessl

tessl review fix ./skills/seo-technical/SKILL.md

Quality

Content

50%

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

The content is well-organized and reasonably actionable with concrete thresholds and commands, but it is verbose with inline time-sensitive detail and references .py scripts that are absent from the bundle, weakening both actionability and progressive disclosure.

Suggestions

Move time-sensitive/version-specific detail (e.g. the AI-crawler tables, JS SEO December 2025 guidance, Googlebot fetch limits) into dedicated reference files and keep the SKILL.md body as a lean overview with pointers.

Provide the referenced .py scripts (sitemap_discovery.py, agent_ux_check.py, render_page.py, pagespeed_check.py, crux_history.py, gsc_inspect.py) in a scripts/ bundle, or mark them as external/optional tooling so commands are verifiably executable.

Add an explicit sequential audit workflow with validation checkpoints (e.g. run scanner -> inspect output -> categorize findings -> re-verify after fixes) to give the multi-category process a clear feedback loop.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient but is long and embeds time-sensitive detail inline (specific 2025/2026 dates, version numbers like "Lighthouse 13.3.0", byte limits), which could be tightened; it stops short of the 'lean, every token earns its place' anchor.	2 / 3
Actionability	It gives concrete commands and thresholds (e.g. "claude-seo run sitemap_discovery.py <url> --json", LCP <=2.5s), but those referenced .py scripts are not present in the bundle (no scripts/ directory), so the guidance is not copy-paste executable as written.	2 / 3
Workflow Clarity	Checklists, an error-handling table, and an output template provide sequence and structure, but there is no explicit per-category validate→fix→retry feedback loop or explicit checkpoint ordering for the audit as a whole.	2 / 3
Progressive Disclosure	One real, clearly signaled one-level reference exists (references/agent-friendly-pages.md), but the body keeps a large amount of inline detail (AI crawler tables, JS SEO guidance) that is not split into reference files, and several referenced scripts have no corresponding bundle files.	2 / 3
	Total	8 / 12 Passed

Description

100%

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

The description is specific, complete, and distinct: it lists concrete audit categories, gives explicit 'Use when...' triggers with natural terms, and occupies a clear niche. No vague fluff or missing trigger guidance.

Dimension	Reasoning	Score
Specificity	The description enumerates 9 concrete audit categories ("crawlability, indexability, security, URL structure, mobile, Core Web Vitals, structured data, JavaScript rendering, and IndexNow protocol"), matching the 'lists multiple specific concrete actions' anchor rather than the partial 'names domain and some actions' level.	3 / 3
Completeness	It answers both 'what' (a 9-category audit) and 'when' with an explicit "Use when user says ..." clause, satisfying the highest anchor; it is not the level-2 case where 'when' is only implied.	3 / 3
Trigger Term Quality	It provides natural trigger phrases users would say — "technical SEO", "crawl issues", "robots.txt", "Core Web Vitals", "site speed", "security headers" — giving good coverage rather than only some relevant keywords.	3 / 3
Distinctiveness Conflict Risk	The technical-SEO niche with named category triggers and explicit trigger phrases is clearly distinguishable and unlikely to fire for unrelated skills, fitting the 'clear niche with distinct triggers' anchor.	3 / 3
	Total	12 / 12 Passed

Validation

93%

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

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: AgriciDaniel/claude-seo
Path: skills/seo-technical/SKILL.md
Commit: 09d37c7

Reviewed: 4 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.