seo-monitoring

When the user wants to build an SEO data analysis system, monitor indexing/traffic/keywords/backlinks, or set up benchmarks. Also use when the user mentions "SEO data analysis," "SEO monitoring," "article database," "traffic benchmark," "penalty recovery," "SEO work document," "SEO dashboard," "keyword tracking," "ranking monitoring," "indexing report," or "backlink monitoring." For GSC API, use google-search-console.

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

75%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-organized, reference-style SEO monitoring framework that stays lean via tables and gives concrete metrics, sources, and navigation paths. Its main weaknesses are organizational redundancy between the two metric-table sections and missing concrete setup/query steps for the attribution and GSC API features it references.

Suggestions

Consolidate the overlapping "Four Core Metrics" tables with the "Monitoring Metrics Table" into a single authoritative metrics section to remove redundancy and tighten token use.

Add concrete, executable steps for the "Attribution config" (User ID) and "GSC API" items you reference — e.g. a sample GSC API query and the GA4 User-ID config steps — so the actionable guidance is complete rather than mentioned.

Make the workflow checkpoints explicit: add a "verify recovery / re-check baseline" step to the Penalty Recovery and Natural Traffic Benchmark sequences so the validate-then-proceed loop is stated, not implied.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean reference tables that assume Claude knows what GA4/GSC/SEO tools are, with no concept over-explanation; however the "Four Core Metrics" tables and the "Monitoring Metrics Table" cover traffic/keywords/backlinks twice, and the Monthly Record Template repeats those rows, so minor trimming is possible.	4 / 5
Actionability	Provides concrete, actionable reference data (specific metrics, data sources, the GA4 navigation path "Reports > Acquisition > Traffic acquisition", numbered benchmark steps, table templates), but the "Attribution config" (User ID to GA4) and GSC API mentions lack concrete setup/query steps, leaving minor gaps.	4 / 5
Workflow Clarity	Multi-step processes are clearly sequenced (the 3-step Natural Traffic Benchmark and the step-ordered Penalty Recovery table with its 3-month wait guidance), but validation/checkpoint feedback loops are only implicit ("Compare periodically," "outcome is uncertain; do what you can, then wait"), not explicit validate-then-proceed gates.	4 / 5
Progressive Disclosure	No bundle files exist and the skill is a self-contained single-file overview organized with clear section headers and a Related Skills map; structure is good, but the redundant metric tables could be consolidated, and the doc has no one-level-deep references to signal, keeping it just short of a 5.	4 / 5
	Total	16 / 20 Passed

Description

91%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, third-person description that clearly states what the skill does and when to invoke it, with a rich set of natural trigger terms. Its only weakness is minor overlap with closely related dedicated skills (backlink-analysis, indexing).

Dimension	Reasoning	Score
Specificity	Lists several concrete actions ("build an SEO data analysis system, monitor indexing/traffic/keywords/backlinks, or set up benchmarks") covering the four core metrics, but article database and penalty recovery appear only as triggers, leaving minor coverage gaps short of a comprehensive 5.	4 / 5
Completeness	Explicitly answers both what (build/monitor benchmarks and the four core metrics) and when ("When the user wants..." plus "Also use when the user mentions...") with concrete trigger phrases, matching the explicit what-and-when anchor.	5 / 5
Trigger Term Quality	A comprehensive list of natural phrases users would say ("SEO monitoring," "keyword tracking," "SEO dashboard," "indexing report," "backlink monitoring," "penalty recovery") with good synonym variation, matching the comprehensive-coverage anchor.	5 / 5
Distinctiveness Conflict Risk	It carves a clear holistic-monitoring niche and redirects GSC API to google-search-console, but triggers like "backlink monitoring" and "indexing report" overlap with the dedicated backlink-analysis and indexing skills listed under Related Skills, giving minor conflict risk short of a 5.	4 / 5
	Total	18 / 20 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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: kostja94/marketing-skills
Path: skills/analytics/seo/seo-monitoring/SKILL.md
Commit: 26cef34

Reviewed: 23 hours 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.