How to Add Reviews to Divi: Three Homes, Three Lifetimes

Divi sits on top of WordPress rather than replacing it, which means a snippet has more places it could live here than on almost any other builder in this series. The module to use is not in question: it is the Code module, and it takes the embed as written. What decides whether the widget is still there in six months is which layer you put that module in, because a page layout, a global module and the site-wide integration tabs have three different lifetimes and only one of them matches what you probably want.

The Code Module, Not the Text Module

Elegant Themes documents the Code module as the place to insert HTML, CSS, JavaScript, shortcodes or third-party code, and notes that CSS should be wrapped in style tags and JavaScript in script tags. That is exactly the shape a widget embed already has, so it goes in unchanged.

A Text module is the common mistake and it fails quietly. The visual editor behind it treats your snippet as content to be tidied, escaping angle brackets and rewriting attributes, and the result is a page that displays the code as visible text instead of running it. Nothing errors, so the cause is not obvious.

Divi 5 also adds an HTML option group in the Advanced tab that sets the semantic tag wrapping the module. It is not required for a widget to work, but choosing a section or an aside rather than a bare div costs nothing and makes the page structure read correctly to anything parsing it.

Home One: A Module in One Layout

The default. You open a page, drop a Code module into a row, paste and save, and the widget belongs to that page. It is the right answer when the reviews are part of a specific argument on a specific page, such as a landing page for one service.

The failure mode is duplication. Divi layouts get copied constantly, from the library, from another page, from a saved section, and a Code module copies with them. Two pages then hold two independent copies of the same embed, and changing one does nothing to the other.

If you are only ever going to have one, this is fine and simplest. If you can already see the widget appearing on three pages, skip ahead rather than pasting three times and regretting it later.

Home Two: Global Modules and Theme Builder

A global module is stored once and referenced wherever it is used, so editing it in one place changes it everywhere. A module inside a Theme Builder template behaves the same way across every page that template applies to. Either is the right home for a reviews block that belongs on many pages.

This is the opposite instinct from the one you need on an agency builder handing sites to different clients, where sharing a configured widget is exactly the thing to avoid. On a single site it is what you want: one business, one profile, one place to edit.

A Theme Builder footer is the usual placement for a compact rating badge, because it puts the proof on every page without a decision per page. Save the full review section for the templates where it earns its space rather than putting it in the global footer as well.

Home Three: The Integration Tabs

Divi Theme Options has integration fields for code that belongs in the site head or body on every page. That is the correct home for analytics, verification tags and anything else with no position on the page.

It is the wrong home for a review widget, and the reason is simple: a widget renders where it is placed, and a site-wide injection has no place to be. Code added there either does nothing visible or appears in whatever position the markup happens to land in, which is not a layout decision anybody made.

The exception is a floating badge designed to sit fixed against the viewport rather than in the document flow. If that is what you want, the integration tab is a reasonable home for it, and it should be the only copy on the site.

Remember There Is a WordPress Under This

Divi does not remove the layers below it. A caching plugin, a minification setting or an optimisation feature that defers scripts sits between your Code module and the visitor, and any of them can be the reason a correct embed does not render.

The quickest check when something is missing is to clear the cache and reload, before assuming the module is wrong. The second check is whether script deferral or combination is switched on in whatever performance plugin the site runs, since that is the usual culprit on an otherwise healthy Divi build.

Divi 5 is a rebuild with its own performance work, which changes the details but not the principle. Something on a WordPress site is nearly always caching output, and it needs telling when the output changed.

How Do You Build the Widget?

Paste your Google, Trustpilot or Facebook profile URL, preview your real reviews and rating, then choose from over 100 layout styles across the slider, marquee, grid, list, masonry and badge families, and set the colours to the Divi theme palette.

The header rating comes from the platform aggregate rather than being averaged from the cards on screen, so the number on the page matches the profile a visitor lands on if they click through. That is what makes the number worth showing.

Free plan, unlimited widget views. A global module means one embed can be rendering on every page of the site, so a per-view cost or a view ceiling would be a poor thing to build into a footer.

Where Should the Reviews Go?

One full review section on the page that does the selling, and a compact badge in the Theme Builder footer for everywhere else. That combination gives every page some proof without repeating the same wall of cards down the site.

Put the full section after the offer rather than before it. A visitor who has not yet understood what you do has no use for evidence that you do it well, and Divi layouts make it easy to move a row once you see the page in order.

If the site has service-specific landing pages, consider a page-level Code module on each with a layout that suits that page, rather than forcing one global block to work everywhere. That is the case where home one beats home two.