Agent skill

E-commerce SEO Analysis

by AgriciDaniel in AgriciDaniel/claude-seo

Analyzes a product page or store for SEO, from title tags and schema to marketplace visibility, with optional live Google Shopping and Amazon data for pricing and keyword gaps.

MITAuto-check passedMarketing & SEO

Install E-commerce SEO Analysis

skills CLI
$ npx skills add AgriciDaniel/claude-seo --skill seo-ecommerce -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install AgriciDaniel/claude-seo seo-ecommerce --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/AgriciDaniel/claude-seo.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/seo-ecommerce .claude/skills/seo-ecommerce && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
seo-ecommerce
GitHub stars
19k
Token cost
~3.7k tokens
SKILL.md length
1,330 words
Files
3 (incl. references)
Skills in repo
33
Repo updated
First seen
Licence
MIT

At a glance

Analyzes a product page or store for SEO, from title tags and schema to marketplace visibility, with optional live Google Shopping and Amazon data for pricing and keyword gaps.

  • Works in 5 steps: Product Page Analysis (No DataForSEO… → Google Shopping Intelligence (DataForSEO… → Amazon Marketplace (DataForSEO) → …
  • Auditing a product page's title tag, meta description and heading structure
  • SKILL.md covers Commands, 1. Product Page Analysis (No…, 2. Google Shopping… and 3. Amazon Marketplace…, plus 6 more sections
  • Reaches schema.org

What it does

This skill covers product-page SEO that works standalone on title tags, meta descriptions, heading structure, image optimization and internal linking, and extends into marketplace intelligence and pricing analysis when the DataForSEO Merchant API is connected. Without that API it can still render and parse any product page and check it against a product SEO checklist, for example requiring the title tag to stay under 60 characters and follow a product-feature-brand format, or requiring at least three images including a hero, detail and lifestyle shot.

With DataForSEO enabled, additional commands analyze Google Shopping competitive positioning for a keyword, find keyword gaps between organic and Shopping visibility for a domain, and validate or enhance product schema. The skill is scoped explicitly to stores, catalogs and product listings, not general content pages.

Supporting references cover marketplace endpoint details and the Universal Commerce Protocol, used when the audit needs to reason about how marketplaces surface product data.

When your agent uses it

  • Auditing a product page's title tag, meta description and heading structure
  • Checking a product catalog's images and internal linking for SEO gaps
  • Comparing Google Shopping visibility against organic rankings for a domain
  • Validating or improving product schema markup

Example prompts

  • “Audit this product page's on-page SEO against the checklist.”
  • “Find the keyword gap between our organic rankings and our Google Shopping visibility.”
  • “Run a competitive Shopping analysis for the keyword wireless earbuds.”
  • “Check and fix the product schema on this listing page.”

Requirements

  • The bundled claude-seo CLI scripts
  • Optionally a DataForSEO Merchant API key for Shopping and marketplace data
  • Compatibility (from SKILL.md): Enhanced with DataForSEO Merchant API (optional)

Workflow steps

5 steps, taken from the step headings in SKILL.md.

  1. Product Page Analysis (No DataForSEO Needed)
  2. Google Shopping Intelligence (DataForSEO Merchant API)
  3. Amazon Marketplace (DataForSEO)
  4. Marketplace Keyword Gaps
  5. Product Schema Enhancement

What it can do on your machine

Read from SKILL.md and the folder at commit 4b99de2. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are bash and json).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Hosts in commands or code, which the agent is likely to contact:

    • schema.org

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

  • Compatibility

    Enhanced with DataForSEO Merchant API (optional)

    From compatibility in the SKILL.md frontmatter.

Context cost

E-commerce SEO Analysis loads about 3.7k tokens when it runs, and up to ~6.8k if it reads all its reference files. Until then it costs about 46 tokens; SKILL.md has 1,330 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~46
When it runs · the whole SKILL.md, loaded when a task matches
~3.7k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~6.8k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from AgriciDaniel/claude-seo at commit 4b99de2, republished under its MIT licence (© AgriciDaniel). 1,330 words, ~3,731 tokens.

Download SKILL.mdSave it as .claude/skills/seo-ecommerce/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.
name
seo-ecommerce
description
Analyze ecommerce SEO across product pages, product schema, Shopping visibility, marketplace signals, and keyword gaps. Use only for stores, catalogs, or product listings.
compatibility
Enhanced with DataForSEO Merchant API (optional)
user-invocable
true
argument-hint
<url or keyword>
license
MIT
metadata.author
AgriciDaniel
metadata.original_author
Matej Marjanovic (Pro Hub Challenge)
metadata.version
2.4.2
metadata.category
seo

E-commerce SEO Analysis

Comprehensive product page optimization, marketplace intelligence, and competitive pricing analysis. Works standalone (on-page + schema) and with DataForSEO Merchant API for live Google Shopping and Amazon data.

Commands

CommandPurposeDataForSEO?
/seo ecommerce <url>Full e-commerce SEO analysis of a product page or storeOptional
/seo ecommerce products <keyword>Google Shopping competitive analysisRequired
/seo ecommerce gaps <domain>Keyword gap: organic vs Shopping visibilityRequired
/seo ecommerce schema <url>Product schema validation and enhancementNo

1. Product Page Analysis (No DataForSEO Needed)

Fetch and parse any product page for on-page SEO quality.

Workflow
1. "${CLAUDE_PLUGIN_ROOT}/scripts/claude-seo" run render_page.py <url> --mode auto → raw/rendered HTML
2. "${CLAUDE_PLUGIN_ROOT}/scripts/claude-seo" run parse_html.py --url <url>   → SEO elements
3. Analyze product-specific signals (below)
Product SEO Checklist
Title Tag
  • Contains primary product keyword
  • Includes brand name
  • Under 60 characters (no truncation in SERPs)
  • Format: [Product Name] - [Key Feature] | [Brand]
Meta Description
  • Contains product keyword + benefit
  • Includes price or "from $XX" (triggers rich snippet interest)
  • Call-to-action present (Shop now, Buy, Free shipping)
  • Under 155 characters
Heading Structure
  • Single H1 matching primary product name
  • H2s for: Features, Specifications, Reviews, Related Products
  • No duplicate H1 tags across product variants
Product Images
  • Alt text includes product name + distinguishing feature
  • File names are descriptive (not IMG_001.jpg)
  • WebP format served (with JPEG fallback)
  • At least 3 images per product (hero, detail, lifestyle)
  • High-resolution images: Google recommends at least 50K pixels (width x height) for merchant listings; larger (for example 800px+) is common practice, not a rule
  • Lazy loading on below-fold images only
Internal Linking
  • Breadcrumb navigation: Home > Category > Subcategory > Product
  • Related products section (cross-sell / upsell)
  • Link back to category page with keyword-rich anchor
  • Reviews section links to full review page (if separate)
Content Quality
  • Unique product description (not manufacturer copy-paste)
  • Word count >= 200 for product description body
  • Specs table present (not just prose)
  • User reviews on-page (UGC signals)
Scoring
CategoryWeightCriteria
Schema completeness25%Required + recommended Product fields
Title & meta15%Keyword placement, length, format
Image optimization20%Alt text, format, sizing, count
Content quality20%Unique description, specs, reviews
Internal linking10%Breadcrumbs, related products, categories
Technical10%Page speed, mobile rendering, canonical

2. Google Shopping Intelligence (DataForSEO Merchant API)

Live competitive analysis from Google Shopping results.

Cost Guardrail (MANDATORY)

Before EVERY Merchant API call:

bash
"${CLAUDE_PLUGIN_ROOT}/scripts/claude-seo" run dataforseo_costs.py check merchant_google_products_search
  • "status": "approved" -- proceed
  • "status": "needs_approval" -- show cost, ask user
  • "status": "blocked" -- stop, inform user

After each call:

bash
"${CLAUDE_PLUGIN_ROOT}/scripts/claude-seo" run dataforseo_costs.py log merchant_google_products_search <cost>
Workflow
bash
# Product search: who sells what at what price
"${CLAUDE_PLUGIN_ROOT}/scripts/claude-seo" run dataforseo_merchant.py search "<keyword>" --marketplace google

# Seller analysis: merchant ratings and dominance
"${CLAUDE_PLUGIN_ROOT}/scripts/claude-seo" run dataforseo_merchant.py sellers "<keyword>"

# Normalize results for analysis
"${CLAUDE_PLUGIN_ROOT}/scripts/claude-seo" run dataforseo_normalize.py results.json --module merchant
Analysis Outputs
Pricing Intelligence
  • Price distribution: min, max, median, P25, P75
  • Price outliers (> 2 standard deviations from median)
  • Price-to-rating correlation
  • Currency normalization to USD (or user-specified)
Seller Landscape
  • Top 10 sellers by listing count
  • Merchant rating distribution
  • Free shipping prevalence
  • New vs established sellers
Product Listing Quality
  • Title keyword patterns in top listings
  • Average rating and review count benchmarks
  • Image count per listing
  • Availability status distribution

Load references/marketplace-endpoints.md for full API parameter details.


3. Amazon Marketplace (DataForSEO)

Cross-marketplace intelligence comparing Google Shopping and Amazon.

Cost Guardrail (MANDATORY)
bash
"${CLAUDE_PLUGIN_ROOT}/scripts/claude-seo" run dataforseo_costs.py check merchant_amazon_products_search

Amazon endpoints are in the warn_endpoints set -- always requires user approval.

Workflow
bash
# Amazon product search
"${CLAUDE_PLUGIN_ROOT}/scripts/claude-seo" run dataforseo_merchant.py search "<keyword>" --marketplace amazon

# Cross-marketplace comparison
"${CLAUDE_PLUGIN_ROOT}/scripts/claude-seo" run dataforseo_merchant.py compare "<keyword>"
Cross-Marketplace Report
MetricGoogle ShoppingAmazon
Avg price$$
Median ratingX.XX.X
Avg review countNN
Top seller share%%
Free shipping %%%

4. Marketplace Keyword Gaps

Identify mismatches between organic and Shopping visibility.

Workflow
  1. Fetch organic rankings via seo-dataforseo: dataforseo_labs_google_ranked_keywords for domain
  2. Fetch Google Shopping presence through the Merchant REST script (not an MCP tool; the cost-ledger key is merchant_google_products_search): "${CLAUDE_PLUGIN_ROOT}/scripts/claude-seo" run dataforseo_merchant.py search <keyword> for the top organic keywords
  3. Cross-reference results
Gap Types
Gap TypeMeaningAction
Organic OnlyRanks organically but no Shopping adsCreate Google Merchant Center feed, bid on these keywords
Shopping OnlyShopping visibility but weak/no organicCreate content (buying guides, comparison pages) for these keywords
Both PresentVisible in both channelsOptimize: ensure price consistency, enhance schema
NeitherNo visibility in eitherLow priority unless high volume
Output Format
## Keyword Gap Analysis: example.com

### Opportunities: Organic → Shopping (12 keywords)
| Keyword | Organic Pos | Volume | CPC | Recommended Action |
|---------|------------|--------|-----|-------------------|

### Opportunities: Shopping → Organic (8 keywords)
| Keyword | Shopping Rank | Volume | CPC | Content Type Needed |
|---------|-------------|--------|-----|-------------------|

5. Product Schema Enhancement

Validate and generate Product schema following Google's current requirements.

Confirmed Required Properties (Google Merchant)

Confirmed required fields are name, image, and offers; use Offer, not AggregateOffer, for merchant listings. Merchant listings require a price greater than zero, and priceCurrency whenever price is set.

json
{
  "@context": "https://schema.org",
  "@type": "Product",
  "name": "",
  "image": [""],
  "offers": {
    "@type": "Offer",
    "url": "",
    "priceCurrency": "USD",
    "price": "49.00",
    "availability": "https://schema.org/InStock"
  }
}
  • sku -- product identifier
  • description, brand, offers.seller -- recommended context fields
  • gtin13 / gtin14 / mpn -- global trade identifiers
  • aggregateRating -- star rating + review count
  • review -- individual reviews (minimum 1)
  • color, material, size -- variant attributes
  • shippingDetails -- ShippingDetails with rate and delivery time (merchant-level shipping via ShippingService is also supported; shipping/returns can be set in Search Console without a Merchant Center account)
  • hasMerchantReturnPolicy -- MerchantReturnPolicy with type and days
  • hasAdultConsideration -- required for adult-oriented products (added 2026-05-20 to Product variant / Merchant listing); Google Search supports only the value https://schema.org/SexualContentConsideration
  • category -- Text, CategoryCode, or an array mixing both. Use custom text for merchant-defined product types and CategoryCode with Google's taxonomy URL plus codeValue for Google Product Categories.
Show full SKILL.md (563 more words)Show less
Validation Rules
  1. price must be a number string, not "$29.99" (no currency symbol)
  2. availability must use full Schema.org URL enum
  3. image should be array with >= 1 high-res image URL
  4. priceCurrency must be ISO 4217 (USD, EUR, GBP)
  5. If brand is present, brand.name must not be empty or "N/A"
  6. Sale periods use validFrom plus either validThrough or priceValidUntil, in ISO 8601 format. Include time and timezone when known.
  7. If aggregateRating present: ratingValue and reviewCount required (the merchant-listing docs list reviewCount; the review-snippet docs also accept ratingCount)
  8. Do not include fake reviews or undisclosed incentivized reviews in visible content or structured data. Clearly and prominently disclose incentives.
Schema Scoring
CompletenessScore
All required fields50/100
+ aggregateRating65/100
+ sku/gtin/mpn75/100
+ shippingDetails85/100
+ merchantReturnPolicy90/100
+ reviews (3+)100/100

Cross-Skill Integration

SkillIntegration Point
seo-schemaDelegates Product schema generation; reuses validation logic
seo-imagesProduct image audit (alt text, format, dimensions), plus DigitalSourceType: TrainedAlgorithmicMedia IPTC label for AI-generated product images (Merchant Center requirement)
seo-contentProduct description E-E-A-T and uniqueness analysis
seo-dataforseoOrganic keyword rankings for gap analysis
seo-technicalCore Web Vitals for product pages (LCP on hero image)
seo-hreflangRegion-specific result units: in the EEA, product and (since 2026-09-18) local business queries can show aggregator and supplier units; the EEA, South Africa and Türkiye also have structured data carousels, each with its own eligibility rules (documented 2026-09-08)
seo-googleGSC indexation + Performance data for product URLs (NOT Merchant Center feed validation, that is done in Merchant Center / the Merchant API; the legacy Content API for Shopping sunsets 2026-08-18)

UCP: Universal Commerce Protocol (live)

Google-initiated open standard (co-developed with Shopify, Etsy, Wayfair, Target, Walmart; payment partners Visa/Mastercard/Stripe/Adyen/Amex) for letting AI agents discover, negotiate, and transact with merchants without one-off integrations. Google confirms a first reference implementation for conversational buying in AI Mode in Search. Broader Universal Cart rollout details are reported from Google I/O 2026 keynote coverage; not confirmed on a Google-owned source. ucp.dev lists 2026-08-25 as the latest spec release (Google's merchant guide still documents 2026-04-08) in its date-based versioning scheme, not 1.0; two integration paths: Native (default) and Embedded (approved merchants). Pairs with AP2 (reportedly moving toward FIDO governance). Canonical: developers.google.com/merchant/ucp and ucp.dev.

Merchants already on Google Merchant Center with clean Product schema can declare a UCP profile at /.well-known/ucp listing capabilities (dev.ucp.shopping.checkout, .fulfillment, .discount). See references/ucp-universal-commerce-protocol.md for audit criteria, capability examples, and the relationship to AP2 (Agent Payments Protocol).

Audit command
bash
# Discover and validate the UCP profile
"${CLAUDE_PLUGIN_ROOT}/scripts/claude-seo" run ucp_check.py https://store.example.com --json

# With endpoint reachability probes (HEAD each declared capability)
"${CLAUDE_PLUGIN_ROOT}/scripts/claude-seo" run ucp_check.py https://store.example.com --probe-endpoints --json

The script returns: profile presence, version, declared capabilities, structural issues (missing fields, unknown capability IDs), and (with --probe-endpoints) per-endpoint reachability. SSRF-blocked endpoints are reported explicitly. Missing profile is reported as opportunity, not failure. UCP itself is live; what's early is broad merchant adoption. Flag a literal "version": "1.0" as invalid (UCP versions are date-based, e.g. 2026-04-08).


Error Handling

ErrorCauseResponse
No Product schema foundPage lacks JSON-LDAnalyze page content, generate recommended schema
DataForSEO credentials missingEnv vars not setRun analysis without marketplace data, note limitation
Cost check blockedDaily budget exceededInform user, offer free-only analysis
Empty Shopping resultsNo products for keywordSuggest broader keyword, check location settings
Amazon API timeoutNetwork/rate limitRetry with backoff, fall back to Google-only
Invalid URLMalformed inputValidate via google_auth.validate_url(), show error
Non-product pageURL is category/homepageRun the store-level checks (UCP profile, category structure, feeds) and ask for a product URL for the product-level checks

Output Template

## E-commerce SEO Report: [URL or Keyword]

### Overall Score: XX/100

### Product Page SEO
- Schema Completeness: XX/100
- Title & Meta: XX/100
- Image Optimization: XX/100
- Content Quality: XX/100
- Internal Linking: XX/100

### Marketplace Intelligence (if DataForSEO available)
- Google Shopping Listings: N products found
- Price Range: $XX - $XX (median: $XX)
- Top Seller: [name] (XX% market share)
- Amazon Comparison: [available/not checked]

### Top Recommendations
1. [Critical] ...
2. [High] ...
3. [Medium] ...

Generate a PDF report? Use `/seo google report`

© AgriciDaniel, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 2 other files (references) in skills/seo-ecommerce of AgriciDaniel/claude-seo.

  • SKILL.md
  • references/marketplace-endpoints.md
  • references/ucp-universal-commerce-protocol.md

Open the folder on GitHubat commit 4b99de2

Compare with similar skills

E-commerce SEO Analysis next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

E-commerce SEO Analysis compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
E-commerce SEO Analysis this skillAgriciDaniel/claude-seo19k—~3.7kAutomated safety check: PassMIT
Amazon Listing Competitor Analysisbrowser-act/skills6.1k1 repos~3.2kAutomated safety check: PassMIT
Ecommerce Keyword Researchnexscope-ai/eCommerce-Skills1.1k—~645Automated safety check: PassMIT
Product Page SEOnexscope-ai/eCommerce-Skills1.1k—~600Automated safety check: PassMIT
Amazon Listing Optimizationnexscope-ai/Amazon-Skills7441 repos~4.3kAutomated safety check: PassMIT
SEO Content Briefseranking/seo-skills161—~2.5kAutomated safety check: PassMIT

Similar skills

  • Analyzes a competitor's Amazon listing by ASIN with BrowserAct data extraction, then reports what it does well, where the market has gaps and opportunity points for your own listing.

    6.1k GitHub starsUsed in 1 repo~3.2k tokens
    Marketing & SEOAuto-check passed
  • Ecommerce Keyword Research

    nexscope-ai/eCommerce-Skills

    Cross-platform keyword research for e-commerce. An agent skill from nexscope-ai/eCommerce-Skills.

    1.1k GitHub stars~645 tokensUpdated 1 mo ago
    Marketing & SEOAuto-check passed
  • Product Page SEO

    nexscope-ai/eCommerce-Skills

    Optimize e-commerce product pages for search engine visibility.

    1.1k GitHub stars~600 tokensUpdated 1 mo ago
    Marketing & SEOAuto-check passed
  • Amazon Listing Optimization

    nexscope-ai/Amazon-Skills

    Amazon listing builder and optimizer for sellers. An agent skill from nexscope-ai/Amazon-Skills.

    744 GitHub starsUsed in 1 repo~4.3k tokens
    Marketing & SEOAuto-check passed
  • SEO Content Brief

    seranking/seo-skills

    Generate a writer-ready SEO content brief from a target domain and topic.

    161 GitHub stars~2.5k tokensUpdated 3 mo ago
    Marketing & SEOAuto-check passed
  • Blog Outline

    AgriciDaniel/claude-blog

    SERP-informed outline generation with H2/H3 heading hierarchy, competitive content gap analysis, section-by-section word count targets, chart and image placement markers, optional FAQ question…

    2.3k GitHub starsUsed in 1 repo~1.5k tokens
    Marketing & SEOAuto-check passed

More from AgriciDaniel/claude-seo

All 33 skills in this repo
  • Hreflang and International SEO

    AgriciDaniel/claude-seo

    Audits, validates and generates hreflang tags for multi-language and multi-region sites in HTML, HTTP headers or XML sitemaps, flagging common code and return-tag mistakes.

    19k GitHub starsUsed in 5 repos~3.4k tokens
    Auto-check passed
  • Google SEO APIs

    AgriciDaniel/claude-seo

    Pulls real Google data for SEO work: Search Console, PageSpeed Insights, CrUX field data, the Indexing API and GA4 organic traffic, through /seo google commands.

    19k GitHub starsUsed in 1 repo~4.2k tokens
    Auto-check passed
  • SEO Keyword Clustering

    AgriciDaniel/claude-seo

    Clusters keywords by how much their search results overlap and designs a hub-and-spoke content plan with an internal link matrix and an interactive cluster map.

    19k GitHub starsUsed in 2 repos~3.3k tokens
    Auto-check passed
  • SEO Content Brief Generator

    AgriciDaniel/claude-seo

    Builds research-backed SEO content briefs with competitor scoring, per-section word counts and page-type templates, for new pages or improving existing ones.

    19k GitHub starsUsed in 2 repos~2.6k tokens
    Auto-check passed
  • FLOW SEO Framework

    AgriciDaniel/claude-seo

    Brings the FLOW framework's stage-specific SEO prompts into the agent, from keyword discovery through backlinks, on-page work and conversion to local SEO, loaded on demand.

    19k GitHub starsUsed in 2 repos~1.4k tokens
    Auto-check passed
  • SEO Image Generator

    AgriciDaniel/claude-seo

    Generates Open Graph previews, blog hero images, product photos and infographics for SEO use through Gemini image tools and the banana extension.

    19k GitHub starsUsed in 2 repos~2.1k tokens
    Auto-check passed

Questions about E-commerce SEO Analysis

What does E-commerce SEO Analysis do?

Analyzes a product page or store for SEO, from title tags and schema to marketplace visibility, with optional live Google Shopping and Amazon data for pricing and keyword gaps. This skill covers product-page SEO that works standalone on title tags, meta descriptions, heading structure, image optimization and internal linking, and extends into marketplace intelligence and pricing analysis when the DataForSEO Merchant API is connected. Without that API it can still render and parse any product page and check it against a product SEO checklist, for example requiring the title tag to stay under 60 characters and follow a product-feature-brand format, or requiring at least three images including a hero, detail and lifestyle shot.

When should I use E-commerce SEO Analysis?

E-commerce SEO Analysis fits situations like: auditing a product page's title tag, meta description and heading structure; checking a product catalog's images and internal linking for SEO gaps; comparing Google Shopping visibility against organic rankings for a domain; validating or improving product schema markup.

How do I install E-commerce SEO Analysis in Claude Code?

Run `npx skills add AgriciDaniel/claude-seo --skill seo-ecommerce -a claude-code`. Or copy the skill folder (skills/seo-ecommerce in AgriciDaniel/claude-seo) into .claude/skills/seo-ecommerce in your project. Claude Code loads it when a task matches its description.

How do I install E-commerce SEO Analysis in Codex?

Run `npx skills add AgriciDaniel/claude-seo --skill seo-ecommerce -a codex`. Or copy the skill folder (skills/seo-ecommerce in AgriciDaniel/claude-seo) into .agents/skills/seo-ecommerce in your project. Codex loads it when a task matches its description.

Can I use E-commerce SEO Analysis in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add AgriciDaniel/claude-seo --skill seo-ecommerce -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/seo-ecommerce, .gemini/skills/seo-ecommerce, .github/skills/seo-ecommerce and .opencode/skills/seo-ecommerce in your project.

What does E-commerce SEO Analysis need to run?

SKILL.md names no scripts, command-line tools or credentials: E-commerce SEO Analysis is instructions for the agent only. Our summary lists: The bundled claude-seo CLI scripts; Optionally a DataForSEO Merchant API key for Shopping and marketplace data. Compatibility (from SKILL.md): Enhanced with DataForSEO Merchant API (optional).

Does E-commerce SEO Analysis access the network?

SKILL.md names 1 domain. In commands or code: schema.org; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.

Is E-commerce SEO Analysis safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does E-commerce SEO Analysis use?

E-commerce SEO Analysis is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does E-commerce SEO Analysis use?

About 3.7k tokens (SKILL.md is roughly 15k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 3k tokens, read only when the agent opens those files.

What are the alternatives to E-commerce SEO Analysis?

Skills that share tags, products or a category with E-commerce SEO Analysis: Amazon Listing Competitor Analysis (browser-act/skills, 6.1k stars), Ecommerce Keyword Research (nexscope-ai/eCommerce-Skills, 1.1k stars), Product Page SEO (nexscope-ai/eCommerce-Skills, 1.1k stars) and Amazon Listing Optimization (nexscope-ai/Amazon-Skills, 744 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains E-commerce SEO Analysis?

AgriciDaniel (a GitHub user) maintains it in AgriciDaniel/claude-seo, which has 18,627 GitHub stars. The repository holds 33 skills in this directory. The repository was last updated on October 4, 2026.

Source: AgriciDaniel/claude-seo on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.