RU Get it free

An honest answer

Embedding Google reviews on your website

Short version: you can, several tools do it, and the result is a block of somebody else’s data drawn on your page by a script. We do not do that. What we do is the other half of the job — reviews your customers leave for you, on your domain, inside your HTML, with the markup that puts stars in search results.

How embedding Google reviews actually works

Every tool in this category does one of two things. It reads your Google Business Profile through Google’s API and re-draws the reviews on your page, or it scrapes the public profile. Both share the same three properties:

  • The content is not yours. It lives on Google, is licensed by Google, and can be changed or removed without you being told.
  • It is drawn by a script. The reviews are not in the HTML that arrives from your server, which is why a page full of them can still look empty to anything that reads HTML rather than running JavaScript.
  • It breaks. API terms change, quotas change, scrapers get blocked. When that happens the block vanishes and there is nothing underneath it.

This is not an argument against Google reviews. Collect them — they matter where buyers look. It is an argument against treating a script that borrows them as the review content of your own site.

Why star ratings rarely follow

The stars people actually want in search results come from review markup on your page. Google’s own guidance for review snippets is direct about the case where a site republishes reviews gathered on another platform: that is not what the markup is for, and marking up borrowed reviews as your own is the fastest way to have the whole rich result ignored.

Reviews collected on your own site are a different case entirely — that is exactly the situation the markup describes. How review schema and star ratings work →

What we do instead

The review is left to you

Your customer opens your link or scans your QR code and writes the review on your page. No account, no app.

You moderate

Nothing is published until you approve it. A reply from the company sits under the review, where it convinces.

It arrives as HTML

Ready markup you paste into the page — reviews in the text, with schema.org attributes, not assembled by a script after load.

It is yours

The reviews stay on your domain. No API to lose access to, nothing to break when a third party changes its terms.

One thing we do not do: automatic import from Google, 2GIS or Yandex. Moving a handful of existing reviews across by hand, with a note saying where they came from, is a decision for the site owner — not something we do quietly in the background.

Questions

So can I embed Google reviews or not?
You can, with one of the widgets built for it. We simply are not one of them, and we would rather say so on this page than after you have signed up.
Should I use both?
That is the usual answer. Google reviews work where buyers compare businesses on a map; reviews on your own site work where buyers are already reading about you and need a reason to believe it.
Will you import my existing Google reviews?
Not automatically. Copying a few across manually, attributed, is your call to make.
What does it cost?
The widget is free to start, with no card. Connect it →