Walkthrough graphic for setting up local service-area pages

Service area pages for local SEO without looking like spam | Ethical AI

August 13, 2026•8 min read

A service-area page is a city page for work you drive to. Publish one only when a photo, a review, or a drive-time note proves it.

A service-area page is a city page for work you drive to. It earns a place on the site when it proves you work there. It fails when it is the same paragraph with one city name swapped for another.

Ethical AI is in Frisco. This is for owners who drive to the job. You need a page for a city you already serve, with proof only that city would have. A page you can reprint by swapping one word is a copy, and copies make the real pages harder to trust.

When you actually need one

You need a page when two things are true together.

You regularly take jobs in that city. You can name recent jobs without guessing. One old ticket is not a service area.

You can show a photo, a review, or a drive-time note. One is enough to start. None of them means the page waits. You do not need a page for a city you visited once. Leave it off the site until the work repeats and you would show the proof to a customer.

Before you open a new URL:

1. Name three jobs in that city from the last few months. If you cannot, stop. 2. Point at one photo from one of those jobs, or one review that names the city, or one honest note about the drive from your shop. If you cannot, stop. 3. Confirm the city is already on the service-area list of your business profile. If it is not, fix the profile first. The site and the profile tell the same story.

A missing page is cleaner than a thin one.

What belongs on the page

Six pieces. A person on a phone should see the proof without hunting.

**The H1 is the trade plus the city.** One H1. Example: AC repair in Plano. Extra claims can sit in a sentence when they are true. They do not get a second heading. Two trades in a serious way means two pages, or an H1 that names the trade this page is about.

**The first paragraph says what you do there and how to book.** Two or three sentences. Name the work in that city, then say how to book: call, or the booking path the rest of the site already uses. Skip the company history and any city portrait copied from a brochure.

**One real job photo from that city.** Not the logo, not a generic truck, and not the van photo already used on the other city pages. Use a photo from a job in that city, captioned with what is in the frame and the city name. No photo means the page waits, unless a review or a drive-time note carries the proof. Do not borrow a photo from another city and change the caption.

**A review that names the city, if you have one.** Quote the customer. The sentence that names the city is the proof. If none of your reviews name a city, skip the block. Do not invent a quote.

**The same NAP as every other page.** NAP means name, address, and phone. Spell the name the same way everywhere. Publish the shop or home-base address you already use, not a made-up address in the city this page covers. Use one phone number on every page.

**A click-to-call number in the header.** The reader is often on a phone. The number at the top is tappable, and it matches the NAP and the profile. Do not bury it under a footer form.

A drive-time note can sit in the opening or under the photo when photos are thin: how long the drive from your shop usually takes, and which days you already run that way. Write only what you would say in the driveway.

What to leave out

**Fifty city pages launched the same day, with no photos.** Proof for three cities means three pages. The next city waits until it has a photo, a review, or a drive-time note.

**A map embed and nothing else.** A map shows that you can paste a map. It does not prove you work there. Add one only after the photo, the review, or the drive-time note is already on the page. If the map is the only local thing, finish the page or remove it.

**Keyword soup in the footer.** A comma-separated list of cities under every page does not replace a real service-area page. A city that deserves a name gets its own page with proof, or one line on a list that matches the profile.

Also leave out a welcome-to-the-city block, a street address in a city where you have no office, and any block you reuse by changing only the city name. Leave out any promise of a map position or a call count. A clear page helps someone who already needs the work decide to call. It is not a ranking guarantee.

The profile list and the site list are one list

The business profile lists service areas. The website lists cities. Those lists match, or you are telling two stories.

If the profile lists five cities and the site lists twenty, the extra fifteen do not help. They name places you told the profile you do not cover. The shorter list is the safer story: cities where you regularly take jobs and can show a photo, a review, or a drive-time note.

Compare them on paper. Profile cities in one column, page cities in the other. The overlap is the candidate list. Write the proof beside each city and cross out any city with none. Cities only on the site come off the site. Cities only on the profile can stay there when you really work them, and they wait for a page until the proof exists. If you would not say a city out loud to a customer in their driveway, take it off both lists.

