Should I Build Service Area Pages? A 5-Step Test

Ask this question in any local SEO forum and you will get two confident answers within an hour. One says build a page for every town you serve. The other says never, they are doorway pages and Google will bury you. Both answers are wrong in the same way: they are arguing about page quality when the decision actually turns on demand.

Here is the honest version. Service area pages are worth building for a small number of towns and a waste of your evenings for the rest, and you can tell which is which before you write a single word. Below is the test, the evidence behind each step, and what to do with the hours if the answer comes back no.

The short answer, and the question to ask instead

Yes, if a specific town clears five tests. No for every town that does not, and no as a blanket strategy applied to a radius on a map.

The version of this question everyone answers is "how do I make service area pages that do not get penalized." That is a real question, and there are decent guides on it, including one from Whitespark that lists twenty elements a strong page should carry. But it starts one step too late. Making an excellent page for a town nobody searches for is still a wasted week. Run demand first.

Test 1: Does anyone in that town type the town name?

This is the step that gets skipped, and it is the one that decides most cases.

There are two different local searches, and they behave nothing alike. A geo-modified search spells out the place: "landscaper Burlington." A geo-implied search does not: "landscaper," typed by someone standing in Burlington, with Google supplying the location silently. A service area page can compete for the first. It has very little to do with the second.

The uncomfortable part is the split between them. A commenter on r/SEO put it bluntly about their own market: most users do not search "digital agency Berlin," they search "digital agency," and Google appends the place. Your trade may skew differently, but the assumption that a meaningful volume of people are typing your town name is exactly that, an assumption, and it is checkable in twenty minutes with Search Console and Keyword Planner.

Now the case study. An agency marketer posted on r/SEO in 2026 under the title "40 location pages, almost zero clicks, but we're ranking locally." They had built roughly forty pages covering suburbs and towns in a fifty to hundred mile radius. Sixteen months of Search Console data later, most of those pages sat at single-digit clicks. Yet when they searched incognito from inside those cities, the site came up third or fourth on a good chunk of them, and a few even pulled map pack appearances.

Ranking, and nothing to show for it. Local SEO consultant Joy Hawkins replied with the line that explains it:

That is the trap. You check your rank, you see position three, you feel good, and the page has never produced a customer. Rank checking tools and bots generate impressions in Search Console, which inflates the number that makes the page look alive. Clicks do not lie in the same way, and phone calls lie even less.

The test: for each candidate town, does "your service + that town" get searched by humans in numbers you would care about, and is anyone actually clicking? If you cannot answer yes with data, the page is a hobby.

Test 2: Have you done paid work in that town?

If test one is about whether anyone is asking, test two is about whether you have anything to say.

A page for a town you have worked in writes itself: three jobs with street-level context, your own photos, what the housing stock does to your quoting, which permit office is slow. A page for a town you have never driven to has to be invented, and invention is exactly what reads as filler to both a homeowner and a ranking system.

There is also a harder ceiling. One practitioner on r/SEO who has published location pages at volume described the pattern they see repeatedly: pages built around the registered business address rank and stay ranked, while pages mass-published for cities far from that address simply do not, regardless of how the content is written. Their conclusion was that distance from the real address predicted outcomes better than content uniqueness did.

That matches what Google is doing structurally. Proximity is a heavy local ranking factor and it radiates from where you actually are, which is also why hiding your address on a Business Profile does not extend your reach. We covered that configuration trap in detail in the service area business setup guide.

The test: can you name at least three real jobs you have completed in this town, with photos? If not, the page is a claim, not a page.

Test 3: Is the page a destination, or a funnel?

Here is the part almost nobody quotes correctly, so let us go to the primary source. Google's spam policies were rewritten to call this "doorway abuse," and the definition is narrower and more useful than the folklore:

Read the mechanism. The violation is not "you made a page about a city." The violation is that the page is an intermediate stop that exists to catch a query and push the visitor somewhere else. That is a structural test you can apply to your own page in ten seconds.

