Why bother, when the reviews are already on Google
Because the person deciding whether to book you is no longer on Google. They searched, they clicked, and now they are on your rooms page, where the reviews that convinced them to click are two taps behind them — and very few people go back.
Putting the reviews on the page moves the proof to where the decision happens. That is the whole argument, and it needs no statistic to be obvious. What follows is an honest comparison of the three ways to do it, including how each one goes wrong.
Option one: screenshots
Free, takes an afternoon, and it is what most small sites have. Screenshot a few good reviews, drop the images on the page.
Two problems, neither obvious on the day you do it.
They rot. The screenshot taken this spring still shows the count from this spring. Reviews collected since do not appear, and an image that is clearly a couple of seasons old quietly says nothing has happened here lately.
A picture of a review is not a review. Nobody can click through to check it, and a reader scrolling testimonials is by definition slightly suspicious. The reviews are real; the format makes them unverifiable.
Option two: Google’s own Places API
Google publishes an interface that returns a place’s details, reviews included, and if you have a developer this is the most direct route: your site, your code, your styling, data straight from the source.
There is one limit that decides whether this option is right for you, and it is documented by Google rather than inferred. The Place resource reference states, of the reviews field: “List of reviews about this place, sorted by relevance. A maximum of 5 reviews can be returned.” That is from developers.google.com/maps/documentation/places/web-service/reference/rest/v1/places, read on 6 September 2026.
Read that twice if you have hundreds of reviews. You can show five, and you do not choose which five — they come back sorted by Google’s own notion of relevance, and that ordering can change without warning. A hotel with several hundred reviews showing five is a strange thing to build deliberately.
The rest is ordinary developer cost, but it is real:
- A Google Cloud project, a key and a billing account — metered access, not a free feed.
- Somebody writes the fetching, the caching and the fallback for a failed request.
- Attribution is required: display a review, and you display its author attribution too. That is a rule, not a nicety.
If you have a developer on hand and five reviews is genuinely enough, this is a clean solution with nobody in the middle. If either of those is untrue, it is the wrong tool.
Option three: an embedded widget
This is the option most small businesses end up with, and it is worth knowing what one actually is, because “widget” sounds vague and the thing itself is not.
You paste two things into your page: an empty element with an identifier, and a
<script> tag. When the page loads, that script finds the empty element, asks
a server for your reviews, and builds the markup inside it. Most good ones then do one more
thing — they render into a shadow root: a sealed compartment inside your page
with its own styles. Nothing inside can be restyled by your theme, and nothing inside can leak
out and break your layout. It is the difference between a widget that looks the same on every
site and one that inherits your headings and falls apart.
That is the entire mechanism. Everything else is what the provider does with it — five questions worth asking before you paste anything into a live site.
Does it charge for being seen?
Some review widgets are priced per view or per impression, which means a page that starts doing well starts costing more, and a post that gets shared widely can produce a bill you did not plan for. A flat monthly price does not have that shape. Ask which one you are buying.
What does it do to the page while it loads?
A script that blocks rendering holds up everything after it, so your own text arrives late because a review box is still thinking. You can check this yourself: load the page on a phone with a poor connection and watch what appears first. Your content should be readable before the reviews arrive. Better still is a widget that fetches them only when the box scrolls into view.
What does it look like when it fails?
Servers have bad days. The question is whether a failed request leaves an empty bordered box sitting in the middle of your homepage or whether the section disappears cleanly. Ask, or test it by loading the page with the widget’s domain blocked in your browser.
Does the rating it prints describe your business, or its own selection?
This is the subtle one, and it is the one we got wrong ourselves before we caught it. A widget shows a handful of reviews — that is the point, a page cannot hold four hundred. But if it also prints an average and a count, those two numbers must describe your whole listing, not the handful it happens to be displaying.
A widget that averages only the reviews it decided to show, after filtering by rating, does something genuinely damaging: it understates how many reviews you have and overstates your score, at the same time, in the one place a visitor is looking for exactly those two figures. If a widget offers to hide reviews below a chosen rating, ask what happens to the average printed above them.
Does the reviewer stay attached to the review?
The author’s name and the link back to Google are what make the thing checkable — the property screenshots lose — and displaying the attribution is what Google’s own rules require. A widget that strips the author has turned your reviews back into testimonials.
The thing not to do, whichever option you pick
Do not show a hand-picked selection under a number that describes something else. Displaying your best reviews on your own site is normal marketing and nobody objects; presenting a filtered average as your Google rating is a claim about a fact, and it is a false one. The same instinct on the collection side — screening customers before deciding who gets the review link — is review gating, and Google’s prohibited content rules for Business Profiles name it directly.
Source: Google Business Profile Help, “Prohibited & restricted content” — support.google.com/business/answer/7400114, read 6 September 2026.
Which one to choose
Screenshots if the page is a leaflet you will never touch again. Google’s own interface if you have a developer and five reviews is enough. A widget if you want the wall to stay current without anybody maintaining it — which is most people.
ReviewQR is the third of those: it renders into a shadow root, fetches when the box scrolls into view, prints the rating and count from your full listing rather than from the visible slice, and does not charge by the view. The free plan covers one location, and the QR side is what fills the wall in the first place.