HOME SKILLS BLOG GITHUB
// SKILL REFERENCE

E-COMMERCE SEO
PAGE EVIDENCE + MARKETPLACE RESEARCH

Audit product-page evidence, validate Product structured data, research Google Shopping listings, and compare organic visibility with Shopping presence using the reviewed Claude SEO command surface.

By Daniel Agrici · Page updated: · Command surface verified:

CONTRIBUTED BY MATEJ MARJANOVIC · PRO HUB CHALLENGE · original repo
$
/seo ecommerce https://your-store.com

REQUIRES CLAUDE SEO INSTALLED IN CLAUDE CODE

Product page data passing through validation checks into shopping and marketplace listings
// RUN PREVIEW

What will happen if you start this skill?

Readiness depends on the command path. Page and schema reviews can use local evidence, while products and gaps require DataForSEO credentials, a location-aware request, and a cost check.

OUTCOME

Product-page or schema findings, plus a marketplace snapshot only when the paid path is selected.

REQUIRED INPUT

A URL for page or schema review, a keyword for products, or a domain for gaps.

READINESS

URL and schema paths can run without DataForSEO. Products and gaps require its paid Merchant API.

OUTPUT

Observed evidence, structured-data findings, available provider data, prioritized actions, and explicit limitations.

SIDE EFFECTS

Fetches the target page. Paid paths also send a provider request and record the request in the local budget ledger.

COST + APPROVAL

Run the cost guardrail before paid Merchant API work. Amazon helper requests always need explicit approval.

// CHOOSE THE RIGHT PATH

What should this skill be used for?

Use the local paths for product-page and structured-data evidence. Add paid marketplace data only when the question needs it and the cost check is approved.

START HERE

Review a page or store

Use the URL command for page content, product evidence, images, internal paths, and visible structured data. Its core review does not require DataForSEO.

NARROW CHECK

Inspect Product markup

Use the schema command when the question is limited to Product and Offer property coverage, truthful correction recommendations, and Google eligibility guidance.

PAID RESEARCH

Add marketplace snapshots

Products and gaps use the paid DataForSEO Merchant API. They require credentials, a location-aware request, and the workflow's cost guardrail.

DO NOT USE IT FOR

Account-state validation

The skill does not inspect Merchant Center or Seller Central accounts. It cannot prove approval, inventory state, rankings, traffic, or sales.

// COMMAND SURFACE

Which e-commerce commands are available?

SOURCE VERIFIED: 2026-08-26

Four public commands

CommandUse it forDataForSEO
/seo ecommerce <url>Product-page or store analysis, with optional marketplace evidenceOptional
/seo ecommerce products <keyword>Location-specific Google Shopping product researchRequired
/seo ecommerce gaps <domain>Compare organic keyword visibility with Shopping presenceRequired
/seo ecommerce schema <url>Product and Offer structured-data reviewNo
Command correction: older page copy listed dedicated Shopping, Amazon, and pricing subcommands. They are not part of the reviewed public command surface. Amazon data remains an internal provider helper and every Amazon request requires explicit approval.

Representative sequence

/seo ecommerce https://shop.example.com/product/example
/seo ecommerce schema https://shop.example.com/product/example
/seo ecommerce products "running shoes"
/seo ecommerce gaps shop.example.com

The first two examples can run without DataForSEO. The last two should stop before a paid request until credentials and the cost decision are available. These are command examples, not claimed results.

// WORKFLOW + BOUNDARIES

What happens after you run a command?

  1. Resolve the input. The skill works from a URL, keyword, or domain, depending on the selected command.
  2. Inspect page evidence. URL paths review the accessible product content, images, internal paths, and visible Product or Offer markup.
  3. Check paid access. Marketplace paths require DATAFORSEO_USERNAME and DATAFORSEO_PASSWORD, followed by the cost guardrail before any request.
  4. Collect a provider snapshot. When approved, DataForSEO can return Google Shopping or internal Amazon helper results for a chosen location and language.
  5. Separate findings from limits. The output should distinguish observed page evidence, structured-data issues, provider data, recommended actions, and unknowns.

Cost and permission boundary

Claude SEO is MIT licensed, but paid provider calls are not free. The products and gaps commands require the optional DataForSEO extension. The full URL command can use that extension, while the schema command does not need it. The workflow must check the configured daily budget before each Merchant API request. Amazon endpoints are warning endpoints in the pinned guardrail and always require explicit approval.

The cost guardrail reads or writes ~/.config/claude-seo/dataforseo-costs.json and ~/.config/claude-seo/dataforseo-ledger.json. Review the configured budget before a paid call, and do not publish either local file.

Failure behavior

ConditionDocumented response
Invalid or non-product URLReject malformed input. For a category or homepage, identify the page type and suggest the schema path.
No Product schemaAnalyze available page content and recommend markup instead of claiming validation success.
Missing DataForSEO credentialsContinue without marketplace data and label the limitation.
Blocked cost checkStop the paid request and offer the page-only analysis.
Empty Shopping resultsSuggest a broader keyword and re-check location settings.
Amazon provider timeoutRetry with backoff, then fall back to Google-only evidence.

Outputs

  • Page and visible structured-data findings for the supplied URL
  • Product or Offer property findings and truthful correction recommendations
  • Marketplace snapshots only when the paid path is configured and approved
  • A prioritized action list with evidence, source, and limitation labels

What the result cannot prove

Valid Product markup can create eligibility for richer search appearances, but it does not guarantee that Google will show one. Provider snapshots are not first-party Merchant Center or Seller Central truth. Marketplace results can vary by location, language, and collection time. No live marketplace request was made for this page update.

// VERIFIED SOURCES

What is this reference based on?

Source review completed on . Product and provider requirements can change, so re-check the linked primary documentation before a consequential implementation.

// FAQ

What should you know before running it?

Start with /seo ecommerce <url> for a product page or store review. It can inspect the page without DataForSEO and add marketplace evidence only when the optional extension and approval are available.
// RELATED SKILLS

EXPLORE MORE

VIEW ALL 25 SKILLS →

AUDIT YOUR STORE
WITH EVIDENCE-LED CHECKS.

$
git clone --depth 1 https://github.com/AgriciDaniel/claude-seo.git && bash claude-seo/install.sh
VIEW SOURCE ALL SKILLS >