You have 500 pages live. Traffic was fine in March. Last month you opened Google Search Console and half your impressions had quietly flatlined. Google didn't penalize you for spam — it looked at 500 pages that all say roughly the same thing and decided most of them weren't worth showing. That's the real wipe: not a penalty, just slow irrelevance.
You can't hand-write 500 refreshes. You also can't let them rot. The fix is a template-batch method built around one idea: most of your pages are the same page with different facts. So you fix the template once, then batch-verify each page instead of rewriting it.
Step 1: The 90-day GSC triage
Export the last 90 days from Google Search Console — queries, impressions, clicks, position — and classify every page into four buckets:
- Keep: impressions are stable or rising, clicks are happening. Do nothing.
- Stale: impressions dropped 30%+ versus 60–90 days ago but the page targets a still-valid query. Needs a refresh.
- Dupes: two or more pages target the same intent. Merge, don't duplicate.
- Dead: impressions near zero, query intent is gone (nobody searches "flip phone ringtones" anymore). These get merged into a relevant neighbor and 301'd.
Sort by impressions, not clicks. A page with zero clicks can still be your best page — it just ranks poorly. The goal of this pass is to find out which pages Google is testing and which it has given up on.
Step 2: The intent drift check
Before you rewrite a single Stale page, verify its intent is still correct. Look at the current top 5 results for your target keyword. Answer two questions:
- Are the top results listings pages, reviews, or informational? If your target keyword now returns a video carousel and how-to articles, but your page is a comparison table, your intent has drifted even if the keyword hasn't changed.
- Do the page titles in the SERP use a phrase you're missing? Those phrases come straight from user expectations.
Intent change is the #1 silent killer of refreshes. You can update the content, speed up the page, and add schema until you're blue — if the query now expects a different format, the refresh won't move the needle.
Step 3: Merge-with-301 instead of deleting
The D and Dupes buckets rarely deserve a fresh page. Deleting wastes whatever links and history they have; keeping them drains crawl budget. The answer is merge-with-301:
- Pick the surviving page — the one with the strongest mix of authority, backlinks, and current traffic.
- Move any useful content from the dead page into the survivor (a section, a table, a handful of strong FAQs).
- 301 the dead URL to the survivor and update internal links to point at the survivor.
- Let the 301 pass link equity and let the survivor inherit the query.
Every time you delete instead of merging, you're burning equity you already paid for.
Step 4: Protect your money slugs
Slugs are part of the URL and therefore part of the ranking signal — and they're also what users read. Your business-critical pages (typically the money pages you convert on) should keep their forever-slug. When you merge into a different page entirely, you should own the conversion-relevant URL yourself on the same domain.
Step 5: Fix the shared template once
This is the memorable move. When you refresh a page that was built from a template, you treat the template as a codebase, not the page as an isolated doc. In the old model your 500 pages were a pile of unique creations; in the template model they're 5 distinct templates being filled by data. Fix the shared template once, and hundreds of pages fix together.
A concrete template-level fix: variable insertion. Web 2.0 marketing pages are identical except for the city or keyword — Google compares the ratio of unique to duplicated content across the page, and near-identical pages get filtered. So you add real data, not just keyword swaps: prices, local differences, unique FAQs, or a genuine answer to the question the template headline doesn't address. One fix in the template cascades to every page that uses it.
Step 6: Re-verify in batches of 25
After the template fix, don't eyeball 500 pages. Verify in batches of 25, because you only need a 25-page sample to catch most template-level problems (missing schema, duplicated title tags, broken variable substitution). The work is now checking whether the data filled in correctly, not writing marketing copy.
Working this way, a 500-page project looks like: 280 pages keep, 120 stale pages get a template-triggered refresh, and 100 get merged into the survivors.
Full disclosure: I work on pSEO Engine, which does exactly this kind of programmatic refresh at scale — turning a query space into a page plan and generating an AI landing page per row, then reviewing and publishing to your own domain. There's a case study (MUA Bishal, a bridal/event makeup artist in India) that published 500 pages live since 31 Aug 2026 with 432 keywords currently tracked. You can see it at https://pseo.quantumcx.net.
If you have hundreds of pages, you don't have a content problem. You have a systems problem — and systems are fixable once you stop treating every page as a separate emergency.
Top comments (1)
lol that template-batch trick saved me hours, but does