Most location pages fail the same test. Swap the town name for another and the page reads just as well, because it says nothing about the town at all. Search engines have become very good at recognising this, and customers recognise it immediately.
A page that works contains things that are only true of that place.
What makes a page genuinely local
| Example | |
|---|---|
| Districts people actually name | Parkstone, Canford Cliffs and Broadstone rather than just Poole |
| How the market behaves | Seasonal visitor demand, a commuter population, a student calendar |
| Geography that affects the service | An island city where travel time matters more than distance |
| Local regulation or constraints | Conservation areas, national park planning rules |
| Real catchment | The villages and neighbouring towns you actually travel to |
| Honest competition picture | Whether this is an easy market or a hard one |
Local knowledge is the hard part
Anyone can write fluent copy. What cannot be faked is knowing that Portsmouth sits largely on an island so travel time decides who customers will use, or that Hebden Bridge behaves nothing like Halifax eight miles away, or that a Wigan resident does not think of themselves as Mancunian. That knowledge is what separates a page that ranks from one that does not, and it is where most of the writing time goes.
Written for the reader first
A good location page answers the questions a customer in that town actually has: do you cover my area, how far will you travel, what does it cost to get here, have you done work near me. Pages written to answer those questions tend to satisfy search engines as a side effect. Pages written for search engines rarely satisfy anyone.
Consistent without being identical
A set of location pages should share structure so they are easy to navigate, while sharing almost no actual sentences. We measure overlap between pages and keep it low — a set where every page repeats the same paragraphs is exactly the pattern that gets a site treated as thin.