Local Search Volatility: Why Sensors Cannot Measure It

Why there is no single local ranking

National organic results are broadly the same for everyone searching the same query in the same country. Local results are not. Google weights proximity heavily, so two people searching the same phrase from opposite ends of the same city see different businesses in a different order.

That has been true since the Vicinity update in November 2021, which increased how much distance matters and reshuffled map packs in cities worldwide. The practical consequence is that ranking third is not a fact about your business. It is a fact about your business measured from one point on a map at one moment.

A volatility sensor takes one snapshot per keyword from one location. For national queries that is a reasonable sample of what everyone sees. For local queries it is one pixel of a map, and movement everywhere else is invisible to it.

Two systems, two kinds of volatility

This is the distinction that decides your entire diagnosis, and most local business owners never make it.

	Map pack	Local organic
What ranks	Your Google Business Profile	Your website pages
Main signals	Proximity, prominence, relevance, reviews, categories	Content quality, links, the same signals as national organic
Measurement (where to check)	Business Profile performance report	Search Console, filtered to those queries
Typical cause of a drop	Profile edits, a new competitor nearby, spam cleanup	Core updates, near-duplicate city pages, thin content
Recovery speed	Days to weeks, sometimes immediate	Waits for a core update, so two to four months
Does a website fix help?	Rarely and indirectly	Yes, this is where site work lands

Read the last two rows together. If you lost map pack visibility and respond with a website content project, you will spend three months on work that cannot affect the thing that moved. This is the single most expensive misdiagnosis in local SEO, and it happens constantly because both look like a phone that stopped ringing.

What actually moves local rankings

Most local swings are not algorithm updates at all. Work through these before reaching for the update tracker.

• A competitor opened, moved or updated their profile. Why: Proximity is weighted heavily, so a new business physically between you and a suburb can take that suburb without anything changing on your side.
• Someone edited your Business Profile. Why: Categories, service areas, hours and the business name all affect ranking. Google also accepts public suggested edits, so a change can appear that nobody at your business made.
• A spam sweep removed fake listings. Why: When Google clears keyword-stuffed names or fake addresses in an area, everyone below them rises. Your position can improve or worsen with no action either way.
• Review velocity changed. Why: A quiet quarter for reviews while a competitor collects steadily shifts relative prominence gradually rather than on one date.
• Google adjusted the radius for that query. Why: How far Google looks varies by query and by how many businesses exist nearby. In dense areas the radius tightens, which can remove you from searches a few streets away.
• A core update hit your website. Why: This affects local organic rather than the map pack, and it is the one case where the update tracker is the right first stop.
• Your city landing pages were reassessed. Why: Near-duplicate service-plus-location pages were the clearest casualty pattern in the October 2025 volatility, with agencies reporting these pages losing half their top-three keywords within days.

Only the last two are algorithm events. The other five produce identical symptoms and none of them appear on any volatility chart.

Measuring your own local volatility

Since no public sensor can do this for you, the tracking has to be your own. Four things worth having in place before a drop rather than after it.

• Grid-based rank tracking. Why: Tools that check your position from a grid of points across your service area show where you rank rather than a single number. A drop that only affects the northern half of your city is a proximity or competitor event, not an algorithm one.
• The Business Profile performance report, separately from Search Console. Why: Calls, direction requests and profile views are your map pack metrics. Website clicks are only part of the picture and can hold steady while calls collapse.
• Search Console filtered to your local queries. Why: This is your local organic performance, which moves for entirely different reasons. The drop analyzer will find the break date in that data.
• A record of profile changes with dates. Why: Categories, hours, service areas, name. When something moves, the first question is what changed and when, and reconstructing that from memory months later is unreliable.

When the national sensor is still worth checking

It has one genuine use for a local business. If your website organic traffic dropped, not your map pack, then the volatility sensor and the update tracker are relevant, because that is ordinary organic search behaving ordinarily.

Check the category breakdown rather than the headline score. The sensor tracks 15 categories including local services, so if that category is elevated while the overall reading looks calm, that is far more relevant to you than the average. What the score does and does not prove is covered in volatility explained.

The city page problem, again

The one local pattern that does show up in national volatility is the reassessment of near-duplicate location pages, because those pages compete in ordinary organic results rather than in the map pack.

The structure is familiar: one page per service per suburb, generated from a template, differing by a place name. It worked for years and it is now the most reliable way for a local business to lose organic traffic. The October 2025 wave was the clearest demonstration, and every core update since has continued in the same direction.

The test is whether a resident of that suburb would learn anything from the page that a resident of the next suburb would not already know. Real staff, real premises, real local detail, honest scope. Most businesses cannot fill that out twenty times, and the answer is to build fewer pages properly rather than more pages thinly. The local SEO recovery guide covers the page structure in detail.

Frequently asked questions

Why is local search more volatile than national search?

Because proximity is weighted heavily, so results change with the searcher’s location. There is no single ranking to be stable. Add competitor openings, profile edits and spam cleanups, and local results move for reasons that never affect national ones.

Can a volatility tracker measure local rankings?

Not meaningfully. Trackers sample from a fixed location, so they miss movement everywhere else in your service area. Grid-based rank tracking across multiple points is the only way to see local volatility properly.

My map pack ranking dropped but my website traffic is fine. Why?

Because they are separate systems. The map pack ranks your Business Profile on proximity, prominence and relevance. Your website ranks in organic results on content and links. A profile edit, a nearby competitor or a spam sweep affects one and not the other.

Did an algorithm update cause my local drop?

Usually not. Most local swings come from competitor changes, profile edits, spam removal or radius adjustments, none of which are updates. Check those first, then match the date against confirmed updates if the loss is in website organic rather than the map pack.

How long does local ranking recovery take?

Map pack issues can resolve in days to weeks, because that system is not tied to core update cycles. Website organic recovery follows the normal timeline, which means waiting for the next core update, historically 43 to 147 days apart.

Should I have a landing page for every town I serve?

Only where you can write something genuinely specific to that place. Near-duplicate location pages were the clearest casualty pattern in recent updates, and a handful of real pages now outperform twenty templated ones.