Programmatic SEO means building many pages from one template and one dataset, so each row in a spreadsheet becomes its own page. It works when every page carries real, distinct information that answers a specific search. It fails, sometimes badly, when the pages are the same paragraph with a city or product name swapped in.
That second version is what Google calls spam. So before the how-to, here's the line you can't cross.
The risk: Google's spam policies describe the lazy version exactly
Two of Google's spam policies apply directly to this technique.
Scaled content abuse. Google's definition: "when many pages are generated for the primary purpose of manipulating search rankings and not helping users." The policy is about purpose and value, and it applies however the pages were made. Its examples include generating many pages with AI tools that add nothing for users, and scraping feeds or search results and republishing them with little added.
Doorway abuse. Google's definition: "when sites or pages are created to rank for specific, similar search queries. They lead users to intermediate pages that aren't as useful as the final destination." The classic case is a set of near-identical city pages that all funnel visitors to the same sales page.
The same document says sites that violate these policies "may rank lower in results or not appear in results at all." If you're using AI to fill the template, Google's guidance on generative AI content repeats the point: generating many pages without adding value for users may violate the scaled content abuse policy.
None of this bans templates or databases. Plenty of well-known sites are built this way: app directories with a page for each integration, currency converters with a page per currency pair, travel sites with a page per destination. What they share is a real dataset underneath.
What separates a legitimate programmatic page from a doorway page
| Legitimate page | Doorway or thin page |
|---|
| What changes per page | Several real data points | One keyword |
| Where the content comes from | A dataset you can verify | Boilerplate, spun or generated text |
| Who it serves | Someone searching that exact thing | Nobody; it exists to rank |
A quick test I'd use: delete the place or product name from two of your pages and compare them. If you can't tell which is which, you have one page published many times.
A second test: would the page still be worth having if search engines didn't exist? A page comparing two specific tools on price, features and limits passes. A page titled "best plumber in [city]" with no information about plumbers in that city doesn't.
How to build a programmatic SEO project step by step
1. Find a repeatable query pattern
You're looking for a search that people make in many variations with the same structure: "[tool A] vs [tool B]", "[service] in [city]", "[app] integration with [app]", "[unit] to [unit]". The pattern has to be real, so check that people search several of the variations and look at what currently ranks. If the results are forum threads and thin pages, there's room. If they're all official product pages, your template probably won't beat them.
The process is the same as keyword research built around realistic opportunity; you're just evaluating a pattern instead of a single phrase.
2. Get a real dataset
This is the hard part, and it decides whether the project is worth doing. The dataset needs enough specific fields per row to fill a useful page. A name and a category won't do it.
Good sources, roughly in order of how defensible they are:
- Data you already own: product specs, service areas, pricing, your own test results or measurements.
- Research you do yourself, row by row.
- Public or licensed datasets, such as government statistics, where you have the right to use them and can add something on top.
Scraping someone else's content and republishing it is one of Google's own examples of scaled content abuse, and it may also break the source's terms. Data everyone can copy is also a weak foundation; what you have that others can't cheaply reproduce matters more here than anywhere.
Before going further, pull ten rows at random and ask whether each one could support a page you'd be comfortable putting your name on. If half of them are mostly empty, fix the data or shrink the project to the rows that are complete.
3. Design a template where the data does the talking
Put the unique information first: the comparison table, the local details, the specific numbers. Keep shared boilerplate short and push it down the page.
Build in conditional logic. If a row has no pricing data, drop the pricing section for that page instead of printing a vague sentence. If an entry has something unusual about it, give the template a field for a short written note. A page that adapts to its data reads like it was made for that entry.
Each page also needs its own title, meta description and heading built from the data, plus sensible links to related entries and back to a browsable index page. Google's doorway examples specifically mention similar pages that sit outside a clear, browsable hierarchy, so a deliberate internal linking structure is part of staying on the right side of the policy as well as helping readers.
For location pages, be especially strict. If you don't serve a city or have nothing specific to say about it, don't make the page. For a real local business, a Google Business Profile and local SEO basics will usually do more than fifty city pages.
The stack is less important than people make it sound. You need somewhere to keep the data (a spreadsheet or a database) and something that turns rows into pages. That can be a CMS with custom fields or collections, a bulk-import plugin, a no-code site builder with a database feature, or a static site generator if you're comfortable with code. Choose whichever you can maintain; the data and template decide the outcome.
5. Publish a small batch first
Publish a small sample, a few dozen pages at most, drawn from your most complete rows. Read every one of them as a visitor would. Template bugs, empty fields and awkward generated sentences show up immediately at this scale and are cheap to fix.
6. Check indexing in Search Console
Add the batch to its own sitemap and submit it in Google Search Console. The Page indexing report can be filtered by sitemap, so you can see how many of those specific pages were indexed.
Indexing can take anywhere from days to weeks, so wait before judging, then look at the reasons given for anything left out. A large share of the batch sitting under "Crawled - currently not indexed" or "Duplicate without user-selected canonical" often means the pages are too thin or too similar to each other. Treat that as feedback on the template and data. Publishing more of the same pages won't change the answer.
For the pages that did get indexed, check the Performance report for impressions and clicks on the queries you targeted. There's no number that counts as a pass, and results vary a lot by niche and site.
7. Prune what doesn't earn its place
If the batch holds up, expand in stages and keep checking. For pages that stay unindexed or never get visits, improve the data, merge them into a stronger page, add a noindex tag, or delete them. A smaller set of useful pages is safer than a large set of marginal ones, because Google's spam policies talk about consequences for sites, and a pile of thin pages puts more than those pages at risk.
Plan for upkeep too. Prices change, businesses close, products get discontinued. One wrong value in the dataset is wrong on every page that uses it, so schedule a regular review of a sample of pages against their sources, the same way you'd run a periodic audit of the rest of your site.
Skip it when the value of the content is judgment or explanation. Tutorials, opinionated reviews and anything where the reader wants your reasoning don't fit a template, and forcing them into one produces weaker pages than writing them by hand.
Skip it as well if you don't have the data yet. "I'll generate the text to fill the gaps" is how a legitimate idea turns into scaled content abuse.
Common questions
How many pages should a programmatic SEO project have?
As many as you have complete, distinct data for, and no more. The number of useful rows sets the size of the project. A set of forty solid pages is a perfectly good outcome.
Can programmatic pages and hand-written articles live on the same site?
Yes. Many sites use templates for structured reference pages and write their guides individually. Link between the two where it helps a reader, and hold both to the same standard.
Start with ten rows
Before choosing tools or building a template, fill in ten rows of your dataset by hand and write one page from them manually. If that page is useful and the next nine would be different in ways that matter, you have a project. If the next nine would all say roughly the same thing, the topic is better served by a handful of hand-written articles, and building depth on one focused topic is the better route.