One service-area page per city, not a list of twenty towns

A row of town names in the footer is not a set of pages. It is one sentence with commas. A person in a city you actually serve needs a page about that city and one job you did there. Ethical AI is in Frisco, Texas. Publish one service-area page for one city you roll trucks to, with one true job story, and take the suburb list off the footer.

A list does not answer the call

Read the footer on your phone. If the towns run together on one line, you do not have a service area on the site. You have a list. The list does not say you have been there. It does not name a failure or a repair. It does not give anyone a reason to trust the drive. It asks them to pretend that naming a place is the same as working there.

A page is different. It has its own address on the site. It has a title a person can say out loud. It has room for one job. It has the shop phone as a tap, with the same digits as the truck. A list item has none of those.

Start from the tickets, not a wish list

Pull the last two months of jobs. Write down the cities that show up more than once. That is the site. A city you visited once for a friend does not get a page. A city you would drive to if the ticket were big enough does not get a page. A hope is not a route.

Most shops that tell the truth land on a handful of cities. That is enough. One page each. The homepage keeps the city you dispatch from, and the phone, above any long form. One city on the first screen is the same habit as click-to-call before the long form. The other cities you truly serve each get a page of their own.

If the footer names a city you have not rolled a truck to this season, delete the name. Do not build a page to justify a drive you rarely make.

What belongs on the one page

The title names one city and the work. Not every neighboring town. Not every trade you could mention if someone asked. If the job was a water heater, the page is about that water heater in that city. If you also clear drains, that can be one sentence. It is not a second page hiding inside the first.

Then the job. One job. Yours. From a ticket. You do not need the customer's last name. You need the work, told so a stranger can picture it.

Say what the customer thought was wrong. Say what you found. Say what you left working. Use the words you would use in the driveway. "No cool upstairs since noon. The capacitor was swollen. We replaced it. The house was cool before pickup." That is a page. A slogan about full-service comfort for the greater area can sit on any site in any state. It does not prove you know the call.

Add the facts a caller uses. Which city. Whether a weekday truck is normal there. Whether after-hours in that city is real, or only on the days you already publish. The phone, same as the listing and the truck. If the hours on this page disagree with the homepage, you have described two shops. Fix that before you write the next city.

Write the story from the ticket

Open the ticket. Leave the price off the page. Read the tech's notes. Write five to eight sentences a neighbor would understand. Keep the city in the title and once in the story. Do not repeat the city name on every line. That is the list habit, moved into a paragraph.

Use the caller's words where you still have them. "The breaker trips when the dryer starts" is a better opening than a category label. Then the work, in ordinary language for the parts. Then the ending. Working, or a return visit you actually scheduled. If you had to come back, say so. A clean lie reads worse than a true second trip.

If the notes are short, stay short. "No heat. Flame sensor cleaned. Heat restored. Tuesday." That becomes a small true paragraph. A copied block with the city name swapped in does not become true because you changed one word. Anyone who opens two of your city pages can see the swap. Write each story from its own ticket.

Ask the tech who ran the call to read it before you publish. If they say the story is wrong, it is wrong. The page has to survive the person who was on the roof or in the attic. Get permission before you name a street or show a face. A photo, if you use one, comes from that job or from your truck.

What to leave off

Leave the comma list off. One page, one city. Do not invent a job for a town you have not worked. If the only story you have belongs to the next city, put it on that city's page. Do not paste one essay onto eight addresses and swap the city name. Do not claim the page will move you up a map or fill the week. You do not control that. You control whether the page matches a truck you already sent.

The footer only names pages you built

A short footer is fine when every name links to a real city page built from real tickets. A town with no page does not belong there. The listing should name that same area, without a dump of every town in the description. The phone on the city page is the phone on the truck. A different number sends the caller to people who never read the page.

Finish one page before the next

Read the draft as a homeowner. Is the city obvious on the first screen? Is there one job, with a start and an end? Can you tap the phone? If any answer is no, the page is not ready. Do not start the next city to feel busy. A few honest pages are easier to trust than a footer full of towns with nothing behind the names.

Tonight

• List the cities on real tickets from the last two months.

• Remove footer towns you do not regularly serve.

• Write one page for one of those cities, from one ticket.

• Put the shop phone on it, same digits as the truck and the listing.

• Have the tech who ran the call read the story before you publish.

Ask for the review the day that city job is finished, on the one listing, the way when to ask for the review lays out.

Need the page to match the cities you already drive? Start at get started. One city, one job, one phone. Ethical AI · Frisco, TX · 469-669-2728.