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".

10,211stars1,470forksUpdated 7/1/2026

Developer Tools #dataforseo #amazon #ecommerce #google-shopping #product-schema #seo

Security Assessment

Safe(100/100)

Security Score100/100

About seo-ecommerce

Performs e-commerce SEO analysis that combines on-page product optimization with marketplace intelligence. It covers Google Shopping visibility, Amazon marketplace comparison, Product schema validation, competitor pricing analysis, and marketplace keyword gaps. It works standalone for on-page and schema checks and is enhanced by the optional DataForSEO Merchant API for live Google Shopping and Amazon data. Trigger it with phrases such as ecommerce SEO, product SEO, Google Shopping, marketplace SEO, product schema, or Amazon SEO, and invoke commands like /seo ecommerce <url> for a full analysis or /seo ecommerce schema <url> for schema validation.

Product page analysis runs without DataForSEO: it renders the page via scripts/render_page.py and parses SEO elements via scripts/parse_html.py, then evaluates a product SEO checklist across title tag, meta description, heading structure, images, internal linking, and content quality, scoring categories by weight (schema completeness 25%, images 20%, content 20%, title and meta 15%, internal linking 10%, technical 10%). The Google Shopping and Amazon modules require DataForSEO and are gated by a mandatory cost guardrail: before every Merchant API call it runs scripts/dataforseo_costs.py check and proceeds only on approved status, asking the user when approval is needed or stopping when blocked, then logs the cost after each call. Amazon endpoints always require user approval.

Outputs include pricing intelligence (distribution, outliers, price-to-rating correlation, currency normalization), seller landscape analysis, product listing quality benchmarks, and a cross-marketplace comparison table. A marketplace keyword gap analysis cross-references organic rankings (via seo-dataforseo ranked keywords) against Google Shopping presence and classifies keywords as Organic Only, Shopping Only, Both Present, or Neither, each with a recommended action. The schema module validates and generates Product schema following Google Merchant requirements, listing required properties (name, image, description, brand, offers) and recommended ones (sku, gtin, mpn, aggregateRating). Reference files such as marketplace-endpoints.md hold full API parameter details.

FAQ

Does this skill require the DataForSEO Merchant API?

Product page analysis and schema validation work standalone without it, but the Google Shopping, Amazon, and keyword gap modules require the DataForSEO Merchant API.

How does it control DataForSEO costs?

Before every Merchant API call it runs a mandatory cost guardrail via scripts/dataforseo_costs.py check, proceeding only when approved, asking the user when approval is needed, and stopping when blocked; it logs the cost after each call.

How is a product page scored?

By weighted categories: schema completeness 25%, image optimization 20%, content quality 20%, title and meta 15%, internal linking 10%, and technical 10%.

What does the keyword gap analysis identify?

It cross-references organic rankings against Google Shopping presence and classifies keywords as Organic Only, Shopping Only, Both Present, or Neither, each with a recommended action.

Which Product schema properties does it check?

Required Google Merchant properties like name, image, description, brand, and offers, plus recommended ones such as sku, gtin, mpn, and aggregateRating.