seo-google

Google SEO APIs: Search Console (Search Analytics, URL Inspection, Sitemaps), PageSpeed Insights v5, CrUX field data with 25-week history, Indexing API v3, and GA4 organic traffic. Provides real Google field data for Core Web Vitals, indexation status, search performance, and organic traffic trends. Use when user says "search console", "GSC", "PageSpeed", "CrUX", "field data", "indexing API", "GA4 organic", "URL inspection", or "real CWV data".

Quality

86%

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

72%

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

The body is highly actionable and well-structured with real one-level-deep reference files, but its inline time-sensitive 2026 update blocks and the absence of explicit validation checkpoints around the batch indexing/inspection operations hold it back on conciseness and workflow clarity.

Suggestions

Move the dated 2026 updates (Generative AI GSC report, GA4 AI Assistants channel, data-reliability caveat) into a dedicated 'Current Google changes / freshness' reference file or a clearly marked section, keeping the inline body free of decaying dates.

Add explicit validation steps for batch operations — e.g. before index-batch, check remaining daily quota; after inspect-batch, summarize verdict counts and flag any FAIL/ERROR rows before proceeding.

Tighten the cross-skill integration and technical-notes prose into compact bullet-only form to recover token budget without losing the operational specifics.

Dimension	Reasoning	Score
Conciseness	The body is dense and operational (per-command Script/Reference/Default blocks, no conceptual filler Claude already knows), but it carries substantial time-sensitive detail inline — e.g. the "AI surfaces in GSC (2026)" block and the GA4 "AI Assistants" channel note with specific dates (2026-06-03, 2026-05-13) — which the rubric says should penalize conciseness when not placed in a deprecated/old-patterns section.	2 / 3
Actionability	Every command maps to a concrete, flag-level invocation such as `claude-seo run pagespeed_check.py <url> --json` and `claude-seo run gsc_inspect.py --batch <file> --json`, with a Quick Reference table, default parameters, and copy-paste-ready scripts throughout.	3 / 3
Workflow Clarity	Sequencing and checkpoints exist (credential pre-check before any command, tier detection "Always communicate the detected tier", report workflow steps, error-handling table with exponential-backoff retry), but the batch operations (inspect-batch, index-batch up to 200 URLs) lack explicit pre/post validation steps, which the rubric says caps workflow clarity at 2.	2 / 3
Progressive Disclosure	SKILL.md is a well-organized command overview with one-level-deep, clearly signaled references — each section states "Reference: `references/<file>.md`" and the Output Format section names `assets/templates/*.md`; all referenced files exist as real bundle files, with no nested two-level reference chains.	3 / 3
	Total	10 / 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.

A strong, third-person description that concisely states concrete capabilities and pairs them with an explicit, natural-language trigger list. It answers both what the skill does and when to use it without fluff or over-claims.

Dimension	Reasoning	Score
Specificity	Names multiple concrete capabilities across distinct APIs — "Search Console (Search Analytics, URL Inspection, Sitemaps)", "PageSpeed Insights v5", "CrUX field data with 25-week history", "Indexing API v3", and "GA4 organic traffic" — matching the rubric's multiple-specific-actions anchor.	3 / 3
Completeness	It clearly answers both what ("Google SEO APIs: ... Provides real Google field data for Core Web Vitals, indexation status, search performance, and organic traffic trends") and when ("Use when user says ..."), with an explicit trigger clause, so it is not capped at 2.	3 / 3
Trigger Term Quality	The explicit trigger list ("search console", "GSC", "PageSpeed", "CrUX", "field data", "indexing API", "GA4 organic", "URL inspection", "real CWV data") covers natural phrasings a user would actually say, including the common acronym "GSC".	3 / 3
Distinctiveness Conflict Risk	The niche is clearly scoped to Google's own field-data APIs and explicitly distinguished from "crawl-based analysis (existing claude-seo skills)", with distinct Google-specific triggers unlikely to fire for the wrong skill.	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-google/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.