A page that ends in "we also serve Milton, click here to see our services" is the doorway pattern by Google's own example. A page where the visitor can read your coverage terms for that town, see work you did there, and book you without leaving is the final destination, which is the thing doorway abuse is defined against.

This is also why the popular alternative answer fails. "Just put all your towns on one areas we serve page" sounds safe until you read Google's keyword stuffing policy, which lists as an example of the violation: "Blocks of text that list cities and regions that a web page is trying to rank for." The wall of town names is named in the documentation as explicitly as the thin city page is.

And a third policy catches the modern version of the mistake. Scaled content abuse covers "many pages generated for the primary purpose of manipulating search rankings and not helping users," with generative AI tooling called out by name. A contractor on r/SEO described exactly this setup: 113 cities on the service area page, a landing page for each, plus a page for each of four services in each city, 565 programmatically generated pages in total. Asked whether they were unique, the owner conceded they were the same, city name aside. The first substantive reply pointed at scaled content abuse and made the useful distinction that the policy is not about duplication, it is about the means of production.

Three policies, one decision. That is unusual, and it is a fair signal of how carefully Google has looked at this exact tactic.

Test 4: Will you still be maintaining this page in a year?

Location pages decay quietly. They do not throw errors, they just stop being indexed.

A consultant on r/localseo posted about a pattern they had never seen before: local pages that had been indexed for months sliding into "Crawled, currently not indexed" in Search Console. Their pages were not templated slop. Each carried location-specific projects, code and inspection differences for that jurisdiction, and outbound links to the relevant authority. Some had earned links from local press. They still fell out.

The community diagnoses landed on two things: the services block repeated identically across every page, and site-level authority not being deep enough to carry that many URLs. Their own frustration is worth quoting, because it is the part that stings: competitors running pure copy-paste city pages with a decade of domain history behind them stayed indexed the whole time.

Which is the real lesson. These pages are not free. They are an ongoing commitment that competes for the same attention as your reviews, your Business Profile, and your quoting. The marketer with forty dead pages summed it up in the post title thread: a neglected thin page that slowly decays feels worse than no page at all.

The test: if this page will not be touched again for eighteen months, do not publish it.

Test 5: Is this the best use of the same hours?

Every serious answer to "should I build service area pages" is really an answer to "compared to what."

Service area pages are a slow organic play. They rank over months, they rank in the blue links only, and their ceiling is capped by your domain's overall authority. That can be a genuinely good deal for a business that already ranks and already has jobs in those towns. It is a poor deal for a business whose phone is quiet this month, because organic will not fix that in the timeframe the payroll runs on.

The blunt version of this came from a commenter on r/localseo, and while it is more pessimistic than we would go, it is worth sitting with: they argued the pages are a waste of time because they do not carry enough authority to rank on their own and will never outrank a dedicated homepage, and that the same effort spent turning your finished work into content builds more local authority. That is at least half right. It is definitely right for a site with no authority to spend.

The test: if you had the same twenty hours to spend on your Business Profile, on getting reviews from customers in those towns, on your quoting speed, or on paid campaigns targeted at those towns, would the city pages still win? Sometimes yes. Often no.

What service area pages will never do

Setting the expectation correctly saves more disappointment than any tactic here.

The "near me" gap is the one that surprises people. Contractors report the split constantly: a page that ranks third for "teeth whitening Frederick MD" and is nowhere for "teeth whitening near me" searched from inside Frederick. One r/localseo commenter described the same thing for their market, noting the page helps for location-modified keywords but gives you very little for near me when your business sits in a neighbouring town.

The AI answer is similar. The same commenter checked what Gemini does with a local query and found it announces that it is searching Google Maps. Local recommendations in AI assistants are largely a re-serving of the map pack, which means your Business Profile and your reviews are doing that work, not your website. If neighbouring cities are the actual goal, the honest options are laid out in how to rank in a city with no office.

The last row is the one worth defending. Even a page that never ranks can earn its keep by closing a visitor who arrived from your Business Profile or a referral and wants to confirm you actually cover their address. That is a conversion asset, and it is a legitimate reason to build a small number of these.

