← Blog · Local SEO

How do I write location pages that aren't duplicate content?

By the Found Agents team · October 5, 2026 · 8 min read

Write the page from the place outward, not from the template inward. First list what is true of that county or city and not of the one next door: the plans sold there this year, the published enrollment numbers, the hospital systems clients ask about, where you meet people, who has reviewed you from there. Then write the page around that list. The template, your intro, your form and your disclaimers can stay identical across every location page. The facts cannot. If the list is empty, you don't have a location page to write, and no amount of rewording will make one.

Does Google actually penalize duplicate content?

Not in the way the phrase suggests. Google's own 2008 post on the subject opens with "There's no such thing as a 'duplicate content penalty.' At least, not in the way most people mean when they say that." Google's canonicalization documentation says it "will identify which version of the URL is objectively the best version to show to users in Search" and shows that one. Twelve city pages that say the same thing collapse to one, or to none, with no notice.

The enforceable rules sit elsewhere. Google's spam policies define doorway abuse as pages "created to rank for specific, similar search queries" and give "pages targeted at specific regions or cities that funnel users to one page" as an example. Scaled content abuse covers "using generative AI tools or other similar tools to generate many pages without adding value for users." At small scale, swapped-city pages are invisible; at scale, they are a policy violation. Neither is a penalty for repetition itself. We covered how many pages to build, and in what order, in county pages vs city pages. This post is about what goes on each one.

What does the swapped-city page look like?

You have seen it, and you may own one:

"Looking for Medicare insurance in [City]? Our licensed agents have helped hundreds of [City] residents find the right coverage. Whether you live in [City] or the surrounding area, we offer free, no-obligation consultations. Contact your trusted [City] Medicare agent today."

Cover the city name and it is true of every town in America, which is why it is worth nothing to anyone. Google's helpful-content guidance asks whether a page provides "original information, reporting, research, or analysis" and "substantial value when compared to other pages in search results." The swapped page fails both, and a machine can see that without reading a word: it matches its sibling apart from one token.

The swap test. Finish the draft, then replace the place name with the neighbouring county or city. Count the sentences that are still true. Every one of them is template, not location content. If most of the page survived the swap, you haven't written a location page yet. The three-facts test is the version to run before you start; this is the one to run before you publish.

Where do place-specific facts come from?

This is where insurance agents have an advantage over the plumber most location-page guides are written for. Insurance is sold by geography, and the geography is published.

What changes by placeWhere to get itUnit and cadence
Medicare Advantage and Part D plans, premiums, carriersCMS landscape source files (CY2026 posted; CY2027 already up)County, annual
MA and PDP enrollment and penetrationCMS contract and enrollment data, state/county filesCounty, monthly
Population and share of residents 65 and overCensus QuickFacts and population estimatesCounty, annual
Flood zone (home and P&C)FEMA Flood Map Service CenterAddress
Minimum auto liability, state filing rulesYour state insurance departmentState
Which hospital systems a plan type includesEach plan's provider directory, confirmed before publishingPlan and county
Where you meet clients, carriers you hold, reviews from thereYour own book and your Google Business ProfileYou

Three of those rows are federal data, refreshed on a schedule and free to quote with a link, which is also what an AI assistant needs in order to cite a page. The pull-and-read walkthrough is in where to get Medicare enrollment data by county. For the Census row, the Bureau's June 2025 estimates release reported that almost 45% of counties (1,411 of 3,144) now have more adults 65 and over than children, up from 31.3% in 2020. That is a local, dated sentence, and it survives the swap test.

A six-part outline that stays unique by construction

  1. Title and H1 name the line and the place, once. "Medicare Advantage plans in [County], [State] for 2026" beats "[City] Medicare Agent | Best Rates." Keep the county or city in the URL as well.
  2. The first paragraph answers the place question with a dated figure. How many plans, from how many carriers, what changed, per the landscape file and the month you pulled it.
  3. A "what's different here" section. Two or three short paragraphs, one sourced fact each: enrollment and penetration, the network question local clients always ask, the age profile of the county.
  4. Local proof. Reviews from clients in that place, with permission. Where you meet: your office, the library, the senior center you present at. No competitor and no AI can produce this part for you.
  5. An FAQ of questions people from there actually ask. Pull from your call notes. "Is the regional hospital in network with any PPO here?" is a local question. "What is Medicare Part B?" is not, and belongs on a national page.
  6. The shared layer. Who you are, how an appointment works, the form, the disclaimers, the schema. Identical across pages is fine here. What canonicalization cannot do is invent the five parts above.

