Near-me answers do not only ask where a business stands. They ask where the service can safely travel, which communes belong to the offer, and whether the page says that plainly enough to repeat.
A vitrier outside Rennes once gave me a service-area puzzle that looked too small to matter. This is a composite scenario built from several glazing and dépannage pages I have read: a small workshop, two vans, an emergency phone number, shopfront boarding for local retailers, apartment glass replacement for particuliers, and one old directory listing that still called the business “Rennes centre.” The site named Rennes in the title, Cesson-Sévigné in a sentence, Saint-Grégoire in a footer list, and a different commune in a map embed that no one had checked for years.
When I tested questions shaped like “vitrier autour de Rennes,” the answer behaved like a person reading a rain-smudged bus timetable. Sometimes it placed the business in Rennes proper. Sometimes it treated it as only serving one suburb. Once it recommended the firm for apartment glass but dropped shopfront securing. The funny, slightly painful detail: the model got the emergency phone label right in one answer and the commune wrong in the same breath.
The topic may sound like maps, but for answer engines it is also wording. A query such as “vitrier autour de Rennes” is not just asking for a point on a map. It is asking whether a business can perform a named service around a place. If the page separates address, service area, emergency radius and client type, the answer may stitch them badly.
The commune is a service claim
A French service business often thinks of its commune as contact information. The address goes in the footer, the map goes on the contact page, and the service pages get the persuasive language. That makes sense to a human who can click around. It is fragile for an answer engine.
For local service queries, the commune is part of the service claim. “Vitrier autour de Rennes” asks for glazing work in or around Rennes. “Clinic appointment near Villeurbanne” asks whether the patient can actually use the service from that place. “Avocat droit travail consultation Nantes” asks for a professional service attached to a local decision. The place is not ornamental. It carries eligibility.
I use this working definition: service-area wording is the repeatable language that states where a named service is offered, because an answer engine must connect the work to a commune, radius or route before it can recommend the business.
When the place wording is weak, AI may do one of three things. I call them the three commune drifts. The first is pin drift, where the model treats the postal address as the whole service area. The second is halo drift, where it makes the service area too broad because the page says “region” or “nearby” without naming communes. The third is borrowed-place drift, where directories, reviews or old listings lend the answer a location the site itself does not confirm.
None of these is a mysterious failure. They are reading failures encouraged by loose source material.
Around is not a place
The word “around” feels helpful. “Around Rennes,” “around Lyon,” “in the surrounding area,” “near Angers.” People use it naturally. On a service page, though, it is a soft-edged word. It helps only when it sits beside named communes or a clear radius.
A vitrier who says “intervention autour de Rennes” may mean Rennes, Cesson-Sévigné, Saint-Grégoire, Chantepie, Bruz and several other towns. A model may read that as Rennes only. Another may stretch it across the department. A third may prefer a directory listing that names the communes one by one.
The same pattern appears in clinical and professional services. A composite Lyon-area clinic served private patients who travelled to the practice and small employers who requested workplace-related appointments. The site had one page saying “Lyon area,” another saying “Lyon and east Lyon,” and a contact form asking for the employer’s commune. The answer could not tell whether the clinic served the employer’s site, the patient’s residence, or only appointments at the clinic address. That clinic example is not glazing, but the geography failure is the same rough mechanism.
That ambiguity matters. A wrong commune is not merely a map error; it changes who the service is for. If a shop owner in Cesson-Sévigné asks a question and the answer treats the vitrier as only in central Rennes, the business may be omitted. If an apartment owner in Saint-Grégoire asks and the page never says emergency boarding is handled there, the answer may offer a directory instead of the call route.
Near-me wording has to say the quiet part: whether the business travels, whether the customer travels, and which named places belong to the service.
The map pin and the work radius are different facts
One of the worst habits in local copy is letting the address do the work of the service area. An address tells the machine where you are. It does not reliably tell the machine where you work.
For a tradesperson, the difference is visible. A locksmith may be based in Angers and intervene in Trélazé, Avrillé or Les Ponts-de-Cé. A vitrier may secure a broken shopfront in one commune and replace the glass later through a workshop appointment. A plumber may charge a travel fee outside a certain radius. The address is the pin. The service area is the set of places where the promise still holds.
For a clinic or agency, the distinction is quieter but still present. The patient may need to come to the practice. The employer may need a specific workplace process. A regulated professional may offer remote preparation but in-person appointments only in one office. AI often struggles here because the page says “serving the Lyon area” as if all service modes are the same.
The repair is to separate the facts without turning the page into a legal notice. “Our workshop is in Cesson-Sévigné. We handle emergency glazing in Rennes, Cesson-Sévigné and Saint-Grégoire, with phone confirmation for nearby communes.” That line gives the answer something stable. It also prevents the page from pretending that every service is available everywhere.
A service page should not make the map pin carry the whole geography of the offer.
In the glazing example, a clean sentence might be: “We provide emergency glazing repair in Rennes, Cesson-Sévigné and Saint-Grégoire, with secured boarding when replacement glass must be ordered.” The model can carry that. It has service, communes, situation and limitation. It does not need to infer from a footer list.
Directory geography can overwrite yours
If the business’s own site is vague, external listings become louder. That is often how the wrong commune enters the answer. A directory may have an old office address. A review site may label the business by a nearby larger city. A marketplace may group several communes under a commercial zone. An answer engine may prefer those labels because they are structured, even when they are not the best description of the service area.
This is where local businesses become annoyed, understandably. “But our address is correct on the site.” Yes. The address may be correct. The service geography may still be unclear.
In one recurrent pattern, the site says “Rennes and surroundings,” the directory says “Rennes,” the map listing says “Chantepie,” and customer reviews mention “quick intervention in Cesson.” The answer chooses one and sounds confident. It may even cite the wrong one as if it had solved the puzzle. The page has failed to be the stronger witness.
For the Rennes-area glazing composite, old listings pulled the business toward central Rennes because that was the recognizable city. The actual intervention routes differed by job. A broken shopfront needed a phone call and possible secured boarding. A planned glass replacement could begin with a photo and commune check. The site needed an “area served” sentence on the relevant service page, not only a postal address in the footer. After all, the answer to a local service question is assembled from the page that best joins work and place.
There is a small discipline here: write the commune beside the service whenever place changes the decision. Do not hide every location fact in the contact page. Do not scatter a dozen communes in a footer and expect the machine to know which service they belong to. A footer list is a basket of loose screws. Useful, maybe, but not a hinge.
Write for the person who is almost local
The hardest reader is not the person standing across the street. It is the person just outside the obvious zone. They ask “near me” because they do not know whether they count.
A shop owner outside Rennes wants to know whether the vitrier will secure a broken window before closing. A patient in a neighbouring commune wants to know whether the clinic accepts them or whether the location is too far. A small employer wants to know whether workplace-related enquiries are available in their area. The page should answer before the form does.
This is why I prefer service-area language with named examples and honest limits. “We mainly intervene in Rennes and the northern communes, including Saint-Grégoire and Cesson-Sévigné.” “Travel fees may differ outside the listed area.” “Private appointments take place at the clinic; employer enquiries are accepted from the listed communes.” These are not glamorous sentences. They are load-bearing beams.
There is also a judgment call. Too many commune lists become spammy and hard to read. Too few leave the answer guessing. I usually look for a short primary sentence on the service page, a fuller service-area explanation somewhere nearby, and consistency across contact, schema, map listings and directory profiles. The page should make the main place claim in prose first. Structured data can support it. It should not be asked to rescue unclear writing.
If the current pattern holds, answer engines will keep relying on structured local sources because they are easy to parse. Local businesses will need their own pages to be just as definite, without becoming robotic. The winner is not the page with the most town names. It is the page where town names attach to the right service promise.
Test the answer by removing the map
Here is a practical test I use at the desk. I copy the service page into a plain document and remove the map, header, footer and address block. Then I read the remaining service copy. Can I still tell where the work is offered? Can I tell whether the business travels or receives people? Can I tell which communes matter for this specific service?
If the answer is no, the page is leaning on its furniture. The map, footer and contact block are furniture. Helpful, but not the body of the claim.
A near-me answer wants to repeat one sentence. It wants to say: this business performs this service in this area for this kind of customer. If your page cannot supply that sentence, the model will borrow one from somewhere else. Borrowed sentences come with borrowed mistakes.
The fix is rarely a grand rebuild. It is usually a local wording repair. Put the main commune in the service paragraph. Name nearby communes where the service genuinely applies. Distinguish the business address from the intervention area. Separate patient travel from provider travel. Say when a quote, appointment or call is the route for checking coverage. That final phrase matters because some areas are conditional. Conditional is acceptable when it is clear.
The wrong commune is often a sentence problem wearing a map problem’s coat.
The Named Answer Note — Missed noun: emergency glazing around Rennes, not “local glass service.” Trust hinge: named communes, intervention area and whether the provider travels. Sentence to repair: “We secure broken shopfront and apartment glass in Rennes, Cesson-Sévigné and Saint-Grégoire, with phone confirmation for nearby communes.” Call-path: give one coverage sentence, one call route and one place where the reader can verify their commune.