Reviews and feedback
Review widget: choose a display source and provider in 2026

Last updated · A-Widget
On this page7
Separate displaying existing opinions from collecting new feedback. A public review, a chosen testimonial and a private support message are distinct records. The screen should make the source and job clear.
Choose the source for your review widget
| Source | Route to inspect | Key distinction |
|---|---|---|
| Current official data route or supported hosted display | API requirements and attribution depend on the implementation | |
| Trustpilot | Official TrustBox and current account entitlement | Display widgets differ from review-collection entrances |
| Yelp | Official supported review embed or source link | A selected recommended review is not a whole scraped feed |
| Your own feedback | A clear collection and publication process | Private responses are not automatically public testimonials |
Choose the source that the page actually discusses. A location page may need an exact business listing. A product page may need a product-exact record. Do not combine unrelated sources into a single score without a clear supported basis.
Check the destination before styling. Similar business names and several locations can lead to a wrong source that still looks convincing. The widget's appearance cannot repair a source error.
Compare display and collection workflows
A display shows content already held by a source. A collection entrance invites a new review under that platform's process. A feedback form sends details privately to the business. Those tasks can use similar-looking buttons while producing very distinct results.
Trustpilot's current help describes TrustBoxes and a Free-plan Review Collector route. Do not assume a collector displays the same content as every paid TrustBox. Check the exact widget plan scope in the current business account.
For private website feedback, use the feedback widget guide. It keeps issue reports and optional reply details separate from public opinions. Do not publish a private complaint as a testimonial without a suitable permission process.
Permissions, attribution and filters
Keep the source visible
Retain the attribution required by the route. Visitors should know who wrote the opinion and where it originated. A vendor's hosted display does not make the review the website owner's original copy.
Google's Places policies address source and author attribution for that data route. Trustpilot's TrustBox guidance names its official display product. Follow the rules for the source you display; Google’s requirements do not grant permission to reuse Trustpilot content.
Describe selection honestly
A chosen subset is not the full source. Do not imply that every review is shown when the layout filters or selects records. A favourable display can mislead if the page disguises its selection basis.
Use the vendor's permitted controls and required notices. Do not hide author or source elements to make the card fit. If the smallest layout cannot retain the needed context, choose a clearer layout or a source link.
Do not infer permission from visibility
A public review is not a universal licence to scrape and store it. Use the official or approved route and inspect current terms for that setup. A screenshot or retyped quotation remains copied content with its own rights and freshness questions.
If permission cannot be established, a normal link can still guide the user to the source. That is a useful route without pretending the website maintains a full review database.
Evaluate review widget limits
Elfsight is a hosted display candidate with widget-specific help and plans. Inspect the real source support, views, number of displays, branding and refresh. A general catalogue page is not proof that every source is included on every tier.
Keep trial access distinct from the ongoing free plan. Check the post-trial state before relying on a layout or feature. Record the chosen billing period when comparing a paid offer.
Unknown limits should remain not verified. Do not invent a refresh interval or claim all reviews appear when the current source does not prove it. The free Google review widget guide shows one checked plan boundary without generalising it to other sources.
Embed and correction workflow
Install the supported display
Use the current code from the correct account and source. Confirm the website plan permits the required frame or script. Keep a copy of the prior page setup and record where the embed is placed.
Open the live page while signed out. Check the business identity, attribution and source links. A successful editor preview does not prove the public page loads the same content.
Make it readable
On a phone, read a long record and its attribution. Inspect controls without relying on hover. If a review opens in a popup, check the close action and keyboard focus.
Keep key business facts outside the review panel. A user should still find services and contact details when the display is blocked. A plain source link is a useful fallback.
Correct the right record
If a business source is wrong, fix the connection rather than editing text to disguise it. If a source review is disputed, use the source platform's supported reporting or correction process. The website owner should not silently rewrite someone else's opinion.
If the display is stale, compare the source, vendor view and public page. Refresh and caching rules differ. Do not announce a vendor-wide outage from a single blank panel without official dated evidence.
Choose the next source guide
Use Google review widgets for that source and WordPress setup for the platform route. Use the Trustpilot guide or Yelp guide for their separate official options.
Keep selected records in context
A single review can help illustrate one user's experience. It does not prove every user had that result. Keep the selection clear and the route to the source easy to find.
If a layout shortens text, check that it does not change the meaning. Use the source's permitted display controls rather than editing the opinion into a new claim. A small card should still give the user enough context to understand what they are reading.
Check the meaning after a layout change
Read a long record again when changing the card size. A shorter display should not hide words that change the opinion's meaning. Keep a source route and required context rather than making the text fit at any cost.
Name the record before choosing its layout
Write a label that describes the content: selected testimonials, reviews from a named source or private feedback. Then read the proposed heading beside it. If the heading suggests a complete independent record while the display contains a chosen few quotes, change the heading. The layout should make the source and selection easier to understand.
Keep the permission record with the content
For a chosen testimonial, retain the original statement and the basis for using it. If a person later requests a correction, staff need to know which page contains that statement. A copied quote with no source record makes that task harder.
A connected review has a different correction route. Find the original record and the source's supported process. Do not silently rewrite someone else's opinion while leaving the display labelled as a live source review.
Continue with the right task
FAQ
Can one service display every network?
Only the current supported source and plan can establish that. Each network has separate permissions and display rules. Do not treat an all-in-one label as a universal licence to copy public content. Check the exact source route and keep unsupported cases not checked.
Can I edit a review to fit the card?
Use only the source and vendor's permitted display behavior. Do not silently rewrite the opinion or remove context that changes its meaning. Preserve required credit and give a useful source link. A chosen quotation and a live source record should not be presented as the same thing.