There is a version of local content that everyone produces and nobody reads: a general article with a town name inserted in the title, the first line, and twice more in the body. Search almost any "[service] [town]" phrase and you will find several. They rank badly, and the reason is that a reader can tell within one paragraph that the writer has never been there.
The version that works requires knowing the place, which is why it is such a good thing for a local business to write and such a hard thing for anyone else to copy.
The short answer
Genuinely local content contains something that would be wrong if you changed the town name. That is the entire test. If you can find and replace "Napier" with "Nelson" and the article still reads correctly, it is not local content and it will not rank as local content.
What actually changes between towns
More than people expect, and it is mostly practical rather than cultural. The things that genuinely differ from one part of the country to another:
- Weather and what it does. Wellington southerlies, Auckland humidity, Central Otago frosts, Taranaki rain, the salt air anywhere coastal. These change what fails, how often, and when to do something about it.
- What the ground is. Auckland clay, Canterbury gravel, Waikato peat, the reclaimed land around several harbours. This changes foundations, drainage, fencing, planting and half the jobs in the trades.
- Which council, and how it behaves. Processing times and requirements are genuinely different between districts, and people search for their own council by name.
- Travel time and what it costs. Whether a job is worth quoting from where you are based, and what the call-out realistically covers.
- The seasonal rhythm. A tourist town empties and fills on a different calendar than a farming district, and both differ from a city suburb.
- The suburbs people actually name. Nobody in Hamilton says "central Hamilton". They say Hillcrest, Rototuna, Frankton — and that is what they type.
Any one of those turns a generic article into something only a local could have written.
The small towns are the easy ones
The instinct is to target the biggest city you serve. It is the hardest thing on your list and usually the last one you will win.
"Electrician Auckland" is contested by hundreds of businesses plus directories plus franchises. "Electrician Te Awamutu" is contested by perhaps four, none of whom have written anything. The Auckland phrase might take two years and may never happen. The Te Awamutu one can be on the first page inside two months.
The volumes look absurd — a town of twelve thousand might generate twenty searches a month for what you do. Twenty searches from people in a town you serve, where you rank first, is a better month than a hundred impressions on page four of an Auckland result.
The practical approach is to work outward from where you are strongest rather than inward from the biggest prize. Win the towns nobody has bothered with, then use the traffic and credibility that builds to have a go at the city.
Where local content goes wrong
Two failures, and the second is more common than people admit.
The first is the template farm: one article duplicated across thirty towns with the name swapped. It is obvious to a reader, obvious to Google, and it tends to result in all thirty pages performing worse than one good page would have. If you genuinely serve thirty towns, write properly about the three that matter most and let a single well-built service-area page cover the rest.
The second is claiming a town you do not really serve. If someone in Whanganui rings and you tell them you do not travel that far, the page that brought them there did you no favours — it cost you a phone call and them their time. Be honest about the radius. "We cover the Waikato within about forty minutes of Hamilton" is more useful to everyone than a list of forty place names.
How much to mention the place
Less than you think, and in specific spots.
Once in the title if the search itself is local. Once early on, so a reader knows immediately they are in the right place. Then only where an example genuinely needs it — which, if the content is properly local, will happen naturally because you are describing real conditions in a real area.
Repeating a town name every second paragraph reads as desperate and stopped helping rankings a long time ago. If a draft feels stuffed, the fix is not fewer mentions, it is more specifics. A paragraph about what the wind does to fences on an exposed ridge is unmistakably local without naming the place at all.
Where this fits with everything else
Local pages are supporting content. Somebody searching "roof repairs Tauranga cost" should land on your article, get the honest answer, and then find a clear way to the page where they can book you. The article earns the visit; the service page takes the enquiry. Keeping those jobs separate is the whole idea behind choosing the page first and the topic second.
It is also worth knowing that generated content is particularly weak here. Ask any AI tool for local colour and it produces Auckland, Wellington, Christchurch and very little else, because it barely knows the rest of the country exists. Everything specific about your area has to come from you, and it is the most valuable thing you can add to a draft.
The test, again
Before publishing anything aimed at a town, change the town name to somewhere else in the country and read it again. If it still makes sense, you have written a national article wearing a local badge, and it will perform like one.
If swapping the name makes the article wrong — because the weather is different, the council is different, the ground is different, the drive is longer — then you have written something genuinely local, and there is a decent chance nobody else in the country has written it at all.