Free Google Review Widgets via iFrame

Use the iframe embed when the host environment strips or blocks <script> tags. The standard script loader is the recommended path because it auto-resizes and mounts inline with the host page. But many environments — locked-down enterprise CMSes, SharePoint, ServiceNow, WordPress.com Free, intranet portals, HTML newsletters — strip scripts as a security policy. In those environments the iframe is the universal fallback. The iframe URL is the same endpoint the script loader mounts internally, so the widget itself looks and behaves identically.

Common ones include: locked-down enterprise CMSes that strip <script> tags as a security policy; SharePoint and ServiceNow intranet portals where IT blocks third-party scripts; the WordPress.com Free plan (which strips scripts); Notion and other headless CMSes that whitelist embeds by domain; some wikis and knowledge bases that allow only iframe URLs; and HTML newsletters where the recipient's email client preserves iframes but strips scripts. Email signatures (HubSpot, Apple Mail templates) are an edge case where iframes sometimes work and scripts almost never do.

Generate the standard embed code in the BlooTrue builder, then read the <div> class. Your ID is the part after blootrue-widget- — for example, in class="blootrue-widget-abc123" the ID is abc123. Copy that string into the iframe src URL: https://api.blootrue.com/api/widgets/embed/abc123/render.

No — and this is the main tradeoff of iframe mode. Cross-origin iframes can't communicate their natural height back to the parent page without postMessage, and most script-restricted environments also strip postMessage handlers. So you have to set a manual min-height on the iframe. For Google review widgets, 600–800px is a reasonable default; pick the higher end if you're using Grid or Masonry styles. If you need true auto-resize, use the standard script embed instead — it's the recommended path whenever the host environment allows JavaScript.

Yes. The iframe URL https://api.blootrue.com/api/widgets/embed/YOUR_ID/render is the same endpoint the script loader mounts internally. Same renderer, same Google reviews, same theme, same layout — pixel-identical visual output. The only difference is the mount strategy: instead of the script injecting the widget into a <div> on your page, the iframe loads the rendered widget in a sub-document.

Maybe — it depends on the email client. Some email signature platforms (HubSpot, Apple Mail templates with HTML support) preserve iframes; most strip both scripts and iframes. Outlook, Gmail web, and the major mobile clients reliably strip iframes. If your platform allows iframes in signatures, paste the same iframe tag described above. If it strips iframes, you'll need to fall back to a static image badge with a link to your Google profile — neither the script nor the iframe embed will work in those environments.

No — and this is a meaningful tradeoff. The schema.org Review and AggregateRating JSON-LD lives inside the iframe document, not on the host page. Google does not bubble schema from a cross-origin iframe up to the parent page, so star rich snippets won't fire on the host URL via the iframe embed. If you need rich snippets on the host page (for example, to show review stars under your homepage in Google search results), use the standard script embed — it injects the JSON-LD directly into the host page's DOM. The iframe embed is purely a visual display option for environments where scripts aren't allowed.