When the user wants to create, optimize, or audit e-commerce category pages or listing pages. Also use when the user mentions "category page," "product category," "faceted navigation," "filter URLs," "e-commerce listing," "category SEO," "category structure," "product filters," or "listing page." For programmatic SEO at scale, use programmatic-seo.
Guides e-commerce category page structure, content, and SEO optimization. Category pages organize products by attributes and drive 3x more organic revenue than product pages by ranking for broad, high-volume keywords.
When invoking: On first use, if helpful, open with 1-2 sentences on what this skill covers and why it matters, then provide the main output. On subsequent use or when the user asks to skip, go directly to the main output.
Check for project context first: If .claude/project-context.md or .cursor/project-context.md exists, read it for product catalog and site structure.
Identify:
| Principle | Practice | |-----------|----------| | Logical grouping | General -> specific (e.g., Furniture -> Bedroom furniture -> Beds) | | User search intent | Match how users search (e.g., "bedroom furniture" vs "furniture") | | Crawl depth | <=4 clicks from homepage; shorter paths improve indexing | | Long-tail categories | Niche categories convert better (36% vs 11.5% for broad) |
example.com/shoes/sneakers, example.com/shoes/outdoor-shoes/category/ prefixFilters create many URL combinations (size + color + price). Manage to avoid duplicate content and crawl waste:
| Strategy | Use | |----------|-----| | Canonical | Point all faceted URLs to base category URL | | robots.txt | Block faceted URLs from indexing if needed | | nofollow | Add to internal links to faceted URLs | | JavaScript | Keep filters client-side; single URL for category |
| Element | Practice | |---------|----------| | H1 | One per page; primary keyword; clear purpose | | Title tag | 50-60 chars; keyword; compelling for CTR | | Meta description | 150-160 chars; value props (free shipping, returns) | | Schema | ItemList, Product; AggregateRating if reviews; FAQ if applicable |
Copy a source-pinned command for your client. You run it yourself.
Destination: .claude/skills/category-pages · pinned to the source commit
git clone https://github.com/kostja94/marketing-skills.git
cd marketing-skills
git checkout 70987bad4ebe9dce1f74858c1c64f3f8810f18e4
mkdir -p ".claude/skills/category-pages"
cp -r "skills/pages/marketing/category-pages" ".claude/skills/category-pages"Review the source before running. This copies files into your project; it is not a one-click install and does not verify runtime safety.
Scanner static-checks@0.1.0 · commit 70987bad4ebe. Static checks cannot prove runtime safety – review the source and the exact diff before installing. How checks work.
No static rules matched. This is not a safety guarantee.