How to embed Google reviews on WordPress

Before you open WordPress

A saved widget, with its script copied exactly from the Embed dialog. You also need a WordPress role that can publish unfiltered HTML (code WordPress does not clean up). On a normal site, Administrators and Editors have this right; Authors and Contributors do not. On a multisite network, only Super Admins have it (see WordPress's roles guide). A sample preview does not mean your own reviews have imported yet, so check the business name and review count first.

If you choose WordPress / PHP in the Embed dialog, the code has two parts. Paste only part 1, the script tag, into the block. Part 2 is optional PHP for your theme's header. PHP does not run inside a block, so it will not work there.

Gutenberg: use a Custom HTML block

1. In WordPress, open the page where reviews should appear. Add a new block at the exact position you want the widget.
2. Search the block inserter for Custom HTML, or type /html in an empty block. Click Edit HTML, paste the copied script into the code box, and press Update. Since WordPress 7.0 the block also has CSS and JavaScript panels, shown only to users allowed to add unfiltered HTML. Put the whole script tag in the HTML panel.
3. Save or update the page, then open the published page in a separate browser tab. Check the result while signed out as well as while editing.

The editor's preview may handle scripts differently from the published page. If the script disappears after saving, your account may lack permission to publish unfiltered HTML, or your host may restrict it. Ask an administrator with the right permissions to place the code. WordPress explains this in its Custom HTML block guide.

Classic Editor: switch to Text

If your site uses the Classic Editor, open the page and switch its editor from Visual to Text. Paste the embed at the point where reviews should appear, then update the page and check the published result. Avoid moving back and forth between modes after pasting without checking whether WordPress changed or removed the script. If the code is stripped on save, ask a site administrator to verify your permissions and the site's security settings.

A script should sit in the page where you want the widget, not inside a code-formatting block that displays it as text. A Text-tab preview can still differ from the public page. Check the finished page on a phone and in a private browser window before calling the installation complete.

Elementor: use an HTML widget

Open the target page with Elementor. Drag the HTML widget into the section where reviews belong, paste the VerifiedWidget script in its code field, and update the page. Open the published page to confirm it loads. Elementor's HTML widget documentation says scripts can be added there, but access may be limited to administrators. If you cannot find or use the HTML widget, check your WordPress role or ask the site owner.

Give the section enough width for the chosen layout. If a carousel appears cut off, inspect the Elementor column width, overflow settings, and spacing. Try a list or slider layout for a narrow sidebar. Do not judge mobile appearance from desktop editor width alone.

Divi: use a Code module

In Divi's Visual Builder, add or open the row where reviews should go. Insert a Code module, paste the embed in the Text field on the module's Content tab, save the module, and publish the page. Divi's Code module guide confirms that it accepts third-party HTML and JavaScript. A script may appear only after you save and leave the builder, so inspect the public page.

If the display is too narrow, try a wider row or a more compact layout. If you placed code in a global Divi header or template, check every page that inherits it before removing an older widget. A page-level Code module is easier to test first.

Theme widget areas: footer or sidebar

Some WordPress themes provide footer and sidebar widget areas. Look under Appearance → Widgets, or the equivalent area in your theme's editor. If the area accepts a Custom HTML block or widget and permits scripts, paste the embed there. Theme support varies: a full-site editing theme may use a template part instead of the classic Widgets screen. WordPress documents both classic widget areas and the block-based Widgets editor.

A footer placement can load on every page, so consider how its views count toward your monthly plan allowance. A list often fits better than a wide review grid in a sidebar. The badge layout is different: it floats in a corner of the screen, wherever you paste the code. Test the site on mobile to confirm the widget does not crowd navigation or cover page content.

Widget not showing? Check these in order

1. Published page: check the public URL outside the editor. If you see the script as text, it went into the wrong block or module.
2. Saved code: reopen the page. If the script tag vanished, check WordPress permissions, your host, and security plugins that remove scripts.
3. Correct listing: confirm the imported business and last successful sync in VerifiedWidget. Check visibility filters and the saved collection if the widget is empty.
4. Allowed domain: if you enabled a domain allowlist, add your live domain. That also covers www and other subdomains, such as staging.yoursite.com. A staging site on a different address must be added on its own.
5. Cache: clear the WordPress cache, any page-cache plugin, and your CDN cache after updating an embed. Disable script delaying or JavaScript combining for a short test if a performance plugin interferes, then configure an exception with your site administrator.
6. Blocked requests: a content security policy, consent manager, ad blocker, or firewall can block the widget script or network request. Check your browser's developer console for blocked requests and ask the site administrator to allow the required source.
7. Usage: check monthly view allowance and, on Free, the review import and refresh limits. A preview with fictional reviews is not proof that your live widget has data.

If it still fails, send support the published page URL, widget ID, what you see, and any browser error message. Avoid sharing private login details or secret keys.

Check the finished page and SEO settings

Verify source attribution and links, review dates, images or video only when available, mobile sizing, and whether your consent manager affects optional analytics. Basic view counts are always sent so your monthly allowance can be tracked. Turn on extra analytics only when you have connected your site's consent signal. If you use conversion events, tie them to a real success action.

VerifiedWidget can publish business identity JSON-LD. If your SEO plugin already adds business information, keep names, addresses, and phone numbers consistent and avoid duplicate or conflicting identities. PHP snippets do not execute in a Custom HTML block; use an approved server-side integration if you need PHP. Back up the site before editing theme code. A business's own reviews on its own site do not qualify for Google review stars, even through a widget. Read our review schema guide and Google's review rules.

Frequently asked questions

Related reading