Parts one through five cannot be written without the facts list. That is the point: the outline enforces the method.

Can AI write the location pages?

It can draft part six and format the rest. It cannot know your facts, and if you ask it to, it will make them up. Google's guidance on generative AI content says the tools "can be particularly useful when researching a topic, and to add structure to original content," and in the same document warns that "using generative AI tools or other similar tools to generate many pages without adding value for users may violate Google's spam policy on scaled content abuse." The difference is whether you fed the model the landscape file row, the enrollment figure and your own notes, or a prompt that said "write a Medicare page for each of these 30 cities."

How do you keep a location page from going stale?

Date every figure and put the month in the sentence, not in a footnote. The plan list changes every fall: CMS posts the next year's landscape file ahead of the Annual Enrollment Period, and the CY2027 file was already on the downloads page in early October 2026. A page still quoting 2026 plan counts in November is wrong in the one place it promised to be right. Fewer pages, each one current, beats a county-by-county archive nobody has touched since launch.

What about the compliance layer on a Medicare location page?

If the page discusses Medicare Advantage or Part D plans, the marketing rules apply. Under 42 CFR 422.2267(e)(41), a third-party marketing organization that does not represent every plan must carry: "We do not offer every plan available in your area. Currently we represent [insert number of organizations] organizations which offer [insert number of plans] products in your area. Please contact Medicare.gov or 1-800-MEDICARE to get information on all of your options." Those bracketed numbers are county-specific too, so the disclaimer is one more line that changes per page. Add the non-affiliation disclaimer your FMO specifies, don't call a $0-premium plan "free," and keep TCPA consent language on any call or text form. Confirm current wording with your FMO or carriers; this isn't legal advice.

Frequently asked questions

Are location pages considered duplicate content?

Only when they are. Google's 2008 post on the subject says there is no "duplicate content penalty" in the way people mean it; near-identical pages are collapsed to one version, and its spam policies separately treat pages targeted at specific regions or cities that funnel users to one page as doorway abuse. A page built around facts only true of that place, inside a shared template, is not duplicate content. A page that differs from its sibling only in the city name is, and it will usually be filtered rather than ranked.

What should a location page include?

A title naming the service line and the place, a first paragraph answering a place-specific question with a dated figure, two or three sourced facts only true there, local proof such as reviews from clients there and where you meet them, an FAQ of questions people from that place actually ask, then the shared layer: who you are, how to book, disclaimers and structured data. For an insurance agent the place-specific facts come from public sources such as CMS county plan and enrollment files, Census estimates and FEMA flood maps.

How long should a location page be?

Long enough to hold the facts, and no longer. Google's helpful-content guidance states plainly that it has no preferred word count. A page that answers the place-specific question in its first paragraph, carries three to five sourced facts about that county or city, shows local proof and includes a short FAQ usually lands under a thousand words. Padding it with town history and generic insurance explanations makes it longer and worse, because the padding is what would be identical on the next page.

Can I use AI to write location pages?

Yes for the structure and the shared sections, no for the facts. Google's guidance on generative AI says it is useful for research and to add structure to original content, and warns that generating many pages without adding value for users may violate its scaled content abuse policy. Give the model the figures, sources and notes for that place and let it draft around them. Never ask it to produce the facts, because it will invent plan counts, and never generate a page for a place you have no facts for.

Do location pages help with AI search like ChatGPT and Perplexity?

They can, for the same reason they work in Google: a page that states a specific, dated, sourced fact about a county is quotable, and a page of adjectives is not. An assistant answering which Medicare plans are available in a county needs a source that names the number and the year. A location page that opens with that figure and links the CMS file it came from is the kind of page that gets cited, especially with FAQPage schema on its questions.

Where we fit

Location pages built this way, one per county you serve, pulled from the CMS files and refreshed after AEP, are part of our Growth plan. The method above is everything we do; our AEO guide for insurance agents covers the schema around it. Either way: facts first, template second.

Bring us your worst location page

We'll run the swap test on it live, pull the county numbers it should be quoting, and show you what the rewrite looks like.

Book a free 15-minute demo →