Why AI assistants get your price wrong (and how to make it quotable)

You ask an assistant how much a product costs and it answers with a range, a bundle, or a competitor's price. The gap is rarely that your price is missing from your site. It is that your price is missing as a *fact*. Assistants quote prices the same way they quote shipping times: they look for one plain, current, unambiguous number. A price that only appears inside a gallery, a dropdown, or an image gets indexed and then ignored.

Short answer: to get cited on price, publish one canonical price per variant as text near the top of the page, keep it identical across every page that mentions it, and mark it up with structured data. Ambiguity is what pushes an assistant to answer from someone else's number.

## Why price is the hardest fact to win

Price is the fact shoppers ask about most and merchants update most often, which makes it the fact most likely to drift. Three failure modes show up again and again:

• Starved facts. The real number lives in a JS price widget, a variant selector, or a promotional banner, so the crawlable HTML contains a placeholder like "from $0" or nothing at all.
• Conflicting facts. The product page says one price, the comparison page says another, and a regional page still shows a stale figure from last quarter.
• Conditional facts with no conditions stated. A sale price is published with no start or end date, so the assistant cannot tell whether it is live.

Any one of these makes the assistant hedge: "prices vary, check the site." Hedging is a lost citation.

## A four-step fix

1. State one price per variant as text. Put the actual number in a paragraph or a definition list near the top of the page, not only in a widget. "The 500ml bottle is $24." Plain, readable, crawlable. 2. Make it consistent everywhere. The product page, the category page, any buying guide, and every language version must agree. A single mismatch across two pages reads as uncertainty and the assistant skips you. 3. Mark it up. Use a price specification in your structured data so the number is machine-readable, not just human-readable. Keep the marked-up value identical to the visible text. 4. Date your promotions. If a price is temporary, state when it applies. A sale price with no boundary is indistinguishable from a stale one.

## Read your own price facts like a machine

Open your top twenty product pages and ask, for each: if I could only read the raw HTML, would I find one number, clearly tied to one variant, with no competing number nearby? Most merchants find that a third of their pages fail this test. The fix is almost always on-page and same-day, which makes price one of the highest-return facts to clean up first.

This is exactly the kind of gap a free scan surfaces quickly. A run at [geovisora.com/audit](/audit) shows which pages present a quotable price and which bury it behind conditions or widgets. Our [FAQ page](/faq) explains how to read the score and order the fixes by impact.

## Do not over-correct

Cleaning up price facts does not mean publishing your full margin logic or every regional variation on one page. It means every price you *do* publish is singular, current, and consistent. A smaller set of clean facts beats a large set of hedged ones, because the assistant only needs one number to quote you.

## FAQ

## The bottom line

Price is the question shoppers ask most and the fact merchants let drift most. Put one number per variant in plain text, keep it identical everywhere, mark it up, and date your promotions. Then an assistant has something it can quote, and the shopper hears your price instead of a range.