Can you use Google reviews on your website? The rules, and how to add them to WordPress

Short answer

Yes. Google says reviews belong to the people who wrote them, so get the reviewer’s consent before copying one onto your site, and show Google’s logo with it. Showing reviews live through Google’s own API, with its attribution, is what its Maps terms provide for. Neither way earns your business review stars in search.

Most businesses want their best Google reviews on their website, and most get them there by pasting the text into a page or installing a widget. Both can be done properly, but they fall under different rules: Google’s guidance on using reviews in marketing, its Maps Platform terms for anything fetched with an API key, and in the UK the advertising code on testimonials. This guide sets out what each one says, then the ways to show reviews on a WordPress site that stay inside them.

What we read. On 5 November 2026 we read Google’s guidance on customer reviews, the Google Maps Platform terms and service-specific terms, the Places API policies, Google’s review snippet guidelines and the CAP Code. This is a practitioner’s summary, not legal advice. If you have already decided to use a plugin and want to know which, our comparison of Google reviews plugins for WordPress covers that.

Who owns a Google review, and what does Google let you do with it?

Not you. Google’s guidance on customer reviews says reviews belong to the people who wrote them, even when they are posted on your business’s listing. To use one in your own marketing, which Google says includes your website and print or digital ads, you need the reviewer’s consent. You can ask by replying to the review; Google will not give you the reviewer’s contact details.

The same guidance sets the rules for mentioning your rating and Google’s name:

  • Say the rating is “on Google”. Not “Google-rated” or “Google rating”, which suggest Google produced the score.
  • Date it. Give an “as of” date whenever you quote your overall rating or the number of reviews, because both change.
  • Show Google’s logo. Use the Google G or the full wordmark when you refer to your reviews on Google, the same size as any other companies’ logos shown beside it.
  • No home-made badges. Don’t put stars next to Google’s name or logo, and don’t use unofficial logos, badges or lockups.

What do Google’s Maps Platform terms allow?

Anything that fetches reviews with your own Google API key, whether your developer’s code or a plugin, works under the Google Maps Platform Terms of Service (last modified 26 August 2026) and the service-specific terms (last modified 28 October 2026). Whoever holds the key has accepted them, which on a small business site is usually the business. Four parts matter for reviews.

  • Attribution. The Places API policies say you must always credit a review’s author (at least their avatar where space is tight), show Google Maps attribution near the reviews and in the same container, preferably as the Google Maps logo, explain how the reviews shown are ordered and filtered, and say when a review has been translated.
  • Storage. The service terms let you keep place IDs indefinitely and coordinates for up to 30 days. Nothing lets you keep reviews. The main terms’ “No Scraping” clause gives as an example that the customer will not “copy and save business names, addresses, or user reviews”, and the “No Caching” clause rules out caching anything not expressly permitted.
  • Maps. Places content can be shown without a map, but not on a non-Google map, and the main terms also rule out using Google’s core services with, or near, a non-Google map. Worth checking if your location pages already carry an OpenStreetMap map.
  • Five at a time. The Places API returns at most five reviews for a place, sorted by relevance. Fetching every review of a location takes the Business Profile API, connected through the account that manages the profile.

The storage rule is easy to miss. Several plugins build a longer list than five by saving each review they fetch with your key, so the list grows over the weeks. Read literally, that is what the terms rule out for the key holder. Google has published nothing about how it applies this to small sites, so weigh it rather than assume it is fine. Plugins that fetch through their vendor’s own service, without your key, move the question to the vendor: how it gets the reviews is between it and Google, and you cannot check it.

The route that keeps to the terms by design is Google’s own. Its Places UI Kit includes a Place Details element that can show a place’s reviews, rendered by Google with Google’s attribution, and the service terms allow it beside any map, including a non-Google one. It needs an API key on a Google Cloud project with billing turned on, and Google bills it in its Essentials tier.

Copying a review by hand, or showing it through Google or a plugin?

Each route sits under a different set of rules, which is the real difference between them.

RouteRules it falls underKeeps itself current?What you need
Your rating, linked to your profileGoogle’s guidance: “on Google”, an as-of date, Google’s logoNo; update the figures when you checkYour profile’s link
A review quoted by handGoogle’s guidance (the reviewer’s consent, Google’s logo); in the UK, the CAP CodeNoThe reviewer’s yes, and a record of the original
Google’s Places UI KitMaps Platform terms, with Google’s attribution built inYesAn API key, a billing account and a little code
A plugin using your own keyMaps Platform terms, including attribution and storageYes, five reviews a requestA key, a billing account, and a look at what the plugin saves
A plugin using its vendor’s serviceThe vendor’s own terms; how it gets the reviews is out of your sightDepends on the planAn account with the vendor

Quoting by hand is the most work to keep fresh, but it has the firmest footing once you have consent, and it lets you choose reviews that answer the questions customers actually ask: whether you turned up on time, whether you cleaned up, what the price was against the quote. A feed of five shows whichever reviews Google ranks as most relevant, which may answer none of those.

What do UK advertising rules say about reviews and testimonials?

