How to Embed Google Reviews on Your Website: 3 Easy Methods

There are three ways to embed Google reviews on a website: add a review widget, copy the reviews in by hand, or pull them through the Google Places API. Google itself has no embed code for reviews. Its "Embed a map" option embeds a map, not your reviews. Below is each method step by step, then the two things that catch people out afterwards: a Google review belongs to a location, not to your company, and reviews get edited and removed after you publish them.

Method 1: Add a Google Reviews Widget (About 2 Minutes)

This is the method for anyone who does not want to write or maintain code. The widget reads your live Google Business Profile, so new reviews show up and removed ones drop off without anyone touching the page.

1. Open the Google review widget builder and type your business name. Add the city if the name is common, then pick your listing.
2. The preview fills with your own reviews and your real rating. Pick a style. Grid, List and the rating badges are free. Sliders, marquees and masonry walls are on paid plans.
3. Set light or dark, your brand colour, and how many reviews to show.
4. Get your embed code: choose your website platform, enter your email, and copy the one line of HTML. The same code and steps arrive by email.
5. Paste it where the reviews should appear, using the block for your builder in the table below, and publish.

The rating shown comes from the profile's own aggregate rather than from the handful of cards on screen. That distinction is what keeps the number on your site identical to the number on Google, which is the entire basis on which a visitor trusts it.

Where to paste the code on each website builder

What it costs: our free plan gives you 1 widget with no limit on views. It shows the 10 latest reviews from the day you create it and carries a small BlooTrue badge. Daily updates, every style and no badge start at $9 a month. If you are comparing tools, we listed what each free plan allows in our comparison of free plan view limits.

Method 2: Copy the Reviews in by Hand

1. Open your Google Business Profile and pick the reviews you want.
2. Copy the reviewer's first name, the star rating, the date and the text exactly as written.
3. Build a testimonial section in your site editor and paste them in. Link each one back to your Google profile so a visitor can check it.

This is the manual route. Open your profile, copy the reviews you like, and hand-build a testimonial section with the reviewer's first name, the stars, the date and the text. It costs nothing and takes ten minutes, and the moment you publish it, it is a snapshot. New reviews will not appear, your displayed average will drift from your real one, and if a review is later edited or removed by Google your page keeps quoting a review that no longer exists.

Method 3: Use the Google Places API

1. Create a Google Cloud project and enable billing on it.
2. Enable the Places API and generate an API key. Restrict the key to your domain.
3. Find your Place ID and call the Place Details endpoint for that place.
4. Render the rating, the review count and the returned reviews in your own HTML, and keep Google's attribution.

This is the developer route. You create a Google Cloud project, enable billing, generate a key, call the Place Details endpoint, and render the JSON yourself. That gives you total control over markup and styling, and it is the right answer if you already employ a developer who will own the code, the key rotation and the quota. It has a hard limitation covered in the next section.

Why Does the Places API Return Only a Few Reviews?

Because the Place Details endpoint is designed to describe a place, not to export its review history. It returns a small sample of reviews per place, historically capped at five, and there is no page parameter that walks the rest. Developers have been asking Google to lift that cap for over a decade on its public issue tracker, and the cap has stayed.

That matters more than it first sounds. A business with 400 reviews using the raw API can show five of them, chosen by Google rather than by you, and the set will not necessarily include your most useful ones. If your plan was to build a wall of thirty reviews from the API, the plan does not survive contact with the endpoint.

It also means an API build cannot honestly claim to display "your Google reviews" in the plural sense a visitor assumes. It displays a handful of them. Knowing that before you scope the work saves the awkward conversation later.

The API is still the right tool for one job: pulling the live rating and total review count for a badge, where five review bodies are irrelevant and the two numbers are the whole point.

Which Method Should You Use?

For most small businesses the answer is the widget. You connect the Business Profile for the location you want, pick a layout, and paste one line of HTML. The widget reads the live profile, so the page stays current without anyone touching it, and the multi-location question above becomes a choice you make per widget rather than a problem you solve in code.

What Happens When a Review Is Edited or Taken Down?

Reviewers can edit their own Google reviews at any time, and Google removes reviews that breach its content policies. Both happen without warning you, and both change what is true about your profile.

A hand-copied testimonial section cannot know. It keeps displaying the four-star review that has since been raised to five, and the review Google removed for policy reasons, which is now a quote on your website with no source behind it. If a visitor clicks through to check, it is not there.

A widget that re-reads the live profile inherits both changes automatically, which is the quiet argument for the widget route that has nothing to do with design. Your page and your profile stay the same document. That is also what makes review schema on the page defensible, because the markup describes reviews that still exist.

What Do Google Reviews Actually Belong To?

A Google Business Profile, which is Google's record of one physical place. When a customer taps the stars, the review is written against that profile. It is not written against your company, your website, or your brand, and nothing about your legal entity ties the profiles together in the eyes of the review system.

This is why the star average you see in Google Search is always the average for the place you searched. Search a chain by brand name and Google shows you the nearest location's rating, not a national one, because a national one does not exist as a number anywhere in Google's data.

For a single-location business this is invisible and harmless. Your profile is your business, its rating is your rating, and the distinction never comes up. Everything below is the part that only bites once you open a second door.

What If Your Business Has More Than One Location?

Then you have one review set per location, each with its own count and its own average, and Google gives you no way to combine them. A practice with three surgeries might sit at 4.9 with 210 reviews at the flagship, 4.7 with 34 at the second, and 5.0 with 6 at the newest. Those are three separate facts, and no supported Google feature turns them into one.

The temptation is to average them yourself and put the result on the homepage. Resist it. A weighted average across three profiles is a number that appears nowhere in Google, so a visitor who checks any single location will find a different figure and conclude, reasonably, that you made yours up.

The honest options are to show the reviews location by location, each attributed to its own profile, or to show one combined wall of review cards without asserting a combined star average. Volume across locations is a real, checkable claim. A blended rating is not.

There is a practical consequence for site structure too. If you have a page per location, the reviews for that location belong on that page. Putting the flagship's reviews on every location page is the same mistake in a quieter form: the visitor reading about the newest branch is being shown proof about a different address.

Building the Widget: What to Get Right

You connect the Business Profile for the location, preview your real reviews and rating, then choose from over 100 layout styles across slider, marquee, grid, list, masonry and badge families. Colours, fonts, card density and which reviews appear are all adjustable, and the preview shows your own reviews rather than samples, so you are judging the real thing.

For multiple locations, build one widget per profile and place each on its own location page, or build a combined wall and let the cards carry their own attribution. Both are honest. Averaging the three ratings into one headline is not.

Where Should the Google Reviews Go?

Where the decision is made, which is rarely the footer. A visitor deciding whether to book, buy or call is doing it at a specific point on the page, and that is where proof earns its space: immediately above the booking form, next to the call button, or below the hero on the page that sells the thing.

A compact badge showing the live rating and count works better than a full wall at those decision points, because it is a number the visitor can absorb without stopping. Save the full wall for one prominent position where someone still weighing you up will actually read the cards.

On a location page, show that location's reviews. On a services page, favour reviews that mention that service. Relevance beats volume at the point of decision, and a visitor reading about emergency callouts is more persuaded by three reviews about a callout than by thirty about anything else.