seo-ecommerce

E-commerce SEO analysis: Google Shopping visibility, Amazon marketplace intelligence, product schema validation, competitor pricing analysis, and marketplace keyword gaps. Combines on-page product SEO with marketplace data from DataForSEO Merchant API. Use when user says "ecommerce SEO", "product SEO", "Google Shopping", "marketplace SEO", "product schema", "Amazon SEO", "product listings", "shopping ads", or "merchant SEO".

Quality

92%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

85%

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

The skill body is highly actionable with concrete commands, a cost-guardrail validation checkpoint, and well-structured one-level references that resolve to real files. Its weakness is conciseness: the UCP section's narrative prose and several inline time-sensitive dates add tokens that don't earn their place.

Suggestions

Tighten the UCP section: replace the partner/I/O-narrative prose with a compact bullet list (what UCP is, the two integration paths, the audit command, the date-based-version note) and move the 2026-04-08 release detail into the UCP reference file.

Consolidate the inline time-sensitive dates (hasAdultConsideration 2026-05-20, Content API sunset 2026-08-18) into a short 'Deprecated / sunset dates' subsection so the main sections stay lean, per the conciseness guideline.

Trim the Cross-Skill Integration and Error Handling tables to the rows that change behavior; some entries restate capabilities Claude can infer from the command names.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient and dense with actionable material, but the UCP narrative paragraph is padded with background (partner lists, Google I/O 2026 coverage) and several time-sensitive dates (2026-05-20, 2026-04-08, 2026-08-18) sit inline in regular sections rather than a deprecated/old-patterns section, which the rubric penalizes. It is not score 1 because it does not explain basic concepts Claude already knows, but it cannot reach 3 given the verbosity and scattered date commentary.	2 / 3
Actionability	It provides concrete, copy-paste-ready commands ('claude-seo run dataforseo_merchant.py search "<keyword>" --marketplace google'), a complete JSON-LD schema example, explicit validation rules, and a full output template — matching the fully-executable anchor rather than the pseudocode/incomplete anchor.	3 / 3
Workflow Clarity	Workflows are sequenced with numbered steps and include explicit validation checkpoints — the mandatory DataForSEO cost guardrail (check before every call: approved/needs_approval/blocked; log after) — plus an error-handling table for recovery feedback loops. This matches the clear-sequence-with-validation anchor, and the destructive/batch cap does not apply because validation is present.	3 / 3
Progressive Disclosure	The body is an overview that defers detail to two one-level-deep references — 'Load references/marketplace-endpoints.md for full API parameter details' and 'See references/ucp-universal-commerce-protocol.md for audit criteria' — and both referenced files actually exist in references/, matching the well-signaled one-level-deep anchor rather than the inline-bloat or nested-reference anchors.	3 / 3
	Total	11 / 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 description: it states concrete capabilities, gives a wide set of natural trigger terms, and explicitly covers both what and when. The only minor conflict surface is 'product schema', which could glance off a general schema skill, but the surrounding e-commerce framing keeps it distinct.

Dimension	Reasoning	Score
Specificity	The description lists multiple concrete actions — 'Google Shopping visibility, Amazon marketplace intelligence, product schema validation, competitor pricing analysis, and marketplace keyword gaps' — matching the anchor for multiple specific concrete actions, not the level-below anchor that names only a domain and some actions.	3 / 3
Completeness	It explicitly states what the skill does (the capability sentence) and when to use it via an explicit 'Use when user says ...' clause, satisfying both halves of the top anchor; the level-2 anchor is ruled out because the 'when' is explicit, not merely implied.	3 / 3
Trigger Term Quality	It provides a broad set of natural trigger phrases users would say ('ecommerce SEO', 'product SEO', 'Google Shopping', 'marketplace SEO', 'product schema', 'Amazon SEO', 'product listings', 'shopping ads', 'merchant SEO'), matching the good-coverage anchor rather than the partial-coverage anchor below.	3 / 3
Distinctiveness Conflict Risk	The e-commerce/marketplace product-SEO niche with DataForSEO Merchant API and shopping-specific triggers is distinct and unlikely to fire for unrelated skills; it is not the level-2 case that could broadly overlap with similar generic skills.	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-ecommerce/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.