Do location pages go stale? When (and how) to refresh service-area pages

Location pages decay when local intent shifts, a new competitor arrives, or the local detail and figures on the page go out of date. A real refresh adds new local proof and corrects the detail that has aged. Bumping the date alone does nothing – Google has said for years that a changed date without changed content is noise, not a freshness signal.

This is a maintenance post, not a recovery one. If a page was hit by a manual action or a scaled-content assessment, that is a different problem with a different fix, covered in recovering from a scaled-content problem. Here we are talking about the slower thing: a page that ranked, then quietly slipped, with no penalty attached. Figures current as of 1 September 2026.

What does it mean for a location page to decay?

Content decay is the gradual loss of traffic and ranking on a page that used to perform. For a general blog post the usual causes are a competitor publishing something better or the topic simply ageing out. Location pages decay for those reasons too, but they have their own failure modes that a generic content-decay guide never mentions, because location pages are tied to a real place and a real trade.

Four things go stale on a service-area page, roughly in order of how often we see them:

• The local intent shifted. What someone in Uckfield wanted from a “boiler repair Uckfield” search in 2024 is not always what they want now. Maybe the dominant query became “boiler service” rather than “repair”, or “heat pump” started eating the demand. The page is answering a question fewer people are asking.
• A new competitor arrived. A national chain opened a depot nearby, or a local firm built a better page for the same town. Your page did not get worse – the bar moved.
• The figures aged. “Same-day call-outs across Lewes” was true when you wrote it. Two years on, your response times changed, your prices changed, the named engineer left. The page now describes a business that no longer exists.
• The local detail died. You referenced a roadworks scheme that finished, a new estate that is now fully occupied, a council grant that closed. Specifics are what made the page worth reading, and specifics rot fastest.

The first two are about the market. The last two are about you, and they are the ones a refresh can actually fix on its own terms.

Which location pages actually decay, and which just never ranked?

This is the distinction most refresh advice skips. A page that decayed had traffic and lost it. A page that never ranked is a different animal – usually thin, or duplicated across towns, or competing with a stronger page on your own site. Refreshing a page that never ranked is mostly wasted effort. You are polishing something that was never the problem.

So before you touch anything, separate the two. Decay shows up as a downward trend on a page that had a baseline. A never-ranked page shows up as a flat line near zero from the start. Search Console will tell you which is which if you compare a recent period against the same window a year earlier. We walk through the exact comparison in measuring location pages in Search Console, so this post will not repeat it – the short version is that you want clicks and average position for each URL across two matched date ranges, not a single snapshot.

If a page that never ranked is also thin or near-duplicate, the fix is not a refresh – it is either real local substance or removal. That is content quality, not content freshness, and what to write on a local page when every town feels the same is the place to start.

How do you spot a decaying page without guessing?

Guessing is the default. Someone looks at the page, decides it “feels old”, and rewrites the intro. That is cosmetic and usually pointless. Spotting genuine decay is a measurement job, and it is the same job whether you have five location pages or five hundred.

Three signals, in plain terms:

• A falling clicks trend on a page that previously had a baseline. Not a single bad week – a sustained slope over a quarter or more. This is the primary signal and the hardest to fake.
• Average position slipping while impressions hold or rise. Demand is still there, you are just being shown lower for it. That points at a competitor or an intent drift, not at a dead page.
• The page no longer matches what you actually do in that town. This one is not in Search Console. It is in your own head and your own job sheets. Read the page as if you were a customer in Lewes and check whether every claim is still true.

The first two come from Search Console. The third comes from knowing your own business, which no tool can do for you.

Finding decay across dozens of pages at once

Doing the page-by-page read for five towns is fine. For fifty it stops being realistic, and that is where a quality score earns its place. The free Townsmith engine scores every location page from 0 to 100 on the substance signals that tend to decay first – whether the local detail is still specific, whether the page is drifting toward looking like its neighbours, whether it has thinned out over successive edits. It runs entirely on your own server, with no external calls and no AI, so the score is just an honest read of the text as it stands. You can see how the score is built in the quality score documentation.

A score does not measure traffic – Search Console does that. What it measures is whether the page still carries the local substance that earned the traffic in the first place. A page whose score has drifted down while its clicks drift down is the clearest refresh candidate you can find. Pro quality reporting tracks that score across the whole estate over time, so you can sort by what slipped rather than reading every page. It is the way to find decaying pages at scale, and you can see what it covers on the pricing page.

