An answer engine can see a business and still fail to recommend it. The failure often sits in one dull sentence where the work is described as activity, not as a service someone can ask for.
In a recurrent emergency-search scene, after closing time, a shopkeeper has a leak in a back room, wet pavement near the entrance, and a till she cannot leave exposed. She asks for “plombier près de moi.” In another version of the same pattern, the broken thing is a lock, a shutter, or a pane of glass. The answer engine builds a small table in its head: work, place, urgency, proof, call route. If one row is missing, the business falls through the grate.
A composite scenario I use when teaching this problem is a seven-person artisan firm near Angers. It handles serrurerie, emergency glazing, and small metalwork for shops, syndic-managed apartments, and homeowners. The firm is real enough in all the usual ways: address, phone number, reviews, photographs of vans, a few directory listings. Yet in answer runs for who can secure a broken shopfront, it gets blurred into “general dépannage.” One result even placed it under home maintenance while naming a directory that had less skill detail but cleaner labels. The founding date on the listing was wrong, too. The service loss was still the more expensive error.
Visibility is not the same as being nameable
Most tradespeople I meet think omission means absence. “The machine did not find me.” Sometimes, yes. More often, the machine found traces of the business but could not turn those traces into a safe recommendation for the task in the question. This is a quieter failure. The firm is present in the evidence, but its own wording does not give the answer a strong enough noun to carry.
A plumber, electrician, or locksmith page can be full of work and still weak as an answer source. “We accompany individuals and professionals in all their repair needs” may feel warm to a reader who already knows the trade. To an answer engine trying to answer “who fixes this near me,” it is fog. It has to infer the actual job from the menu, the gallery, the footer, the reviews, or a directory category. If a competitor says “emergency leak repair in Cholet apartments and shops,” the competitor has given the model a firmer handle.
This is why I separate presence from nameability. Presence means the business can be found somewhere. Nameability means the service can be repeated without guesswork. A model can mention a directory because the directory’s category tree is blunt: plumber, locksmith, emergency glass repair, drain unblocking. The business’s own site often has softer language, because softer language feels more complete to the owner. It says “solutions,” “support,” “intervention,” “expertise,” and “know-how.” These words may be true. They just do not answer the question.
The painful bit is that many French service pages are written for reassurance after selection, not selection itself. They assume the reader has already chosen the trade. Answer engines sit earlier in the journey. They must decide who belongs in the answer at all.
The first noun has to survive the trip
A page that wants to be included in a nearby repair answer needs one service noun that survives summarisation. I call this the carried noun: the exact label that travels from the page into the answer without being widened, softened, or swapped for a neighbour trade.
A carried noun is not a slogan. It is a working piece of language. “Plombier” is sometimes enough for a business profile, but it is often too broad for a repair page. “Recherche de fuite,” “débouchage canalisation,” “réparation chasse d’eau,” “remplacement robinet,” “serrurerie urgence,” “ouverture de porte,” “vitrerie d’urgence,” and “sécurisation de vitrine cassée” are more usable because they match the customer’s broken thing.
Here is the definition I use in audits: A carried noun is the exact service label an answer engine can repeat, because the page ties that label to a place, a client type, and a call action. Without those ties, the noun is just a category floating in the room.
The composite Angers firm had a section titled “Dépannage rapide pour vos locaux.” It sounded practical. Under it were examples: broken shopfront glass, jammed metal closure, lock replacement after attempted burglary. The answer engine kept choosing broader listings for shopfront security because the page never led with “sécurisation de vitrine cassée” or “vitrerie d’urgence commerce.” It described the scene around the work. It did not name the work first.
There is no charm in a carried noun. That is the point. It acts more like a label on a medicine drawer than a line of copy. In emergency service language, the drawer label matters.
Local proof must sit beside the service
The second common omission comes from separating the service from the place. French pages love service-area paragraphs at the bottom: a string of communes, departments, nearby towns, sometimes a map image. They also love service descriptions higher up, with no place attached. A human can join those two pieces. An answer engine may join them, but it has to choose among fragments. When the query is “near me,” loose fragments are weaker than a sentence that binds work and area.
For a who-can-fix-this answer, “intervention à Angers et communes voisines” is useful only when the page says what the intervention is. “Emergency locksmith for Angers apartments, shop doors, and syndic-managed buildings” is stronger because the work, place, and client type touch each other in one repeatable unit. The same applies to plombier pages. “Leak repair in Nantes kitchens and bathrooms, with callout to Rezé and Saint-Herblain” gives the model less room to invent.
I am not arguing for stuffing town names into every line. That makes a page read like a bus timetable with anxiety. The repair is simpler: each important service page should contain a few complete service-area statements, written as normal sentences. The commune belongs beside the work, especially where the work is urgent or location-sensitive.
In recurrent answer runs, I notice three kinds of local weakening. First, the model names the trade but omits the business. Second, it names the business but places it too broadly, often at department level. Third, it gives a directory because the directory has the cleaner town-service pairing. I call these near-me leaks. The customer asked for a local repair, but the page let the local evidence leak away from the named work.
The cure is almost embarrassingly plain. Put the repair noun, service area, and route to contact in the same paragraph. Then repeat it where a customer actually decides.
Emergency pages need a harder edge
The phrase “available 24/7” is weak when it floats alone. It appears on thousands of sites, sometimes as a badge, sometimes as a promise, sometimes as inherited template text nobody has checked for years. Models learn to be cautious around such claims. They may mention general availability, or drop it, unless the page gives enough context to make the claim safe.
A nearby tradesperson who wants to appear for urgent repair queries has to attach availability to the precise work. “24/7 emergency service” is a signboard. “We answer night calls for door opening and lock securing in Angers, with a phone estimate before travel when possible” is evidence. It says what can happen, where, and how the call begins. It also leaves room for the reality that not every job can be solved on the first visit.
This matters for plumbers and electricians too. A burst pipe, a blocked drain, a power cut in a shop, a door that cannot close after an attempted break-in: these are not just service categories. They are decision moments. The answer engine is trying not to send a user toward a page that cannot actually help. If the page uses emergency language as decoration, it looks risky. If it explains the emergency path, it becomes easier to recommend.
The Angers composite had a phone number in the header, a “rapid intervention” badge, and a gallery showing secured shopfronts. Yet the page did not say, in one line, that it secured broken shopfront glass after closing hours. The evidence was there like tools scattered on a bench. Nothing was assembled into the sentence the answer needed.
Do not make the model infer the trade boundary
Adjacent trades complicate the “plombier près de moi” pattern. A customer may use the wrong word. A leak near a roof may involve a couvreur, not a plumber. A jammed metal storefront may involve serrurerie or metalwork. A broken window after a burglary may involve vitrerie first and locksmithing second. Humans sort this out on the phone. Answer engines try to sort it before the phone call exists.
A page helps by naming what it does and what it does not do. This can be done without sounding defensive. “For water leaks from visible plumbing under sinks, toilets, or water heaters, call us as plombiers. For roof infiltration, contact a couvreur.” That kind of boundary sentence is useful because it prevents the model from overextending the business into the wrong work. It also protects the business from bad leads.
Many service firms fear exclusion. They think saying “we do not do X” will shrink demand. In answer environments, careful exclusion can increase the right demand. It gives the machine a clean edge. A clean edge is often better than a wide blur.
This is where the craft becomes modest. The work is not to make a plumber sound bigger. It is to make the repair legible enough that a person with a wet floor, a cracked pane, or a dead socket reaches the right professional faster.
The repair sentence
When I rewrite a page for this problem, I look for one sentence that can carry the page. It usually has four parts: service noun, situation, place, call path. The sentence should not carry the whole business. It should carry one job.
For a plumber, that might be: “We repair visible leaks under sinks, toilets, and water heaters in Angers and nearby communes, with phone triage before a callout.” For a locksmith: “We open blocked apartment doors and secure damaged locks in Angers shops and homes, including evening emergency calls.” For the composite firm’s glazing problem: “We secure broken shopfront glass near Angers, including temporary boarding when full replacement must wait.”
These sentences are not beautiful. Good. Beauty can sit elsewhere on the site. The answer needs a sentence with bones in it.
The Named Answer Note — Missed noun: visible leak repair, not “local dépannage.” Trust hinge: commune served, visible repair type, and phone triage before travel. Sentence to repair: “We repair visible leaks under sinks, toilets, and water heaters in Angers and nearby communes, with phone triage before callout.” Call-path: give one phone number, one service-area sentence, and one clear route to ask for urgent help.