Since 2011 the Advertising Standards Authority’s remit has covered marketing on a business’s own website and other online space it controls, where the material is directly connected with selling its goods or services. So reviews on your service and location pages are likely to be in scope. Section 3 of the CAP Code has the rules, including three added when the consumer review provisions of the Digital Markets, Competition and Consumers Act 2024 came into force on 6 April 2025:

  • Rule 3.44: no fake consumer reviews, meaning reviews that claim to be based on a genuine experience when they are not.
  • Rule 3.45: make clear where a review was incentivised.
  • Rule 3.46: don’t publish reviews, or figures drawn from them such as a star rating or review count, in a misleading way. Its examples include publishing positive reviews while leaving out or removing negative ones, and giving positive reviews greater prominence than negative ones.
  • Rule 3.47: hold documentary evidence that a testimonial is genuine, and contact details for the person who gave it.
  • Rule 3.49: a factual claim inside a testimonial must not mislead. If a review calls you the cheapest in town, that is now your claim to back up.
  • Rule 3.50: don’t feature a testimonial without permission, although exceptions are normally made for accurate statements taken from a published source. Google’s own guidance asks for consent regardless, so ask.

The ASA’s advice on consumer reviews says that suppressing or hiding accurate reviews is unlikely to be acceptable, and describes a ruling of 14 October 2026 against a retailer whose website showed a higher rating and more reviews than its Trustpilot profile did, with featured reviews whose names, wording and dates differed from the originals. The lesson for a Google rating on your site is simple: the figure and the quotes must match what the profile shows, on the date you say.

In the US, the FTC’s rule on consumer reviews and testimonials, in force since 21 October 2024, bans fake reviews, paying for reviews that must express a particular sentiment, and undisclosed reviews by a company’s own managers. Should you buy Google reviews? covers what Google itself does about fake ones.

Why won’t marking up your own reviews earn stars?

Because Google’s review snippet guidelines rule it out. If the business being reviewed controls the reviews about itself, its pages using LocalBusiness or any other Organization structured data are ineligible for the star review feature. Google’s own example is a review of a business placed on that business’s website, either in its structured data or through an embedded third-party widget, and it names Google Business reviews widgets.

Taking your Google rating and adding it to your pages as an AggregateRating fails a second rule in the same guidelines: ratings must be sourced directly from users, and you should not aggregate reviews or ratings from other websites. So switch off review markup in any reviews plugin that adds it, and expect the reviews to help the visitor rather than the search result. Why your Google review stars are not showing goes through the rule in more detail, and common schema mistakes on local pages covers the markup that often comes with it.

How do you add Google reviews to a WordPress site?

Five ways, from least to most moving parts. Most small businesses need the first two and nothing else.

  1. A rating line. In a Paragraph block near your contact details, give your rating “on Google”, the number of reviews and the date you checked, with Google’s G logo, linked to your profile. Beside it, a link straight to your review form; our Google review link generator builds one.
  2. Hand-picked quotes, with consent. Ask the reviewer, by replying to the review or through the contact details you already hold from the job. Put each review in a Quote block with the name as it appears on Google, the month it was written and “Review on Google” with the logo, linked to the review. Keep a screenshot of the original and a note of when consent was given, which is the evidence rule 3.47 asks for.
  3. Google’s Places UI Kit in a Custom HTML block. For a developer, or anyone comfortable pasting code: a Place Details element with its reviews content, loaded with a Google Maps API key restricted to your domain. Google renders and attributes the reviews, and nothing is stored on your site.
  4. A reviews plugin. Choose one from our plugin comparison, then check four things before you rely on it: whether it adds review markup (turn it off), whether it saves reviews fetched with your key, whether it has a filter that hides low ratings (rule 3.46), and where it sends your Place ID.
  5. Reviews per branch. If you have several branches, each Business Profile has its own reviews. Point each branch page at its own profile and show that branch’s reviews there, not head office’s best five on every page.

Which reviews should go on which page?

A review is most useful on the page where the reader is deciding. On a service page, choose reviews about that service. On a branch page, use that branch’s reviews. On a page for a town you travel to, a review from a customer in that town, quoted with their consent and with what the job was, does two jobs: it reassures the visitor, and it is local content no sibling page can share. Repeating the same three quotes on every location page does neither, and adds to the text the pages have in common. Location page content ideas has more material of that kind.

Where Townsmith fits

Local Pages Engine does not fetch or display Google reviews, and the schema it writes contains no review or rating markup, so it cannot put your pages on the wrong side of the self-serving rule. Every page it builds has an empty, named slot for something true of that town, and a consented review from a customer there is good material for it. Pro’s local-proof library lets you write a town’s proof once and reuse it on every service page for that town. For the widget itself, use one of the plugins in our comparison, or Google’s own UI Kit.

Common questions

Do I need permission to put a Google review on my website?

To copy one onto your site, yes: Google’s guidance says you must get the reviewer’s consent to use their review in your own marketing, and names your website as an example. Reply to the review to ask. Showing reviews live through Google’s own API or UI Kit, with Google’s attribution, is the use Google’s Maps terms are written for.

Can I show only my five-star reviews?

Picking a few testimonials is normal. Presenting a filtered feed as if it were all your reviews is not: CAP rule 3.46 names leaving out negative reviews and giving positive ones greater prominence as misleading. Show your overall rating on Google beside the quotes and link to the full list.

Can I shorten or tidy up a review?

Google’s guidance does not say. Under the CAP Code the quote must not mislead, so cut only where the meaning is unchanged, mark the cut with an ellipsis, and never change what the reviewer said. If in doubt, ask them when you ask for consent.

Can I put my Google rating on a van or a flyer?

Yes, following the same guidance: the rating “on Google”, an as-of date, Google’s official logo and no stars beside it. For print that stays in circulation, the date matters most, because the rating will move after it is printed.

Will a reviews widget get stars next to my site in Google?

No. Google’s review snippet guidelines make a business’s own reviews ineligible for stars when marked up as LocalBusiness or Organization, and they name embedded Google reviews widgets as an example.

Checked on 5 November 2026. Written by Stephen Evans.