Stall library · Buy
Choosing a variant needs JavaScript the AI agent cannot run
This stall is a product page whose size or colour control does not exist in the delivered HTML, because a script is expected to build it after load. An AI agent reading the page as delivered never sees an option to choose, so it does not conclude that your product lacks variants. It concludes there is nothing here it can act on.
Why the agent stops
There is a real difference between an agent that runs a full browser and one that reads the response, and both exist. A control that is created client side is invisible to the second kind, and it is fragile for the first, because it depends on a script that has to load, execute and finish before an interaction is possible.
This differs from a hover only picker in an important way. There, the options exist and cannot be activated. Here, the options never arrive, so there is nothing to activate and no signal that anything is missing.
How often we see this
Not stated here. A frequency means nothing without the cohort it was counted over, and this page is about one stall rather than one category. Where a category has enough stores measured at every stage, the share of them showing this stall is published on its benchmark page, with the methodology beside it.
See it for yourself
- Fetch a product page with curl and search the response for the option values you expect, for example Small or Medium.
- If they are absent from the source but visible in the browser, the control is built client side.
- Load the page in a browser with JavaScript disabled and check whether a usable option control appears.
- Look for an empty container with a variant related id or a data-options attribute, which is the usual placeholder.
What to change
- Render the option controls in the HTML and let scripts enhance them, rather than creating them from nothing.
- Use a real form control as the base, so the page is functional before any script runs.
- Keep the option values in the markup even when the visual presentation is script driven.
- Make sure the same values appear in your structured data, so the page and the data agree.
What Ottom looks at
The journey agent looks for an empty variant container or a placeholder that a script is expected to fill, and raises this finding rather than the hover only one when the options were never rendered. The finding is recorded against the step of the journey where it stopped.
Questions
Does fixing variant pickers mean we stop using JavaScript?
No, and it would be a strange thing to ask. It is asking that the option control exist in the HTML and be enhanced by scripts rather than created by them, which is the ordinary progressive enhancement pattern and costs nothing at runtime. Your shoppers see exactly what they see now. The difference is that something reading the page before the scripts run can still tell which sizes exist.
Do JavaScript only variant options hurt search rankings?
Possibly, since indexers vary in how thoroughly they render, and the ones that render do it on their own schedule. The agent case is stricter for a structural reason: an indexer that cannot read a page today can come back tomorrow, and an agent answering a shopper who is choosing right now cannot. So treat this as an agent problem that a search engine may also have, rather than as an SEO task.