Are Your Google Reviews Visible to ChatGPT? What AI Search Actually Sees in a Review Widget

Ask ChatGPT for a driving school in Adelaide, a plumber in Austin or a dentist in Leeds and it answers with names, a sentence of reasoning and, more and more often, a line about what customers say. Where does that line come from? From pages the assistant could read. If your reviews sit inside a widget that only exists in a visitor's browser, the assistant read your page and found no reviews at all. This guide shows what AI crawlers actually receive from a review widget, a two-minute test you can run on your own site right now, and what it takes to make your reviews readable by AI search without giving up the animated widget your visitors see.

What an AI crawler sees when it opens your page

A browser and an AI crawler open the same URL and get very different pages. The browser downloads your HTML, runs every script, loads every iframe and paints the result. That is where a review widget comes alive: the script fetches the reviews, builds the cards, starts the slider. The crawler behind ChatGPT, Perplexity or Claude does the first step and stops. It reads the HTML your server sent, extracts the text, and moves on. As of 2026 the major AI crawlers do not execute your page's JavaScript and do not fetch the contents of a third-party iframe as part of your page. Google is the partial exception: Googlebot can render JavaScript for its index, but the content of a cross-origin iframe still belongs to the iframe's domain, not to yours.

So the question is never "is the widget on my page?" It is "is the review text in the HTML my server sends?" Those are different things, and for most widgets the answer to the second one is no.

The three ways review widgets render, and what each one leaves for AI

Every review widget on the market renders in one of three ways. The way it renders decides what a crawler gets.

The first two are the norm, including for the free tier of almost every widget tool and for BlooTrue's own free plan. They are not broken. They do the job they were designed for, which is showing social proof to a human who is already on the page. They just do not leave anything behind for a machine that reads pages without a browser.

The two-minute test: what does AI see on your page?

You do not need a tool for this. Open the page on your site that carries the widget, then:

1. Open the source. In Chrome, Edge or Firefox press Ctrl+U (Cmd+Option+U on a Mac), or put view-source: in front of the URL. This is the HTML your server sends, before any script runs. It is roughly what an AI crawler reads.
2. Search for a review sentence. Pick five or six words from one of your real reviews, something specific like "explained everything clearly", and search the source with Ctrl+F. Found it? Your reviews are in the HTML. Not found? AI cannot see them.
3. Search for your rating and count. Look for the number of reviews your profile shows, for example "32" next to a rating. A widget that writes the aggregate into the page will have it there as text.
4. Check who is allowed in. Open yoursite.com/robots.txt. If it lists GPTBot, ClaudeBot, PerplexityBot or Google-Extended under a Disallow rule, or your host or CDN has "block AI bots" switched on, the text can be perfect and still never be read. Blocking is a legitimate choice; just make it on purpose.

If you are comfortable with a terminal, the same check from the crawler's side is one line: curl -A "GPTBot" https://yoursite.com/page | grep -i "explained everything". An empty result means the reviews are not in the page.

Why this matters more in 2026 than it did last year

A growing share of "which company should I use" questions are now typed into an assistant rather than a search box, and the assistant answers with a short list and a reason. Those answers are assembled from pages the model could read at answer time or during training. A business whose own site carries thirty specific, recent, positive reviews as text gives the assistant something to quote. A business whose site carries an empty frame gives it nothing, and the assistant falls back to whatever third-party directories say, or says nothing. You already collected the reviews. The only question is whether your website lets machines read them.

Two honest limits. First, being readable is a requirement, not a guarantee: no tool can promise that an assistant will cite you, any more than a schema plugin can promise Google will show stars. Second, this is about your own website. Your Google Business Profile is read separately, through Google's own systems, whatever your widget does.

What "visible to AI" actually requires

Strip the marketing away and four things have to be true at once:

• The review text is in the HTML your server sends, not only in what a browser builds afterwards. Reviewer name, rating, date and the review body, as plain text.
• The rating and count are there as text and as schema.org markup. Text is what an assistant quotes; the structured data is what search systems parse. Both should match the real number on your profile.
• The page is crawlable. No AI-bot block in robots.txt or at the CDN, no noindex on the page, no login wall.
• The text stays current. A snapshot from the day you installed the widget goes stale; new reviews should reach the page too.

Everything else people list under "AI SEO" (clear headings, a real FAQ, consistent business name and address, fast pages) helps the assistant understand the page. But if the reviews themselves are not in the HTML, none of it puts your reviews in front of AI.

How BlooTrue makes your reviews visible to AI (paid plans)

On paid plans (Starter, Pro and Business), BlooTrue's embed code carries your reviews as real HTML: reviewer, rating, date and text for your latest reviews, plus your live rating and review count, plus schema.org markup of the aggregate. A visitor never notices, because the widget script replaces that text with the animated widget the moment the page loads. A crawler never runs the script, so it reads the text. Same page, both audiences served. On WordPress the BlooTrue plugin fetches that text on the server, so it refreshes on its own; on a pasted embed it is the set of reviews you had when you copied the code, so re-copy the snippet after a big batch of new reviews. The rating and count are always the real totals from your profile, never an average of the cards on screen, so what AI reads matches what a customer would find on Google.

The free plan does not do this. Free BlooTrue widgets render inside an iframe with the latest 10 reviews from the day you created them, and AI crawlers skip iframes. That is the honest line between the plans: free shows your reviews to visitors; paid also shows them to the machines that now recommend businesses. You can build the widget free, run the two-minute test on your own page, and upgrade when you want the second audience. See the pricing page for the full comparison, and the free vs. paid star-ratings guide for the schema side of the story.

Five more things that help AI understand your business page

1. Say what you do in the first sentence of the page, in plain words, with your city. Assistants weight the opening lines heavily.
2. Add a short, real FAQ (hours, service area, pricing range, what to bring). Question-and-answer text is the easiest format for an assistant to reuse.
3. Keep name, address and phone identical across your site, your Google Business Profile and directories. Mismatches make an assistant hedge.
4. Do not block the crawlers you want. Review robots.txt and any "AI bot protection" toggle at your host or CDN, and decide deliberately.
5. Refresh the page when things change. New services, new reviews, new hours. Assistants prefer pages that look alive.

Frequently asked questions