← All articles

How to show Google reviews on your website

google-reviewswebsite

A guest who has reached your website is already interested — but not yet convinced. The strongest argument you can show at that moment isn't your words about yourself but other people's: reviews from real guests, with names and stars. Which is why "what our guests say" isn't decoration, it's part of the sale.

There are three ways to do it. They differ in cost, in how much they weigh the page down, and in how much they maintain themselves.

1. By hand: copy a few reviews across

The simplest option — pick five or six of your best reviews and type them into your HTML as plain text with the guest's name and a star count.

For: costs nothing, loads nothing from elsewhere, keeps the site fast. Against: it doesn't refresh itself; a year later it looks stale. And it lacks the verifiability a live Google profile gives.

If you go this route, put a link to your Google profile next to the block — anyone who wants to check goes and sees everything else too. And always include a date or period; undated reviews read as invented.

2. A ready-made widget

Review-display services (there are a dozen, from free plans to a few euros a month) give you a snippet you paste into your site, and they pull new reviews from your profile themselves.

For: refreshes itself, looks tidy, needs no developer. Against: a monthly fee, and third-party scripts almost always slow the page down — sometimes badly. Before leaving a widget in place, measure the page in PageSpeed Insights before and after; if your performance score drops, you've gained social proof and lost speed, which is a poor trade for a local site.

A practical compromise: a widget that loads lazily (once the visitor scrolls to that section), or one that renders a static snapshot of the reviews.

3. The Places API: pull the data yourself

Technically the cleanest solution. The Google Places API returns profile data including the rating, review count and a handful of the most recent reviews. Your site fetches them server-side, caches them for a few hours, and renders them as your own HTML.

For: fast (no third-party script), under your control, no widget subscription. Against: you need a developer for the initial setup, an API key and a Google Cloud account; the API bills per call, so caching isn't optional.

One important limit: the Places API returns a limited number of recent reviews, not all of them. If you want the full archive, this route won't give it to you.

What you may and may not do

A few rules that are easy to break with the best intentions:

What about stars in search results?

A common misconception: if I put reviews on my site, I'll get stars in Google's results. You won't — Google explicitly doesn't show so-called self-serving ratings, meaning reviews about your business published on your own site, as a rich result. The stars guests see in search come from your Business Profile, not your website.

So the priority is the opposite of what feels intuitive: profile first, site second. Reviews on your site help convert people who already arrived; reviews on your profile are what bring new people in and lift you in local search.

The recommendation

For most small businesses: the Places API with caching if you have someone to set it up, a hand-built block if you don't. Take a widget only if self-refreshing matters more to you than a few dozen milliseconds of load time.

And in all three cases — reviews on your site are worth exactly as much as the profile they come from is alive. A block showing three-year-old reviews with no replies works against you; a tidy profile with replies works for you both on the site and in search.