How to Show Google Reviews on Your Website: Rules, Options, and Risks
Short answer
How do you show Google reviews on your website the right way?
Showing Google reviews on your website means displaying genuine customer ratings from your Google Business Profile, with clear attribution to Google. You have three legitimate options: the official Places API, a direct review link, or a third party widget. Your choice depends on speed, privacy, and Google's terms.
In this guide, we at Talha Aslan and team walk through that decision step by step. First, we cover the official routes. Then we look at widget risks, the structured data limit, and the rules on fake reviews. Finally, you get a launch checklist. If you want help with the visual layout of a review block, our guide to testimonial section design covers that separately.
Why put Google reviews on your website at all?
In practice, most visitors arrive with one quiet question: can I trust this business? Reviews on an independent platform answer that question better than your own sales copy. That is why so many owners want their Google ratings on the homepage or next to a quote form.
However, two goals often get mixed up. For example, displaying reviews builds trust on the page. Getting star ratings in Google Search is a different matter with different rules. Businesses that confuse the two add markup, wait for stars, and end up disappointed. For the broader picture, see our article on website trust signals. Here, we focus only on Google reviews.
- If your goal is trust, show real reviews with source and date.
- If your goal is conversions, place reviews near the decision point, such as a form or pricing block.
- For stars in search results, read the schema section carefully, because the rules differ.
In short, decide on the goal first. The method follows from it.
How does the Places API method work?
The Google Places API is an official service that returns details about a place, such as address, rating, and reviews, based on its Place ID. Your site sends a request and renders the reviews in your own design. As a result, nobody copies text by hand, and the content stays as Google holds it.
This route needs a Google Cloud project, a billing account, and an API key. Pricing and quotas change from time to time, so check the current figures on the official Google Maps Platform pricing page. In addition, you should restrict the key to your domain and, ideally, make the request on the server side.
In practice, the API does not hand you every review you have. Instead, it returns a limited selection chosen by Google. So do not pick this route expecting to hand select your best reviews. Google decides the order; you decide the presentation.
The policy page also recommends field masks. That means you request only the fields your interface needs. For example, if rating, text, author, and date are enough, you skip photos and opening hours. The response gets smaller, the page gets faster, and you avoid needless cost.
Which Google terms apply when you use the Places API?
The Places API policies page from Google Maps Platform sets clear rules for review display. These rules shape your design decisions directly. Here is the short version:
- Credit each review's author: name, photo, and profile link when space allows, or at least the photo when space is tight.
- Show Google Maps attribution: the logo, or the text "Google Maps" without changes or translation.
- Separate Google content visually from the rest of your page, for instance with a border, background, or whitespace.
- Do not copy, store, or redistribute reviews outside the permitted caching rules.
- Give users a way to open the original review on Google Maps.
The policy also recommends that you explain how reviews are ordered, show the relative publish date, and label translated reviews. Before you build anything, read the Places API policies page in full.
Why does the caching rule matter so much?
Many developers write reviews into a database for speed and then read them from there forever. The Places API policy does not allow that. You may store the Place ID indefinitely. Review content, on the other hand, you should fetch again when you need it.
A setup that breaks this rule looks fine on day one. Over time, though, a review that Google removes keeps living on your page. For example, if Google takes down a fake review and your site still shows it, you have a terms problem and a misleading page at once.
So we build it like this: the server keeps reviews in memory for a short time, then asks Google again. Visitors do not trigger an API call on every page view. Still, the data never turns into a permanent archive. Check the policy page for the current caching details, since such specifics can change.
Is a simple review link enough?
For many small businesses, yes. It is the lightest and safest place to start. Google Business Profile lets you create a link and a QR code that take customers straight to the review screen. According to Google's own help page on getting more reviews, customers can leave a review by visiting a Google link or scanning a QR code.
On your site, you can use that link in two ways. First, a "Read our reviews on Google" button that opens your profile. Second, a "Share your experience on Google" prompt after a completed job or purchase. Either way, you add no outside script, so speed and privacy stay untouched.
Of course, the review text itself will not appear on your page. The trust effect is smaller as a result; however, the terms risk is close to zero. If reviews are missing from your profile, our guide on Google reviews not showing explains the usual causes.
Which method should you choose? A comparison table
The table below compares four ways to put Google reviews on your website using the same criteria. The ratings come from our field experience and serve as a starting point, not a guarantee. Your own stack may shift them.
| Method | Setup effort | Speed impact | Privacy risk | Terms risk | Best for |
|---|---|---|---|---|---|
| Review link and QR code | Very low | None | None | Very low | Every business, as a first step |
| Places API with your own design | Medium, needs a developer | Low when done well | Low on the server side | Depends on attribution and caching | Sites that want a custom look |
| Third party widget | Low | Medium to high | Medium to high | Depends on the vendor | Teams that can audit the vendor |
| Screenshot or copied text | Very low | Depends on image size | Contains personal data | High, never current | Not recommended |
In short, start with the review link. If you want review text on the page, then choose a Places API build that follows the rules.
Should you build it yourself or hire a developer?
First, you can add a review link yourself in a few minutes. The Places API is another story. Storing the key safely, calling the API from the server, keeping the cache within policy, and fitting attribution into your design all take developer skill.
When clients come to us for web design services, we plan the review block from the start. We match Google's attribution to the visual style and protect the page speed budget. That way, the review section never looks like a patch added later. If you already have a developer on staff, the checklist in this guide gives them a solid frame too.
Also, agree in writing on who owns the integration code. We cover that question in our article on who owns website source code.
What are the risks of a third party review widget?
Put simply, a widget is a snippet from a vendor that you paste into your page. It then loads reviews from the vendor's servers. Setup is easy; in exchange, you hand much of the control to someone else. When we review a widget, we ask about four things.
- Speed. Widgets often load extra scripts, fonts, and images. If that runs before your main content, the page feels slow.
- Privacy. The visitor's browser connects to the vendor, which sees at least the IP address. Your privacy notice should cover that transfer.
- Terms. Does the vendor use the Places API, or does it scrape pages? Scraping can conflict with Google's terms and may stop working without warning.
- Dependency. If the free plan ends or prices change, your review block can go blank overnight.
So ask the vendor in writing how it gets the reviews and how it processes visitor data. In addition, open your browser's developer tools once and check which outside addresses the widget calls and which cookies it sets.
How does a widget affect page speed?
In practice, every outside script is extra work for the browser: download, parse, execute. Google's web.dev guides explain that heavy or late JavaScript can hurt responsiveness and cause layout shifts. If a review box loads late and pushes content down, the reader loses their place.
Therefore, if the widget sits lower on the page, load it lazily, which means only when it comes near the screen. Also reserve a fixed height for the box so the layout does not jump. We collect general ways to cut script weight in our article on how site speed affects SEO.
On phones, review carousels often overflow their container. If your page suddenly scrolls sideways, our guide on a website that scrolls sideways on mobile helps you find the element at fault.
What does a widget mean for privacy compliance?
When a browser connects to an outside server, that server sees at least the IP address. Under many privacy laws, including the GDPR for visitors in the EU, an IP address can count as personal data. For that reason, list the widget vendor in your privacy notice and cookie policy, and review any international data transfer.
If you call the Places API from your own server, the visitor's browser does not talk to Google for the review text. Author profile photos, however, may still load from Google's servers. Mention that detail as well. Our guide on building a GDPR compliant website covers the wider steps.
Note: This section is general information, not legal advice. Talk to a lawyer or privacy professional about your own situation.
Why are screenshots and copy and paste a bad idea?
At first glance, this is the fastest route. You take a screenshot of a review or paste its text onto your page. Yet this method has three weak points. First, the content never updates; if the customer deletes the review, it still sits on your site. Second, the reviewer's name and photo are their personal data, and you now use them in your own marketing.
Third, visitors cannot check whether the review really exists on Google. Without a link to the source, the text reads like copy you wrote yourself. Moreover, the Places API policy explicitly bars copying and redistributing reviews outside the permitted rules.
Images of text also fail screen readers and search engines alike. In short, a screenshot is the weakest choice for trust, accessibility, and compliance. A quote you collect directly from a customer, with written permission, is your own content. A copied Google review is not.
Will Review or AggregateRating schema get you stars in search?
For most business websites, no. Google Search Central's review snippet documentation sets a clear limit for LocalBusiness and Organization types. If the entity being reviewed controls the reviews about itself, those pages are not eligible for star review features. Reviews of your own business on your own site fall into that group.
The same documentation also says not to aggregate reviews or ratings from other websites. So pulling Google reviews onto your site and marking them up as AggregateRating does not bring stars. It also conflicts with the structured data guidelines. You can read the rule in Google's review snippet documentation.
We explain where AggregateRating does make sense in our guide to AggregateRating schema guidelines.
Which schema type should you use instead?
First, use LocalBusiness or a fitting subtype for your business page. Add address, phone, opening hours, and a sameAs link to your Google profile. However, leave out reviews and overall ratings you got from Google. That keeps your structured data accurate and defensible.
Instead of writing markup by hand, you can draft it with our schema generator and then validate it with Google's Rich Results Test. Put simply, Google reviews on your website are a trust decision, not a structured data decision. Keep the two apart.
The same logic applies to reviews you collect directly. Pages where a business controls reviews about itself still do not qualify for star snippets. Product pages on an online store follow different rules, which sit outside this guide.
Why should you never use fake or incentivized reviews?
Above all, Google's Maps user contributed content policy requires reviews to reflect a real experience. Paid reviews, reviews in exchange for discounts, reviews by employees, and reviews from several accounts run by one person are all prohibited. The policy also bars asking only happy customers for reviews.
In the United States, the FTC has a rule on consumer reviews and testimonials. Among other things, it targets buying and selling fake reviews and suppressing negative ones through threats or intimidation. The FTC's questions and answers on the reviews rule explain the details. This is not legal advice; ask a lawyer about your own case.
Buying reviews or creating fake accounts is an attempt to get around platform rules, and we never recommend it. If you face fake reviews from someone else, our guide on how to report fake Google reviews walks you through it.
Is it smart to hide negative reviews?
The Places API returns reviews in Google's order. Technically, you could filter that list to five star reviews only. The policy, however, recommends that you tell users how reviews are ordered and filtered. So if you filter, say so honestly.
Our field experience also points the other way. A wall of perfect reviews can make visitors suspicious. A critical review with a calm, helpful reply often shows that a business is open and fair. Therefore, we suggest showing your overall rating plus a "Read all reviews on Google" link instead of a hand-picked set.
For instance, if a service page shows only reviews about that service, label them as "selected reviews about this service." Then put a link to all reviews right below. That way, visitors know about the selection and can check it themselves.
Do Google reviews on your website help SEO?
First, do not expect a direct ranking boost. Google will not lift your page because you show its own review data. Still, there is an indirect benefit. Visitors who trust you stay longer, fill in the form, and call. In other words, the effect shows up in conversions.
On the other hand, a poor setup can hurt. A heavy widget slows the page, and wrong markup triggers structured data warnings. Therefore, protect speed and schema first when you add Google reviews on your website.
To measure the effect, track form submissions and call clicks on pages with the review block. Compare the period before and after launch, and account for seasonality and campaigns. That way, you decide with data instead of hunches.
How do you find your Place ID for the Places API?
In short, a Place ID is a unique identifier that Google keeps for every place. Your site uses it to request reviews. The Google Maps Platform documentation offers an official lookup tool; you type your business name and the tool shows the ID.
Next, save the ID in your site's configuration or in the right field of your admin panel. The policy lets you store Place IDs indefinitely, so you do not need to look it up on every request. Even so, an ID can change if your business moves or profiles merge. If the review block ever comes back empty, check the ID first.
- Does the profile name and address match the Google Maps listing exactly?
- Are there two separate profiles for the same business?
- Does the ID live in one place in your configuration?
How should the review block work on mobile and for accessibility?
Designers often build review blocks as carousels. An auto playing carousel, though, frustrates slow readers and confuses people using screen readers. For that reason, turn off auto play or add a clear pause button.
Also, never show stars as images alone. Add a text version such as "4 out of 5." Keep the font readable on small screens and the contrast strong. The Places API policy itself asks for a minimum contrast ratio on the "Google Maps" text attribution. So accessibility and compliance pull in the same direction here.
- Turn off auto play, or offer a pause control.
- Write the rating as text, too.
- Shorten long reviews with a "read more" link.
- Stack the cards in one column on narrow screens.
Where should the review block go on your site?
Above all, place reviews close to the moment of decision. A short strip on the homepage, a few relevant reviews on each service page, and a profile link on the contact page make a good balance. Putting the same widget on every page, however, wastes your speed budget.
- Homepage: rating summary and a link to your profile.
- Service page: a few matching reviews with attribution.
- Quote or contact form: a short trust line and the review link.
- Thank you page: a "Share your experience on Google" prompt.
If you mix your own testimonials with Google reviews on one page, separate them visually. Visitors should see at a glance which ones come from Google. That also matches the visual separation rule in the Places API policy.
What should you check before launch?
Next, here is the list our team runs before a review block goes live. We suggest you tick each item.
- Do reviews come from an official route, the Places API or a profile link?
- Does each review show the author name or photo and the Google Maps attribution?
- Does Google content stand apart visually from the rest of the page?
- Is review text kept out of
- Is the API key restricted and used on the server side?
- Does the box have a reserved height, and does it fit on mobile?
- Does your privacy notice cover the new data flow?
- Is your schema free of reviews and ratings taken from Google?
- Can visitors reach the original review and all reviews?
Example scenario: how does a small service business roll this out?
As an example scenario, picture a local auto repair shop. It has steady reviews on its Google profile, and the owner wants them on the homepage. First, the shop adds the review link and QR code to its thank you emails and to a counter card. That starts a clean, policy friendly review flow.
Second, a developer builds a small block that calls the Places API from the server. It shows a few reviews with author names and photos, the Google Maps attribution, and an "All reviews" link. Third, the schema holds only LocalBusiness details, with no review markup. Fourth, the privacy notice gets an update about profile photos loaded from Google.
Finally, every few months the owner checks that the block still works, the attribution is in place, and nothing overflows on phones. This scenario is illustrative, not a real client case.
When should you get professional help with Google reviews on your website?
If all you need is a link, you do not need help. Things get layered, however, once you want review text on the page, a design that fits your brand, correct caching and attribution, and an updated privacy notice. A mistake in one part can quietly push the whole block out of compliance.
At Talha Aslan and team, we build review blocks as part of the full site, with speed and privacy budgets in mind. If you plan a redesign or a new build, our business website design process includes a compliant structure for Google reviews on your website. We do not promise rankings or sales; we promise a setup that is correct and easy to maintain.
