Seo Ecommerce
Query Google Shopping and Amazon merchant APIs via DataForSEO to research competitor listings, prices, sellers, and SERP shopping visibility for ecommerce SEO.
Overview
seo-ecommerce is an agent skill most often used in Launch (also Validate, Grow) that documents DataForSEO Google Shopping and Amazon merchant endpoints for competitive ecommerce SEO research.
Install
npx skills add https://github.com/agricidaniel/claude-seo --skill seo-ecommerceWhat is this skill?
- Documents merchant_google_products_search and merchant_google_sellers_search with $0.02-per-call queue pricing
- Maps keyword, location_code, language_code, price filters, sort_by, and depth parameters
- Exposes title, price, seller, rating, reviews_count, availability, and delivery_info response fields
- Covers standard task queue workflow (POST task / GET results) for cost-efficient pulls
- Reference for ecommerce competitive intel tied to DataForSEO Merchant API endpoints
- $0.02 per merchant API call
- Standard queue noted as 60–80% savings vs live
- Default depth 100 results
Adoption & trust: 1.3k installs on skills.sh; 8.5k GitHub stars; 2/3 security scanners passed (skills.sh audits).
What problem does it solve?
You need Google Shopping and marketplace listing data for SEO but do not have endpoint names, parameters, or response fields memorized for DataForSEO Merchant API.
Who is it for?
Indie shop owners and solo SaaS builders running DataForSEO-backed competitive shopping SERP and marketplace intel before or after launch.
Skip if: Teams that want on-page Shopify theme edits, checkout flows, or non-merchant SEO APIs without DataForSEO credentials and budget.
When should I use this skill?
You need Google Shopping or Amazon merchant endpoint details, parameters, or response fields for ecommerce SEO research with DataForSEO.
What do I get? / Deliverables
Your agent can request merchant product and seller searches with correct filters and interpret title, price, seller, rating, and availability fields for listing and pricing decisions.
- Correctly shaped merchant API task payloads
- Interpreted product and seller field maps for SEO notes
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Canonical shelf is Launch because solo builders use merchant SERP and marketplace data to optimize product discovery and competitive positioning after the store exists. SEO subphase fits shopping-keyword research, listing titles, and marketplace visibility—not checkout or catalog backend implementation.
Where it fits
Pull Shopping SERP prices with price_min and price_max before setting your SKU bands.
Compare listing titles and ratings for target keywords in US location_code 2840.
Track seller ratings and reviews_count to refresh comparison and FAQ content.
How it compares
API field reference for merchant SERP data—not a scroll-design or front-end animation skill.
Common Questions / FAQ
Who is seo-ecommerce for?
Solo builders selling physical or digital products who use Claude Code or similar agents with DataForSEO to research Google Shopping listings, sellers, and pricing.
When should I use seo-ecommerce?
During Validate when scoping pricing against competitors, at Launch when optimizing product SEO and shopping visibility, and in Grow when monitoring rival listings and merchant ratings.
Is seo-ecommerce safe to install?
Treat it as documentation-only procedural knowledge; review the Security Audits panel on this Prism page and never paste live API keys into untrusted copies of the skill.
SKILL.md
READMESKILL.md - Seo Ecommerce
# DataForSEO Merchant API Reference Endpoint details for Google Shopping and Amazon marketplace data. ## Endpoints ### Google Shopping Products | Field | Value | |-------|-------| | Endpoint | `merchant_google_products_search` | | Method | POST (task) / GET (results) | | Cost | $0.02 per call | | Queue | Standard (60-80% savings vs live) | **Parameters:** - `keyword` (required) -- search query - `location_code` (default: 2840 = US) -- DataForSEO location ID - `language_code` (default: "en") -- language - `price_min` / `price_max` (optional) -- filter by price range - `sort_by` (optional) -- "relevance", "price_low_to_high", "price_high_to_low", "rating" - `depth` (optional, default: 100) -- number of results **Response fields:** - `title` -- product listing title - `price` -- numeric price value - `currency` -- currency code (USD, EUR, etc.) - `seller` -- merchant name - `rating` -- product rating (float, 0-5) - `reviews_count` -- number of reviews - `url` -- product listing URL - `image_url` -- product image URL - `availability` -- "in_stock", "out_of_stock", "preorder" - `delivery_info` -- shipping details text - `product_id` -- Google Shopping product ID ### Google Shopping Sellers | Field | Value | |-------|-------| | Endpoint | `merchant_google_sellers_search` | | Method | POST (task) / GET (results) | | Cost | $0.02 per call | **Parameters:** Same as products search. **Response fields:** - `seller_name` -- merchant name - `seller_rating` -- merchant rating (float) - `seller_reviews_count` -- merchant review count - `price` -- price offered by this seller - `delivery_info` -- shipping and delivery text - `url` -- seller listing URL ### Amazon Products | Field | Value | |-------|-------| | Endpoint | `merchant_amazon_products_search` | | Method | POST (task) / GET (results) | | Cost | $0.02 per call | | Note | In `warn_endpoints` -- always requires user approval | **Parameters:** - `keyword` (required) -- search query - `location_code` (default: 2840 = US) - `language_code` (default: "en") - `depth` (optional, default: 100) - `sort_by` (optional) -- "relevance", "price_low_to_high", "price_high_to_low", "avg_customer_review" **Response fields:** - `title` -- product title - `price` -- numeric price - `currency` -- currency code - `seller` -- seller/brand name - `rating` -- star rating (float, 0-5) - `reviews_count` -- review count - `url` -- Amazon product URL - `image_url` -- product image - `availability` -- stock status - `asin` -- Amazon Standard Identification Number - `is_prime` -- Prime eligibility (boolean) - `is_best_seller` -- Best Seller badge (boolean) ## Task/Poll Pattern All Merchant endpoints use the standard DataForSEO queue pattern: 1. **POST** task with parameters to create endpoint 2. **Poll** for results with exponential backoff (2s, 4s, 8s, max 60s) 3. **GET** completed results by task ID This saves 60-80% compared to live endpoints. ## Rate Limits - Max 2000 tasks per minute (across all endpoints) - Max 30,000 tasks per day on standard plans - Backoff on HTTP 429: wait 60 seconds, then retry ## Data Normalization When consuming responses, normalize: | Field | Raw | Normalized | |-------|-----|-----------| | Price | String "$29.99" or float | Float `29.99` | | Currency | Mixed formats | ISO 4217 code (USD, EUR, GBP) | | Availability | Various strings | Enum: `in_stock`, `out_of_stock`, `preorder`, `unknown` | | Rating | Integer or float | Float rounded to 1 decimal | | Reviews | String or int | Integer | Use `scripts/dataforseo_normalize.py --module merchant` for automatic normalization. ## Cost Reference See `skills/seo-dataforseo/references/cost-tiers.md` for the full pricing table, budget presets, and cost reduction tips. All Merchant endpoints are $0.02/call on standard queue. # UCP — Universal Commerce Protocol (May 2026) UCP is a Google-led open standard, co-developed with Shopify and endorsed by Etsy, Target, Walmart, Wayfair, plus payment partners (Stripe, Visa, Mas