Fix local landing pages that rank in the wrong city

You built a landing page for one city, but it shows up in Google for a different one, or not for its own. A page targeting Denver ranks in Boulder, and the Denver page you actually want is nowhere.

This almost always comes down to conflicting geographic signals. Something on or around the page tells Google a different location than the one you intended, so it places the page where those signals point.

This post covers why a location page ranks in the wrong city, how to find which signal is off, and how to correct it without spinning up more thin pages.

A local page ranks in the wrong city when its strongest geographic signals do not match its target. The usual culprits are a title or heading that names the wrong place, near-duplicate city pages that Google merges, an address or map pointing elsewhere, or internal links that frame the page under another location. Align the on-page signals to one clear city, make each city page genuinely distinct, and the placement corrects over the following weeks.

Why a page ranks in the wrong city

Google decides where a page belongs from the signals it can read, not the city you had in mind. When those signals disagree, the strongest ones win.

Local results also weigh the searcher's own location. A page can look like it ranks in the wrong city simply because someone nearby searched, which is normal behavior rather than a fault. Google's explanation of local ranking factors describes how relevance and distance combine, so rule out proximity before treating it as an error.

Once you have confirmed the page really is misplaced for its target term, the cause is almost always a signal mismatch you can fix.

Diagnose which signal is off

Check the signals in order of weight, starting with the ones on the page itself.

On-page location signals

Read the title, H1, headings, and body copy for the city name. If the target city appears once in passing while another city is mentioned repeatedly, the page is telling Google the wrong location. The address block, embedded map, and any structured data should all name the same place.

Duplicate city pages

Compare the page against your other location pages. When several city pages are near-identical, Google may treat them as duplicates and pick one to represent the group, which is often not the one you expected. That is a canonicalization outcome, and Google's guidance on consolidating duplicate URLs explains how it chooses.

Correct the signals

Fix the mismatch by making the target city the clear, repeated signal and removing the competing ones.

Put the target city in the title, the H1, and the opening sentence, and use it naturally through the body where it fits. Match the address, phone, and any map embed to that city so every element agrees.

Then make the page genuinely different from your other location pages. Unique local detail, real projects, and area-specific information stop Google from merging them and let each rank for its own city. Thin, swapped-noun pages are the reason the group gets consolidated in the first place.

Check the internal links pointing at the page too. If most links describe it under a different location, that anchor context pulls the page toward the wrong city.

Confirm the fix and what to expect

Recrawling takes time, so confirm with evidence rather than refreshing rankings daily.

Use a location-neutral check, or a rank tracker set to the target city, so your own location does not distort what you see. Searching from an office in a different city will show a skewed result every time.

Expect placement to settle over a few weeks as Google recrawls the corrected signals. If it still ranks wrong after that, the cause is usually leftover duplication, which ties back to the consistency of your listings and details across the web.

Sorting out geographic signals across a set of location pages is part of local search and Google Business Profile work. For a review of why your pages rank where they do, start with Get Free Assessment.