How to Add Reviews With an iframe: The Fallback, and What It Costs

An iframe is the tool you reach for when a platform refuses to run a script tag, and several popular ones do refuse. It is the one embed method that works essentially everywhere, which is why it is worth understanding properly rather than treating as a last resort. It is also not free. An iframe loads a separate document inside your page, so whatever is in there is not part of your page: not for search engines reading your markup, not for your stylesheet, and not for the browser working out how tall the thing should be. Those three consequences are the whole subject. Here is when to use one, and what you are trading away when you do.

When Is an iframe the Right Answer?

When the platform will not run a script. That is a real constraint on more builders than people expect, and it is not a sign of a bad platform: sandboxing user-pasted code is a sensible security decision for a hosted product with millions of sites on it.

Notion is the strictest of the common ones: it accepts no script tags, and its embed block takes a public URL rather than markup. Google Sites offers an Embed code option that renders inside a fixed-height sandboxed frame. Wix wraps custom code in its own sandboxed HTML element. Drupal filters block and node bodies through a text format that strips tags not on its allow list, and Joomla applies both editor cleanup and per-group text filters on save.

Where a platform does accept a script embed, use the script embed. WordPress, Squarespace on a plan that allows code, Shopify, Webflow, Framer, HubSpot and Blogger all do, and on those the script version avoids everything in the next section.

There is one other legitimate reason to prefer a frame: a strict Content Security Policy on your own site that blocks third-party scripts. That is a deliberate security posture and an iframe respects it.

The Host Page Gets No Credit for What Is Inside

Structured data inside an iframe describes the framed document, not the page that contains it. So a review schema block rendered inside the frame does nothing for the hosting page's eligibility for a rich result, because as far as a crawler reading your page is concerned, the reviews are not on it.

This is the cost people are least aware of and the one that matters most if search is why you added the reviews. If your goal was star ratings appearing under your listing in Google, a framed widget will not get you there and a script embed might.

It is worth saying that star ratings in search results are governed by Google's own rules about which reviews qualify, and self-serving review markup for a business on its own page has been restricted for years. So the frame is often not the only thing standing between you and a rich result. But it is a hard blocker regardless.

If the reviews are there to persuade a human reading the page, none of this matters. A visitor sees the reviews either way.

Sizing a Frame That Cannot Measure Itself

A cross-origin iframe cannot tell the parent page how tall its contents are, and the parent cannot look inside to find out. Browsers block that deliberately, and it is not a limitation any embed provider can engineer around without both sides cooperating.

So you set a height by hand. Too short and the content scrolls inside a box that looks broken; too tall and there is a band of empty space under the reviews. The workable answer is to pick a widget layout whose height is predictable, then set the frame a little taller than it needs.

Horizontal layouts are the easy case. A slider, a marquee or a badge has a height that barely changes with content, so one number works. A masonry grid or a list that grows with the number of reviews is the hard case, because the right height today is the wrong height after ten more reviews arrive.

Check the height on a phone as well as on desktop. A three-column grid becomes a tall single column on a narrow screen, and a frame sized for the desktop layout will clip most of it.

Your CSS Does Not Reach Inside

The framed document has its own stylesheet and none of yours. Your fonts, your colour variables, your spacing scale, your dark mode: none of it crosses the boundary.

That is why an iframe embed can look pasted on in a way a script embed does not. The fix is to do the matching inside the widget rather than in your stylesheet: set the colours and typography in the widget builder so the frame arrives already looking like your site.

Get the surrounding container right too. Because you cannot style the frame's contents, the framing around it does the work: give it the same max width, padding and border treatment as your other sections so the edges line up even if the interior is a separate document.

How Do You Build the Widget?

Paste your Google, Trustpilot or Facebook profile URL, preview your real reviews and rating, then pick from over 100 layout styles across slider, marquee, grid, list, masonry and badge families. For a frame, favour the layouts with a stable height, because that is the constraint you are designing around.

Set the colours and fonts in the builder rather than planning to override them later, since the previous section explains that you cannot override them later.

The rating comes from the profile's own aggregate rather than from the cards on screen, so the number in the frame matches the number a visitor finds if they check. Free plan, unlimited widget views.

Where Should a Framed Widget Sit?

Somewhere with a stable, generous slot. Because the height is fixed by you rather than by the content, a frame is happiest in a section of its own with room around it, and least happy squeezed between two tight elements where a few pixels of misjudgement show.

Keep it out of the space immediately above a form or a button if you can. A frame whose height you guessed slightly wrong pushes the thing below it, and the thing below it is usually the thing you want clicked.

One frame per page is plenty. Each one is a separate document load, so several on one page costs real time on a slow connection, and the reviews are worth more concentrated in one place anyway.