suede-programmatic-seo

Designs data-backed programmatic SEO page systems with templates, quality gates, and rollout checks.

123|10|Updated May 24, 2026
One-click install
npx skills add https://github.com/JasonColapietro/suede-creator-skills --skill suede-programmatic-seo-jasoncolapietro
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: suede-programmatic-seo
Source: https://github.com/JasonColapietro/suede-creator-skills/tree/main/skills/suede-programmatic-seo
Command: npx skills add https://github.com/JasonColapietro/suede-creator-skills --skill suede-programmatic-seo-jasoncolapietro

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Scaling search traffic with templated pages often produces thin, duplicate content that Google refuses to index. This Skill turns defensible data and recurring search intent into bounded page systems with explicit index-worthiness, uniqueness, linking, and rollout gates, so scale is earned through sample-page quality rather than page count. ## Core Features & Use Cases - 12 Proven Playbooks: Choose from Templates, Curation, Conversions, Comparisons, Examples, Locations, Personas, Integrations, Glossary, Translations, Directory, and Profiles patterns, with per-playbook implementation detail in the bundled reference. - Quality-Gated Rollout: Run pre-launch checks on a bounded sample (10 pages or 5% of the set), requiring at least 5 page-unique data fields, under 40% template-shared text, unique titles and metas, and no orphan pages before expanding. - Structured Output Contract: Every pass closes with a filled-in block covering playbook choice, data defensibility tier, page-count bounds, literal URL/title/meta/H1 templates, link plan, sample verdict, and a ship/hold gate. - Use Case: A CRM company wants 'CRM for [industry]' pages across 20 industries. The Skill identifies the Personas playbook, defines the data needed per industry, designs the template and hub-and-spoke internal linking, and gates expansion on a passing sample. ## Quick Start Ask the agent to design a programmatic SEO strategy for your target pattern, for example: plan 'integration' pages for the 50 tools our product connects with, including templates, uniqueness requirements, and rollout gates.

Frequently Asked Questions about suede-programmatic-seo

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create programmatic SEO pages at scale?

Start by matching your data assets to one of the 12 playbooks (templates, comparisons, locations, integrations, etc.), then design a template with at least 5 page-unique data fields per page. Validate a bounded sample of 10 pages or 5% of the set against quality gates before generating the full page set.

What are the main programmatic SEO playbook patterns?

The 12 playbooks are Templates, Curation, Conversions, Comparisons, Examples, Locations, Personas, Integrations, Glossary, Translations, Directory, and Profiles. Each maps a repeating search pattern like '[X] vs [Y]' or '[service] in [location]' to a template structure, and playbooks can be layered together.

Why is Google not indexing my programmatic pages?

Low indexation usually means thin content: pages that only swap variables in a shared template. Check that each page has unique data fields, keep template-shared body text under 40%, verify internal linking and XML sitemaps, and stop expanding if the 30-day indexation rate falls below 60%.

Should programmatic pages use subfolders or subdomains?

Use subfolders, not subdomains. Subfolders like yoursite.com/templates/resume/ consolidate domain authority, while subdomains split it. The Skill also recommends segmented XML sitemaps per page type and hub-and-spoke internal linking.

When should I not use programmatic SEO?

Avoid it when you lack defensible data, when pages would only swap keywords without unique value, or when there is no real search demand for the pattern. For auditing an existing site use a technical SEO audit, and for editorial planning use a content strategy workflow instead.