Content Buckets
Organize programmatic SEO content into templated buckets for scalable publishing.
10 min read
Content Buckets
Content buckets are the engine behind programmatic SEO in WISEROWS. Each bucket is a complete template that defines a content type — its data schema, AI generation prompts, SEO configuration, CMS field mappings, and publishing rules — all in one package. Pick a template, fill it with seed data, generate hundreds of pages with AI, and publish to your CMS.
Why Content Buckets?
Programmatic SEO works by creating large numbers of pages targeting long-tail search queries. Instead of manually writing each page, you define a template once and let AI fill in the content for every variation.
Without buckets: You manually create an entity type, figure out which fields you need, write AI prompts from scratch, configure SEO settings, set up CMS mappings, and wire up the publishing pipeline. For every content type. Every time.
With buckets: You pick a template, click create, and everything is pre-configured. The entity type, fields, prompts, SEO rules, CMS mappings, and publishing workflow are ready to go.
Built-in Templates
WISEROWS ships with six battle-tested templates:
Template | URL Pattern | Use Case | Batch Size | SEO Score Threshold |
|---|---|---|---|---|
| Glossary Term | /glossary/{{slug}} | Industry term definitions that capture informational search intent | 10 | 70 |
| Blog Post | /blog/{{slug}} | Long-form articles for content marketing and organic traffic | 5 | 75 |
| Comparison Page | /compare/{{slug}} | "X vs Y" pages targeting high-intent comparison queries | 5 | 70 |
| Guide | /guides/{{slug}} | In-depth tutorials with difficulty levels and estimated read times | 3 | 75 |
| Case Study | /case-studies/{{slug}} | Customer success stories in challenge/solution/results format | 3 | 70 |
| Connection Page | /integrations/{{slug}} | Integration landing pages targeting "tool + integration" queries | 5 | 70 |
Creating a Content Bucket
Choose a template
Go to SEO > Content Buckets and click New Bucket. Browse the template gallery and select the one that matches your content strategy. Each template shows a description, example fields, and the URL pattern it produces.
Review the entity type
The template creates an entity type with pre-configured fields. Review the fields and customize if needed — add fields, rename them, or change field types. The template's AI prompt and field mappings update automatically.
Add your seed data
Populate the bucket with your seed data. For a Glossary bucket, this means entering your terms. For a Comparison bucket, enter your product pairs. You can:
- Manually enter entities one at a time
- Import from a CSV or spreadsheet
- Use the AI chat to bulk-create entity titles
Generate content
Select entities and click Generate. The AI uses the bucket's prompt template to fill in all content fields. Generated items go to the review queue.
Review and publish
Approve generated content, then push it through the publishing pipeline to your CMS.
Anatomy of a Bucket Template
Every bucket template defines five interconnected pieces:
1. Entity Type & Fields
The data schema for your content. Each template pre-configures the right fields for its content type.
Example — Comparison Page fields:
Field | Type | Required | Shown in Table |
|---|---|---|---|
title | text | Yes | Yes |
product_a | text | Yes | Yes |
product_b | text | Yes | Yes |
comparison | richText | Yes | No |
slug | text | Yes | Yes |
meta_title | text | Yes | Yes |
meta_description | text | Yes | No |
verdict | longText | No | No |
winner | select (Product A, Product B, Tie, Depends) | No | Yes |
2. AI Generation Prompt
A pre-written prompt template that the AI uses to generate content. Placeholders like {{field.product_a}} are replaced with actual entity data at generation time.
3. SEO Configuration
Each bucket defines which fields are required for SEO readiness and how URLs are constructed.
requiredFieldsstring[]requiredmetaTitleFieldstringrequiredMaps your entity fields to your CMS fields (e.g., Sanity document fields). Each mapping defines:
Source Field | Target Field | Direction |
|---|---|---|
term | title | push |
definition | body | push |
slug | slug | push |
meta_title | metaTitle | push |
meta_description | metaDescription | push |
Mappings support three directions: push (WISEROWS to CMS), pull (CMS to WISEROWS), and both (bidirectional sync).
5. Publishing Configuration
Controls when and how content gets published.
autoPublishbooleanpublishOnStatusstringrequireSeoScorenumberThe Publishing Pipeline
Every bucket uses the same four-stage pipeline:
Draft
AI generates the initial content. The entity exists in your system but is not visible on your website. Fields may still need human editing.
In Review
A human reviewer checks the content for accuracy, tone, and completeness. They can edit fields directly, regenerate specific fields, or send the entity back to Draft.
Approved
The content passes review and meets the minimum SEO score requirement. It is now eligible for publishing. If a workflow is configured, it triggers automatically at this stage.
Published
Content is pushed to your CMS via the integration connector. The entity's status updates and the publish date is recorded.
requireSeoScore setting is enforced at the publishing step. If an entity has an SEO score below the threshold, the publish action will fail even if the status is "Approved." Make sure all required SEO fields are filled.Programmatic SEO Strategy Examples
Glossary Terms for Topical Authority
Goal: Build topical authority by creating a comprehensive glossary for your industry.
- Create a Glossary Term bucket
- Brainstorm 50-200 industry terms (use the AI chat: "Give me 100 terms related to headless CMS that beginners would search for")
- Bulk-create entities with just the term names
- Run content generation to fill definitions, meta tags, and categories
- Review and approve in batches of 20-30
- Publish to your
/glossary/section - Interlink terms that reference each other
Expected outcome: Each glossary term targets a long-tail informational query. Together, they signal to search engines that your site is authoritative on the topic.
Comparison Pages for High-Intent Traffic
Goal: Capture "X vs Y" search traffic from people evaluating solutions.
- Create a Comparison Page bucket
- List your product against each competitor (e.g., "YourProduct vs Competitor A", "YourProduct vs Competitor B")
- Also create competitor-vs-competitor comparisons where relevant
- Generate content that is balanced and honest — Google penalizes biased comparison pages
- Each page targets the exact "[Product A] vs [Product B]" query
Expected outcome: Comparison pages typically have high conversion intent. Searchers are actively evaluating options and are closer to a purchase decision.
Integration Pages for Partnership SEO
Goal: Create a landing page for every integration your product supports.
- Create a Connection Page bucket
- List all integrations with their names and categories
- Generate feature descriptions and setup guides for each
- Target "[Your Product] + [Integration] integration" queries
Expected outcome: Integration pages capture users searching for specific tool combinations and drive both organic traffic and partner co-marketing opportunities.