A customer across the river: describing where you travel

Describe your service area using the towns you actually visit, the work you accept there, and any conditions that affect the trip. A customer across a river should be able to tell whether you can help before sending an inquiry. A large colored circle on a map rarely answers that question by itself.

This matters when the shortest line between two addresses differs from the route you would drive. It also matters when your business accepts a substantial project farther away but cannot make the same trip for a small appointment. Those are useful distinctions. Put them into words customers can act on.

Start with recent journeys

Make a private list of the places your business has served recently. Use your own job records, with customer details removed before sharing them with a writer. Beside each town, note the service provided, typical travel conditions, and whether you would accept similar work again. Past coverage is evidence to consider, not an obligation to keep offering the same territory forever.

Then list the places you want to serve. Keep these separate from completed work so nobody turns a future goal into a claim about established coverage. The owner should confirm which proposed areas can be handled now. If a route depends on combining several appointments, say that in the planning notes.

The result should be a short operating description that the person answering inquiries recognizes. If that person would reject requests from half the towns on the list, revise the list before publishing it.

Explain the crossing that changes the decision

A state line or river can create a question even when the destination is familiar to your team. Customers may wonder whether you travel across it, whether a different charge applies, or whether the service changes. Answer the questions your business can answer accurately without trying to write a regional travel guide.

For a hypothetical service company, the useful distinction might be that routine visits are available in its regular territory while longer trips require a project description first. That wording is more informative than saying the company covers an entire region with no conditions. It also gives the customer a sensible next step.

Avoid publishing driving times as permanent facts. A route can vary with the starting address, time of day and current access. You can describe the towns served and ask for a postal code without promising an arrival time before reviewing the request.

Separate a service area from a place customers can visit

A page about serving a town does not establish a branch there. Use verbs that describe the relationship: travel to, deliver to, serve customers in, or arrange appointments in. Reserve phrases such as "visit our location" for a real customer destination.

Google requires an accurate address or service area in its Business Profile representation guidelines. A mailing address is not a substitute for an operating location.

Keep that distinction consistent in headings, map labels, photos and contact details. A heading can say that your team serves a town, while the contact page explains how appointments are arranged. Do not place a map pin at a convenient landmark merely because it makes your coverage look more local. A reader could treat it as directions.

Our local search services include reviewing how a business describes its coverage across its website and listings. The starting point is always the real operation, including the places it can reasonably serve.

Write coverage at the service level when needed

Not every service has to share the same boundary. Delivery, installation, collection and on-site consultation may involve different journeys. If your business offers several, a single broad coverage sentence can leave readers with the wrong expectation.

Add the relevant condition close to the service description. A hypothetical shop might allow collection from its premises while quoting delivery separately. Its product pages should explain both options rather than letting a footer statement imply that delivery is included everywhere.

Use a small table only when the distinctions are easier to compare in rows. Otherwise, a few sentences work well. State what is offered, where it is offered, and what information is needed for an exception. Avoid filling a page with town names that add no new meaning.

Ask for enough location information

At the first inquiry, a town and postal code may be enough to decide whether a request is in range. Ask for a full address when the next step actually needs it. Requiring detailed directions before you know whether you offer the requested service adds work for both sides.

Explain why you ask. "Your town helps us check travel coverage" gives the field a purpose. A customer near a boundary can also use an optional note to identify the area without having to choose an inaccurate town from a fixed list.

Make the reply useful when you cannot take the request. An accurate explanation of the boundary is better than silence. Keep internal notes about rejected locations so you can see whether your website is encouraging inquiries you routinely decline.

Test the wording against real questions

Ask a colleague to read the coverage page as someone who has never used the business. Can they answer whether the team travels to them, whether a visit must be booked, and whether the displayed address is a place to visit? Have them try a location near the edge of your territory as well as one near the center.

Look for contradictions between the page, inquiry form and listing. A form that rejects a valid postal code undermines an otherwise clear coverage description. A directory that still lists a former branch can send a customer on the wrong journey even when the website is correct.

Review coverage whenever staffing, travel policy or service scope changes. Give one person responsibility for approving those changes so a writer does not have to guess. If your current pages leave the boundaries uncertain, request a search review with your website and the towns you want to serve. That provides a concrete starting point for deciding what customers need to know.