Programmatic Seo
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.
Install
$ agentstack add skill-cbrock84-headcount-programmatic-seo ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-cbrock84-headcount-programmatic-seo) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Programmatic SEO
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:
- A real query pattern with verified volume across many instances — not one popular term and a
long tail of zeroes.
- Data you actually have, at quality, for most instances. Missing data produces empty pages,
and empty pages are the failure mode.
- Genuine per-page value. If two pages differ only by a swapped noun, they are duplicates
however they are generated.
- 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.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: cbrock84
- Source: cbrock84/headcount
- License: MIT
- Homepage: https://cbrock84.github.io/headcount/
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.