How to display Google reviews on your website, and what not to do

You may display your Google reviews on your own website, provided they are shown as Google reviews, with attribution and a route back to the source, and provided you show them as they are rather than as a selection you curated. The technical work is straightforward. The two ways to get this wrong are cherry-picking which reviews appear, and attaching review structured data to them in the hope of stars in search results.

What you are allowed to display

The reviews belong to their authors and are published by Google, which means the display has conditions attached.

• Attribute them. Reviewer name, their photo where the source provides it, and a visible link back to the listing. A quote with the platform name stripped off becomes a testimonial, which is a different and more regulated thing.
• Do not edit the text. Truncating with a “read more” is fine. Tidying the grammar is not.
• Keep them current. A widget frozen with reviews from 2023 is stale content on your own site and misrepresents your present standing.
• Do not scrape. Pulling the listing page with a crawler breaches Google’s terms regardless of whether it is your own listing.

The four ways to do it

The honest recommendation for a single property is the widget. Building against the Business Profile API directly means owning OAuth token refresh, quota, and the API’s own approval gate, which is a disproportionate amount of engineering for a strip of reviews on a homepage. Revify ships a widget for exactly this reason.

The structured data trap

This is the mistake worth reading the whole article for.

Sites embed reviews and then add AggregateRating markup to the page hoping for a star rating in search results. For reviews a business has collected about itself, this does not work, and it can be actively harmful. Google’s review snippet documentation sets out the restrictions, including that self-serving reviews about an organisation are not eligible for the rich result.

If you mark up a hand-picked selection of five star reviews as your aggregate rating, you are publishing a rating that disagrees with the rating on your own Google listing. That is a structured data misrepresentation, and the penalty is a manual action against the site rather than merely an ignored snippet.

Choosing which reviews to show

A widget that shows your most recent reviews is defensible. A widget that shows only five star reviews is a curated advertisement wearing the clothes of independent feedback, and that is precisely the framing consumer protection regulators use when they act on fake and misleading reviews.

The defensible configurations, in descending order of how comfortable they are to explain:

1. Most recent, unfiltered. Honest, current, and the easiest to justify to anyone.
2. Most recent above a stated threshold, with the threshold visible and a link to the full listing beside it.
3. A fixed, attributed selection presented explicitly as selected quotes, alongside the real overall rating and count.

In every case, show the real average and the real review count next to the quotes. It costs nothing, it is more persuasive than the quotes, and it is the element that makes the rest read as genuine. A visitor who senses selection discounts everything on the page, which is the opposite of what the widget is for.

Keeping it from slowing the page down

Review widgets are a common source of page weight, because the convenient ones load a script that loads a framework that fetches data client side, on a page that had no JavaScript requirement before.

• Prefer server rendered. Fetch the reviews when the page is built or cached and send them as HTML. It is faster and the content is present for crawlers.
• Cache aggressively. Reviews change slowly. Refreshing hourly is generous; refreshing on every page view is wasteful and will hit rate limits.
• Reserve the space. A widget that injects itself after load shifts the page under the reader, which is a measurable layout shift and an avoidable one.
• Watch the cookie question. A third-party script that sets cookies before consent turns a review strip into a compliance problem. See review requests and GDPR for the wider data picture.

Where it actually earns its place

Not the homepage, where visitors expect to be sold to and discount anything positive. Reviews work hardest immediately before a decision: on the room type page, next to the booking form, on the reservations page, beside the price.

One more thing worth knowing: the reviews on your own site are read by the systems that summarise businesses as well as by people. A page that shows current, attributed reviews with the real average beside them gives an answer engine something specific and checkable to quote about you, in a place it can actually reach, which your Google listing is not. For the wider question of which platforms connect and how, see which review platforms connect by API.