Google Reviews Webflow: Widget, Plugin and Embed Options for Your Site

Almost every guide in this category opens with a vendor recommendation. On Webflow that is the wrong first step, because the platform decides whether you can paste anything at all. Webflow documents the Code Embed element with an explicit requirement: you can use it "if you have a Core, Growth, Agency, or Freelancer Workspace, or if your site has an active Site plan". The identical sentence appears on the help page for custom code in head and body tags. And the Site plan comparison on Webflow's pricing page lists the "Custom code" row, described as adding "custom code and scripts to your entire site or individual pages", with a dash under Starter.

Read together, those three first party statements say the same thing three ways: a free Webflow site cannot run a third party Google reviews widget. Not a cheap one, not a free one, none of them. That is different from Wix, where the drag and drop Embed HTML element works on any plan and only the cleaner Custom Code route is gated, and different again from self hosted WordPress, where a plugin installs regardless of what you pay anyone.

The practical order, then, is: confirm the plan, pick the route, and only then compare what the vendors charge. A Basic Site plan is $15 a month billed yearly and a Premium Site plan is $25 a month billed yearly, both read from Webflow's pricing page in August 2026. Budget that before you budget the widget, because it is usually the larger number of the two.

Search autocomplete puts "webflow custom code character limit" second only to the bare phrase itself, which tells you how often people hit it or fear they will. The number is 50,000. Webflow states that the Head code and Footer code sections in Site settings "can accommodate up to 50,000 characters each", that page level head and before body code carry the same allowance each, and that code in a Code Embed element "can't exceed 50,000 characters".

A Google reviews widget almost never approaches that on its own. What vendors ship is a loader: a script tag pointing at their CDN plus a div carrying your widget ID, usually well under 500 characters. The limit becomes real in two situations. The first is a vendor that hands you the reviews inline as static HTML rather than a loader, which some tools do specifically so the review text is in your page source for search engines. Ninety reviews rendered as markup will pass 50,000 characters comfortably. The second is accumulation: analytics, a consent banner, a chat widget, a heatmap script and two font loaders all sharing one Footer code field, and the reviews snippet is simply the one that would not fit.

Webflow gives three escapes, and they are not equivalent. You can host the code elsewhere and reference the script, which is what a loader already does. You can minify it. Or you can split it "across multiple Code Embed elements, as long as that doesn't break any JavaScript functions", which is Webflow's own wording and also its own warning: splitting a script mid function will break it, and splitting static review markup will not. Know which kind you are holding before you cut it in half.

This is the single most useful thing to know about running any widget on Webflow, and it is a line most reviews tutorials leave out. Webflow says plainly: "If you'd like to reuse the same embedded content across your site, turn your Code Embed element into a component."

The reason it matters is maintenance, not convenience. Social proof belongs on more than one page. A home page section, the pricing page above the plan table, a services page, and each of five landing pages is nine placements before anyone calls it excessive. Paste the snippet nine times and you have nine independent copies of the same code. When the vendor changes its embed format, when you swap to a different widget ID, or when you decide the block should load lower down the page, that is nine edits and one of them will be missed. Make it a component and it is one edit.

There is a second reason, specific to reviews. Widgets that meter monthly views count every load. Nine sloppy placements, including two on pages you forgot were still published, burn the meter faster than nine deliberate ones. A component gives you a single place to see where the block actually lives, which makes the view count something you can reason about instead of something that surprises you on the 22nd of the month.

If your reviews sit inside CMS content rather than static pages, the equivalent move is the rich text custom code block, and Webflow also supports pulling Collection fields into embedded code so the snippet can vary per item. That is the route for a case study template where each entry shows its own client's quote.

Worth reading before you commit, because it changes who you escalate to at 4pm on a launch day. Webflow's help documentation on the Code Embed element states: "Custom code is an advanced modification that may conflict with Webflow's underlying functionality, so Webflow can't guarantee its full compatibility. Our support team can't help troubleshoot custom code, since that falls outside our customer support policy." The custom code help page carries the same position and points you to the Webflow Community instead.

That is a reasonable policy and it is not a criticism of Webflow. It is a fact about your support path. A Google reviews widget on a Webflow site has exactly one owner, the widget vendor, and if that vendor's answer is that the problem is on the Webflow side, you are the person holding both ends. It is a genuine argument for choosing a vendor whose support you have actually tested, and for preferring a plain script loader over anything that reaches into the page's layout, because the plain loader has fewer surfaces to conflict with.

