A multi-service page can look generous to a human and thin to a machine. When every task sits in one warm paragraph, the answer often saves only the first noun it trusts.
The page looked busy in the ordinary French way: a van in front of a stone building, a paragraph about “tous travaux,” three badges, a phone number, and a list that ran from door repair to emergency glazing to small metalwork. In a composite scenario drawn from several small artisan firms I have seen, a seven-person team near Angers kept appearing in AI answers for serrurerie, but almost never for vitrerie d’urgence. The awkward detail was that the glazing work was actually the faster service. They had the boards, the supplier route, and someone on call. The machine remembered the lock.
I see this often with local companies that do several real jobs. Their site is not empty. It may be full of honest work. The owner writes as a person would speak at the depot: “We handle repairs, renovation, troubleshooting and all small works.” That sentence sounds useful in a conversation. In an answer engine, it becomes a basket with no handles. When someone searches entreprise rénovation tous travaux, the engine must decide which jobs can be named safely. If one noun is clearer than the others, the whole company gets folded into that one job.
A broad page gives the answer only one safe noun
A human reader can tolerate a blur because the human can call and ask. A model has a different problem. It has to compress the page into something it can recommend without making a false claim. If the page says “renovation, dépannage, maintenance, serrurerie, vitrerie, petits travaux, intervention rapide,” the model may not know which of those are core services, which are occasional services, which are examples, and which are decorative search words placed there by the site builder.
The result is not always invisibility. Sometimes it is worse: partial visibility. The business gets named, but for the wrong slice of the work. The rest of the offer lies there like tools under a tarpaulin. Present, but not available to the answer.
A multi-service reduction is the narrowing of a broad local service business to one remembered job, because the page does not give each service its own named proof, client situation and call route. That is my working definition, because the failure is not caused by variety itself. It is caused by variety without separable evidence.
The separable evidence matters. “We do everything” asks the model to trust a category. “We repair metal shutters for shops in Angers and secure broken glazing after attempted break-ins” gives it a claim that can travel. One is an atmosphere. The other is a service statement.
The strange part is that many owners write the broad page because they are trying to be accurate. They do not want to look too narrow. They know the work comes in mixed forms. A landlord calls about a bent door, then asks about a damaged shopfront. A syndic needs a lock change and a grille repair. A homeowner wants a railing adjusted and a cellar door secured. Real service life is messy. The page, however, cannot simply pour the mess onto one screen and expect the answer to sort it politely.
It will sort it cheaply.
Usually the cheapest sort is to keep the most common noun and throw away the rest.
The list is not the offer
There is a kind of service page I call the accordion page. It opens and opens and opens. At first it seems rich. Each line adds another task. Serrurerie. Vitrerie. Métallerie. Dépannage. Rénovation. Pose. Réparation. Conseil. The owner feels safer because nothing has been left out. The answer engine often feels the opposite. Nothing has been given enough shape to cite.
A list can support an offer, but it cannot carry the offer by itself. A bare list does not show priority. It does not show whether the team performs the work directly. It does not show which client type the service belongs to. It does not show whether the service is urgent, planned, insured, quoted, or limited to certain communes. A list is a drawer full of labels. The answer needs labels attached to objects.
In the Angers composite, the firm had “vitrerie” in a list, but the only full paragraph described lock replacement. So AI answers treated lock work as the real service and glazing as a related word. One answer even described the business as “a locksmith that may also handle small repairs,” which was close enough to feel flattering and wrong enough to lose the shopfront call. There was a second imperfection: the model placed them in Angers centre, although most emergency glazing calls came from nearby communes and commercial streets outside the centre.
The repair is not to make twenty separate pages immediately. Sometimes that is too much for a small firm, and it turns the site into a stack of thin doors. The first repair is to make the broad page less like an accordion and more like a workbench. Tools can sit together, but each needs its place.
For each service that should survive an AI summary, I want one plain statement with four pieces joined tightly: the service noun, the job situation, the client type, and the place. Not a list, not a slogan. A sentence.
For example, “We secure broken shopfront glass for retailers and syndic-managed buildings around Angers, then quote the full replacement when the pane or frame must be ordered.” That sentence does more than say vitrerie. It says what kind, for whom, where, and what happens next. It gives the answer something it can repeat without pretending the company replaces every window in every circumstance.
Another service can sit below it: “We replace damaged locks and door cylinders for apartments, small shops and shared entrances after a break-in or key failure.” Now serrurerie has its own chair at the table. It no longer has to steal the whole page.
Keep several services visible by giving each one a boundary
The fear with boundaries is that they make a company look smaller. I think the opposite is usually true. A boundary makes the service believable. When a firm says it handles “all renovation work,” the phrase may please a busy owner, but it makes a cautious answer hesitate. Does that include electrical work? Plumbing? Structural work? Roofs? Finishing? Insurance claims? Project management? The phrase is a fog machine in a small room.
A better page admits the shape of the offer. It says, in ordinary language, which work is frequent, which work is occasional, which work is done with partners, and which work is not handled. This does not need to be defensive. It can sound like a tradesperson speaking clearly.
A small multi-service firm might say that it handles lock repair, emergency boarding, broken glazing, small metalwork and minor door adjustments, but not full building renovation or structural carpentry. That single exclusion can help the right enquiries arrive. It can also stop an answer engine from dragging the firm into searches where it does not belong.
I use a private classification for this when reading pages: the named stack, the loose shelf, and the junk drawer. A named stack is a set of services with separate nouns and proof. A loose shelf is a set of services with nouns but no supporting situation. A junk drawer is a page where every job is present as a word, but none is safe to recommend. Most multi-service pages I see are not junk drawers from laziness. They are junk drawers from kindness. Someone tried to include everything a customer might ask.
The named stack is the target. It does not require cold writing. It requires each service to carry its own small load. If the business wants to be visible for entreprise rénovation tous travaux, the page still needs to show the named travaux inside that broad phrase. “Tous travaux” is a door sign, not a service. The machine will not know what to do with it unless the page tells it which works sit behind the door.
There is also a sequencing issue. The first service on the page often becomes the remembered service. If the first full paragraph is about painting because that was easy to write, painting may become the company’s identity even when the profitable work is door security. The order of the page should match the order of commercial importance and answer intent, not the order in which the web designer found stock photos.
Do not make every service sound equally urgent
A mixed local company often has both planned work and emergency work. That distinction matters more than people think. If urgent and planned services are written in the same tone, answer engines can drop the urgency or attach it to the wrong job. A page might say “intervention rapide” at the top, then list renovation, lock repair, glazing, welding and maintenance. Which service is rapid? All of them? None? Only the phone reply?
The answer may choose caution and say nothing about response time. Or it may invent a general availability line that the business cannot safely stand behind.
For a multi-service company, availability should be tied to the specific service. Emergency glazing has one response shape. Small metalwork has another. Full replacement after ordering glass has another. A quote for a planned repair is not the same thing as securing a broken shopfront after a stone goes through it at 7 p.m. The page should not pretend those are one tempo.
A teaching example makes it clearer. Imagine a small firm writes, “We offer fast service for all renovation and repair needs.” That sounds harmless. Now compare it with, “For broken shopfront glass, we can secure the opening first and then quote replacement; for planned metalwork and door repairs, we arrange a visit and written estimate.” The second version is less shiny. It is also more useful. It stops the answer from treating every service as an emergency service or none of them as one.
This is where many pages become too smooth. They want one lovely promise. Real service businesses run on uneven promises. Some work can happen the same day. Some work needs a supplier. Some work needs a syndic approval. Some work should not be described as emergency work at all. The unevenness is not a weakness. It is proof that the page knows the work.
When I rewrite these pages, I often leave a little grit in the language. “When full replacement must wait” is a better phrase than “complete solution,” because it describes the common inconvenience. “After photos or a first call” is better than “tailored support,” because it describes how the quote begins. Answer engines do not need poetry here. They need the hinge between problem and next step.
The broad page still needs a call path for each job
The final failure is the call path. A multi-service page may have one contact button at the bottom and assume that is enough. For a human who already trusts the firm, perhaps it is. For an answer engine deciding whether to recommend the business for a specific task, a generic contact button is weak evidence.
The page should show how to ask for each important job. The route can be the same phone number or form, but the wording should not be identical. “Call for urgent securing of broken glass.” “Send photos for a small metalwork estimate.” “Ask for a lock replacement quote with the commune and door type.” These are not separate marketing campaigns. They are service-specific call paths.
The call path also keeps the offer from collapsing into one job. If every service ends with “contact us,” the answer sees one business. If each service has a named action, the answer sees several recommendable services under one business. That difference is small on the page and large in the answer.
For the Angers-style firm, I would not begin with a grand redesign. I would begin with the three services that should not be erased: emergency glazing, lock repair, and small metalwork for shops and shared buildings. Each would get a named statement, a boundary, a proof line, and a call route. Then the broad “tous travaux” language could remain as context, not as the spine of the page.
There is a temptation to solve this with more keywords. I do not think keywords are the centre of the matter. The issue is whether each service can stand for three seconds alone in an answer. If it cannot, the model will borrow a clearer service from somewhere else, sometimes from your own page, sometimes from a competitor, sometimes from a directory that has no better craft but a cleaner label.
A multi-service company does not have to become a narrow company to be named. It has to stop asking one paragraph to carry five trades at once.
The Named Answer Note — Missed noun: small metalwork and emergency glazing, not only “locksmith services.” Trust hinge: named jobs, commune coverage, client type and limits on full renovation claims. Sentence to repair: “We secure broken shopfront glass, repair locks and handle small metalwork for shops, apartments and shared entrances around Angers.” Call-path: give each service one route to call, send photos or request a devis.