Programmatic SEO

SkillSearch

Builds large sets of search-targeted pages from a template and a dataset — the location, comparison, integration, and use-case pages that capture long-tail demand at scale. Use this when there is a repeating query pattern with real volume, when a dataset could answer many similar searches, or to judge whether a programmatic approach is viable before building it.

Available today. Use it from your connected AI after setup.

Connect ahel once, and every AI you use reads what you have installed.

Then ask your AI: use the Programmatic SEO skill

What this skill tells your AI

The instructions your AI receives, as published by cbrock84/headcount in plugins/demand-generation/skills/programmatic-seo/SKILL.md and read by ahel’s review.

Done well, one template covers thousands of real searches. Done badly, it is a mass of thin pages that damages the whole domain.

Qualify before building

All four must hold:

  1. A real query pattern with verified volume across many instances — not one popular term and a long tail of zeroes.
  2. Data you actually have, at quality, for most instances. Missing data produces empty pages, and empty pages are the failure mode.
  3. Genuine per-page value. If two pages differ only by a swapped noun, they are duplicates however they are generated.
  4. A reason to be better than what ranks now. Usually completeness, freshness, or data nobody else has.

Fail any one and the answer is fewer, better pages.

Building

  • Design the best single page first, by hand, and confirm it is genuinely useful. Then find what in it is variable. Templating before you know the good page scales a mediocre one.
  • Vary the substance, not just the strings. Each page needs data, comparisons, or context specific to it.
  • Set a minimum data threshold. Below it, the page does not get generated. This single rule prevents most programmatic disasters.
  • Internal linking is not optional — thousands of orphaned pages will not be crawled. Build hub pages and cross-links into the template.
  • Roll out in batches. Publish a few hundred, wait for indexation and performance, then continue. A full launch that goes wrong is hard to unwind.

Maintaining

Stale programmatic pages rot faster than editorial ones because there are so many. Set a refresh cadence tied to the data source, and prune: pages with no impressions after two quarters should be consolidated or removed. Volume is not the goal.

Never

  • Generate pages for instances with no data.
  • Spin text to create the appearance of uniqueness.
  • Launch without a plan for removing what does not work.

Signals

GitHub stars
1k
Forks
209
Last commit
Sep 2026
Advanced
Catalog kind
skill
Gateway key
programmatic-seo-cbrock84
Source
github.com/cbrock84/headcount