CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

indexability

Use when auditing a site for accidental noindex directives, investigating why important pages are not appearing in Google Search, or reviewing CMS settings that control indexing at the page or category level.

Quality

85%

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

78%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 lean, highly actionable audit-and-fix guide with a clean sequence, verification checkpoints, and a properly signaled one-level reference to references/rule.md. The main cost is token redundancy: the same three-block check is repeated across Quick Reference, Check, and Code Review, and the Explain section reiterates SEO basics Claude already knows.

Suggestions

Consolidate the triple-stated noindex/X-Robots-Tag/robots.txt check (Quick Reference, Check, and Code Review) into one authoritative checklist and have the other sections reference it instead of restating it.

Trim or remove the Explain section's general SEO principles ('A page that cannot be crawled or indexed cannot rank') — Claude already knows this; keep only the user-facing phrasing if it is meant for stakeholder communication.

Add an error-recovery branch to the Fix workflow, e.g. what to do if the page still shows 'URL is not on Google' after Request Indexing and the Coverage report monitoring window.

DimensionReasoningScore

Conciseness

The noindex/robots.txt/X-Robots-Tag check is restated three times (Quick Reference bullet 1, the Check section, and the Code Review section), and the Explain section covers general SEO knowledge Claude already has ('A page that cannot be crawled or indexed cannot rank'). The redundancy is more than minor, so it sits at 'mostly efficient but could be tightened' rather than 'efficient with minor trim'.

3 / 5

Actionability

Guidance is fully executable for an audit/instruction skill: exact search targets ('<meta name=robots content=...>', 'X-Robots-Tag HTTP response header', robots.txt Disallow patterns), exact tool paths ('URL Inspection → Request Indexing', 'Coverage report'), and framework-specific fixes (remove Next.js 'robots: { index: false }', check 'vercel.json' headers) covering the common cases.

5 / 5

Workflow Clarity

The Check section's (1)–(4) sequence and the Fix section's 1–5 steps are clearly ordered with verification checkpoints ('Test with Google's robots.txt tester', 'Monitor the Coverage report… to confirm the page moves to Indexed'), but there is no error-recovery loop for pages that remain unindexed after fixes.

4 / 5

Progressive Disclosure

A ~40-line overview with well-organized sections and one clearly signaled, one-level-deep reference ('For full implementation details, code examples, and framework-specific guidance, see references/rule.md') that exists in the bundle; bulk detail is appropriately split out.

5 / 5

Total

17

/

20

Passed

Description

87%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 well-formed description with explicit 'Use when…' trigger guidance naming three concrete audit/investigation activities in a clearly distinct niche. The only weaknesses are a missing remediation action and a few uncovered natural synonyms (robots.txt, X-Robots-Tag).

DimensionReasoningScore

Specificity

Lists three concrete actions — 'auditing a site for accidental noindex directives', 'investigating why important pages are not appearing in Google Search', and 'reviewing CMS settings that control indexing' — but omits remediation (the Fix workflow is a major part of the skill), a minor coverage gap that keeps it below the 'comprehensive coverage' anchor.

4 / 5

Completeness

'Use when auditing… investigating… or reviewing…' explicitly answers when to use the skill with concrete trigger phrases, and the gerund verb phrases explicitly state what the skill does (audits noindex directives, investigates missing pages, reviews CMS indexing settings).

5 / 5

Trigger Term Quality

'noindex', 'not appearing in Google Search', and 'CMS settings' are phrases users would naturally say, but common variations the skill itself covers — 'robots.txt', 'X-Robots-Tag', 'SEO', 'indexability' — are missing.

4 / 5

Distinctiveness Conflict Risk

'noindex directives', 'pages not appearing in Google Search', and 'CMS settings that control indexing' carve a clear technical-SEO indexability niche with distinct triggers and minimal risk of firing for the wrong skill.

5 / 5

Total

18

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository

thedaviddias/Front-End-Checklist

Path

skills/indexability/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.