# Content velocity: how many pages a small site can add without harm

There is no page count that triggers a penalty. What matters is whether each page in a batch holds something of its own, because Google's spam policies judge the intent behind many pages, not the number. This page is about scale: how big a batch can be and what makes it safe. The rhythm question, how often to publish at all, is a separate one.

Updated 2026-09-15 · Source: https://porteur.ai/guides/content-velocity

## What the policy actually says

Google's spam policies, updated in March 2024, name scaled content abuse: producing many pages primarily to manipulate rankings rather than to help people, whatever produces them, automation, humans, or both.

- The number of pages is not the test. Large sites publish thousands of pages a day without issue.
- The producer is not the test either. The policy explicitly covers human-written pages made at scale.
- The test is whether the pages exist to help someone, and whether each holds value of its own.

The same guidance is clear that Google does not penalise AI assistance as such. A hundred pages written with a model, each holding real data and a real answer, is not what the policy targets. Ten pages spun from one template with the nouns swapped is.

## What makes a batch of pages safe

Before publishing a batch, check every page against this. If a page fails all four, it should not ship, whatever the batch size.

| The test | Passes | Fails |
| --- | --- | --- |
| It holds a method | Steps somebody can follow to get a result. | A description of what the thing is, in general. |
| It holds a worked example | A named page, a real figure, a before and after. | "For example, you could optimise your content." |
| It holds data or a table | A comparison, a threshold, a list of what applies where. | Three paragraphs of prose that could be about anything. |
| It holds a tool or a check | Something the reader does on the page or with the page open. | A call to action and nothing else. |

> The honest version of the test: if you swapped the subject noun for a different one, would the page still read as finished? If yes, it is a template, and Google will read it as one.

## The page families that earn their scale

Some families are legitimately large because the underlying questions are legitimately many. They share one property: the difference between two pages in the family is real.

- One page per error message or status, where each has a different cause and a different fix.
- One page per term, where each definition is more precise than what ranks today.
- One page per tool comparison, where each holds a judgement about who should choose what.
- One page per task in documentation, where each is something a user must actually perform.
- One page per data slice, where you hold the data and nobody else publishes it.

The families that do not earn their scale are the ones built from a grid: every city crossed with every service, every tool crossed with every integration, when you have nothing to say about most of the cells. Those are the doorway pages the policies describe.

## How big a batch can be

There is no published limit, so the constraint is practical rather than algorithmic. A batch is too big when you can no longer check it, or keep it accurate.

1. **Read three pages of the batch in full** Not skim: read. If you find an invented figure, a paragraph that says nothing, or a claim you cannot source, the batch is not ready and the sample was random.
2. **Check the batch against the four tests** Method, example, data, check. Pages failing all four come out of the batch.
3. **Publish and stop** Ship the batch, then wait for the index to judge it before shipping the next. A month is enough to see the pattern.
4. **Size the next batch by what you can maintain** Every page joins the quarterly review. A hundred pages is a hundred pages to keep accurate, forever.

## The signals that tell you Google judged the template

After a batch, you are watching for a judgement about the family rather than about individual pages. Give it three to six weeks, then read three reports.

| Where | What good looks like | What a judgement looks like |
| --- | --- | --- |
| Page indexing report | Most of the batch indexed within a few weeks. | The batch sitting in "Crawled, currently not indexed" together. |
| Performance report | Impressions appearing across the family, spread over many queries. | Impressions on two pages of forty, nothing on the rest. |
| Crawl stats | Steady crawling of the new folder. | Fetches dropping off after the first pass. |
| The rest of the site | Unchanged. | Older pages losing positions at the same time as the batch lands. |

> The last row is the one that matters. A batch that does nothing costs crawl. A batch that drags the rest of the site down is a judgement about the whole site, and the fix is to remove the batch, not to add to it.

## What to do if a batch goes wrong

1. **Stop publishing that family** Before anything else. Adding more pages to a family Google has judged makes the signal louder.
2. **Decide page by page** Keep the ones with impressions or links. Merge the near-duplicates into the strongest URL with a 301. Remove the rest with a 410.
3. **Take them out of the sitemap** The sitemap should list the pages you want indexed, not everything you ever published.
4. **Wait a full cycle** Recovery from a quality judgement is slow and often waits for a broader update. Do not undo the cleanup because nothing moved in two weeks.

The library that survives this is the one where every page would have been worth writing on its own. That is the whole rule, and it is simpler than any threshold.

## Questions

### How many pages can I publish at once without a penalty?

There is no number. Google's policy judges whether pages exist primarily to rank rather than to help, not how many arrived. A hundred pages that each hold a method, an example and data are fine; ten spun from one template are not.

### Is publishing a hundred pages in a day suspicious?

Not by itself. Large sites do it constantly. What draws a judgement is a hundred near-identical pages with nothing of their own, which is visible in the pages themselves rather than in the timing.

### Does AI-written content count as scaled content abuse?

Not because it is AI-written. Google's guidance says it does not penalise AI assistance as such, and that the policy covers pages made at scale without value of their own whoever made them. The test is the page, not the tool.

### How do I know if a batch hurt my site?

Watch three things over three to six weeks: whether the batch gets indexed, whether it earns impressions across many queries, and whether the pages you already had lose position at the same time. The third is the serious one.

### What is the difference between content velocity and publishing frequency?

Velocity is how many pages arrive at once and whether the family earns its scale. Frequency is the rhythm you can hold over a year. A site can have low frequency and high velocity, publishing one considered batch a quarter.

## Read next

- [Scaled content abuse](https://porteur.ai/glossary/scaled-content-abuse): What scaled content abuse means in Google’s spam policy, how to avoid it on a small site, how to check risk, and what to fix fast.
- [How often to publish: what actually matters](https://porteur.ai/guides/how-often-should-you-publish): Frequency is not a ranking signal. What a thin page costs, why refreshing counts as publishing, and a rhythm one founder can hold for a year.
- [Programmatic SEO for a small product: page families that earn](https://porteur.ai/guides/programmatic-seo): Design a page family that ranks without spam: pick the right template, prove demand per page, add unique data, and measure the folder.
- [Thin content](https://porteur.ai/glossary/thin-content): Thin content is a page with little value of its own. See why it drags a small site, how to spot it, and how to expand, merge or remove.
- [Doorway page](https://porteur.ai/glossary/doorway-page): Doorway pages are many near-duplicate pages funnelling to one destination. See how to spot them, fix them, and protect rankings on a small site.
- [Google spam updates: the policies they enforce and how to stay clear](https://porteur.ai/guides/google-spam-update): See what a Google spam update enforces, the policies that trip small product sites, how to check your risk, and how to recover if you’re hit.
- [How many pages does a product site need?](https://porteur.ai/guides/how-many-pages-does-a-website-need): The eight pages every product needs, what each page after those must earn, and the point where adding pages starts costing you instead of paying.
- [Link velocity](https://porteur.ai/glossary/link-velocity): Link velocity is the rate at which a site gains backlinks. No safe rate is documented. What Google has said, and when a spike is worth a look.

Paste your URL and the free check reads your site and the searches around it in about thirty seconds, then shows which of your pages Google shows and which it has quietly set aside. Free check: https://porteur.ai/