Name them honestly

A distinction most contractors get wrong, and one with more downside than SEO.

A location page represents somewhere you physically are. A service area page says you drive there from somewhere else. SEO consultant Bill Hartzer, arguing this on r/localseo, said he only gives clients a location page where they have an actual office, and that everything else is an areas we serve page. His reasoning was not about rankings:

For a contractor the stakes are lower than a bar association complaint, but the customer experience is identical. A homeowner who reads "Our Milton Office" and later learns you drive an hour from two towns over has been misled, and that shows up in the review, not in Search Console. Write the page as "Plumbing in Milton" or "Areas we serve: Milton," never as a location you do not occupy.

If you pass the test: the build order

Assume two or three towns cleared all five tests. Do not build them in parallel.

1. Start with the strongest single town. Highest demand, most completed jobs, most reviews from customers there.
2. Write it as the destination. Coverage terms for that town, your minimum for a call-out there, three real jobs with your own photos, permit and inspection reality for that jurisdiction, reviews from customers in that town, and a form that submits without a second click.
3. Link it properly. From your services pages and from a plain areas we serve page written in sentences, not from an orphaned sitemap entry. Google's doorway examples specifically call out pages that are "closer to search results than a clearly defined, browseable hierarchy."
4. Leave it a full quarter. Watch clicks and calls, not rank.
5. Then decide about town two. If page one produced nothing in a quarter, town two will produce nothing either, and you have saved yourself thirty-eight pages.

On depth, the guidance from practitioners running these for small service clients is consistent: eight hundred to fifteen hundred words of genuinely local content per page, and a total site somewhere in the range of a dozen to fifteen pages covering both services and areas. Not hundreds.

One more practical note. Crawl budget is not your problem at this scale. For a local business with ten services and ten areas, you are talking about tens of pages, and Google indexes vastly more than that daily. The constraint is quality and authority, not crawling capacity, so do not let a crawl budget argument talk you out of five good pages.

If you fail the test: where the hours go instead

For every town that failed, the same effort has better homes.

• Your Google Business Profile. It drives the map pack, the near me results, and most of what AI assistants report back for local queries. It is the highest-leverage surface a service business has and most are half-configured.
• Reviews from customers in the towns you want more of. A review that names the neighbourhood does work no page can do, and it feeds both the profile and any page you build later.
• One strong service page with an honest coverage section. Merging is often the correct SEO answer. If "AC repair in Town A" and "AC repair in Town B" would say the same thing, one strong AC repair page with a real service area section beats both.
• Documenting the work you already do. Job stories, photos, and the specifics of a completed project build the local authority that any future city page would need in order to rank at all.
• Paid, if the phone is quiet now. Organic city pages are a next-quarter answer. If you need work this month, targeted campaigns are the only lever with the right latency, which is most of what our lead generation work is built around.

And if your leads are already arriving from towns you do not want, adding pages for those towns is the wrong direction entirely. That is a targeting problem, covered in why your leads come from outside your service area.

The twenty-minute version

Run this per town, not per radius.

• Does "my service + this town" get searched by humans, with clicks, not just impressions?
• Have I completed at least three paid jobs here, with photos I own?
• Can I write a full section that is true only of this town: housing stock, permits, drive time, coverage terms?
• Does the page end with the visitor able to book me, rather than being sent to another page?
• Will I still update this page in a year?
• Would twenty hours on my Business Profile, reviews or ads beat this?

Six yeses, build it. Four or fewer, do not. And whatever the count, build one page and wait a quarter before building the second.

The bottom line

Service area pages are not a strategy, they are a tool with a narrow correct use. They work when a real town with real demand meets real proof of work you did there, and they fail predictably when they are generated to fill a map. Google has named the failure mode in three separate policies, practitioners have posted the receipts on sixteen months of flat data, and the pages that quietly die do it without ever showing you an error.

Pick your best three towns. Build one. Wait. That is the whole answer, and it costs you an evening instead of a quarter.