Widget SEO & AI visibility

How the widget renders

Your embed snippet is a <div> plus a <script>. The script (served from api.blootrue.com) mounts the widget inside a sandboxed iframe, which keeps the widget's CSS and JavaScript fully isolated from your page — zero style or script conflicts. That isolation is the reason review content and schema do not automatically appear in your page's own HTML, which is what the rest of this page is about.

What each plan gets

Review schema markup (and why no stars)

On paid plans (Starter $9/mo and up), the loader injects schema.org Review + AggregateRating + LocalBusiness JSON-LD straight into your page's <head> — so it lives in your own HTML and Google reads it when it renders your page (Googlebot runs JavaScript), and so do Bing and the AI crawlers that render pages.

What it does not do: put stars under your Google result. Google's review-snippet guidelines (updated July 2026) make a business's own pages ineligible for star results when the reviews about it come through an embedded third-party widget, and ask sites not to aggregate ratings from other websites. Our markup passes Google's Rich Results Test, which checks the markup, not eligibility. The rule and the pages that can still show stars are in review rich snippets in 2026.

Prefer to control placement (for example on a specific product or landing page)? Reference the standalone endpoint instead:

AI crawlers & answer engines

Most AI crawlers — GPTBot, ClaudeBot, PerplexityBot — read your page's raw HTML and do not execute JavaScript. Because the reviews render in an iframe (and the schema is JS-injected), those crawlers do not see your review text on your page by default. To put the review text in your raw HTML where they can read it, inline the content.html endpoint server-side:

// Inline BlooTrue reviews into your page HTML, server-side, so
// non-JS AI crawlers (and search engines) read them as your content.
const html = await fetch(
  'https://api.blootrue.com/api/widgets/embed/YOUR_EMBED_ID/content.html'
).then((r) => r.text());

// Render it into the page (server component, edge middleware, or build step):
<div dangerouslySetInnerHTML={{ __html: html }} />

This is a server-side step by design: a script-embed widget cannot put content into your raw HTML on its own, because the JavaScript has not run when a non-JS crawler reads the page.

If your site is behind Cloudflare

Cloudflare can stop AI crawlers before they reach your page, whatever the widget does. It sorts AI bots into three groups, Search, Agent and Training, and every plan, Free included, can allow or block each group. Domains added to Cloudflare since 15 September 2026 start with Training and Agent bots blocked on pages that show ads, and Search allowed.

• Search crawlers stay allowed by default. These are the bots answer engines use to find and cite pages, such as OAI-SearchBot (ChatGPT search), Claude-SearchBot and PerplexityBot.
• Training crawlers are what a block stops. GPTBot and ClaudeBot collect pages for model training. Cloudflare says blocking training-only crawlers like these does not affect search.
• Check the Training setting. Cloudflare now applies “Block” and “Block on pages with ads” to mixed-use crawlers too, including Googlebot, Bingbot and Applebot, so either one also affects search. To refuse AI training and stay in Google, choose “Disallow AI Training”, which keeps those crawlers allowed for search.

To check yours, open your domain in the Cloudflare dashboard and go to Security settings, then the AI bot policies. None of this changes what visitors see in the widget. It only decides which crawlers can read the page it sits on, including review text you inline with content.html. Cloudflare's own guides: AI bot settings and mixed-use crawlers.

The “Powered by BlooTrue” backlink

Free widgets add one small, visible “Powered by BlooTrue” link into your page — a normal followed link that credits BlooTrue. Paid plans remove all BlooTrue branding, including this link. It never changes your embed code.

FAQ