How to add Google reviews to Drupal

Quick answer

1. Copy the script tag from your widget's Embed dialog in VerifiedWidget.
2. Go to Content → Blocks and add a content block, or open the page (node) that should show reviews.
3. Set the Text format to one that allows scripts, click Source and paste the script.
4. For a block, go to Structure → Block layout, click Place block in a region and pick it. Clear caches and view the page logged out.

What you need

Administrator access, or permission to use a text format that keeps scripts. Drupal filters HTML by default and advises limiting Full HTML to trusted users.

Steps for Drupal

1. Block or node?

   A block in a footer region shows reviews across the site; the body of one node suits a single landing page. Since Drupal 10.1, what used to be a “custom block” is called a content block. Its library moved from Structure to Content → Blocks (Drupal change record). Save the widget and copy its script either way.

2. Choose the text format

   In the body field switch Text format (the setting that decides which HTML Drupal keeps) to one that permits scripts, such as Full HTML. Do this only if your site has it and your account may use it. Do not loosen a format that anonymous or untrusted users can use.

3. Paste through Source

   If the editor has a Source button, click it and paste the script there so the editor does not rewrite it. Save. Early CKEditor 5 releases in Drupal dropped script tags even in Full HTML; Drupal marked that fixed in 2022. If yours still drops it, update Drupal core first.

4. Place the block and test

   On Structure → Block layout, pick the tab for your front-end theme, click Place block next to a region and choose your block. Under its Pages visibility setting, list the paths that should show reviews. Clear Drupal's caches if you see old content, and test on mobile.

Drupal-specific problems

• The script is gone after saving. The text format's filters removed it. Use a format that allows it, and the Source view.
• The script shows as text. A rich text editor encoded the tags. Edit in Source mode.
• Region names differ per theme. Check the block layout tab for your front-end theme, not the admin theme.
• Can't find Custom block library. On Drupal 10.1 and later it is Content → Blocks.
• Old content keeps appearing. Page caches on Drupal and any CDN need clearing after changes.

A security note for site owners

A text format that keeps scripts also lets whoever can use it publish scripts. Restrict that format to trusted administrators, and let editors work in a stricter format. A footer-region block with a script is a reasonable pattern: only administrators can change the block, and editors can still edit page content safely. Put the widget after a section that explains your service so it supports a decision.

After you save

Open the page in a private browser window, because logged-in administrators can see different cached content from visitors. If the block does not appear, check its visibility settings on the block layout screen, then the region name in your active theme. If you use a full-page cache, clear it once after the change. Keep a note of which block holds the script so a later theme change does not leave you with an empty region.

Frequently asked questions

Related reading