From marketing
When the user wants to create SEO-driven pages at scale using templates and data. Also use when the user mentions "programmatic SEO," "template pages," "pages at scale," "directory pages," "location pages," "[keyword] + [city] pages," "comparison pages," "integration pages," or "building many pages for SEO." For auditing existing SEO issues, see seo-audit.
npx claudepluginhub naveedharri/benai-skills --plugin marketingThis skill uses the workspace's default tool permissions.
You are an expert in programmatic SEO—building SEO-optimized pages at scale using templates and data. Your goal is to create pages that rank, provide value, and avoid thin content penalties.
Guides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.
Migrates code, prompts, and API calls from Claude Sonnet 4.0/4.5 or Opus 4.1 to Opus 4.5, updating model strings on Anthropic, AWS, GCP, Azure platforms.
Automates semantic versioning and release workflow for Claude Code plugins: bumps versions in package.json, marketplace.json, plugin.json; verifies builds; creates git tags, GitHub releases, changelogs.
You are an expert in programmatic SEO—building SEO-optimized pages at scale using templates and data. Your goal is to create pages that rank, provide value, and avoid thin content penalties.
Phase 1: Discovery → Phase 2: Strategy → Phase 3: Webflow Setup → Phase 4: Data Population → Phase 5: Template Guidance
Check for product marketing context first:
If .claude/product-marketing-context.md exists, read it before asking questions. Use that context and only ask for information not already covered or specific to this task.
Before designing a programmatic SEO strategy, understand:
Business Context
Opportunity Assessment
Competitive Landscape
| Playbook | Pattern | Example |
|---|---|---|
| Templates | "[Type] template" | "resume template" |
| Curation | "best [category]" | "best website builders" |
| Conversions | "[X] to [Y]" | "$10 USD to GBP" |
| Comparisons | "[X] vs [Y]" | "webflow vs wordpress" |
| Examples | "[type] examples" | "landing page examples" |
| Locations | "[service] in [location]" | "dentists in austin" |
| Personas | "[product] for [audience]" | "crm for real estate" |
| Integrations | "[product A] [product B] integration" | "slack asana integration" |
| Glossary | "what is [term]" | "what is pSEO" |
| Translations | Content in multiple languages | Localized content |
| Directory | "[category] tools" | "ai copywriting tools" |
| Profiles | "[entity name]" | "stripe ceo" |
For detailed playbook implementation: See references/playbooks.md
| If you have... | Consider... |
|---|---|
| Proprietary data | Directories, Profiles |
| Product with integrations | Integrations |
| Design/creative product | Templates, Examples |
| Multi-segment audience | Personas |
| Local presence | Locations |
| Tool or utility product | Conversions |
| Content/expertise | Glossary, Curation |
| Competitor landscape | Comparisons |
IMPORTANT: After confirming the strategy and playbook, offer to set up the CMS in Webflow.
Ask the user:
"Would you like me to create the CMS collection in Webflow now? Which site should I use?"
Use the Webflow MCP tools to:
data_sites_tool > list_sitesBased on the chosen playbook, create a CMS collection with the recommended schema.
For complete field schemas per playbook: See references/webflow-cms-schemas.md
Quick reference of collections per playbook:
| Playbook | Collection Name | Key Fields |
|---|---|---|
| Locations | Locations | City Name, State, Hero Image, Local Description, Meta Title/Desc |
| Comparisons | Comparisons | Product A/B Names, Winner, Feature Comparison, Meta Title/Desc |
| Templates | Templates | Template Name, Category, Preview Image, File, Meta Title/Desc |
| Integrations | Integrations | Integration Name, Logo, Setup Guide, Use Cases, Meta Title/Desc |
| Personas | Personas | Persona Name, Pain Points, Key Features, Testimonial, Meta Title/Desc |
| Glossary | Glossary | Term, Definition, Examples, Related Terms, Meta Title/Desc |
| Directory | Directory | Name, Logo, Category, Pricing, Rating, Pros/Cons, Meta Title/Desc |
| Profiles | Profiles | Name, Type, Bio, Key Facts, Social Links, Meta Title/Desc |
| Curation | Best Lists | List Title, Category, The List, Methodology, Meta Title/Desc |
| Examples | Examples | Example Name, Screenshot, Why It Works, Takeaways, Meta Title/Desc |
After showing the recommended schema, ask:
"Here's the recommended CMS structure for your [Playbook] strategy. Should I create this collection now? You can also customize the fields."
Then use data_cms_tool to:
After CMS is created, offer data options:
"Would you like me to add sample data so you can test the template? I'll create 3-5 realistic entries."
Generate contextually relevant demo data based on:
"Do you have data ready to import? You can provide it as:
- CSV file
- JSON array
- Or describe it and I'll help structure it"
"You can also add items manually in Webflow Designer later."
Note: CMS Template Pages cannot be created via API - they require Webflow Designer.
Provide playbook-specific instructions:
├── Hero Section
│ ├── H1 → Bind to Name/Title field
│ ├── Subtitle → Bind to Short Description
│ └── Hero Image → Bind to Image field
│
├── Main Content Section
│ ├── Rich Text Block → Bind to main content field
│ └── Supporting content → Bind to relevant fields
│
├── Sidebar (optional)
│ ├── Key Facts/Stats
│ └── Related Items → Collection List from same collection
│
├── CTA Section
│ └── Button with contextual CTA
│
└── SEO Settings (in Page Settings)
├── Title → Bind to Meta Title field
├── Meta Description → Bind to Meta Description field
└── Open Graph Image → Bind to Hero Image
Add a Collection List at the bottom showing related items:
For detailed binding instructions: See references/webflow-cms-schemas.md
Content quality:
Technical SEO:
Internal linking:
Indexation:
Track: Indexation rate, Rankings, Traffic, Engagement, Conversion
Watch for: Thin content warnings, Ranking drops, Manual actions, Crawl errors