Your Reviews Might Be Invisible to AI

Short answer: open your page, turn JavaScript off, and reload it. If the reviews vanish, that is roughly what a machine sees.

Corroboration is the strongest thing you have. When an answer engine decides whether to name your business, what it is really deciding is whether it can back the claim up. Reviews are the most direct corroboration most businesses own.

Which is why it is worth knowing that a lot of them are, functionally, not there.

How reviews go missing

Most review widgets work the same way. The page arrives, the browser runs a script, the script goes and fetches the reviews from somewhere else, and then they appear. To a person this is invisible — it happens in a fraction of a second and the page looks complete.

To something reading the page as a document, the reviews were never in it. What arrived was an empty container and an instruction to go and get some content later.

Some crawlers execute that script. Many do not, or do it inconsistently, or do it on a second visit that may not come. And the review markup — the structured data that says this is a rating, this is who left it, this is what it was for — usually gets written by that same script, which means it is missing at exactly the moment the page is being read.

From the outside, a business with six hundred reviews in a widget can look identical to a business with none.

The two-minute check

One. Open your page in a browser, disable JavaScript, and reload. What remains is close to what a plain document reader gets. If your review section is empty, you have found your answer.

Two. View the page source — the actual source, not the inspector, which shows you the page after scripts have run. Search it for a review you know is real. Search it for aggregateRating. If neither is in there, neither is in the page.

That distinction between view source and inspect element is the one that catches people. The inspector shows the assembled page. The source shows what was delivered. Only the second one tells you anything here.

What to do about it

Get the reviews into the page itself. Not fetched afterward — present in the HTML that gets sent. How you do that depends on your platform, and on some platforms it is genuinely hard, but the goal is simple: a machine reading the document should find the review text without running anything.

Write the structured data server-side. Your aggregate rating, your review count, and enough individual reviews to be meaningful, declared in the markup rather than assembled by a script. This is the part that turns "some nice words on a page" into something an engine can use with confidence.

Do not fake it. Structured data that claims a rating the page does not show, or reviews that were never left, is the one mistake here with real consequences. The markup has to describe what is genuinely on the page and genuinely true.

Keep your profile reviews where they are. Your Google Business Profile reviews live on Google and are already visible to the systems that matter most for local queries. This is about the reviews on your own site, which are usually the ones you paid a subscription to collect.

Why this is worth your afternoon

Most of the work in getting cited is unglamorous cleanup — details that disagree, pages that assert nothing, load times that hide half the site. This one is different, because the asset already exists.

You already did the hard part. Somebody asked customers for reviews and customers wrote them. That is the part money cannot shortcut.

Everything after that is plumbing, and plumbing is fixable.