[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71AS3CJ9QNG465Y8DZ3PDEN":3,"skill-same:01M71AS3CJ9QNG465Y8DZ3PDEN":80},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":28,"publishedAt":49,"linkOnly":50,"markdownContent":51,"markdownBody":52,"frontMatter":53,"refName":56,"commitSha":57,"skillDirectory":58,"forksCount":59,"repositoryHtmlUrl":60,"repositoryHomepageUrl":61,"ownerHtmlUrl":62,"ownerBlogUrl":63,"ownerDescription":64,"updatedAt":65,"install":66,"resources":79},"01M71AS3CJ9QNG465Y8DZ3PDEN","programmatic-seo",null,"When the user wants to create SEO pages at scale using templates and data—including AI-assisted, grounded copy for per-URL differentiation (vs rigid mail-merge templates). Also use when the user mentions \"programmatic SEO\", \"programmatic SEO pages\", \"template pages\" or \"scale content\". Uses a playbook matrix aligned to skills under skills\u002Fpages. For user-facing template galleries or marketplaces (browse → use), use template-page-generator.","ariadoss\u002Fsuperskills","ariadoss","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F414341?v=4","01M71AC7383PT6JCRZSQJ4AVTM","Danilo Stern-Sapad","01M71AC73Y7NTBTJ9KQYNENRRE",12,"MIT","https:\u002F\u002Fgithub.com\u002Fariadoss\u002Fsuperskills\u002Fblob\u002Fmain\u002Fmarketing-skills\u002Fseo\u002Fprogrammatic-seo\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000019","营销推广","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000035","市场营销","PROFESSION","适用职业",[29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48],"programmatic seo","seo","programmatic","generator","use","pages","page","for","browse","data","matrix","playbook","at","merge","template","mail","create","differentiation","URL","when","2026-11-10 10:12:30",false,"---\nname: programmatic-seo\ndescription: When the user wants to create SEO pages at scale using templates and data—including AI-assisted, grounded copy for per-URL differentiation (vs rigid mail-merge templates). Also use when the user mentions \"programmatic SEO\", \"programmatic SEO pages\", \"template pages\" or \"scale content\". Uses a playbook matrix aligned to skills under skills\u002Fpages. For user-facing template galleries or marketplaces (browse → use), use template-page-generator.\nmetadata:\n  version: 1.4.1\n---\n\n# SEO: Programmatic SEO\n\nGuides programmatic SEO—creating large numbers of SEO-optimized pages automatically using templates and structured data, rather than writing each page manually. **Classic “mail merge” pSEO** (one rigid template + swapped variables) often produced **low differentiation** and thin-feeling URLs. **With AI used responsibly on top of the same data spine**, you can scale **per-URL customization**—intent-aligned copy, section depth, FAQs, tone, localization—while still following **evidence blocks**, **data tiers**, and **QA** (see **Data strength hierarchy** and **AI-assisted generation** below).\n\n**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.\n\n**Project context**: If `.claude\u002Fproject-context.md` or `.cursor\u002Fproject-context.md` exists, read product\u002FICP sections before proposing playbooks or page types.\n\n## Definition\n\n**Programmatic SEO** = Building a single template and populating it with data from a database, API, or spreadsheet to generate hundreds or thousands of unique pages. Each page targets a long-tail keyword (e.g., \"best SEO tool in [city],\" \"[App A] + [App B] integration\").\n\n**Key differences from traditional SEO**: Technical (SEOs + engineers); long-tail focus; data-driven (data quality = success); automation; built for scale.\n\n## Classic limits vs AI-enhanced differentiation\n\n| Era | What breaks | What helps |\n|-----|-------------|------------|\n| **Rigid pSEO** | One template, minimal variance → similar titles\u002Fbodies, weak **E-E-A-T**, “obvious mail merge” | Still needs **unique evidence per URL** and selective indexation |\n| **AI-enhanced pSEO** | Same **structured rows** (facts, SKUs, metrics) drive the page, but models add **per-URL narrative**: intros, FAQ depth, persona angles, localization, internal-link suggestions—**higher differentiation** at scale | **Facts stay in your data layer**; AI shapes **phrasing and structure**, not invented numbers—see **AI-assisted generation** |\n\n**Best-practice stance**: AI is an **accelerator and customizer**, not a substitute for **data defensibility** (Tiers 1–5) or **technical SEO** (URLs, schema, CWV). Used well, it aligns with **quality over quantity**: fewer thin URLs, more **distinct** useful pages.\n\n## Three-Part Framework\n\n| Component | Role |\n|-----------|------|\n| **Templates** | Reusable page structures: layout, headings, internal links, content blocks; conditional logic for empty fields |\n| **Data** | Structured information: locations, products, prices, features—must be accurate, complete, and add genuine value |\n| **Automation** | Systems connecting data to templates; pages generated dynamically or published in bulk |\n| **AI layer (optional)** | On **grounded inputs** (row JSON + rules), generates **varied copy**, FAQ expansions, and section emphasis **per URL**—reduces “same template” fatigue while staying auditable |\n\n## Page Playbook Matrix (`skills\u002Fpages`)\n\nPage types in this library live under `pages\u002F{brand|content|legal|marketing|utility}\u002F`. Use the matrix below to map **search pattern → playbook → which `*-page-generator` skill** to open for structure, copy, and schema—not every folder is a good fit for mass-generated URLs.\n\n| Playbook | Example intent \u002F keyword pattern | Page skill (`name`) | Path (reference) |\n|----------|----------------------------------|---------------------|------------------|\n| **Alternatives \u002F comparisons** | \"[Competitor] alternatives\", \"X vs Y\" | alternatives-page-generator | `pages\u002Fmarketing\u002Falternatives` |\n| **Integrations** | \"[Product A] [Product B] integration\" | integrations-page-generator | `pages\u002Fmarketing\u002Fintegrations` |\n| **Category \u002F catalog** | Faceted listings, product grids | category-page-generator, products-page-generator | `pages\u002Fmarketing\u002Fcategory-pages`, `products` |\n| **Glossary \u002F definitions** | \"what is [term]\", term landings | glossary-page-generator | `pages\u002Fcontent\u002Fglossary` |\n| **FAQ \u002F Q&A** | Question banks, PAA-style pages | faq-page-generator | `pages\u002Fcontent\u002Ffaq` |\n| **How-to \u002F procedures** | Step libraries, \"[how to] [task]\" blocks in templates | howto-section-generator | `components\u002Fcontent\u002Fhowto-section` |\n| **Comparison matrix (blocks)** | Feature\u002Fcriteria grids, \"vs\" cells from data feed | comparison-table-generator | `components\u002Fcontent\u002Fcomparison-table` |\n| **Tools & lead magnets** | \"free [x] tool\u002Fcalculator\" | tools-page-generator | `pages\u002Fcontent\u002Ftools` |\n| **Template gallery** | Browse → detail (your templates) | template-page-generator | `pages\u002Fcontent\u002Ftemplate-page` |\n| **Resource hub** | Guides, hubs, download centers | resources-page-generator | `pages\u002Fcontent\u002Fresources` |\n| **Use cases \u002F solutions** | \"for [role]\", \"by industry\" | use-cases-page-generator, solutions-page-generator | `pages\u002Fmarketing\u002Fuse-cases`, `solutions` |\n| **Migration \u002F switching** | \"migrate from [X]\" | migration-page-generator | `pages\u002Fmarketing\u002Fmigration` |\n| **Campaign landing** | Paid\u002Fsegment LPs | landing-page-generator | `pages\u002Fmarketing\u002Flanding-page` |\n| **Blog \u002F article** | Long-tail articles at scale | blog-page-generator, article-page-generator | `pages\u002Fcontent\u002Fblog`, `article` |\n| **Docs \u002F features \u002F API** | Scalable doc sections, feature landings, `\u002Fapi` marketing | docs-page-generator, features-page-generator, api-page-generator | `pages\u002Fcontent\u002Fdocs`, `features`, `api` |\n| **Social proof** | Logos, case studies, galleries | press-coverage-page-generator, customer-stories-page-generator, showcase-page-generator | `pages\u002Fmarketing\u002Fpress-coverage`, `customer-stories`, `showcase` |\n| **Programs & offers** | Startups\u002Feducation, contests, downloads, affiliate, media kit | startups-page-generator, contest-page-generator, download-page-generator, affiliate-page-generator, media-kit-page-generator | `pages\u002Fmarketing\u002F*` |\n| **Pricing \u002F services** | Plans, offerings (use sparingly for pSEO) | pricing-page-generator, services-page-generator | `pages\u002Fmarketing\u002Fpricing`, `services` |\n\n**Usually not mass programmatic** (single primary URL or compliance-heavy): `pages\u002Fbrand\u002F*` (home, about, contact), `pages\u002Flegal\u002F*`, most `pages\u002Futility\u002F*` (404, status, signup-login, etc.)—treat as one-off or policy-driven, not template×data scale.\n\n## Choosing a Playbook\n\n| If you have… | Lean toward… | Open first… |\n|----------------|--------------|-------------|\n| Competitor list + positioning | Alternatives \u002F comparisons | alternatives-page-generator |\n| Integration directory (your + partners') | Integrations matrix | integrations-page-generator |\n| Product catalog or SKUs | Category \u002F product grids | category-page-generator, products-page-generator |\n| Term \u002F definition database | Glossary | glossary-page-generator |\n| Support tickets \u002F PAA mined questions | FAQ scale | faq-page-generator |\n| How-to step banks \u002F procedure templates | HowTo sections in scaled pages | howto-section-generator |\n| Competitor\u002Ffeature matrix from data | Comparison table blocks in scaled pages | comparison-table-generator (+ alternatives-page-generator for URL intent) |\n| Lead magnets, calculators | Tools hub + per-tool | tools-page-generator |\n| **Your own templates** (exports, gallery items) | Template marketplace | template-page-generator |\n| ICP × industry matrix | Use cases \u002F solutions | use-cases-page-generator, solutions-page-generator |\n| Import paths from competitors | Migration | migration-page-generator |\n| Campaign or geo LPs | Landing pages | landing-page-generator |\n| Long-form SEO articles | Blog index + single post | blog-page-generator, article-page-generator |\n\n## Template Structure (Recommended)\n\n| Section | Purpose |\n|---------|---------|\n| **Intro** | Introduction; matches user intent |\n| **Evidence block** | Data-driven content unique to each page (tables, lists, verified stats); differentiates from thin content |\n| **Decision** | Comparison, recommendation, or next steps |\n| **FAQ** | Frequently asked questions |\n| **CTA** | Call-to-action |\n\n**Evidence block** = Real, structured data per page (business listings, pricing, reviews, verified stats). Ensures each page delivers genuine value, not recycled boilerplate with swapped variables.\n\n## Data strength hierarchy (defensibility)\n\n**Strongest programmatic pages are fueled by what only your product (or your customers inside your product) can produce**—especially **templates, exports, and generated artifacts**. Third-party or scraped lists alone are the weakest foundation.\n\n| Tier | Source | Examples | Relative risk |\n|------|--------|----------|----------------|\n| **1 — Product-generated** | Assets created or rendered by your product: page\u002Flayout **templates**, email\u002FNotion\u002Fcode templates, export packs, generated previews, branded snippets, “built with [Product]” examples | Template gallery rows tied to real `.json` \u002F CMS fields; screenshots of exports; unique preview URLs | **Lowest** when each URL shows distinct generated output |\n| **2 — Product-derived** | Telemetry and in-product data you own: aggregates, cohorts, benchmarks, feature adoption | “Teams in [industry] median time-to-value” from your warehouse (aggregated) | Low if aggregated \u002F anonymized and policy-compliant |\n| **3 — UGC \u002F customer** | Reviews, submissions, showcase items, moderated community content | Showcase grid; verified quotes | Medium—needs moderation + consent |\n| **4 — Licensed \u002F partner** | Exclusive feeds, co-marketing datasets | Partner pricing tiers; licensed industry stats | Medium—contract and citation discipline |\n| **5 — Public \u002F scraped** | Open web, directories, generic enrichment | Name\u002Faddress fills; commodity facts | **Highest**—needs editorial layer, fact-checking, and a real **Evidence block** |\n\n**Why Tier 1 (templates & generated content) wins**: Pages built from **your** template system carry proprietary structure, variables, and brand-safe blocks—harder for competitors to copy verbatim and easier to prove uniqueness (embeds, downloads, IDs). Pair with **template-page-generator** when the UX is “browse gallery → use template.”\n\n### Tier 2 — Product-derived (practical)\n\n| What it is | What to watch |\n|------------|----------------|\n| Metrics from **your** backend, data warehouse, or support\u002FCRM exports: activation rates by segment, integration popularity, error budgets, time-to-value—not generic “industry reports.” | **Privacy & ToS**: Minimum cell sizes; no individual identification; document what was aggregated and over what window. |\n| Good fit when you can show **“only we could know this because it runs in our product.”** | **Stale data** hurts trust: pipeline jobs, “as of [date]” labels, automated invalidation. |\n\n**AI here**: Use models to **turn structured aggregates into prose** (intro paragraphs, “what this means for [segment]”)—**input must be verified numbers\u002Ftables from your pipeline**, not free-form invention. Keep a **machine-readable table or JSON** on-page or in appendix so claims stay auditable.\n\n### Tier 3 — UGC \u002F customer (practical)\n\n| What it is | What to watch |\n|------------|----------------|\n| Quotes, reviews, showcase submissions, community templates—**per-user artifacts** with consent. | **Moderation**: spam, PII, competitor attacks; **consent** for name\u002Flogo use; **schema** (Review, CreativeWork) only when accurate. |\n| Strong when combined with **Tier 1** (e.g. “customer-built template” gallery). | **Volume without quality** → thin pages; cap or score submissions. |\n\n**AI here**: Summarize long reviews into bullets; **generate draft alt text** for images; **cluster** submissions into topic pages—always **human approve** before publish. Do not fabricate testimonials.\n\n### Tier 4 — Licensed \u002F partner (practical)\n\n| What it is | What to watch |\n|------------|----------------|\n| Partner price lists, co-marketed reports, API-fed **allowed** fields (logos, SKUs). | **Contract scope**: Which fields can appear on which URLs; attribution line; **DMCA \u002F trademark** on logos. |\n| Often **one feed → many URLs**; uniqueness must come from **your framing**, comparison logic, or calculator—not the raw feed alone. | **Refresh cadence** tied to partner SLAs. |\n\n**AI here**: Draft **comparison copy** and **FAQs** from a **fixed attribute table** (license + partner rules); never invent SKUs or prices—**pull from feed**, let AI phrase and shorten.\n\n### Tier 5 — Public \u002F scraped (practical)\n\n| What it is | What to watch |\n|------------|----------------|\n| Open data, directories, Wikipedia-style facts, **enrichment** of public entities. | **Highest** duplicate\u002Fthin risk: everyone has the same facts; **you must add** synthesis, editorial angle, or a **unique tool** (calculator, filter) on top. |\n| **Entity SEO** and **citations** matter: link to authoritative sources; date-stamp volatile facts. | Plan for **pruning** or **noindex** on low-traffic thin URLs. |\n\n**AI here**: Use models to **structure** messy public text into tables, **outline** sections, **suggest** internal links—then **fact-check** names, numbers, and dates. **Do not** use AI to invent statistics or citations; treat output as **draft** until verified.\n\n### AI-assisted generation (cross-tier)\n\n**Why AI fits modern pSEO**: Early programmatic SEO earned a bad reputation because **templates were frozen** and **copy was interchangeable**—little real differentiation per query. **LLMs**, when **grounded** on each row’s facts and your brand rules, make it practical to **customize** headlines, intros, FAQs, and “why this page matters” **per URL** without hand-writing thousands of pages. That moves execution closer to **best practices** (intent match, helpful content, unique value) **at scale**, provided you **do not** let the model invent data.\n\n| Principle | Why |\n|-----------|-----|\n| **Ground AI in structured inputs** | Pass JSON\u002FCSV rows (tier, source URL, metrics) into prompts; **forbid** hallucinated numbers in system prompts. |\n| **Separate “facts” from “phrasing”** | Data layer = source of truth; AI = tone, shortening, localization, FAQs, **per-segment emphasis**—never the other way around. |\n| **Vary structure, not only adjectives** | Ask for different **section order**, FAQ count, or “beginner vs power user” angles **by intent flags** in the row—reduces template sameness. |\n| **Human or automated QA** | Spot-check high-traffic URLs; block publish if required fields empty or citation missing. |\n| **Disclose when useful** | e.g. “Intro generated with AI; figures from [internal report, Q3 2025].” Builds trust and matches policy trends. |\n\n**When AI generation is a strong lever**: Tiers **2–5**—where raw material is already tabular or repetitive but **needs readable, differentiated copy at scale**. Tier **1** still benefits from AI (drafts from export JSON), but the **differentiator remains** the product artifact itself.\n\n### Operational requirements (all tiers)\n\n| Requirement | Practice |\n|-------------|----------|\n| **Provenance** | Log data sources; track origin per field |\n| **Freshness rules** | e.g., ratings every 90 days, prices every 30 days, template version bumps when layouts change |\n| **Prefer 1–2 over 5** | Fill evidence with product-generated or product-derived data before reaching for public scraping |\n| **AI governance** | Structured inputs only; no unverified numbers; moderation on UGC; optional disclosure |\n| **Clean & merge** | Deduplicate keys; drop rows that produce duplicate intents |\n\n## Ideal Use Cases\n\nFor **which page-generator skill to use**, see **Page Playbook Matrix** above. Generic patterns:\n\n| Use case | Example |\n|----------|---------|\n| **Location-specific pages** | \"Plumber in [city],\" \"Best restaurants in [neighborhood]\" with real local data |\n| **Product comparison** | \"[Product A] vs [Product B]\" with structured specs |\n| **Alternatives pages** | \"[Competitor] alternatives\" at scale; 50+ competitors; see **alternatives-page-generator** |\n| **Software integration** | \"[App A] + [App B]\" integration pages (e.g., Zapier 50K+ pages) |\n| **Free tools** | \"[X] checker,\" \"[Y] calculator,\" \"[Z] generator\" — standalone tool pages; toolkit hub; same ICP as main product; lead gen |\n| **Travel \u002F destination** | City + attraction combinations with reviews, photos |\n| **E-commerce** | Category pages, product variations (size, color, material) |\n| **FAQ \u002F Q&A** | Pages powered by user question databases |\n| **Salary \u002F pricing** | Comparison pages with structured data |\n\n**Avoid when**: Site structure is weak; page differences are superficial (city\u002Fname swaps only); content requires original expertise or UGC participation.\n\n## Real-World Examples\n\n*Examples are illustrative; no endorsement implied.*\n\n| Company | Scale | Pattern |\n|---------|-------|---------|\n| **Zapier** | 50,000+ pages | \"[App A] + [App B]\" integration |\n| **Airbnb** | — | Location search; destination × property |\n| **Review platforms** | — | User reviews + automated comparison pages |\n| **Travel sites** | — | Destination, hotel, flight, activity pages |\n| **NomadList** | 2,000+ city pages | Cost-of-living, internet speed (dynamic data) |\n| **Semrush, Ahrefs** | 50+ free tools | SEO checker, keyword tool, backlink checker; toolkit hub + per-tool pages |\n\n## Content Requirements\n\n| Requirement | Purpose |\n|-------------|---------|\n| **300+ words per page** | Avoid thin content penalties |\n| **Unique, verifiable data** | Each page must add meaningful page-specific content beyond simple data swaps |\n| **Evidence block** | Tables, lists, examples with real numbers\u002Fattributes on every page |\n| **Semantic HTML** | Proper structure; conditional logic to avoid empty or repetitive sections |\n| **Internal linking** | Link related programmatic pages; compounds traffic and indexation |\n\n## Technical Considerations\n\n| Topic | Practice |\n|-------|----------|\n| **Subfolder vs subdomain** | Prefer **subfolders** (`yoursite.com\u002Fintegration\u002Fslack-notion\u002F`) over **subdomains** (`integrations.yoursite.com\u002F...`) so authority consolidates on the primary domain; see **url-structure**, **domain-architecture** if restructuring |\n| **Selective indexation** | Don't index all pages; use noindex rules for low-value pages |\n| **Sitemap segmentation** | By country, language, division; manage crawl budget |\n| **URL structure** | Descriptive URLs; clean hierarchy; see **url-structure** |\n| **Schema** | JSON-LD: Product, Place, FAQ, ItemList per page type |\n| **Performance** | Caching, static generation; Core Web Vitals |\n\n## Critical Pitfalls\n\n| Pitfall | Consequence |\n|---------|-------------|\n| **Thin content** | Minimal info beyond keyword; generic copy; placeholder sections → penalties |\n| **Duplicate pages** | Same content with only data swaps → thin content penalties |\n| **Index bloat** | Generating pages that should never be indexable → crawl budget waste |\n| **Large dumps** | Publishing many similar pages at once → spam signals |\n| **Filter URLs** | Using filters instead of unique URLs\u002Ftitles → cannibalization |\n\nPages with only a title, one paragraph, and swapped city names will not rank and may incur Google penalties.\n\n## Step-by-Step Workflow\n\n1. **Research** — Niche, intent; include low-volume keywords; SEO tools, question databases\n2. **Collect data** — Provenance log, freshness rules; first-party\u002Flicensed; define template fields\n3. **Choose stack** — Next.js + DB, Webflow CMS, WordPress, headless; API + template reuse\n4. **Design template** — Intro, Evidence, Decision, FAQ, CTA; schema; conditional logic\n5. **Build database** — Map fields to template slots; hide empties\n6. **Generate pages** — Descriptive URLs; optimize performance\n7. **Deploy & monitor** — Sitemaps; indexation, rankings, CTR, bounce, conversions\n8. **Optimize** — Prune weak pages; refresh data; A\u002FB test layout, CTA\n\n## Best Practices\n\n| Practice | Purpose |\n|----------|---------|\n| **Quality over scale** | Each page must provide genuinely unique, verifiable value |\n| **Differentiation over clone** | Prefer **AI-grounded** copy variance + evidence blocks over one static paragraph with `{city}` swaps |\n| **Launch in batches** | Small batches you can measure; avoid large dumps |\n| **Strong IA** | Internal links to related guides\u002Fcategories |\n| **Visual elements** | Tables, maps, comparisons where relevant |\n| **Match intent** | Avoid generic template text; precise user intent |\n\n## Timeline & Expectations\n\n- **Typical time to ranking**: ~6 months\n- **Reported gains**: 40%+ traffic increases from well-designed topic clusters\n- **AI search**: Structured, data-rich content performs better in AI Overviews and citation layers\n\n## Output Format\n\n- **Template design** (Intro, Evidence, Decision, FAQ, CTA; required data fields)\n- **Data requirements** (provenance, freshness, accuracy)\n- **Internal linking** (hub-and-spoke, related pages)\n- **Indexation strategy** (selective indexation, sitemap segmentation)\n- **Checklist** for audit\n\n## Related Skills\n\n- **template-page-generator**: Template structure; aggregation (gallery) + detail pages; **Tier 1 product-generated** template URLs\n- **landing-page-generator**: Conversion-focused programmatic pages; LP structure for campaign CTA\n- **tools-page-generator**: Free tools pages; toolkit hub; programmatic tool pages; lead gen\n- **alternatives-page-generator**: Alternatives\u002Fcomparison pages at scale; competitor brand traffic\n- **category-page-generator**, **products-page-generator**: Category \u002F catalog grids\n- **glossary-page-generator**, **faq-page-generator**, **howto-section-generator**, **comparison-table-generator**, **resources-page-generator**: Definitions, Q&A banks, HowTo step blocks, comparison matrices, content hubs\n- **use-cases-page-generator**, **solutions-page-generator**, **migration-page-generator**: ICP\u002Findustry matrix, migration SEO\n- **integrations-page-generator**: Integration pair pages at scale\n- **blog-page-generator**, **article-page-generator**, **docs-page-generator**, **features-page-generator**, **api-page-generator**: Long-form and product surface scale\n- **press-coverage-page-generator**, **customer-stories-page-generator**, **showcase-page-generator**: Proof at scale\n- **startups-page-generator**, **contest-page-generator**, **download-page-generator**, **affiliate-page-generator**, **media-kit-page-generator**, **pricing-page-generator**, **services-page-generator**: Programs and offers (use selectively for pSEO)\n- **content-strategy**: Content clusters, pillar pages; programmatic pages as cluster nodes\n- **website-structure**: Site IA before scaling URL sets\n- **url-structure**, **domain-architecture**: Paths, subfolder strategy\n- **schema-markup**: Structured data (Product, Place, FAQ, ItemList)\n- **internal-links**: Linking programmatic pages\n- **xml-sitemap**: Sitemap segmentation for large programmatic sites\n- **canonical-tag**: Duplicate\u002Fthin content handling\n- **seo-strategy**, **seo-audit**: Roadmap and post-launch audits\n","# SEO: Programmatic SEO\n\nGuides programmatic SEO—creating large numbers of SEO-optimized pages automatically using templates and structured data, rather than writing each page manually. **Classic “mail merge” pSEO** (one rigid template + swapped variables) often produced **low differentiation** and thin-feeling URLs. **With AI used responsibly on top of the same data spine**, you can scale **per-URL customization**—intent-aligned copy, section depth, FAQs, tone, localization—while still following **evidence blocks**, **data tiers**, and **QA** (see **Data strength hierarchy** and **AI-assisted generation** below).\n\n**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.\n\n**Project context**: If `.claude\u002Fproject-context.md` or `.cursor\u002Fproject-context.md` exists, read product\u002FICP sections before proposing playbooks or page types.\n\n## Definition\n\n**Programmatic SEO** = Building a single template and populating it with data from a database, API, or spreadsheet to generate hundreds or thousands of unique pages. Each page targets a long-tail keyword (e.g., \"best SEO tool in [city],\" \"[App A] + [App B] integration\").\n\n**Key differences from traditional SEO**: Technical (SEOs + engineers); long-tail focus; data-driven (data quality = success); automation; built for scale.\n\n## Classic limits vs AI-enhanced differentiation\n\n| Era | What breaks | What helps |\n|-----|-------------|------------|\n| **Rigid pSEO** | One template, minimal variance → similar titles\u002Fbodies, weak **E-E-A-T**, “obvious mail merge” | Still needs **unique evidence per URL** and selective indexation |\n| **AI-enhanced pSEO** | Same **structured rows** (facts, SKUs, metrics) drive the page, but models add **per-URL narrative**: intros, FAQ depth, persona angles, localization, internal-link suggestions—**higher differentiation** at scale | **Facts stay in your data layer**; AI shapes **phrasing and structure**, not invented numbers—see **AI-assisted generation** |\n\n**Best-practice stance**: AI is an **accelerator and customizer**, not a substitute for **data defensibility** (Tiers 1–5) or **technical SEO** (URLs, schema, CWV). Used well, it aligns with **quality over quantity**: fewer thin URLs, more **distinct** useful pages.\n\n## Three-Part Framework\n\n| Component | Role |\n|-----------|------|\n| **Templates** | Reusable page structures: layout, headings, internal links, content blocks; conditional logic for empty fields |\n| **Data** | Structured information: locations, products, prices, features—must be accurate, complete, and add genuine value |\n| **Automation** | Systems connecting data to templates; pages generated dynamically or published in bulk |\n| **AI layer (optional)** | On **grounded inputs** (row JSON + rules), generates **varied copy**, FAQ expansions, and section emphasis **per URL**—reduces “same template” fatigue while staying auditable |\n\n## Page Playbook Matrix (`skills\u002Fpages`)\n\nPage types in this library live under `pages\u002F{brand|content|legal|marketing|utility}\u002F`. Use the matrix below to map **search pattern → playbook → which `*-page-generator` skill** to open for structure, copy, and schema—not every folder is a good fit for mass-generated URLs.\n\n| Playbook | Example intent \u002F keyword pattern | Page skill (`name`) | Path (reference) |\n|----------|----------------------------------|---------------------|------------------|\n| **Alternatives \u002F comparisons** | \"[Competitor] alternatives\", \"X vs Y\" | alternatives-page-generator | `pages\u002Fmarketing\u002Falternatives` |\n| **Integrations** | \"[Product A] [Product B] integration\" | integrations-page-generator | `pages\u002Fmarketing\u002Fintegrations` |\n| **Category \u002F catalog** | Faceted listings, product grids | category-page-generator, products-page-generator | `pages\u002Fmarketing\u002Fcategory-pages`, `products` |\n| **Glossary \u002F definitions** | \"what is [term]\", term landings | glossary-page-generator | `pages\u002Fcontent\u002Fglossary` |\n| **FAQ \u002F Q&A** | Question banks, PAA-style pages | faq-page-generator | `pages\u002Fcontent\u002Ffaq` |\n| **How-to \u002F procedures** | Step libraries, \"[how to] [task]\" blocks in templates | howto-section-generator | `components\u002Fcontent\u002Fhowto-section` |\n| **Comparison matrix (blocks)** | Feature\u002Fcriteria grids, \"vs\" cells from data feed | comparison-table-generator | `components\u002Fcontent\u002Fcomparison-table` |\n| **Tools & lead magnets** | \"free [x] tool\u002Fcalculator\" | tools-page-generator | `pages\u002Fcontent\u002Ftools` |\n| **Template gallery** | Browse → detail (your templates) | template-page-generator | `pages\u002Fcontent\u002Ftemplate-page` |\n| **Resource hub** | Guides, hubs, download centers | resources-page-generator | `pages\u002Fcontent\u002Fresources` |\n| **Use cases \u002F solutions** | \"for [role]\", \"by industry\" | use-cases-page-generator, solutions-page-generator | `pages\u002Fmarketing\u002Fuse-cases`, `solutions` |\n| **Migration \u002F switching** | \"migrate from [X]\" | migration-page-generator | `pages\u002Fmarketing\u002Fmigration` |\n| **Campaign landing** | Paid\u002Fsegment LPs | landing-page-generator | `pages\u002Fmarketing\u002Flanding-page` |\n| **Blog \u002F article** | Long-tail articles at scale | blog-page-generator, article-page-generator | `pages\u002Fcontent\u002Fblog`, `article` |\n| **Docs \u002F features \u002F API** | Scalable doc sections, feature landings, `\u002Fapi` marketing | docs-page-generator, features-page-generator, api-page-generator | `pages\u002Fcontent\u002Fdocs`, `features`, `api` |\n| **Social proof** | Logos, case studies, galleries | press-coverage-page-generator, customer-stories-page-generator, showcase-page-generator | `pages\u002Fmarketing\u002Fpress-coverage`, `customer-stories`, `showcase` |\n| **Programs & offers** | Startups\u002Feducation, contests, downloads, affiliate, media kit | startups-page-generator, contest-page-generator, download-page-generator, affiliate-page-generator, media-kit-page-generator | `pages\u002Fmarketing\u002F*` |\n| **Pricing \u002F services** | Plans, offerings (use sparingly for pSEO) | pricing-page-generator, services-page-generator | `pages\u002Fmarketing\u002Fpricing`, `services` |\n\n**Usually not mass programmatic** (single primary URL or compliance-heavy): `pages\u002Fbrand\u002F*` (home, about, contact), `pages\u002Flegal\u002F*`, most `pages\u002Futility\u002F*` (404, status, signup-login, etc.)—treat as one-off or policy-driven, not template×data scale.\n\n## Choosing a Playbook\n\n| If you have… | Lean toward… | Open first… |\n|----------------|--------------|-------------|\n| Competitor list + positioning | Alternatives \u002F comparisons | alternatives-page-generator |\n| Integration directory (your + partners') | Integrations matrix | integrations-page-generator |\n| Product catalog or SKUs | Category \u002F product grids | category-page-generator, products-page-generator |\n| Term \u002F definition database | Glossary | glossary-page-generator |\n| Support tickets \u002F PAA mined questions | FAQ scale | faq-page-generator |\n| How-to step banks \u002F procedure templates | HowTo sections in scaled pages | howto-section-generator |\n| Competitor\u002Ffeature matrix from data | Comparison table blocks in scaled pages | comparison-table-generator (+ alternatives-page-generator for URL intent) |\n| Lead magnets, calculators | Tools hub + per-tool | tools-page-generator |\n| **Your own templates** (exports, gallery items) | Template marketplace | template-page-generator |\n| ICP × industry matrix | Use cases \u002F solutions | use-cases-page-generator, solutions-page-generator |\n| Import paths from competitors | Migration | migration-page-generator |\n| Campaign or geo LPs | Landing pages | landing-page-generator |\n| Long-form SEO articles | Blog index + single post | blog-page-generator, article-page-generator |\n\n## Template Structure (Recommended)\n\n| Section | Purpose |\n|---------|---------|\n| **Intro** | Introduction; matches user intent |\n| **Evidence block** | Data-driven content unique to each page (tables, lists, verified stats); differentiates from thin content |\n| **Decision** | Comparison, recommendation, or next steps |\n| **FAQ** | Frequently asked questions |\n| **CTA** | Call-to-action |\n\n**Evidence block** = Real, structured data per page (business listings, pricing, reviews, verified stats). Ensures each page delivers genuine value, not recycled boilerplate with swapped variables.\n\n## Data strength hierarchy (defensibility)\n\n**Strongest programmatic pages are fueled by what only your product (or your customers inside your product) can produce**—especially **templates, exports, and generated artifacts**. Third-party or scraped lists alone are the weakest foundation.\n\n| Tier | Source | Examples | Relative risk |\n|------|--------|----------|----------------|\n| **1 — Product-generated** | Assets created or rendered by your product: page\u002Flayout **templates**, email\u002FNotion\u002Fcode templates, export packs, generated previews, branded snippets, “built with [Product]” examples | Template gallery rows tied to real `.json` \u002F CMS fields; screenshots of exports; unique preview URLs | **Lowest** when each URL shows distinct generated output |\n| **2 — Product-derived** | Telemetry and in-product data you own: aggregates, cohorts, benchmarks, feature adoption | “Teams in [industry] median time-to-value” from your warehouse (aggregated) | Low if aggregated \u002F anonymized and policy-compliant |\n| **3 — UGC \u002F customer** | Reviews, submissions, showcase items, moderated community content | Showcase grid; verified quotes | Medium—needs moderation + consent |\n| **4 — Licensed \u002F partner** | Exclusive feeds, co-marketing datasets | Partner pricing tiers; licensed industry stats | Medium—contract and citation discipline |\n| **5 — Public \u002F scraped** | Open web, directories, generic enrichment | Name\u002Faddress fills; commodity facts | **Highest**—needs editorial layer, fact-checking, and a real **Evidence block** |\n\n**Why Tier 1 (templates & generated content) wins**: Pages built from **your** template system carry proprietary structure, variables, and brand-safe blocks—harder for competitors to copy verbatim and easier to prove uniqueness (embeds, downloads, IDs). Pair with **template-page-generator** when the UX is “browse gallery → use template.”\n\n### Tier 2 — Product-derived (practical)\n\n| What it is | What to watch |\n|------------|----------------|\n| Metrics from **your** backend, data warehouse, or support\u002FCRM exports: activation rates by segment, integration popularity, error budgets, time-to-value—not generic “industry reports.” | **Privacy & ToS**: Minimum cell sizes; no individual identification; document what was aggregated and over what window. |\n| Good fit when you can show **“only we could know this because it runs in our product.”** | **Stale data** hurts trust: pipeline jobs, “as of [date]” labels, automated invalidation. |\n\n**AI here**: Use models to **turn structured aggregates into prose** (intro paragraphs, “what this means for [segment]”)—**input must be verified numbers\u002Ftables from your pipeline**, not free-form invention. Keep a **machine-readable table or JSON** on-page or in appendix so claims stay auditable.\n\n### Tier 3 — UGC \u002F customer (practical)\n\n| What it is | What to watch |\n|------------|----------------|\n| Quotes, reviews, showcase submissions, community templates—**per-user artifacts** with consent. | **Moderation**: spam, PII, competitor attacks; **consent** for name\u002Flogo use; **schema** (Review, CreativeWork) only when accurate. |\n| Strong when combined with **Tier 1** (e.g. “customer-built template” gallery). | **Volume without quality** → thin pages; cap or score submissions. |\n\n**AI here**: Summarize long reviews into bullets; **generate draft alt text** for images; **cluster** submissions into topic pages—always **human approve** before publish. Do not fabricate testimonials.\n\n### Tier 4 — Licensed \u002F partner (practical)\n\n| What it is | What to watch |\n|------------|----------------|\n| Partner price lists, co-marketed reports, API-fed **allowed** fields (logos, SKUs). | **Contract scope**: Which fields can appear on which URLs; attribution line; **DMCA \u002F trademark** on logos. |\n| Often **one feed → many URLs**; uniqueness must come from **your framing**, comparison logic, or calculator—not the raw feed alone. | **Refresh cadence** tied to partner SLAs. |\n\n**AI here**: Draft **comparison copy** and **FAQs** from a **fixed attribute table** (license + partner rules); never invent SKUs or prices—**pull from feed**, let AI phrase and shorten.\n\n### Tier 5 — Public \u002F scraped (practical)\n\n| What it is | What to watch |\n|------------|----------------|\n| Open data, directories, Wikipedia-style facts, **enrichment** of public entities. | **Highest** duplicate\u002Fthin risk: everyone has the same facts; **you must add** synthesis, editorial angle, or a **unique tool** (calculator, filter) on top. |\n| **Entity SEO** and **citations** matter: link to authoritative sources; date-stamp volatile facts. | Plan for **pruning** or **noindex** on low-traffic thin URLs. |\n\n**AI here**: Use models to **structure** messy public text into tables, **outline** sections, **suggest** internal links—then **fact-check** names, numbers, and dates. **Do not** use AI to invent statistics or citations; treat output as **draft** until verified.\n\n### AI-assisted generation (cross-tier)\n\n**Why AI fits modern pSEO**: Early programmatic SEO earned a bad reputation because **templates were frozen** and **copy was interchangeable**—little real differentiation per query. **LLMs**, when **grounded** on each row’s facts and your brand rules, make it practical to **customize** headlines, intros, FAQs, and “why this page matters” **per URL** without hand-writing thousands of pages. That moves execution closer to **best practices** (intent match, helpful content, unique value) **at scale**, provided you **do not** let the model invent data.\n\n| Principle | Why |\n|-----------|-----|\n| **Ground AI in structured inputs** | Pass JSON\u002FCSV rows (tier, source URL, metrics) into prompts; **forbid** hallucinated numbers in system prompts. |\n| **Separate “facts” from “phrasing”** | Data layer = source of truth; AI = tone, shortening, localization, FAQs, **per-segment emphasis**—never the other way around. |\n| **Vary structure, not only adjectives** | Ask for different **section order**, FAQ count, or “beginner vs power user” angles **by intent flags** in the row—reduces template sameness. |\n| **Human or automated QA** | Spot-check high-traffic URLs; block publish if required fields empty or citation missing. |\n| **Disclose when useful** | e.g. “Intro generated with AI; figures from [internal report, Q3 2025].” Builds trust and matches policy trends. |\n\n**When AI generation is a strong lever**: Tiers **2–5**—where raw material is already tabular or repetitive but **needs readable, differentiated copy at scale**. Tier **1** still benefits from AI (drafts from export JSON), but the **differentiator remains** the product artifact itself.\n\n### Operational requirements (all tiers)\n\n| Requirement | Practice |\n|-------------|----------|\n| **Provenance** | Log data sources; track origin per field |\n| **Freshness rules** | e.g., ratings every 90 days, prices every 30 days, template version bumps when layouts change |\n| **Prefer 1–2 over 5** | Fill evidence with product-generated or product-derived data before reaching for public scraping |\n| **AI governance** | Structured inputs only; no unverified numbers; moderation on UGC; optional disclosure |\n| **Clean & merge** | Deduplicate keys; drop rows that produce duplicate intents |\n\n## Ideal Use Cases\n\nFor **which page-generator skill to use**, see **Page Playbook Matrix** above. Generic patterns:\n\n| Use case | Example |\n|----------|---------|\n| **Location-specific pages** | \"Plumber in [city],\" \"Best restaurants in [neighborhood]\" with real local data |\n| **Product comparison** | \"[Product A] vs [Product B]\" with structured specs |\n| **Alternatives pages** | \"[Competitor] alternatives\" at scale; 50+ competitors; see **alternatives-page-generator** |\n| **Software integration** | \"[App A] + [App B]\" integration pages (e.g., Zapier 50K+ pages) |\n| **Free tools** | \"[X] checker,\" \"[Y] calculator,\" \"[Z] generator\" — standalone tool pages; toolkit hub; same ICP as main product; lead gen |\n| **Travel \u002F destination** | City + attraction combinations with reviews, photos |\n| **E-commerce** | Category pages, product variations (size, color, material) |\n| **FAQ \u002F Q&A** | Pages powered by user question databases |\n| **Salary \u002F pricing** | Comparison pages with structured data |\n\n**Avoid when**: Site structure is weak; page differences are superficial (city\u002Fname swaps only); content requires original expertise or UGC participation.\n\n## Real-World Examples\n\n*Examples are illustrative; no endorsement implied.*\n\n| Company | Scale | Pattern |\n|---------|-------|---------|\n| **Zapier** | 50,000+ pages | \"[App A] + [App B]\" integration |\n| **Airbnb** | — | Location search; destination × property |\n| **Review platforms** | — | User reviews + automated comparison pages |\n| **Travel sites** | — | Destination, hotel, flight, activity pages |\n| **NomadList** | 2,000+ city pages | Cost-of-living, internet speed (dynamic data) |\n| **Semrush, Ahrefs** | 50+ free tools | SEO checker, keyword tool, backlink checker; toolkit hub + per-tool pages |\n\n## Content Requirements\n\n| Requirement | Purpose |\n|-------------|---------|\n| **300+ words per page** | Avoid thin content penalties |\n| **Unique, verifiable data** | Each page must add meaningful page-specific content beyond simple data swaps |\n| **Evidence block** | Tables, lists, examples with real numbers\u002Fattributes on every page |\n| **Semantic HTML** | Proper structure; conditional logic to avoid empty or repetitive sections |\n| **Internal linking** | Link related programmatic pages; compounds traffic and indexation |\n\n## Technical Considerations\n\n| Topic | Practice |\n|-------|----------|\n| **Subfolder vs subdomain** | Prefer **subfolders** (`yoursite.com\u002Fintegration\u002Fslack-notion\u002F`) over **subdomains** (`integrations.yoursite.com\u002F...`) so authority consolidates on the primary domain; see **url-structure**, **domain-architecture** if restructuring |\n| **Selective indexation** | Don't index all pages; use noindex rules for low-value pages |\n| **Sitemap segmentation** | By country, language, division; manage crawl budget |\n| **URL structure** | Descriptive URLs; clean hierarchy; see **url-structure** |\n| **Schema** | JSON-LD: Product, Place, FAQ, ItemList per page type |\n| **Performance** | Caching, static generation; Core Web Vitals |\n\n## Critical Pitfalls\n\n| Pitfall | Consequence |\n|---------|-------------|\n| **Thin content** | Minimal info beyond keyword; generic copy; placeholder sections → penalties |\n| **Duplicate pages** | Same content with only data swaps → thin content penalties |\n| **Index bloat** | Generating pages that should never be indexable → crawl budget waste |\n| **Large dumps** | Publishing many similar pages at once → spam signals |\n| **Filter URLs** | Using filters instead of unique URLs\u002Ftitles → cannibalization |\n\nPages with only a title, one paragraph, and swapped city names will not rank and may incur Google penalties.\n\n## Step-by-Step Workflow\n\n1. **Research** — Niche, intent; include low-volume keywords; SEO tools, question databases\n2. **Collect data** — Provenance log, freshness rules; first-party\u002Flicensed; define template fields\n3. **Choose stack** — Next.js + DB, Webflow CMS, WordPress, headless; API + template reuse\n4. **Design template** — Intro, Evidence, Decision, FAQ, CTA; schema; conditional logic\n5. **Build database** — Map fields to template slots; hide empties\n6. **Generate pages** — Descriptive URLs; optimize performance\n7. **Deploy & monitor** — Sitemaps; indexation, rankings, CTR, bounce, conversions\n8. **Optimize** — Prune weak pages; refresh data; A\u002FB test layout, CTA\n\n## Best Practices\n\n| Practice | Purpose |\n|----------|---------|\n| **Quality over scale** | Each page must provide genuinely unique, verifiable value |\n| **Differentiation over clone** | Prefer **AI-grounded** copy variance + evidence blocks over one static paragraph with `{city}` swaps |\n| **Launch in batches** | Small batches you can measure; avoid large dumps |\n| **Strong IA** | Internal links to related guides\u002Fcategories |\n| **Visual elements** | Tables, maps, comparisons where relevant |\n| **Match intent** | Avoid generic template text; precise user intent |\n\n## Timeline & Expectations\n\n- **Typical time to ranking**: ~6 months\n- **Reported gains**: 40%+ traffic increases from well-designed topic clusters\n- **AI search**: Structured, data-rich content performs better in AI Overviews and citation layers\n\n## Output Format\n\n- **Template design** (Intro, Evidence, Decision, FAQ, CTA; required data fields)\n- **Data requirements** (provenance, freshness, accuracy)\n- **Internal linking** (hub-and-spoke, related pages)\n- **Indexation strategy** (selective indexation, sitemap segmentation)\n- **Checklist** for audit\n\n## Related Skills\n\n- **template-page-generator**: Template structure; aggregation (gallery) + detail pages; **Tier 1 product-generated** template URLs\n- **landing-page-generator**: Conversion-focused programmatic pages; LP structure for campaign CTA\n- **tools-page-generator**: Free tools pages; toolkit hub; programmatic tool pages; lead gen\n- **alternatives-page-generator**: Alternatives\u002Fcomparison pages at scale; competitor brand traffic\n- **category-page-generator**, **products-page-generator**: Category \u002F catalog grids\n- **glossary-page-generator**, **faq-page-generator**, **howto-section-generator**, **comparison-table-generator**, **resources-page-generator**: Definitions, Q&A banks, HowTo step blocks, comparison matrices, content hubs\n- **use-cases-page-generator**, **solutions-page-generator**, **migration-page-generator**: ICP\u002Findustry matrix, migration SEO\n- **integrations-page-generator**: Integration pair pages at scale\n- **blog-page-generator**, **article-page-generator**, **docs-page-generator**, **features-page-generator**, **api-page-generator**: Long-form and product surface scale\n- **press-coverage-page-generator**, **customer-stories-page-generator**, **showcase-page-generator**: Proof at scale\n- **startups-page-generator**, **contest-page-generator**, **download-page-generator**, **affiliate-page-generator**, **media-kit-page-generator**, **pricing-page-generator**, **services-page-generator**: Programs and offers (use selectively for pSEO)\n- **content-strategy**: Content clusters, pillar pages; programmatic pages as cluster nodes\n- **website-structure**: Site IA before scaling URL sets\n- **url-structure**, **domain-architecture**: Paths, subfolder strategy\n- **schema-markup**: Structured data (Product, Place, FAQ, ItemList)\n- **internal-links**: Linking programmatic pages\n- **xml-sitemap**: Sitemap segmentation for large programmatic sites\n- **canonical-tag**: Duplicate\u002Fthin content handling\n- **seo-strategy**, **seo-audit**: Roadmap and post-launch audits\n",{"name":5,"metadata":54,"description":7},{"version":55},"1.4.1","main","c7ec8d78e5dc37484c2cfe90ab04de163d97dd41","marketing-skills\u002Fseo\u002Fprogrammatic-seo",0,"https:\u002F\u002Fgithub.com\u002Fariadoss\u002Fsuperskills","https:\u002F\u002Fhyperion360.com\u002Fblog\u002Fparallel-ai-agents-engineering-workflow\u002F","https:\u002F\u002Fgithub.com\u002Fariadoss","https:\u002F\u002Fdanilosapad.com\u002F","CEO & Founder of @Hyperion360","2026-11-13 04:11:07",{"source":8,"skillName":5,"commands":67,"prompt":77,"zipAvailable":78},[68,71,74],{"tool":69,"command":70},"npx","npx skills add ariadoss\u002Fsuperskills --skill programmatic-seo",{"tool":72,"command":73},"bunx","bunx skills add ariadoss\u002Fsuperskills --skill programmatic-seo",{"tool":75,"command":76},"pnpm","pnpm dlx skills add ariadoss\u002Fsuperskills --skill programmatic-seo","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fariadoss\u002Fsuperskills\u002Fblob\u002Fmain\u002Fmarketing-skills\u002Fseo\u002Fprogrammatic-seo\u002FSKILL.md",true,[],[81,105,129,148,177,193],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":90,"publishedAt":49},"01M71AZE3MPF891RM354EMRYA1","youtube","Download YouTube video transcripts when user provides a YouTube URL or asks to download\u002Fget\u002Ffetch a transcript from YouTube. Also use when user wants to transcribe or get captions\u002Fsubtitles from a YouTube video.","https:\u002F\u002Fgithub.com\u002Fariadoss\u002Fsuperskills\u002Fblob\u002Fmain\u002Fskills\u002Fyoutube\u002FSKILL.md",[87],{"categoryNo":88,"categoryName":89,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000016","图像与多媒体",[83,91,92,93,94,95,96,97,47,48,98,99,100,101,102,33,103,104],"user","download","transcribe","write","transcript","video transcripts","Bash","Captions","get","fetch","Video","read","subtitles","transcripts",{"skillNo":106,"name":107,"nameZh":6,"description":108,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":109,"categories":110,"keywords":111,"publishedAt":49},"01M71AZAYR85PW6BJGSQXS4BN2","write-plan","Use when you have a spec or requirements for a multi-step task, before touching code. Produces an engineering plan complete with TDD tasks, DRY\u002FSOLID\u002FYAGNI principles, a required Test Plan & Verification section, and a coverage target — then auto-runs \u002Fplan-eng-review as an independent double-check before execution.","https:\u002F\u002Fgithub.com\u002Fariadoss\u002Fsuperskills\u002Fblob\u002Fmain\u002Fskills\u002Fwrite-plan\u002FSKILL.md",[],[112,113,94,114,115,116,117,118,119,48,120,121,122,123,124,36,125,126,127,128],"write plan","plan","dry","verification","review","tasks","code","you","auto","eng","coverage","complete","section","test plan","target","as","yagni",{"skillNo":130,"name":131,"nameZh":6,"description":132,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":133,"categories":134,"keywords":135,"publishedAt":49},"01M71AZ8NDDP5ZMGEE6FSC4FKR","worktrees","Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification","https:\u002F\u002Fgithub.com\u002Fariadoss\u002Fsuperskills\u002Fblob\u002Fmain\u002Fskills\u002Fworktrees\u002FSKILL.md",[],[131,136,137,138,33,139,140,141,142,143,144,115,145,48,146,147],"implementation","workspace","with","plans","feature","isolation","git","directory","work","git worktrees","selection","Safety",{"skillNo":149,"name":150,"nameZh":6,"description":151,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":152,"categories":153,"keywords":157,"publishedAt":49},"01M71AZ4ZQHTNWFRZVYHKQFP08","web-perf","Analyzes web performance using Chrome DevTools MCP. Measures Core Web Vitals (LCP, INP, CLS) and supplementary metrics (FCP, TBT, Speed Index), identifies render-blocking resources, network dependency chains, layout shifts, caching issues, and accessibility gaps. Use when asked to audit, profile, debug, or optimize page load performance, Lighthouse scores, or site speed. Biases towards retrieval from current documentation over pre-trained knowledge.","https:\u002F\u002Fgithub.com\u002Fariadoss\u002Fsuperskills\u002Fblob\u002Fmain\u002Fskills\u002Fweb-perf\u002FSKILL.md",[154],{"categoryNo":155,"categoryName":156,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",[158,159,160,161,162,163,164,165,166,48,167,168,169,170,171,172,173,174,175,176],"web","perf","web perf","resources","MCP","layout","optimize","documentation","caching","qa","knowledge","devtools","issues","render","re","performance","chrome devtools","vitals","never",{"skillNo":178,"name":179,"nameZh":6,"description":180,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":181,"categories":182,"keywords":183,"publishedAt":49},"01M71AZ2KZNWYEGKKRMJH8PYG2","verify","Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always","https:\u002F\u002Fgithub.com\u002Fariadoss\u002Fsuperskills\u002Fblob\u002Fmain\u002Fskills\u002Fverify\u002FSKILL.md",[],[179,123,184,185,144,115,186,187,48,188,33,189,190,191,192],"commands","about","claims","output","assertions","claim","prs","evidence","running",{"skillNo":194,"name":195,"nameZh":6,"description":196,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":197,"categories":198,"keywords":199,"publishedAt":49},"01M71AZ0ACCK7N1QMWQK1FV2HJ","validate-idea","Validate a business idea using the minimalist entrepreneur framework. Use when someone has a business idea and wants to test if it's worth pursuing before building anything.","https:\u002F\u002Fgithub.com\u002Fariadoss\u002Fsuperskills\u002Fblob\u002Fmain\u002Fskills\u002Fvalidate-idea\u002FSKILL.md",[],[200,201,202,203,204,205,206,48,207,33,208],"validate","idea","validate idea","framework","it","minimalist","test","business","before building"]