category-page-generator
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.
Best use case
category-page-generator is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
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.
Teams using category-page-generator should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/category-pages/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How category-page-generator Compares
| Feature / Agent | category-page-generator | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
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.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Pages: Category Pages 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. ## Initial Assessment **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: 1. **Catalog**: Product count, categories, subcategories 2. **Facets**: Filters (size, color, price, brand, etc.) 3. **URL structure**: Current hierarchy, parameter handling ## Category Structure ### Hierarchy | 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) | ### URL Structure - **Subfolders**: `example.com/shoes/sneakers`, `example.com/shoes/outdoor-shoes` - **Slugs**: Descriptive, keyword-rich; lowercase; no stop words - **Avoid**: Dates, timestamps, `/category/` prefix - **Breadcrumbs**: Show path; help users and crawlers ## Faceted Navigation (Filters) Filters 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 | ## On-Page Content ### Content Requirements - **150-300 words** unique copy; pages with this rank ~2.7x higher than product-only grids - **Placement**: After hero/H1; FAQ block at bottom - **Purpose**: Help users decide; answer curation, materials, recommendations - **Avoid**: Manufacturer copy; crowding product grid ### SEO Elements | 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 | ### Trust & Conversion - **Reviews**: Star ratings in SERPs; 99.9% of users read reviews; see **serp-features** for review rich results - **FAQ**: Answer materials, quality, recommendations; +157% conversion when used - **Guides**: Link to product guides; internal linking for SEO ## Technical - **Consistent layout**: Same template across categories; predictable UX - **Mobile**: Responsive; touch targets >=44x44px - **Redirects**: 301 to category when product pages move; avoid breaking hierarchy ## Output Format - **Structure** (hierarchy, URL paths) - **Facet strategy** (canonical, nofollow, robots) - **Content** (H1, intro copy, FAQ) - **SEO** (metadata, schema) - **Checklist** for audit ## Related Skills - **programmatic-seo**: Programmatic SEO strategy; category pages as template-based scale - **card**: Card layout; product card structure, grid design - **grid**: Product grid layout; responsive columns - **products-page-generator**: Product cards, grid layout - **canonical-tag**: Faceted URL canonicalization - **schema-markup**: ItemList, Product, FAQ schema - **internal-links**: Category linking - **breadcrumb-generator**: Breadcrumb trail for category hierarchy - **url-structure**: URL hierarchy
Related Skills
page-metadata
When the user wants to optimize meta tags other than title, description, Open Graph, or Twitter Cards. Also use when the user mentions "hreflang," "meta robots," "viewport," "charset," "canonical meta," "other meta tags," "meta robots noindex," "meta robots nofollow," "hreflang tags," "viewport meta," or "meta charset." For title tags, use title-tag. For meta descriptions, use meta-description. For Facebook/LinkedIn previews, use open-graph. For X previews, use twitter-cards.
status-page-generator
When the user wants to create, optimize, or structure a status page. Also use when the user mentions "status page," "status.yourdomain.com," "uptime," "service health," "incident page," or "system status." For incident comms, use public-relations.
signup-login-page-generator
When the user wants to create, optimize, or audit signup and login pages. Also use when the user mentions "signup page," "login page," "registration page," "auth page," "sign up form," "create account," "student discount at signup," or "auth subdomain." For indexing/auth URLs, use indexing.
feedback-page-generator
When the user wants to create, optimize, or audit a feedback or roadmap page. Also use when the user mentions "feedback page," "roadmap," "feature requests," "vote on features," "Canny," "UserVoice," or "product feedback." For sitewide page planning, use website-structure.
disclosure-page-generator
When the user wants to create, optimize, or audit an affiliate, sponsor, or paid partnership disclosure page. Also use when the user mentions "disclosure," "affiliate disclosure," "sponsored content," "FTC disclosure," or "paid partnership." For sitewide page planning, use website-structure.
changelog-page-generator
When the user wants to create, optimize, or structure a changelog or release notes page. Also use when the user mentions "changelog," "release notes," "what's new," "updates," "product updates," "version history," or "changelog.yourdomain.com." For sitewide page planning, use website-structure.
use-cases-page-generator
When the user wants to create, optimize, or audit use case pages. Also use when the user mentions "use cases," "use case page," "for [role]," "by persona," "by scenario," "by business goal," "ICP pages," or "audience-specific pages." For sitewide page planning, use website-structure.
startups-page-generator
When the user wants to create, optimize, or audit a startups, education, or special program page. Also use when the user mentions "startups program," "for startups," "education discount," "student plan," "for students," or "special pricing." For education discounts, use education-program.
solutions-page-generator
When the user wants to create, optimize, or audit solutions pages. Also use when the user mentions "solutions," "solutions page," "by industry," "industry solutions," "by company size," "SMB," "enterprise," "by outcome," "business outcomes," or "how we solve X." For sitewide page planning, use website-structure.
showcase-page-generator
When the user wants to create, optimize, or audit a showcase or gallery page for user-generated content. Also use when the user mentions "showcase," "gallery," "user work," "UGC," "creator showcase," "examples," or "made with [product]." For social proof components, use testimonials-generator.
services-page-generator
When the user wants to create, optimize, or audit a services page. Also use when the user mentions "services page," "what we offer," "service offerings," "consulting services," "service page," "offerings page," "service catalog," or "professional services." For sitewide page planning, use website-structure.
products-page-generator
When the user wants to create, optimize, or audit a product listing or category page. Also use when the user mentions "product page," "product listing," "shop," "e-commerce products," "product catalog," "product grid," "product cards," or "product overview." For category SEO, use category-page-generator.