Customer feedback is useful when visitors can understand its source and relevance. A trustworthy review section explains where comments came from and avoids turning selected praise into an unsupported claim about every customer. Plan collection, display permissions and ongoing maintenance before installing a review widget.
This guide covers review sources, testimonial presentation, widget dependencies and credible supporting project information. Discuss the relevant requirements through ITZ’s Website Development service.
Collecting feedback
Request feedback through an appropriate process after a genuine customer interaction. Avoid incentives or selection practices that misrepresent the overall experience, and follow the review platform’s current policies.
Invite feedback through an appropriate, consistent process after a genuine interaction. Google's review guidance prohibits incentives for reviews. Do not offer a reward for positive wording or ask staff to impersonate customers. A business should be prepared to receive criticism and assign someone to respond through the appropriate platform rather than trying to engineer a perfect rating.
Displaying reviews
Make the source and context clear. If showing a rating or review count, establish how it will remain accurate over time. Obtain any required permission before publishing customer names, photographs or detailed testimonials.
Preserve meaning when quoting a review and identify its source honestly. Check whether republishing names, photographs or comments requires permission and whether the platform's terms allow your proposed use. If you select a few testimonials, label them as selected feedback rather than implying that the collection is a complete current review feed.
Review Your Website Trust Evidence to discuss review sources, testimonial presentation, widget dependencies and credible supporting project information.
Widgets and structured data
Assess the loading cost and accessibility of external review widgets. Structured data must match visible content and meet the applicable feature policies; adding rating markup does not automatically make a business eligible for review stars.
Ask what a widget downloads, what account it depends on and how it behaves when the provider is unavailable. Test page performance and an accessible fallback. Google places restrictions on self-serving review rich results for organisations and local businesses; displaying a testimonial does not automatically make a page eligible for stars in search results.
Case studies and evidence
A factual case study can explain the work and its outcome in more detail than a rating alone. Publish only approved information and distinguish measured results from descriptions or expectations.
Use project evidence to answer questions reviews cannot. A concise, approved account of the task, your actual contribution and the delivered scope can help a visitor judge fit. Keep any outcome claim tied to a verified record. Where metrics are unavailable, describe the work completed without inventing a percentage improvement or attributing all results to the website.
A practical example
Illustrative example: a testimonial praises a team's responsiveness during an installation. It supports that customer's experience, not a guaranteed response time for every future enquiry. Pair it with accurate contact arrangements and a relevant service description, allowing the visitor to understand what can actually be requested.
Your review checklist
- Collect feedback without incentives or fabricated identities.
- Record sources and permissions for republished testimonials.
- Test widget performance and fallback behaviour.
- Separate customer comments from verified project outcomes.
Frequently asked questions
Can a static rating be displayed indefinitely?
Only if there is a process to maintain its accuracy and attribution. A link to the current review source may be more appropriate when automatic updates are unavailable.
References and further reading
Related services and guides
Discuss the next step
Review Your Website Trust Evidence. Use the form below to discuss review sources, testimonial presentation, widget dependencies and credible supporting project information. Share the relevant goals and existing arrangements; do not include passwords, private records or access tokens.
Review Your Website Trust Evidence ↗
Reviewed and expanded on 15 October 2026. Examples are illustrative; the appropriate approach depends on your business requirements and existing systems.
