Prompt: programmatic SEO pages Google will index, not spam
Paste this into Claude Code, Cursor or Codex inside your repo. The agent maps the data you already own, shows a plan with URL counts after quality gates, and waits for your OK. It then adds hubs and term pages that each answer a distinct query with real numbers - and refuses the thin filter-combination pages that get programmatic SEO a bad name.
Copy prompt
The prompt
Paste it into an agent that has your repo open. It plans first and waits for your OK before writing code.
Or paste one line
Fetch https://www.scrolllaunch.com/prompts/programmatic-seo.md and carry out the prompt in its "Prompt" section on this repo. Show me your plan before writing code.For agents that can fetch URLs. The agent pulls the full prompt from this page's markdown version, which includes the last step above.
What you get
What your repo has when the agent is done
- A plan table: family, example URL, query, dataset, gate, URL count after the gate, and skip reasons
- One
resolveIndexable*function per family, used by the route, the sitemap, the hub and every chip - Entity pages and collection pages only - no category x price x country URLs
- Alias spellings fold onto one slug and 308 to it
- Titles and intros built from the same count the page lists; a doorway test before publish
- Below-gate URLs 404 or 308 to the hub; they never appear in the sitemap or as chips
lastmodfrom real content dates; archive HTML on a 24h cache, not hourly- CollectionPage + ItemList + FAQPage JSON-LD with no invented ratings
- Tests that fail if the gate, sitemap and chips drift apart
The result
ScrollLaunch ships the same setup
These are live on this site. Open them to see what a passing result looks like.
/categories
Hub of gated category archives
/tech
Freeform terms, aliases folded onto one slug
/alternatives
Collection pages only when two+ products qualify
/compare
Pairs gated on long-form content + shared topic
/sitemap.xml
Same gate as the routes
Sitemap link counter
Count the URLs this catalog actually advertises
Check your result
Deployed? Score your site
Runs your live URL through the free Sitemap Link Counter. Free sitemap link counter - count URLs in XML sitemaps and sitemap indexes, including gzipped files.
The counter shows how many URLs you advertised. A healthy result is enough pages to cover real queries, not every filter combo. After deploy, compare that number to Search Console's indexed pages. A huge sitemap with a tiny index is the thin-page failure this prompt is built to avoid.
How to use
4 steps from paste to deploy
- 1
Open your repo in a coding agent
Claude Code, Cursor (agent mode), Codex or Windsurf, with read access to the database or a recent copy of it.
- 2
Paste the prompt and read the plan table
Check the after-gate URL counts. Cut any family that only exists as a filter combination, or that is built on fields people fill in carelessly. Ship one family first.
- 3
Say OK, then spot-check three URLs
The agent builds the gate, routes, hub, sitemap wiring and tests. Open one hub, one child, and one below-gate slug (that last one must 404 or 308).
- 4
Deploy and count the sitemap
Submit the sitemap in Google Search Console, then run your live domain through the sitemap link counter. The unique URL count should match the after-gate number, not the unfiltered dump.
Next
Shipped it? Put it in front of people
Launch on ScrollLaunch
A week on the leaderboard and a permanent product page with a markdown version that AI agents can read. Free launches get a dofollow backlink while the badge stays on your site.
Questions
Safe programmatic SEO prompt FAQ
Isn't programmatic SEO just spam?
The spammy kind is: every filter combination, same template, one keyword swapped, thousands of pages with nothing unique on them. This prompt forbids that. It only publishes a URL when the data can state a fact that would be false on a sibling page, and it uses one quality gate for the route, the sitemap and every internal link.
Will this get me a Google manual action?
Not if you leave the hard-no list in place. The prompt refuses doorway pages, invented ratings, cloaking, and intersection URLs. Those are the patterns in Google's spam policies. If an agent tries to add them anyway, reject the diff.
How is this different from sites like Dealroom?
Data catalogs that get cited do entity pages (one company, one city) and collection pages (companies in a city) with first-party numbers on each URL. They do not index every combination of industry x headcount x country x year. Run a large data site through the sitemap link counter and you will see a big but structured catalog, not a facet explosion. That is the pattern this prompt copies.
Do I need a huge dataset?
No. A few hundred clean rows is enough for one family. The prompt tells the agent to skip a family that would only produce a handful of thin pages, and to never publish a collection with a single item (that is a duplicate of the entity page).
Which other prompts should I run first?
If titles, canonicals or a sitemap are missing, run those prompts first. This one reuses those helpers and will stop and ask if they are absent. The AI-readable site prompt and the AI-cited data pages prompt are optional follow-ups: markdown twins and original research reports, not the catalog itself.
More prompts
Other prompts
Fix titles, meta descriptions, canonicals and social cards
One metadata helper for every page: titles that fit, unique descriptions, absolute canonicals, Open Graph and X cards, noindex on private pages.
Add correct JSON-LD structured data to every page type
Organization, WebSite, SoftwareApplication, Article, FAQPage, BreadcrumbList and ItemList, built from your real data with no invented ratings.
Build a sitemap that stays correct, plus IndexNow pings
Sharded sitemap index from your database, honest lastmod dates, no noindex URLs, and IndexNow pings when content is published or updated.
Make your site readable by AI agents
Markdown version of every page, plus llms.txt, llms-full.txt, ai.txt and AI-crawler rules in robots.txt.


