Diagnose
What ChatGPT sees on your website
By Ankit Minocha, founding team at Atomz. Updated January 21, 2026.
An assistant does not see your design. It reads a stripped-down version of your page, and on most stores the part that sells is the part it never sees. Here is how to check.
When ChatGPT reads your page it does not see the photography, the layout, or the hover states. It sees text and structure, roughly what is left if you stripped the styling away, and on a large share of stores the description, the specs, and the attributes are not in that layer at all. They are painted in by JavaScript after load, or they live only inside images, so the assistant arrives at what looks like a near-empty page and moves on.
That is why a page can rank perfectly well on Google and still be invisible to an assistant. The two read different things, and the assistant reads the harder one.
The fastest way to see what it sees
You do not need a tool for the first check. Open one of your product pages, turn off JavaScript in your browser, and reload. What remains is close to what an assistant reads. If the description collapses, the specs disappear, and the attributes are gone, you have found the problem, because everything that vanished is invisible to the systems now driving discovery.
| Element | What a shopper sees | What the assistant sees |
|---|---|---|
| Hero image and gallery | The product | Nothing, unless described in alt text |
| Description painted by JS | Full copy | An empty container |
| Specs in a tab widget | Full specs | Often nothing |
| Attributes implied in prose | Inferred by a human | Not matched, because not structured |
| Price and availability in schema | Shown on page | Read cleanly, if the schema exists |
What to put back in the readable layer
The fix is to move the parts that sell into the layer the assistant reads. The description and specs should be in the server-rendered HTML, not injected after load, so they are present the moment the page is fetched. The attributes a shopper searches on should exist as structured data rather than as adjectives. Images should carry real alt text, since that is the only way their content reaches an assistant at all. And the core facts, price, brand, availability, type, should sit in product schema so they are never left to guesswork.
The 30-second test
Turn JavaScript off, reload, and read. If the page still explains what the product is, who it is for, and the attributes that define it, an assistant can read it too, but if it goes blank, that blankness is exactly your AI visibility.
Why it is worth doing
This is not a ranking tweak, it is the difference between being readable and being absent. The encouraging part is that the fix is durable and shared. A page that renders its content server-side and carries its attributes as data is readable to ChatGPT, Claude, Perplexity, and Gemini at the same time, because they all read that same stripped-down layer. The audit runs this check across your whole catalog and tells you which pages go blank.
Subscribe to The Agentic Operator