1. What LLM Discoverability is
Shoppers increasingly ask AI tools what to buy. ChatGPT, Gemini, Perplexity and Google AI Overviews read product pages and answer in their own words, quoting whatever they find there.
There is a catch. Those crawlers read the page’s raw HTML. They usually do not run JavaScript. Your WiserReview widget is drawn by JavaScript after the page opens, so to an AI crawler your product page looks like it has no reviews at all.
LLM Discoverability closes that gap. It puts your review content into the page’s initial HTML, so AI crawlers and search engines can read it the moment they fetch the page.
Two pieces of content are involved:
- Readable review text – your reviews as plain HTML: reviewer name, rating, title, review text and date.
- Rich snippet (schema) – the same reviews as structured data, the format Google and AI tools use to read a product’s rating and review count reliably.
2. Why this matters
- You become quotable. AI answers are built from text the model can actually read. Reviews are the part of your page that describes the product in a customer’s own words – exactly what a shopper is asking about.
- Star ratings alone are not enough. A rating out of five tells an AI nothing about fit, durability or quality. Detailed review text does.
- It helps traditional SEO too. The same rich snippet is what Google uses for star ratings in search results, so one setup serves both AI answers and classic search.
- Your reviews already exist. This is not new content to write. It is content you have already collected, made readable by machines that could not see it before.
- Nothing changes for shoppers. The widget still loads, looks and behaves exactly as before.
3. What shoppers see
Nothing new. The review content added to the page source is visually hidden, so your page looks identical to before. Your normal WiserReview widget continues to load and display as usual.
This content is there for machines that read the page source: AI crawlers and search engines.
4. Where it already works automatically
You do not need to do anything on these platforms:
- Shopify – if you use the WiserReview app and added the Product Review widget as a theme app block, the review text is already written into your product page HTML.
- WooCommerce – if you use the WiserReview plugin, both the review text and the rich snippet are added by the plugin. The snippet is also merged into your SEO plugin’s product schema when you use Yoast, RankMath or SEOPress.
5. Why we cannot set this up automatically on other platforms
This is the question we are asked most, so it is worth explaining plainly.
To put content into a page’s initial HTML, something has to run on the server that builds the page, before it is sent to the browser. On Shopify and WooCommerce we have exactly that: an app block in your theme, and a plugin inside WordPress. Both run while the page is being built, so we can add the review content for you.
On every other platform we only have the pixel – a JavaScript file that runs in the shopper’s browser after the page has arrived. By then the HTML has already been sent, and any crawler that does not run JavaScript has already read the page without your reviews in it.
There is no way around this from our side. Only code running on your own server or in your own page template can add content before the page is sent. That is why platforms like BigCommerce, Wix, Squarespace, Ecwid, PrestaShop, OpenCart, headless Shopify and custom storefronts need a small one-time integration by whoever maintains your site.
The work is small – one API call and two values printed into your product page template – but it has to happen in your code, not ours.
6. How to set it up on other platforms
Ask your developer to follow these steps. It is usually under an hour of work.
API reference: LLM discoverability review HTML – the exact URL, every parameter and the full response format are documented there.
Step 1: Call the API while the product page is being built
The call is made from your server, not from the browser, once per product page.
It takes two required values:
- wsid – your workspace ID, the same one used by your WiserReview widget code.
- pid – the ID of the product whose page is being rendered. Every review is stored against a product ID, so without it no reviews are returned.
Two more values decide what you get back: ihtml for the readable review HTML and ijsonld for the rich snippet. Pass true for the parts you want – at least one of them is required.
Step 2: Print the response into your product page
The response contains two ready-to-use strings.
Put the html value inside the body of your product page, anywhere below the product details. It is already visually hidden, so it will not affect your layout.
Put the jsonld value into the page as well. If your site already outputs Product schema from an SEO tool, skip this part rather than adding a second Product block.
Step 3: Cache it
Do not call the API on every page view. Store the response with the product – in your product record, a cache table, or your existing page cache – and refresh it when reviews change or on a schedule, for example once a day.
Notes for your developer
- Only the product’s own reviews are returned. Reviews borrowed from other products for display purposes are never included, so the rich snippet always matches the page it is on.
- If the product has no published reviews, the rich snippet comes back empty. That is intentional – a rating with zero reviews is rejected by Google as invalid.
- The html value is a single line, ready to print as-is.
7. How to check it is working
1. Open one of your product pages in your browser.
2. View the page source – use Ctrl+U on Windows or Cmd+Option+U on Mac. Do not use “Inspect”, which shows the page after JavaScript has run.
3. Search the source for a phrase from one of your reviews, or for wiserreview_.
If you find your review text there, crawlers can see it too.
To check the rich snippet, run the page through Google’s Rich Results Test.
If you do not find it:
- Confirm the API call is made on the server, not in browser JavaScript.
- Confirm the correct product ID is being passed – a wrong ID returns no reviews.
- Clear your page cache and CDN cache, then reload.
8. What to expect afterwards
Making your reviews readable is the part you control. What happens next is not guaranteed.
Each AI platform decides on its own whether to crawl a page, keep what it finds, and use it in any given answer. Results differ between one question and the next, between users, and over time. Asking ChatGPT about your product once or twice is not a reliable test of whether the setup worked – checking your page source is.
What you can rely on is this: if the content is not in your page source, it will not be used. If it is there, your reviews are in the running.
9. Frequently asked questions
Does this slow down my product page?
No. The content is already in the HTML your server sends, so the browser has no extra work. Cache the API response and your page speed is unchanged.
Will Google treat hidden review text as cloaking?
No. The content shown to crawlers is the same review content shown to shoppers in the widget. Nothing is hidden from one and shown to the other.
Do I need this if I am on Shopify or WooCommerce?
No. It is already handled for you.
Can I add the review text but not the rich snippet?
Yes. Pass ihtml=true on its own. Do that when your SEO tool already produces Product schema for your pages.
How many reviews are included?
The same reviews your widget shows on its first page, so the snippet matches what shoppers see.