It is also an argument for keeping the number of third party scripts on a Webflow site small. Every one of them shares the same unsupported status. If reviews, chat, consent and analytics are four separate vendors, a conflict between any two of them is a problem nobody has agreed to own.

Suppose you clear the plan gate, paste the embed and connect your Google Business Profile, which carries eighty reviews. Most widgets will show five of them. This is not a limitation the vendors invented and it is not something a higher plan removes. Google's Places API reference describes the reviews field on a place as: "List of reviews about this place, sorted by relevance. A maximum of 5 reviews can be returned."

Two consequences follow. Google chooses which five, by its own relevance ordering, so the review you would put first is not necessarily the one that appears. And when a customer leaves a new one, the set can change without you touching anything, which is fine until the review that rotates in is the lukewarm three star.

Vendors that display more than five are not calling that endpoint live. They are caching a larger set that was collected earlier, or they are asking you to paste review text in yourself, which is a different product with different compliance implications. When a tool advertises unlimited Google reviews, the honest question to ask its support is whether the reviews refresh from Google and how often, because the answer decides whether you are displaying live proof or a snapshot.

There is also an eligibility question underneath all of this. A Google Business Profile needs a physical location customers can visit or a defined service area you travel to. A Webflow site is very often a studio, a SaaS product, a consultancy or an agency with no qualifying address, and those businesses have no listing, therefore no Google reviews, therefore nothing for any widget on this page to display.

Another phrase autocomplete surfaces on its own. When a reviews embed shows nothing on a Webflow site, the cause is almost always one of five things, and they are worth checking in this order because the cheap checks eliminate the expensive ones.

One more that catches people: the site settings code fields only apply to published pages, so editing them and then not republishing leaves the old version live. And Webflow accepts only HTML, CSS and JS in these fields. It states you cannot integrate server side languages such as Perl, PHP, Python or Ruby, which matters if you were planning to proxy the Google API yourself from inside Webflow. You cannot. That has to live somewhere else.

Prices in this category look close together and the metering does not, which is where the bill actually comes from. The unit each vendor counts decides whether your cost tracks your traffic, your number of pages, your number of client sites, or nothing at all. Every figure below was read from each vendor's own pricing page in August 2026.

Two things in that table are worth more than the headline numbers. The first is that POWR prices per app rather than per account, and the prices genuinely differ between apps. On the day this page was written, POWR's Reviews app listed Starter at $5.94 and Pro at $14.19 a month, while POWR's Social Feed app listed Starter at $7.04 and Pro at $15.84. Same vendor, same tier names, different prices. Only the $98.99 a month Business plan is constant, because that one covers all the apps in the library. If you are budgeting for two POWR widgets, check both pricing pages rather than doubling one number.

The second is that Elfsight's Basic tier is 5,000 widget views a month. A widget view is one load of the block, not one visitor session, so a reviews block placed in a site wide footer records a view on every page of every visit. A modest Webflow marketing site doing 2,000 sessions a month at three pages a session is 6,000 loads, over the cap, and the consequence is deactivation rather than a surcharge. The vendor that meters domains and the vendor that meters nothing both get cheaper as your traffic improves, which is the opposite of how the view metered plans behave.

Elfsight is running a promotion at the time of writing, so its $4, $8 and $16 tiers are discounted against $6, $12 and $24 regular. Prices in this category move. Re-check before you buy.

Everything above solves a display problem. Reviews already exist on a Google listing and you want them visible on a Webflow page. That is a real job and the widgets do it. It is worth being clear about what it does not cover, because a lot of Webflow sites go looking for a Google reviews widget when the thing they actually need is different.

A Google review is public, short, written for Google rather than for you, and it is gone from your page if the customer deletes it or Google filters it. You cannot ask for a specific detail, you cannot get a second sentence about the outcome, and you certainly cannot get video. If a business has no qualifying address, it cannot have any of it. That is the position most agencies, studios, SaaS companies and consultancies on Webflow are actually in, and no widget on any plan changes it.

A testimonial you collect answers a question you asked. It carries a name, a role and a company. It can be a thirty second clip of a client saying the thing your sales page has been claiming, which no Google review will ever be. It stays up because you have permission to use it, and it appears in the order you decided rather than the order Google chose. Both can live on the same page: the Google block for the local trust signal, your own wall for the substance.

On Webflow, the collected wall goes in through the same Code Embed element you were going to use anyway, so it clears the same plan gate and adds nothing new to the checklist. Paste it, make it a component, place it wherever proof belongs. For a wider look at the same decision on other builders, the Webflow testimonials page covers collecting and displaying your own proof on Webflow specifically, and the Google reviews widget page compares the display vendors without the platform constraint.