Before buying 20 city pages, ask what the office can verify
A useful service-area page helps a homeowner decide whether your shop can take the job. A changed city name cannot supply that answer.
TL;DR
- Buy contractor city service pages around verified coverage and customer decisions. A page count alone cannot establish usefulness or search performance.
- Google's spam policies address doorway abuse and scaled pages made mainly to manipulate rankings. Similar-looking city pages require investigation; repetition alone is not a complete policy verdict.
- In the hypothetical 17-page inventory below, four pages have a clear job, five need verified facts and eight need a decision about meaningful differences or consolidation.
An agency offers an HVAC shop 20 new city pages. Before comparing the writing price, the owner should ask what a homeowner will learn on each page that helps the office accept the right job.
If the answer is the same paragraph with a different town name, the proposal needs a stronger brief. Start with where the trucks actually go, which work the shop accepts and how a customer confirms an appointment.
What should contractor city service pages help someone decide?
A plumbing customer needs to know whether the company serves the address and handles the problem. A homeowner requesting an electrical estimate needs to understand what information to provide and what happens next. Those questions give a page a practical purpose.
Build the purpose from the office's records. Coverage might vary by job type: a shop could accept a planned installation farther away than an urgent service call. Hours for answering the phone might differ from appointment availability. State those differences only when they are true and the office can maintain them.
A city page should also fit the website's service structure. A reader arriving there should be able to understand the business, find the relevant service and make an appropriate request without hunting through unrelated location pages.
This is separate from advertising geography. A website page is not an instruction telling an ad campaign where to show. Review that setting through the Google Ads service-area targeting guide when planning paid traffic.
Where Google's policy enters the buying decision
Google's spam policies, checked October 17, 2026, describe doorway abuse as pages made to rank for similar queries that send readers through less useful intermediate pages. Examples include city pages funneling visitors onward and substantially similar pages without a useful site hierarchy. Scaled content abuse concerns many low-value, unoriginal pages produced primarily to manipulate rankings, however they are created.
Those definitions do not let an owner diagnose a site from the number 20. Inspect the actual pages, what readers can accomplish and why separate pages exist. A template used for consistent navigation can still contain useful information. A template filled with interchangeable promises may add little.
Google's helpful-content guidance, checked the same day, asks whether content contributes original value and gives its intended audience enough information to achieve a goal. It does not prescribe a preferred word count. Use that as a review question, rather than demanding 1,000 words for every town.
Sort a 17-page inventory before commissioning more
This is an original hypothetical audit, not a finding about a real contractor. Assume a shop has 17 existing coverage pages. The review considers what the reader needs, verified office facts and how each page fits the site.
| Group | Pages | What the review finds | Initial disposition |
|---|---|---|---|
| Complete and useful | 4 | Clear service scope, accurate coverage and a usable request path | Maintain |
| Useful purpose, incomplete facts | 5 | A legitimate coverage question, but hours or job limits are missing | Repair after verification |
| Same copy with city names changed | 8 | No established reader benefit from the separate versions | Investigate differences or consolidate |
| Total | 17 | A working inventory, not a policy score | Assign an owner to each decision |
The arithmetic is 4 + 5 + 8 = 17. Thirteen pages need a documented next action; that does not mean thirteen pages should disappear. Five already have a useful purpose that needs supporting facts. The eight repeated pages need investigation before anyone changes their URLs.
For each repeated page, ask the dispatcher whether the location changes an actual customer decision. Is the accepted work different? Are there real service restrictions? Can the page answer a question the broader area page leaves unresolved? Record evidence beside the answer.
If a separate page has no useful distinction, consider combining its coverage information into a stronger regional page. Before changing existing pages, have the website operator identify current links, traffic, inquiries and the technical handling of old URLs. Preserve useful customer information during the change. This inventory is a work queue, not an automatic deletion instruction.
Give the writer a coverage brief the office can verify
Use the following fields as a collection sheet. They are prompts for true facts, not ready-made claims to copy onto a public page.
| Brief field | Evidence to obtain | Publication check |
|---|---|---|
| Actual coverage | Current dispatch area and exceptions | Office can confirm the boundaries |
| Accepted job types | Service list used when taking requests | Page does not advertise work the shop declines |
| Hours and availability | Phone coverage and appointment rules | No unsupported response-time promise |
| Request process | Information the CSR needs to assess the job | Form and phone instructions match the office |
| Local examples | Documented work the business may accurately describe | Permissions and location details are checked |
| Business identity | Actual trading details and offices, if any | Coverage is not presented as a fabricated branch |
Do not fill an empty evidence field with generic local color. A neighborhood name, weather paragraph or landmark reference cannot establish that the company accepts a particular job there.
For example, a writer might propose round-the-clock emergency repair on every page. The brief should return to the person staffing the phone and dispatching technicians. If the shop offers an after-hours answering service with next-day scheduling, publish the actual arrangement. Do not upgrade it into an immediate technician arrival promise.
Apply the same discipline to images. Use real, accurately described work when you have permission, or clearly appropriate general illustrations. A stock truck photograph cannot document a completed project in a named city. Never invent a job photograph, office address or licensing claim to make the page feel local.
Price the deliverable around decisions and maintenance
Ask the agency to identify the reader purpose and required facts for each proposed page before agreeing to a batch. The agency-quote comparison helps separate writing, website changes and ongoing management when those appear under one monthly price.
The scope should also name who checks the coverage brief and who updates pages when service changes. If the shop stops accepting one job type in an outer area, both the office instructions and public copy need attention. Buying more pages increases that maintenance responsibility.
Approve the completed brief and inspect a finished page against it. Count the decisions the page helps a customer make: service eligibility, relevant work and the next contact step. The number of new URLs belongs in the delivery record; it cannot substitute for that acceptance check.
What this doesn't cover
This guide does not determine whether a particular site violates Google's policies or promise rankings, indexing or inquiry volume. A policy assessment requires the actual content and context.
It also does not establish Google Business Profile eligibility, local licensing requirements or a technical migration plan. A city coverage page proves none of those things.
Do this in your account
- Export the existing city-page URLs into a sheet. Record purpose, accepted work and the person responsible for each page.
- Compare a sample against the dispatch rules. Mark facts as confirmed, missing or contradicted.
- Classify pages for maintenance, repair or further consolidation review. Keep the reason beside each decision.
- Complete a coverage brief using records the office can verify. Remove unsupported claims before writing more copy.
- Inspect a finished page, its request path and its place in the website. Assign the next accuracy check.
The agency buyer guides cover the scope and ownership questions to settle with that work.
FAQ
Should every city in our service area have its own page?
Give a separate page a customer purpose before commissioning it. Several places may be served clearly by one regional page, while another location may need accurate detail. There is no useful universal page quota for that decision.
Are eight similar pages automatically spam?
No. Eight is simply a group in this invented inventory. Assess purpose, reader value and the site's structure against Google's policy; then decide whether to improve the pages or combine coverage information.
Can we publish an office address in a city where we only send trucks?
Publish the real coverage arrangement. Do not invent a branch address to decorate a service-area page. If customers cannot visit an office there, the page should not suggest that they can.
Sources
- Spam policies for Google web search, Google Search Central. Read October 17, 2026.
- Creating helpful, reliable, people-first content, Google Search Central. Read October 17, 2026.
Lonta AI handles advertising strategy, setup and ongoing management for home service businesses. Get a free strategy.