The home page names the business and the home base once. The Ethical AI home page is one business with one home base. Your city pages should work the same way: one name, one phone, one address, and a clear admission that these are places you drive to.

A worked example

This is the shape of one page, using AC repair in Plano as the pattern. Fill every blank from your own job. It is not a client and not a result. In the pattern, the shop is in Frisco, Plano is a route you already drive, Plano is already on the profile, and you already have a Plano photo or a review that names Plano.

**H1:** AC repair in Plano

**Header:** the business name, spelled the same way as on the home page, and the click-to-call number you already use on the shop and the profile.

**Opening:**

We repair air-conditioning systems on homes we already reach from our shop in Frisco, and Plano is on that route. [One sentence from a recent Plano ticket: the equipment and the kind of building.] Call the number at the top and we will book you on a day we are already headed that way.

Now change Plano to another city. The route sentence and the ticket sentence should break. If they still read fine, they are stencil. This is the version that fails the test. Do not publish it:

We are the trusted team for AC repair in Plano. We serve Plano and nearby areas with fast, reliable work. Contact us today for AC repair in Plano.

Every sentence in that version survives a city swap. Mark any sentence in your draft that does the same. Replace it from the ticket, or cut it.

**Photo:** the Plano job, captioned with what is in the frame and the city. A photo from another city means this page waits.

**Review:** the customer's sentence that names Plano, unchanged. No such sentence means no review block.

**NAP:** the name, address, and phone already on every other page. No Plano street address unless that office is already on the profile.

**Drive-time note:** one sentence you can say out loud.

The next city gets this same shape and none of these sentences. It needs its own photo, its own review, or its own drive note.

How to draft it so a city swap fails

Keep one folder per city: one photo, one review if you have it, and three lines of job notes. The draft starts in the folder, not on the last city's page.

If you use a model, the proof stays in your notes. The model does not get to invent a city, a quote, or a drive time. Move the same notes through this order.

**Claude.** Paste the notes for that one city and ask for an outline only. It does not add cities, reviews, or numbers you did not type.

**GPT.** Turn the outline into a draft of the H1, the opening, and the line that says how to book. Copy the caption and the review from your notes.

**Grok.** Mark every sentence that stays true if the city name changes. Rewrite those lines from the job notes.

**Gemini.** Check the draft for one H1, the opening, one local photo, a review only if it names the city, the same NAP, and click-to-call in the header. Report gaps. Do not fill them with new claims.

**Perplexity.** Confirm the spelling of one public place name you already mean to print. If you cannot confirm it, cut it. Do not ask for cities to target.

Don't have Claude? No problem. Start at GPT with the job notes.

Don't have GPT? No problem. Start at Grok for the outline and the swap test, then run the swap yourself.

Don't have Grok? No problem. Draft in Gemini, change the city name yourself, and delete every sentence that still works.

Don't have Gemini? No problem. Keep the checklist next to the draft and use Perplexity only for the spelling check.

Don't have any of them? No problem. Write from the photo, the review, or the drive-time note. A few lines from the driveway are enough.

What to check before you publish

As the customer, you should see the trade, the city, and a tappable number without a lecture. As the skeptic, mark any sentence that survives a city swap, confirm the photo is from this city, and confirm the review names it or is absent on purpose. The NAP matches the home page. The city is on the profile list. You did not publish a second empty city page today.

If that pass fails, hold the page. Then count profile cities against city pages. If the site list is longer, remove pages until they match. When five is the truer list, the extra fifteen do not help.

One page this week

Pick the single city you already drive to that has a photo or a review and is already on your profile. Write that page in the shape above. Leave every other city on a note until it has the same proof.

If the profile list and the site list disagree, or you are holding a stack of pages that differ only by the city name, book a short call. Bring both lists. Keep the pages that prove the route, and take the rest down to the list you can say out loud.

Ethical AI · Frisco, TX · 469-669-2728

AI Chief

AI Chief

Ethical AI: Explore AI's future and ethical considerations. Discover insights and resources for businesses interested in ethical AI practices.

Back to Blog