What does a real refresh look like versus a date bump?

A real refresh changes the page in ways a reader would notice. A date bump changes a number in the markup and nothing else. Google has been explicit that the second one does nothing. In its guidance on page dates (Google Search Central, March 2019), Google warns against artificially freshening a story without adding significant information. John Mueller put it plainly in 2022: changing the date without doing anything else is “just noise and useless”. Gary Illyes noted in 2024 that the visible date is one small signal among hundreds, not a lever you can pull on its own.

So the comparison is not subtle. Here is what each side actually involves:

• Real refresh: adds new local proof – a recent job in that town, an updated response time, a current photo, a named engineer who still works there.
• Date bump: leaves the body untouched and edits the published or modified date.
• Real refresh: corrects figures and detail that aged – prices, coverage area, anything that is now wrong.
• Date bump: keeps the stale figures in place because nobody read them.
• Real refresh: re-checks the page against current local intent and adjusts the angle if the dominant query moved.
• Date bump: answers the same question the page answered two years ago.
• Real refresh: produces a genuine dateModified, because the page genuinely changed.
• Date bump: produces a dateModified that Google treats as noise.

The honest rule: change the date because you changed the page, never change the page because you want to change the date. This very post follows it – the dateModified moves only when the text below it genuinely moves.

Does freshness affect whether AI answers cite you?

It does, but not through a freshness trick. Google’s February 2026 Discover core update (Google Search Central, February 2026) – which covers Discover, not AI Overviews – says Google is highlighting “more in-depth, original, and timely content from websites with expertise in a given area”, while reducing sensational content and clickbait. The principle carries over: timeliness sits alongside depth and originality, it is not a substitute for them. A current, genuinely useful page is more likely to be surfaced and cited than a stale one, but a freshly dated empty page is still an empty page.

There is no separate optimisation for getting lifted into an AI answer beyond being indexed and useful. Google states in its AI optimisation guidance (Google Search Central) that structured data is not required for AI Overviews or AI Mode and there is no special schema.org markup to add for them. The fundamentals carry over: be crawlable, answer the question early, keep the detail accurate. A page that is current because you actually maintain it is the optimisation. A page that is “current” because a plugin rewrote the date is not.

How often should you refresh service-area pages?

On a trigger, not a timer. A calendar reminder that says “refresh all location pages every six months” is how you end up date-bumping fifty pages that did not need it. Refresh when one of these is true:

• The page is showing a sustained decline in Search Console, not a one-off dip.
• Something you say on the page is now factually wrong – price, coverage, a named person, a response time.
• The local situation changed in a way customers would care about – a new development, a competitor, a change in what the town searches for.
• The page’s quality score has drifted down, flagging that the substance has thinned.

If none of those is true, the page does not need a refresh, and forcing one wastes time you could spend on the pages that do. Maintenance is triage, not a rota.

Common questions about refreshing location pages

Will updating the modified date on its own help rankings?

No. Google has said repeatedly that changing a date without changing the content is noise. The modified date is one small signal among many, and it only carries weight when it reflects a genuine edit. A plugin that bumps dates automatically can make it harder for Google to spot your real updates, not easier.

Should I delete a location page that decayed, or refresh it?

If it once ranked and the decline is down to aged detail or a shifted angle, refresh it – the page proved it can earn traffic. If it never ranked and it is thin or near-duplicate, refreshing rarely helps. In that case improving the local substance or removing the page is the better call, and that is a quality question rather than a freshness one.

How is this different from recovering from a scaled-content problem?

Decay is a slow slide with no penalty attached – the page just slips. A scaled-content problem is a sharper drop tied to a Google assessment of the whole estate as low-value or mass-produced. The fix for decay is targeted refreshing. The fix for scaled content is structural and is covered separately in the scaled content recovery guide.

Can I refresh pages automatically with AI?

Auto-rewriting pages with AI to look fresh is the date-bump trick wearing a different hat – it changes words without adding anything a local customer could not find anywhere else. The Townsmith free plugin has no AI and makes no external calls at all. The optional Pro assistant only ever works with facts you type in, never invents specifics about a town, and never publishes anything itself. Freshness has to come from real local information you actually have, not from generated filler.

Written by Stephen Evans. Figures and policy references current as of 1 September 2026, drawn from Google Search Central. Re-verify any moving figure against the primary source before relying on it.