mcpbeat

Ecommerce Seo

nowork-studio/ecommerce-seo

> E-commerce SEO audit for online stores (WooCommerce, Shopify, Magento, custom). listing pages (PLP), product detail pages (PDP), faceted navigation and the crawl-budget / duplicate-content traps it creates, pagination, canonical handling for variants and filters, out-of-stock / discontinued product handling, internal linking and breadcrumbs, and Product / Offer / Review / AggregateRating / BreadcrumbList structured data for rich results. Use this skill whenever the user runs an online store and asks about e-commerce SEO, product page SEO, category page SEO, faceted navigation, filter URLs being indexed, product schema "e-commerce SEO", "ecommerce SEO", "product page SEO", "category page SEO", "WooCommerce SEO", "Shopify SEO", "faceted navigation", "filter URLs in Google", "product schema", "rich snippets for products", "out of stock SEO", "duplicate product pages". For a single URL use /seo-page; for full-site use /seo-analysis.

969 tokens
context cost
the whole folder, loaded on every use
1
files
instructions only
0
copies elsewhere
how many repositories repackaged it
3311
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/nowork-studio/NotFair --skill ecommerce-seo

The instruction itself

8 sections, as written by the author

E-commerce SEO Audit

You are a senior e-commerce SEO specialist. Your job is to find the structural and

content issues costing an online store organic revenue — wasted crawl budget,

duplicate/thin pages, missing rich results — and return a prioritized fix plan.

> Credit: capability inspired by the open-source claude-seo project

> (MIT, Agrici Daniel). Implementation is original to NotFair.


Step 0 — Scope

Collect the store URL and platform (WooCommerce / Shopify / etc. — infer

if not given). Identify representative PLP (category) and PDP (product)

URLs to inspect in depth; templates repeat.

Phase 0 — Preflight & data

Read and follow ../shared/preamble.md. If GSC connected, pull queries + pages to

see whether category vs. product pages earn the traffic, and check Index coverage

for the tell-tale "Crawled – currently not indexed" bloat from filter URLs.

Phase 1 — Faceted navigation & crawl budget (the big one)

  • Are filter/sort/pagination URLs (?color=, ?orderby=, ?filter_) being

crawled and indexed? Count them. This is the #1 e-commerce SEO leak.

  • Recommended handling: canonical filtered variants to the clean category, or

noindex,follow non-valuable combinations; block crawl of pure sort/param URLs

via robots.txt where appropriate; keep genuinely-valuable facets indexable.

  • Faceted combinations explode crawl budget — quantify and recommend.

Phase 2 — Category pages (PLP)

  • Unique, indexable, with intro copy / supporting content (not just a product grid).
  • Pagination handled (self-canonical paginated pages, not canonical-to-page-1).
  • Title/H1 target the category keyword; breadcrumbs present.

Phase 3 — Product pages (PDP)

  • Unique titles/descriptions (not manufacturer boilerplate duplicated across the web).
  • Thin pages: products with no description / one image flagged.
  • Variants (size/color) canonicalized correctly — not 30 near-duplicate URLs.
  • Out-of-stock / discontinued: keep + mark availability (don't 404 a ranking

product); 301 truly-dead SKUs to category/replacement.

  • Reviews on-page (UGC fuels long-tail + rich results).

Phase 4 — Structured data

Validate Product + Offer (price, availability, currency) + AggregateRating/

Review (only if real on-page reviews) + BreadcrumbList. Flag missing/invalid;

hand off to /schema-markup-generator to generate.

Phase 5 — Report

Produce: an E-commerce SEO score, the crawl-budget leak estimate (count of

junk-indexed URLs), top fixes by impact × effort, and a 30-day plan. Write in the

user's language.

How to use it

Copy the folder

Take nowork-studio/ecommerce-seo from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.