Category Page Generator Agent Skill
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.
Install
one command, takes just this skill from the repositorynpx skills add https://github.com/kostja94/marketing-skills --skill category-page-generatorThe instruction itself
13 sections, as written by the authorPages: 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:
- Catalog: Product count, categories, subcategories
- Facets: Filters (size, color, price, brand, etc.)
- 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
Other skills for the same job
different authors, same section of the catalogue
A set of resources to help me write all kinds of internal communications, using the formats that my company likes to use. Claude should use this skill whenever asked to write some sort of internal communications (status reports, leadership updates, 3P updates, company newsletters, FAQs, incident reports, project updates, etc.).
Extracts and analyzes competitors' ads from ad libraries (Facebook, LinkedIn, etc.) to understand what messaging, problems, and creative approaches are working. Helps inspire and improve your own ad campaigns.
Identifies high-quality leads for your product or service by analyzing your business, searching for target companies, and providing actionable contact strategies. Perfect for sales, business development, and marketing professionals.
Analyzes your recent Claude Code chat history to identify coding patterns, development gaps, and areas for improvement, curates relevant learning resources from HackerNews, and automatically sends a personalized growth report to your Slack DMs.
Complete App Store Optimization (ASO) toolkit for researching, optimizing, and tracking mobile app performance on Apple App Store and Google Play Store
NGS analysis toolkit. BAM to bigWig conversion, QC (correlation, PCA, fingerprints), heatmaps/profiles (TSS, peaks), for ChIP-seq, RNA-seq, ATAC-seq visualization.
Materials science toolkit. Crystal structures (CIF, POSCAR), phase diagrams, band structure, DOS, Materials Project integration, format conversion, for computational materials science.
Transforms vague UI ideas into polished, Stitch-optimized prompts. Enhances specificity, adds UI/UX keywords, injects design system context, and structures output for better generation results.
How to use it
Take kostja94/category-page-generator from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
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.