Trust signals and customer decisions
Google has added guidance on fake and undisclosed incentivised reviews. For a service business, the practical move is simple: ask every suitable customer for an honest review, disclose any thank-you that is offered, and never make a reward depend on a positive rating.
The decision rule: if a customer could reasonably feel that a benefit was conditional on praise, do not use that review as a trust signal. Make the request neutral, make any incentive explicit, and use feedback to improve the service whether it is flattering or not.
Why the new guidance matters
Google’s July 2026 documentation update added guidance on fake and undisclosed incentivised reviews in review snippets. The immediate topic is structured data in Search, but the customer-facing lesson is wider: reviews only help a website when people can understand where they came from and why they should trust them.
Many firms mean well when they offer a small thank-you, run a prize draw, or ask their happiest clients to leave feedback. The risk starts when the request quietly selects only praise, hides the benefit, or turns a customer quote into a marketing claim that no longer reflects an independent experience.
This is not a reason to remove genuine reviews. It is a reason to separate three things that are often mixed together: asking for feedback, rewarding participation, and claiming an independent endorsement.
Use the right boundary for each review request
What it looks like: “If you have a moment, please share an honest review of your experience. Your feedback helps us improve.” The request goes to an appropriate set of customers, not only people expected to give five stars.
What it looks like: every eligible customer can enter a draw or receive the same modest thank-you for completing feedback, regardless of sentiment. Make the arrangement clear wherever the review may be presented as a trust signal, and check the relevant platform’s rules before running it.
What it looks like: “Leave us a five-star review for a discount,” or a benefit that is available only after positive wording. This creates a credibility problem even when the reviews are real customers’ words.
What to publish on your own website
A website testimonial is not automatically a Search review snippet, and a happy client quote can still be useful. The test is whether the page gives a visitor enough context to judge it fairly. Name the service or project type, use the customer’s permission, and do not rewrite a qualified comment until it becomes a blanket claim.
For example, “The team clarified our service pages and made our enquiry route easier to use” is more credible than “The best agency in Belgium.” The first tells a prospective customer what changed; the second asks them to trust a superlative.
A better review-request pattern
After completing a web project, send a short follow-up that works for every client:
“Thank you for working with us. We would value an honest review of the project, including what was useful and what we could improve. We may ask permission to feature a short excerpt on our website, with your name and business context.”
This message does not promise a reward for praise. It also creates a clean distinction between public platform feedback and permission to reuse a quote on a service page.
Run a five-step credibility check before displaying reviews
Trace the source
Know whether the review came from a verified customer, a project follow-up, a survey, or a third-party platform. Do not use anonymous praise with no reliable relationship behind it.
Check the request wording
Confirm that the customer was invited to be honest—not instructed to give a score, use a phrase, or avoid mentioning a problem.
Record any benefit
If a draw, discount, gift or other benefit was involved, record it. Do not describe the resulting quote as wholly independent if participation was rewarded.
Keep the context
Attach a testimonial to the relevant service, project type or customer situation. Context is more helpful than a rotating wall of unconnected praise.
Make correction possible
Give the customer a clear way to update or withdraw a quote, especially if the relationship, service or circumstances later change.
Do not turn review collection into a conversion shortcut
Reviews support a decision after a visitor understands the offer, scope and next step. They cannot repair an unclear service page or compensate for a difficult contact process. Put the basics first: a specific service, realistic process detail, useful limits and a straightforward route to enquire.
That is why review credibility belongs alongside website creation and SEO and GEO optimisation. Trust is strongest when the claim, the evidence and the customer journey agree. If you need an outside view of which proof belongs on priority pages, a focused SEO audit can identify where visitors still need clearer evidence before they contact you.
Frequently asked questions
Can a business ask customers for reviews?
Yes. Ask for honest feedback from an appropriate group of real customers. Do not require a positive rating or selectively request reviews only from people expected to praise the business.
Can we offer a discount or prize draw for a review?
Check the review platform’s terms and applicable rules first. A benefit tied to a positive review is not credible. If participation is rewarded regardless of sentiment, disclose the arrangement clearly before presenting the feedback as a trust signal.
Can customer testimonials appear on a service page?
Yes, when the customer has given permission and the quote retains useful context. State the service or project situation rather than relying on unsupported superlatives.
Will review schema guarantee a rich result?
No. Structured data helps search engines understand eligible content, but it does not guarantee a rich result. Focus first on truthful, well-contextualised feedback.
Sources
Make the proof on your website earn trust
TrendTransformers can help clarify service pages, customer proof and the enquiry route so visitors can make a confident decision.