Article

The Pre-Writing Checklist for City Pages That Aren't Duplicates

A repeatable habit for finding what's actually different about each city before you write about it, instead of a new way to reword the page you already have.

By Brandon Kelly · Updated June 2026 · 7 min read

Duplicate city pages are not a writing problem, they are a research problem: nothing city-specific existed before the page got drafted. The fix is a repeatable pre-writing checklist, run once per city, that pulls together completed jobs, local conditions, permitting or HOA friction, and the landmarks customers actually use as reference points. If a city cannot fill that checklist yet, it does not get its own page until it can.

The pattern behind every duplicate city page

Almost every duplicate city page starts the same way. One page gets written, usually for the city where the business is based, and the same page gets copied across every other city on the list. The city name changes. Maybe a line about "proudly serving [City]" gets swapped in. The service list, the reasons to hire, the closing pitch, all stay identical, because none of it was written about a specific place to begin with.

The instinct at that point is to fix it with better wordsmithing: reorder the paragraphs, swap a few adjectives, write three different versions of the same intro. That produces pages that read differently and say nothing differently. The sentence structure was never the problem. Nobody gathered anything true and specific about that city before the page got written, so there was nothing for the wordsmithing to work with. That is the same discipline behind any content marketing built for a business with more than one service area: the writing only holds up if there is real material behind it.

Where real city-specific material actually comes from

City-specific material is not something you invent at the keyboard. It comes from four places, and if a business cannot point to any of the four for a given city, that is the actual reason the page reads generic.

Jobs completed there

What you did in that city: the type of property, the kind of job, what the site conditions were like. A completed job is a specific, checkable fact, and it is the single best source of city-specific material. It is also the one most businesses skip, because it takes a phone call or a look through old invoices to dig up.

Local conditions

Soil, water table, storm exposure, older housing stock versus new construction, canal-front lots versus inland lots. These vary from one Southwest Florida city to the next, and they change what a job actually involves once you are on site.

Permitting and HOA friction

Every city, and every HOA inside it, has its own quirks: which permits a job requires, how long the county or city takes to turn one around, whether a deed-restricted community layers its own approval on top. A business that has run into this friction firsthand has something no template page has.

Landmarks customers use as reference points

Not landmarks for decoration. The cross streets, neighborhoods, and reference points a real customer in that city would use to describe where they live, the way they would give directions to a friend rather than the way a tourism brochure describes the city.

None of these require a client roster or a set of numbers to back them up. They require having actually been there and paid attention, which is also what makes them impossible to fabricate convincingly. That firsthand detail is the same thing covered in E-E-A-T for local service content. A page missing all four is easy to spot, because it reads like it could belong to any city on the list.

The pre-writing checklist to run before a word gets written

Run this per city, before opening a blank document. If most of the boxes are empty, that is your answer about whether the page should exist yet.

  1. Can you name at least one completed job in this city, specific enough that a customer from there would recognize it as real?
  2. Do you know anything about this city's housing stock, terrain, or climate exposure that changes how the job gets done here versus a neighboring city?
  3. Have you, or has anyone on the team, actually pulled a permit, dealt with an inspector, or worked inside an HOA's rules in this specific city?
  4. Could you name three streets, neighborhoods, or landmarks a resident of this city would use, without looking them up?
  5. Is there a reason a customer in this city specifically would call you, something beyond already serving the area?
  6. If the city name were removed from the page, would a local reader still be able to tell which city it was written for?

A business building out location page content for several cities at once should run this checklist on every city before any of them get written, not just the first one. The first page usually gets the most attention because it is the founder's own city. The fifth and sixth pages are where the checklist matters most, because that is where the shortcuts start.

What a city-specific paragraph looks like next to a generic one

A generic version reads like this: "We proudly serve homeowners in [City] with fast, reliable service and a commitment to quality." That sentence is true of every city on the list and therefore true of none of them.

A specific version, built from the checklist above, might read like this instead: "Homes in the older inland neighborhoods here often run on well water and septic rather than city utilities, which changes what gets checked before a job starts. On the barrier islands, older construction built before current wind codes needs a different approach than new builds on the mainland." Neither sentence needs a client count or a percentage attached to prove itself. It proves itself by being something only a business that has genuinely worked there could have written.

When a city doesn't clear the checklist

Some cities on a service list will not clear the checklist yet, and that is a normal outcome, not a failure. A city you have never worked in, know nothing specific about, and cannot name a real landmark for is not ready for its own page. Publishing one anyway just adds another thin page to the site, and a pile of thin pages drags down the pages that are actually earning their keep.

The honest move is to leave that city off the page list for now and list it as a service area instead, the way a multi-location business handles coverage without pretending every city has its own dedicated content behind it. See how this plays out across a real service area in city and service-area pages for Southwest Florida, or in the broader case for multi-location local SEO. Once a real job happens in that city, the material for a real page exists, and the page can get written from something true instead of something padded.

Running this checklist for every city on the list, before any of them get written, is what actually keeps location pages from reading like the same page over and over. If you want a second set of eyes on which of your cities are page-ready and which need a plan first, a free audit is the place to start.

Frequently asked questions

Only the cities where a business actually has something specific to say: completed jobs, familiarity with local conditions, and landmarks customers recognize. A business with real work in six cities and none in a seventh should have six pages, not seven.
Rewriting only hides the problem. If two pages are built from the same generic claims with a city name swapped in, rewriting them into different sentence structures still leaves two pages that say nothing specific about either city. The fix is gathering real material for each city first, then writing from that.
Anything a business actually knows about that place: jobs completed there, local conditions like terrain or storm exposure, permitting or HOA quirks encountered on the job, and the streets or neighborhoods a real customer from that city would recognize. General claims about quality or reliability do not count, because those apply equally everywhere.
That happens, and it is fine to say so honestly instead of inventing differences that do not exist. If two neighboring cities really do share the same conditions and the same type of work, one page that names both service areas is more honest than two pages pretending to be different.
It is better to wait. A page built before real work has happened in a city usually ends up generic by necessity, since there is nothing specific yet to draw from. List the city as a service area in the meantime and write the dedicated page once real material exists.
Whenever a business starts doing regular work in a new city, or picks up enough jobs there to have real material to draw from. There is no fixed schedule. The trigger is the work itself, not the calendar.
Ready to get found?

See where you stand in Google and AI search

We will run a free audit of your local rankings and your visibility across ChatGPT, Gemini, Perplexity, and Google AI Overviews, then show you the fastest path to more booked jobs.

Call (239) 747-0465Free audit