Imported from Suresh-cs-q/claude-marketing-skills (skills/programmatic-seo/SKILL.md). Install upstream with npx skills add Suresh-cs-q/claude-marketing-skills --skill programmatic-seo. Copyright stays with the author.

Programmatic SEO

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.

Applied to n8nmake.tech

Read .claude/product-marketing.md first (the shared source of truth). It defines the offer (§1–2), ICP (§3), the honesty rule (§7), known technical gaps (§8), and the current→target sitemap (§9). The notes below make these playbooks concrete for this business.

The business: A done-for-you, no-code AI automation agency building workflows on n8n and Make.com with AI layered in. Buyers are non-technical SMB founders, ops managers, and marketing directors (§3). Conversion goal for every scaled page = book the free consultation (Calendly). Right now the site is a single page with anchor sections (§9) — there is essentially no programmatic surface area yet, so this is a high-leverage opportunity.

Playbooks that fit this business

These map directly to the target sitemap's use-case/persona pages, comparison pages, and blog/glossary (§9). Integrations is likely the largest pattern — the App A × App B matrix across the n8n/Make connector catalog is enormous. Start with the highest-intent, highest- volume combinations, hand-written and deep, then template outward.

Honesty and quality constraints (hard rules)

• No thin or fabricated content (§7). The site already shows unverified numbers (500+, 98%, 10K+) and generic testimonials — do not propagate those onto programmatic pages. Each page must give genuine, page-specific value: real integration steps, a real workflow outline, an honest comparison. If we can't say something true and specific about an App A × App B pair, we don't generate that page yet.
• Comparisons stay fair. "n8n vs Make.com / vs Zapier" pages must present accurate trade-offs (n8n = flexible/self-hostable/complex; Make = fast visual no-code), not strawmen. We profit either way because we build on both.

Machine-readable discovery (fix the §8 gaps)

The audit flagged two missing AI-discovery files our own ai-seo skill recommends:

• /llms.txt — does not exist yet. As programmatic pages launch, list the page-type hubs (integrations, comparisons, use-cases, glossary) so LLMs can find and cite them.
• /pricing.md — does not exist yet. Decision-stage searches ("automation agency pricing") have no landing surface. Pair the scaled pages with a real /pricing page and a machine-readable /pricing.md.

Also note: the current sitemap contains only the homepage (§8.8). Every programmatic page type needs its own sitemap entries (see Indexation Strategy below) or none of this gets crawled.

Initial Assessment

Check for product marketing context first: Read .claude/product-marketing.md 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:

1. Business Context

   • What's the product/service?
   • Who is the target audience?
   • What's the conversion goal for these pages?

2. Opportunity Assessment

   • What search patterns exist?
   • How many potential pages?
   • What's the search volume distribution?

3. Competitive Landscape

   • Who ranks for these terms now?
   • What do their pages look like?
   • Can you realistically compete?

Core Principles

1. Unique Value Per Page

• Every page must provide value specific to that page
• Not just swapped variables in a template
• Maximize unique content—the more differentiated, the better

2. Proprietary Data Wins

Hierarchy of data defensibility:

1. Proprietary (you created it)
2. Product-derived (from your users)
3. User-generated (your community)
4. Licensed (exclusive access)
5. Public (anyone can use—weakest)

3. Clean URL Structure

Always use subfolders, not subdomains:

• Good: yoursite.com/templates/resume/
• Bad: templates.yoursite.com/resume/

4. Genuine Search Intent Match

Pages must actually answer what people are searching for.

5. Quality Over Quantity

Better to have 100 great pages than 10,000 thin ones.

6. Avoid Google Penalties

• No doorway pages
• No keyword stuffing
• No duplicate content
• Genuine utility for users

The 12 Playbooks (Overview)

For detailed playbook implementation: companion reference not included in this skill set.

Choosing Your Playbook

You can layer multiple playbooks (e.g., "Best coworking spaces in San Diego").

n8nmake.tech: the strongest fits are Integrations (huge App A × App B matrix on n8n/Make), Personas (multi-segment ICP), Comparisons (real competitor landscape: n8n, Make, Zapier), Use-cases, and Glossary. Layer them — e.g. "Automate lead routing for agencies with n8n."

Implementation Framework

1. Keyword Pattern Research

Identify the pattern:

• What's the repeating structure?
• What are the variables?
• How many unique combinations exist?

Validate demand:

• Aggregate search volume
• Volume distribution (head vs. long tail)
• Trend direction

2. Data Requirements

Identify data sources:

• What data populates each page?
• Is it first-party, scraped, licensed, public?
• How is it updated?

3. Template Design

Page structure:

• Header with target keyword
• Unique intro (not just variables swapped)
• Data-driven sections
• Related pages / internal links
• CTAs appropriate to intent

Ensuring uniqueness:

• Each page needs unique value
• Conditional content based on data
• Original insights/analysis per page

4. Internal Linking Architecture

Hub and spoke model:

• Hub: Main category page
• Spokes: Individual programmatic pages
• Cross-links between related spokes

Avoid orphan pages:

• Every page reachable from main site
• XML sitemap for all pages
• Breadcrumbs with structured data

5. Indexation Strategy

• Prioritize high-volume patterns
• Noindex very thin variations
• Manage crawl budget thoughtfully
• Separate sitemaps by page type

Quality Checks

Pre-Launch Checklist

Content quality:

• Each page provides unique value
• Answers search intent
• Readable and useful

Technical SEO:

• Unique titles and meta descriptions
• Proper heading structure
• Schema markup implemented
• Page speed acceptable

Internal linking:

• Connected to site architecture
• Related pages linked
• No orphan pages

Indexation:

• In XML sitemap
• Crawlable
• No conflicting noindex

Post-Launch Monitoring

Track: Indexation rate, Rankings, Traffic, Engagement, Conversion

Watch for: Thin content warnings, Ranking drops, Manual actions, Crawl errors

Common Mistakes

• Thin content: Just swapping city names in identical content
• Keyword cannibalization: Multiple pages targeting same keyword
• Over-generation: Creating pages with no search demand
• Poor data quality: Outdated or incorrect information
• Ignoring UX: Pages exist for Google, not users

n8nmake.tech caution: the biggest risk here is generating thousands of near-identical "Connect [A] + [B]" pages with swapped app names and no real workflow detail. That is both a penalty risk and a violation of our honesty rule (§7). Generate only pairs/personas/comparisons we can describe truthfully and usefully.

Output Format

Strategy Document

• Opportunity analysis
• Implementation plan
• Content guidelines

Page Template

• URL structure
• Title/meta templates
• Content outline
• Schema markup

Task-Specific Questions

1. What keyword patterns are you targeting?
2. What data do you have (or can acquire)?
3. How many pages are you planning?
4. What does your site authority look like?
5. Who currently ranks for these terms?
6. What's your technical stack?

Related Skills

• content-strategy: For deciding which pillars and patterns to build
• copywriting: For writing the unique copy on each template
• copy-editing: For QA'ing generated pages before launch
• ai-seo: For /llms.txt, /pricing.md, and LLM citability of scaled pages
• frontend-design: For the look and feel of templated pages
• website-revamp: For sequencing the build and fixing the §8 technical gaps