How to add Google reviews to Webflow

What you need

A saved widget and Designer access. Webflow lists an active Site plan, or a Core, Growth, Agency or Freelancer Workspace, for Code Embed access (Webflow's Code Embed article). Test on a static page before a CMS template.

Add the widget in five steps

1. Check code embed access

   Webflow's current help says the Code Embed element is available with an active Site plan, or a Core, Growth, Agency, or Freelancer Workspace. That is the code feature to check; a free widget account does not unlock a Webflow plan feature. Ask the site owner to confirm the site's plan or workspace access if the element is unavailable. The Code Embed accepts HTML and JavaScript inside script tags, but not server-side code.

2. Create and copy your review widget

   Connect your business in VerifiedWidget with its Google Maps link. Confirm the review source, dates, and business identity. Choose a grid for a full-width section, a list for a narrow column, or a slider for a compact area. Save the widget, then copy the complete script tag from its Embed dialog. The Free plan has one widget, up to 20 imported reviews refreshed monthly, and 10,000 views per month.

3. Place the Code Embed in the Designer

   Open the target Webflow page in the Designer. In the Add panel, add a Code Embed element to the page at the point where reviews should appear. Paste the entire VerifiedWidget snippet into its code editor and save and close the modal. Leave the supplied opening and closing script tags intact. Do not wrap the snippet in html, head, or body tags; Webflow warns they will break your layout. In the Designer a script shows only as a placeholder box, which is normal.

4. Set the placement and publish

   Give the element a suitable parent container and spacing in Webflow's Style panel. Avoid placing a wide grid inside a narrow card. Publish the site to the Webflow staging domain or your custom domain, then inspect the public URL. Webflow says script effects only go live when you publish, and custom code does not run in expand canvas view. If VerifiedWidget's domain allowlist is enabled, add each hostname you will test.

5. Check the CMS scope and phone view

   If the Code Embed is on a Collection page template, every item using that template can show it. That works for a shared business review widget, but it should not imply each review describes a particular article, project, or product. For item-specific displays, plan separate widget or collection rules before reusing the template. Test one Collection item and another unrelated item, then check both at phone width.

Webflow CMS pages need a scope decision

Webflow lets a Code Embed sit on a Collection page or inside a Collection list. If you put one saved business widget on a Collection page template, it can appear for every item in that collection. For example, a local service company might want the same business reputation section on all service pages. An agency showing different client businesses needs a separate plan for which widget appears on which client page. Do not paste one client's widget into a template shared by other clients.

Webflow also documents custom code within a CMS rich text field. That can be useful when one Collection item needs its own embed, but it gives editors more opportunity to paste incorrect code. A template-level Code Embed is easier to maintain when the same business reviews belong on every item. If you bind fields dynamically, test more than one published item and check for an empty or wrong field. Do not assume a single preview item proves all CMS pages are correct.

For a reusable static display on several ordinary pages, Webflow says a Code Embed can be turned into a component. Update the shared component once and inspect every page that uses it. Be deliberate about view counts: a site-wide component can load a widget on many pages, using more monthly views than one contact page.

Best placements and mobile check

A homepage can show a grid below the primary service explanation. On a product or service page, put a compact list after the main details and label it as business reviews rather than product-specific ratings. A contact page can place a short list near the form while leaving enough room for input fields. A booking page should keep its appointment controls visible and use a short review section that does not crowd the calendar. On a CMS case study page, put the widget after the case study rather than inside an unrelated project quote.

Webflow's Code Embed takes the width of its parent when its code does not specify dimensions. Check the parent container and breakpoints [screen size settings] if cards are too narrow or overflow. Use the Designer's phone view, but also open the published URL on a phone. Read a full long review, tap the navigation controls, and make sure source attribution is not clipped. If a full grid is crowded, switch to a list or slider in VerifiedWidget rather than hiding review text with CSS.

Widget not showing? Check these first

• Not published. Designer changes appear only after you publish to your staging or custom domain.
• Wrong CMS template. A Code Embed on one Collection template does not affect another template.
• Page-level tags. Do not add html, head or body tags inside the Code Embed.
• Size. Webflow caps a Code Embed at 50,000 characters; the widget script is far shorter, so a rejected paste usually means extra text was pasted.

Webflow's support team does not troubleshoot custom code, so send widget questions to VerifiedWidget with the published page address.

If the widget is still blank on the published page, work through the general checklist.

Code Embed versus a Webflow Marketplace app

Webflow's Marketplace lists apps, which Webflow describes as third-party applications. Some may show reviews. An app may be useful if you want its own Designer controls or a broader review workflow. Read the individual listing for permissions, supported sources, limits, and current price. A direct VerifiedWidget Code Embed is simpler when you already have the widget and want a specific saved layout on a page or CMS template. Both approaches still require testing the published page and matching the review source to the page claim.

See also our guide to Google star ratings.

Frequently asked questions

Related reading