Reviews can make a business feel trustworthy to a person already looking at it. Perplexity has a different problem: it needs a source it can footnote for facts, not a pile of praise it must interpret.
A plumbing and heating company in Nantes has a familiar complaint. Its Google reviews are strong. Customers mention fast callouts, clean work, and a technician who explained the boiler fault without making the client feel stupid. A few reviews even name nearby communes. The company owner looks at Perplexity and sees a national directory cited instead. The directory is flatter, less personal, and probably less knowledgeable. It still wins the footnote.
The composite scenario is ordinary enough to be irritating. The company has 14 people, handles emergency repairs, boiler maintenance, and small bathroom refits, and serves Nantes plus surrounding communes. Its website has warm paragraphs and project photos. The directory has fewer human details, but it states the trade, city, emergency radius, opening hours, service categories, and sometimes the legal name in a tight block. Perplexity is not choosing the better plumber. It is choosing the page that makes the answer easier to source.
A review is evidence of satisfaction, not a service description
Reviews are not useless. They matter to buyers. They may influence whether someone calls, especially in local services where trust begins with other people’s irritation being solved. I would never tell a French business to ignore reviews. The problem is more precise: reviews are unstable source material for Perplexity’s numbered answers.
A review is usually written from the customer’s side of the table. It may say the team was fast, careful, kind, expensive, late, brilliant, or disappointing. It may mention “my leak,” “the heating,” or “the bathroom.” The words are real, but they are not a clean business fact. They are fragments of experience. Perplexity can read fragments, but a numbered source usually needs something firmer when the answer has to state what a business does, where it operates, and why it fits a query.
Here is the definition I use when reviewing these pages: source-worthiness is the ability of a page to support a specific factual claim because it states the entity, service, place, scope, and proof in extractable form. Reviews often support reputation. They rarely state the whole claim.
That distinction explains why a business with hundreds of favorable reviews can be absent from source-based recommendations. A high rating says people liked the work. It does not necessarily say whether the company offers emergency heating repair on Sunday evenings, whether it covers Rezé or Saint-Herblain, whether boiler maintenance is still available, or whether bathroom refits are small works rather than full renovation contracts.
Perplexity has to footnote the answer, not the feeling.
Why the directory looks stronger than the praise
The national directory wins because it behaves like a fact shelf. It may be ugly. It may contain outdated material. It may have copied half its categories from a generic database. Still, it often gives Perplexity a compact answer shape.
A typical directory listing says: company name, trade, address, phone, hours, service labels, map area, maybe a review count, maybe a registration or category field. The page is not rich. It is organized. For source-based answer engines, organization has weight.
The Nantes plumbing company’s owned page might say, “For years, our team has supported clients with responsiveness and care across their projects.” That sentence sounds normal on a French local-business site. It also says almost nothing Perplexity can safely cite. Supported clients with what? Which team? Which city? Which service categories? Which current availability? What counts as a project? A boiler maintenance visit and a bathroom refit are different buyer intents. If the page blurs them, the directory’s blunt labels win.
I sometimes call this the review mirage. The owner sees public trust and assumes the source engine sees authority. It sees scattered sentiment unless the owned site turns the reputation into verifiable facts.
The irony is that the reviews often contain clues for the repair. If customers repeatedly mention emergency response in Nantes, the owned page should not merely celebrate “reactivity.” It should state the emergency service area and hours policy. If reviews praise boiler maintenance reminders, the page should describe the maintenance service, frequency, and covered equipment. If reviews mention small bathroom work, the page should separate small refits from general renovation. The review is the smoke. The citeable page sentence is the brick.
The credibility signals Perplexity can actually use
When I audit a local French service page, I look for credibility that can survive extraction. Not grand reputation language. Not a wall of testimonials. The signals are more modest.
First, the business needs a clean identity block. Legal name or trade name, city, trade, service area, and a branch or no-branch statement when needed. If the company operates under a common name, the legal name helps prevent confusion. If it has one office only, say that. If it has several, each location needs its own source surface. The entity has to stand still before Perplexity can cite it.
Second, the service categories need plain wording. “Plomberie et chauffage” is a start, but Perplexity’s questions are often narrower. Emergency leak repair, boiler servicing, heating fault diagnosis, bathroom fixture replacement, and small refits are different claims. A page can group them, but it should not dissolve them into one warm paragraph.
Third, proof should be attached to the claim. Photos can help a human, yet a gallery without captions may be almost silent to a source engine. A caption saying “boiler maintenance visit in Nantes, 2026 service area unchanged” is more useful than another image titled “IMG_4821.” A short note about qualification, insurance, years of operation, or the type of work normally accepted can also help. The proof should be sober. Overclaiming makes the page less trustworthy.
Fourth, freshness needs a visible mark. Local services change hours, coverage, delays, and emergency availability. A small update line can do a great deal: “Opening hours and emergency-callout area checked for 2026.” That is enough if it is true. I dislike theatrical freshness. A page does not need to pretend that plumbing has reinvented itself every month. It needs to show that the facts still breathe.
Fifth, the page should translate customer language into business facts. Reviews may say “came quickly to fix the heating.” The owned page should say “heating fault diagnosis and boiler repair appointments in Nantes and nearby communes.” The customer phrase and the service phrase need a bridge.
A strong review profile may influence trust after discovery, but source visibility depends on facts the business publishes about itself.
What to do with reviews without making them do the wrong job
The worst response is to copy reviews into the service page and hope Perplexity treats them as proof. That can make the page noisy. It can also create privacy problems or invite vague reputation copy. Reviews should be used as diagnostic material first.
I usually read reviews in clusters. Not for star averages. For recurring nouns. Do people mention the same service? The same district? The same emergency moment? The same type of building? The same staff role? The same limitation? In a plumbing company’s reviews, “boiler,” “leak,” “Nantes,” “quick,” “bathroom,” and “appointment” may appear often. Those words point to facts that should exist on the owned site.
Then I compare those review-derived clues with the actual pages. If customers repeatedly describe boiler maintenance but the site hides it under “heating solutions,” the repair is obvious. If clients mention emergency leak visits in surrounding communes but the site says only “Nantes region,” the service-area sentence needs tightening. If bathroom refits appear in reviews but the page makes the company look like a broad renovation contractor, the entity boundary needs correction.
There is a small roughness in this work. Reviews are messy. One customer may call a boiler a heater. Another may name the wrong commune. A third may praise a service the company no longer accepts. The page should not blindly repeat review language. It should turn stable patterns into accurate public facts.
The Nantes composite shows the problem clearly. The company is not losing because customers distrust it. It is losing because the best public source for its facts is not its own domain. Reviews gave the business social proof. The directory gave Perplexity source proof.
Those are different currencies.
The page sentence that reviews cannot replace
A citeable sentence for this company might read: “The Nantes plumbing and heating company handles emergency leak repairs, boiler maintenance, and small bathroom refits in Nantes and nearby communes.” That sentence is plain enough to feel almost embarrassing. Good. It names the trade, city, services, and area. It gives Perplexity a footnote candidate.
The surrounding page can then carry richer material: service details, opening hours, emergency-callout conditions, exclusions, captions, qualifications, and a few carefully selected review themes rewritten as factual support. The tone can stay human. It does not have to become a database entry. But the factual core should be impossible to miss.
A testimonial might sit below that core. “They arrived quickly on a Sunday” is useful to a reader. For Perplexity, it becomes stronger when the business also states its emergency policy. Otherwise the model may not know whether the review describes a current service, an exception, an old arrangement, or a customer’s interpretation.
This is why I separate review strength from citation readiness in audits. Review strength asks: do people publicly trust the business? Citation readiness asks: can Perplexity footnote a factual answer from the business’s own page? A good local company can pass the first test and fail the second.
The repair is not to beg Perplexity to respect reviews. It is to publish the factual sentences those reviews have been hinting at all along.
The Numbered Source Note
Footnote candidate — “The Nantes plumbing and heating company handles emergency leak repairs, boiler maintenance, and small bathroom refits in Nantes and nearby communes.” Citation rival — a national directory with cleaner trade, hours, service-area, and category labels. Freshness mark — “Opening hours and emergency-callout area checked for 2026.” Entity lock — legal name, Nantes base, plumbing-heating trade, nearby-commune coverage, and no borrowed general-renovation label.