AI assistants are starting to expose conflicting facts across merchant pages

A pattern worth watching through late September 2026: AI shopping assistants are increasingly surfacing inconsistencies between merchant pages rather than simply selecting one version. Where an assistant used to pick the most prominent statement and move on, it now tends to state a caveat — or to route around the merchant entirely — when two live pages disagree on the same fact.

The clearest cases are the constraint facts. Shipping windows, return periods, warranty length, and lead times appear in at least two places on most stores: a dedicated policy page and a product page or FAQ. When those two agree, the assistant treats the fact as confirmed. When they disagree, the assistant has no way to know which page is authoritative, because neither page says so. The practical result is that the merchant is treated as having an unreliable record on that fact.

This is a meaningfully different failure from the more familiar one of missing information. A missing fact makes a merchant invisible for a question. A contradicted fact makes them quotable and wrong, which is worse — the wrong version enters the answer, and according to merchant reporting it can persist in later sessions even after the page is corrected.

What makes the shift notable is that it rewards maintenance rather than publishing. Stores that add content but never reconcile it are accumulating contradictions at a rate proportional to their publishing cadence. Merchants who run frequent promotions are the most exposed, because promotional copy is where a temporary number most often outlives its window.

The countermeasures are unglamorous and cheap. State time-bound facts with their window in the text so they expire visibly. Keep one canonical page per constraint and have every other page reference it rather than restating the value. And after any policy change, re-check the pages that restate it — a policy change on one page is, in practice, a change request on every page that copied it.

Contradiction detection is one of the checks a scan can do cheaply and a manual audit cannot do at all, because the conflict is only visible when you read two pages side by side. Visora reports where your product pages and policy pages state the same fact differently — price, lead time, returns, warranty — so the reconciliation work becomes a short list instead of a catalog read. See [the audit page](/audit) for what the consistency checks cover. Publishing more content does not fix drift; reconciling what you already published does.