agentleFS
ZachArticulateVZachArticulateV/designer-pro-and-seo/skills/seo-ecommerce/SKILL.md

seo-ecommerce

Skill10 starsChanged 27 days agoMITView on GitHub

Optimizes e-commerce SEO across product and category pages — on-page product elements, Product schema validation, image SEO, and faceted/canonical strategy for filters and variants. Uses DataForSEO Merchant for Google Shopping and Amazon marketplace intelligence when connected; otherwise audits feed basics and on-page signals manually. Trigger when the user says "ecommerce SEO", "product SEO", "product schema", "Google Shopping", "Amazon SEO", "marketplace SEO", "product listings", "shopping ads", or "merchant SEO".

18 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use seo-agentic, brandkit and 3 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • AgriciDanielSkill

    seo-agentic

    Audit and fix agent readiness: the Lighthouse Agentic Browsing fraction, accessibility tree for agents, robots.txt and Content-Signal for AI agents, WAF treatment of agent traffic, llms.txt, Markdown delivery, ai-catalog.json, /.well-known discovery files, and WebMCP tools. Use when the user asks whether AI agents can use or browse the site, or about llms.txt or WebMCP. Exclude AI citability and brand signals (seo-geo) and commerce protocol depth (seo-ecommerce).

    Also in 4 projects that use this

  • AnasX7Skill

    brandkit

    Premium brand-kit image generation skill for creating high-end brand-guidelines boards, logo systems, identity decks, and visual-world presentations. Trained for minimalist, cinematic, editorial, dark-tech, luxury, cultural, security, gaming, developer-tool, and consumer-app brand systems. Optimized for intentional logo concepting, refined composition, sparse typography, strong symbolic meaning, premium mockups, art-directed imagery, and flexible grid layouts.

    Also in 3 projects that use this

  • AnasX7Skill

    minimalist-ui

    Clean editorial-style interfaces. Warm monochrome palette, typographic contrast, flat bento grids, muted pastels. No gradients, no heavy shadows.

    Also in 3 projects that use this

  • StrayDragonSkill

    ui-ux-pro-max

    UI/UX design intelligence. 50 styles, 21 palettes, 50 font pairings, 20 charts, 8 stacks (React, Next.js, Vue, Svelte, SwiftUI, React Native, Flutter, Tailwind). Actions: plan, build, create, design, implement, review, fix, improve, optimize, enhance, refactor, check UI/UX code. Projects: website, landing page, dashboard, admin panel, e-commerce, SaaS, portfolio, blog, mobile app, .html, .tsx, .vue, .svelte. Elements: button, modal, navbar, sidebar, card, table, form, chart. Styles: glassmorphism, claymorphism, minimalism, brutalism, neumorphism, bento grid, dark mode, responsive, skeuomorphism, flat design. Topics: color palette, accessibility, animation, layout, typography, font pairing, spacing, hover, shadow, gradient.

    Also in 4 projects that use this

  • +1 more from AnasX7

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 18 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Marketplace (optional): If DataForSEO is configured, pull Google Shopping presence and Amazon/keyword-gap data.

    line 53

“Common” is measured: kept by at least 6 in 10 of the 18 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

seo-ecommerce

Family: seo Status: Stable

Purpose

E-commerce-specific SEO. The free path fully covers on-page product SEO and Product schema; marketplace intelligence (Google Shopping, Amazon) is the optional DataForSEO-Merchant path.

Triggers

  • "ecommerce seo" / "product seo" / "merchant seo"
  • "product schema" / "product listings"
  • "google shopping" / "shopping ads" / "amazon seo" / "marketplace seo"

Inputs

  • Domain or product URL(s)
  • Marketplace coverage (Google Shopping / Amazon / both / none)
  • Competitor domains (optional)

Steps

  1. Run the product audit on each key product page — merchant-listing eligibility and agreement between markup and the visible page:
    python3 "${CLAUDE_PLUGIN_ROOT}/scripts/seo/product_audit.py" --file product.html --url <URL> --as-of <YYYY-MM-DD> --human
    P1–P14: Product/ProductGroup markup validated through schema_gen.py, availability, GTIN/MPN/brand, return policy (Offer or Organization) and shipping details, expired priceValidUntil, marked-up price not visible, rating markup with no visible rating, InStock vs "sold out", variants without a ProductGroup, H1, thin copy (references/seo-ecommerce/merchant-checks.md).
  2. Run the category audit on listing, filtered and paginated URLs (pass the real URL with its query string):
    python3 "${CLAUDE_PLUGIN_ROOT}/scripts/seo/product_audit.py" --file list.html --url "<URL?color=red&page=2>" --type category --human
    C1–C6: self-canonical indexable facets, page N canonicalized to page 1, noindexed pagination, indexable sort URLs, thin category copy, ItemList.
  3. Image SEO via seo-image-audit (product photos are conversion- and ranking-critical: alt, format, size, CLS).
  4. Faceted strategy — decide which few facets deserve indexable landing pages (real demand + unique copy); canonicalize or noindex the rest (coordinate with seo-programmatic).
  5. Marketplace (optional). If DataForSEO is configured, pull Google Shopping presence and Amazon/keyword-gap data; otherwise state what it would add and check feed basics manually.
  6. Render per-product scores, schema validation, and a prioritized fix list.

Outputs

  • Per-product on-page scores + prioritized fixes
  • Product schema validation report
  • Marketplace presence/gap report (when DataForSEO present) or a manual checklist

Dependencies

  • scripts/seo/product_audit.py (required) — product + category audit (imports schema_gen)
  • references/seo-ecommerce/merchant-checks.md (required) — codes, severities, scoring
  • seo-schema (Product schema), seo-page (per-product), seo-image-audit (images)
  • Optional: DataForSEO Merchant (Google Shopping/Amazon), seo-programmatic (facets)

Notes

Conditional in seo-audit — fires on e-commerce signals (cart, checkout, Product schema). Never fabricate ratings/reviews in schema — it's a manual action risk.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.