E-commerce SEO Analyzer
Audits product pages, shopping visibility, marketplace competition, and product schema.
The skill shows security awareness through mandatory DataForSEO cost checks, user approval for Amazon calls, credential-missing fallback, and explicit endpoint probing; however, confirmation for arbitrary URL fetching and probing, data-flow disclosure, third-party retention, and comprehensive rollback are incomplete, so 9 points are deducted.
Workflows, cost checks, polling, error cases, and credential-free fallback are documented; however, the referenced scripts, API implementation, and skill-specific tests are not reproducible from the supplied material. Static calibration therefore limits the score to below 10.
Trigger phrases, URL-or-keyword inputs, standalone mode, and DataForSEO-enhanced mode are reasonably clear; however, the default market is US English, Chinese-language behavior and mainland-China reachability are unspecified, and several functions depend on external services, so 7 points are deducted.
The skill provides a name, purpose, argument hint, MIT license, version, command table, references, output template, and error handling; maintenance ownership, update path, changelog, dependency-install details, and some cross-skill references remain incomplete, so 6 points are deducted.
Product-page analysis, schema validation, and report templates can support the core task directly; however, live competition, keyword-gap, and UCP results depend on unavailable implementations and external data, with correctness and comparative value not statically verified, so 9 points are deducted.
The repository materials include CI, tests, pinned dependencies, and security documentation, but these mainly cover shared repository functionality rather than this skill's key paths. The UCP material also depends on a moving specification, so only limited evidence credit is justified.
- DataForSEO, Google Shopping, Amazon, and possible UCP probes issue external requests and may incur costs; confirm cost, locale, and data-processing boundaries before each call.
- The defaults use a US location and English, which may not fit mainland-China users or other markets; set localization explicitly and confirm service reachability.
- The UCP reference states that the specification is changing and does not provide a stable canonical URL; do not treat its capabilities, adoption, or version claims as verified facts.
- The skill references multiple scripts and cross-skill components, but the supplied material does not prove interface compatibility for this path; check installed versions and failure output before use.
What does this skill do, and when should you use it?
This is the e-commerce skill inside AgriciDaniel/claude-seo, focused on product-page optimization, Google Shopping, Amazon marketplace intelligence, Product schema, and marketplace keyword gaps. It works standalone for on-page and schema analysis, with optional DataForSEO Merchant API enrichment for live Google Shopping and Amazon data. The skill produces scoring, pricing, seller, listing-quality, cross-marketplace, and schema outputs. It is a good fit for teams auditing commerce pages and feeds, but live marketplace analysis requires credentials, network access, and cost approval.
Fetches and parses product-page HTML; checks titles, meta descriptions, headings, images, internal links, product content, and technical signals; runs repository Python scripts for rendering, parsing, DataForSEO cost checks, and logging; optionally calls the DataForSEO Merchant API for Google Shopping and Amazon pricing, seller, rating, review, shipping, availability, and listing-pattern analysis; compares organic rankings with Shopping visibility to identify keyword gaps; validates or generates Product JSON-LD covering pricing, availability, brand, identifiers, ratings, shipping, and return-policy fields; and audits UCP profiles for presence, declared capabilities, structural issues, and optional endpoint reachability.
- An e-commerce SEO lead needs a structured audit of a product page's metadata, images, content, links, and Product schema.
- An agency needs to compare prices, ratings, sellers, reviews, and shipping across Google Shopping and Amazon for a target keyword.
- A brand wants to find keywords that rank organically but have no Shopping visibility.
- An SEO or development team needs to validate Product structured data against Google Merchant requirements.
- A merchant wants to inspect whether a UCP profile exists and identify declared commerce capabilities.
What are this skill's strengths and limitations?
- Runs product-page and Product schema analysis without requiring DataForSEO.
- Covers Google Shopping, Amazon, pricing, sellers, keyword gaps, and listing quality.
- Defines concrete schema requirements, validation rules, scoring, and report structures.
- Includes mandatory cost-check and logging procedures for DataForSEO Merchant calls.
- Live Google Shopping, Amazon, and keyword-gap analysis requires a DataForSEO account, credentials, network access, and user approval for applicable costs.
- Page analysis depends on repository Python scripts and local filesystem access.
- The supplied source does not show a dedicated test suite or compatibility evidence for this sub-skill's individual scripts.
- Timeouts, empty Shopping results, invalid URLs, and non-product pages can reduce or change the analysis output.
How do you install this skill?
This skill is bundled in the AgriciDaniel/claude-seo repository at skills/seo-ecommerce/SKILL.md rather than published as a separate package. Install the public collection with /plugin marketplace add AgriciDaniel/claude-seo followed by /plugin install claude-seo@agricidaniel-claude-seo; alternatively, run git clone --depth 1 https://github.com/AgriciDaniel/claude-seo.git and then bash claude-seo/install.sh. The source does not document a standalone installation method for this sub-skill in other clients.
How do you use this skill?
In Claude Code, use /seo ecommerce <url> for a full e-commerce SEO analysis; /seo ecommerce schema <url> for Product schema validation; /seo ecommerce products <keyword> for Google Shopping competition; and /seo ecommerce gaps <domain> for organic-versus-Shopping keyword gaps. The products and gaps workflows require DataForSEO. Before every Merchant API call, run the required cost check; if it returns needs_approval, show the cost and request approval first.