Google's own Places API terms require every review to keep its author's name and a link
You have a decent rating on Google and you want to show it off on your own site. Stars right at the entrance to your homepage sell better than an empty headline, so why not.
Someone offers you a widget. It pulls your latest Google reviews straight onto the page, stars next to the logo, done in a few minutes. It looks like the shortest path to exactly what you want.
Whoever sells the widget usually will not tell you two things. One is written down by Google. The other follows from who is actually publishing the reviews once they are on your site. Both change what you can actually expect from a widget, and both are things you can check yourself before you install anything.
Google publishes the reviews on Maps, under its own brand and its own rules. The moment you put them on your own website, you take over that role, in your own layout and your own design.
A business that publishes consumer reviews on its own site takes on a disclosure obligation that a business relying only on Maps does not carry. It does not require you to verify every review, only to state plainly whether you verify reviews and, if so, how. A widget will not write that sentence for you; that has to appear on your own site in your own words. This page is not legal advice, and the exact wording that satisfies your state's consumer protection rules is worth a few minutes with an attorney before you launch a widget, not after a complaint arrives.
Google's Places API content policies set out three conditions, and almost nobody reads them.
You must credit the author: "You must always credit the author when displaying photos or reviews." Every review needs the author's name, their avatar, and a link to their profile, not just the review text on its own.
A visitor has to be able to reach the original review: "For each photo and review, end-users must always have access to view the individual source photo or review on Google Maps." And you cannot set the content aside for later: "You must not pre-fetch, cache, or store Places API content beyond the allowed exceptions." A place identifier is exempt from that rule. Review text is not.
Google Places API Policies, read September 14, 2026
Copied text next to a logo breaks the first and third conditions at once: no author, no link back, and it keeps sitting there even after the author edits or deletes it on Google. A screenshot of a review has the same flaw and also cannot be read comfortably on a phone. A widget built to satisfy all three conditions honestly can be written. One that just copies text cannot.
The short answer: this path does not get you stars in search results, and Google states it directly.
"If the entity that's being reviewed controls the reviews about itself, then pages that use LocalBusiness or any other type of Organization structured data are ineligible for star review feature."
Google's structured data guidelines for reviews, read September 14, 2026
A business that decides for itself which reviews about itself to show does not qualify for star results. Google gives an example that lands exactly on a widget: "a review about entity A is placed on the website of entity A, either directly in their structured data or through an embedded third-party widget (for example, Google Business reviews or Facebook reviews widget)."
One more rule from the same family targets what people most often do with a widget in practice, show only the good ones:
"Don't rely on human editors to create, curate, or compile ratings information for local businesses."
Google's structured data guidelines for reviews, read September 14, 2026
Hand-picking reviews, whether a widget does it or a person does it, is exactly what that rule forbids. A widget can be useful for a visitor reading your page, but it will not earn you a star result in search, however carefully it is built. The rule does not target execution, it targets who is publishing a review about themselves. So a widget sold to you as a path to stars in search is selling something Google's own rules say does not work.
If you decide on a widget anyway, for the visitor reading the page rather than for search stars, ask the vendor three things.
Three no answers means a widget that breaks the Places API terms the same way copied text does, just less visibly. A vendor's answer that does not clearly answer one of these is effectively a no.
An honest alternative for a business that is not an e-shop is often no widget at all, just a link or a button pointing at the Google profile. The reviews stay exactly where Google already handles the disclosure obligation itself, and nothing about your own site claims otherwise.
No widget delivers stars for a business reviewing itself, since that path does not exist, and the obligation to say whether you verify reviews cannot be handed off to a widget either way. For a business without an e-shop, a link or a button to the Google profile is often the more honest answer than trying to reproduce the reviews on your own page at all.
Valtela does not sell a review widget. A Valtela card on the counter leads to a screen with a public Google review and a private message to the owner, and that has nothing to do with what is on your own website. This page exists because a straight answer to this question is hard to find written down anywhere else.
Only care about the legal boundary? The reviews and the law page covers the obligation in full. What Google generally forbids and allows around reviews, dated and sourced, is on the Google review policy page. And if this is really about getting more reviews rather than displaying the ones you have, the demo shows the real dashboard with a sample business's data in it.
The plan runs $599 a year, an extra card is $79 a year, and the full pricing is on the pricing page.
Every citation on this page comes from one of these pages. The link goes to the original source, not to our summary of it.
$599a year, plus $79 for each extra card. See the full price.