Why Do AI Answers Show the Wrong Currency or Payment Options to Shoppers in Another Country?

Why does one country's version win?

• Duplicate country pages. Google's documentation says localised versions of a page are only considered duplicates if the main content stays untranslated. A UK and an Australian page in the same English, differing only in price, can be clustered, and one chosen as the canonical.
• Redirects by location. If your site redirects visitors by IP address, crawlers see only the version for their location. Googlebot crawls mainly from addresses that appear to be in the US, without a language header, according to Google, which recommends separate URLs for each locale rather than automatic redirects.
• Prices loaded by script. A currency switcher that changes prices after the page loads leaves crawlers with the default currency.
• Feeds in one currency. Product feeds submitted only in your home currency give shopping features a single price to show.
• Third-party listings in another currency, such as marketplaces and comparison sites.

Why does Google AI Overviews describe our UK pricing on searches from Australia?

Usually because Google has only one version to draw on, or has chosen the UK version as the one to represent both. Check three things:

1. Do the Australian pages have their own URLs, such as an /au/ path or an .com.au domain, reachable without a redirect? If Australian prices appear only after an IP check, Google may never have seen them.
2. Are the versions linked with hreflang? Each version should list itself and every other version, with an x-default for everyone else. Without that, Google has no signal that the Australian page is the right one for Australian searchers.
3. Does the Australian page differ in more than price? Say plainly on the page that prices are in Australian dollars and include GST, and add local delivery times, returns address and payment methods. Content that is genuinely local is less likely to be folded into the UK page.

Then make sure your structured data and Merchant Center feed for Australia use AUD prices that match the Australian page. How the same problems affect stock and availability by country is covered in why AI answers get product availability by country wrong.

Why do AI assistants convert my prices incorrectly between EUR and GBP?

Because they convert instead of reading your GBP price. If an assistant finds only your euro price, it may convert it at a rate from training data or a rate it looked up. The result will not match what you actually charge in pounds. Prices across markets are rarely straight conversions anyway. They reflect different VAT rates, shipping costs and pricing decisions.

As an illustration, a product priced at €49 in Germany, including 19% VAT, and £45 in the UK, including 20% VAT. Converted at 0.86, the euro price becomes £42.14, and at an older rate of 0.84, £41.16. Both understate your real UK price by several pounds, and neither accounts for the VAT difference. Before VAT, the German price is about €41.18 and the UK price £37.50.

To prevent it, give assistants the real price in each currency, in text, on a page they can reach. Say "Prices in GBP include UK VAT" on the UK store. Check that your price markup on each country page uses that country's currency and matches the visible price. Google Merchant Center can convert prices automatically when you submit one currency for another country. Its own guidance says to consider fully localising the price and currency for each target country instead. If AI answers keep quoting converted prices, local prices are the fix. How assistants end up quoting old prices is covered in why AI quotes your old prices, plans or pricing tiers.

Can AI search engines tell whether my international prices include VAT or GST?

Only if you tell them in words, and even then they may not carry it into the answer. A bare number such as "£45" says nothing about tax. Consumer price rules differ by market, and assistants do not reliably apply them:

Merchant Center follows the same split. Its price requirements say not to include taxes in the price for the US and Canada. For countries including Australia, the UK and the EU members listed, the price should include VAT or GST and match the landing page. Business-to-business stores that quote prices before tax should say so on every price, such as "£450 excl. VAT". Schema.org's valueAddedTaxIncluded property can mark tax treatment on a price specification, but the text statement is what assistants are most likely to read.

Why do Perplexity citations omit my local payment methods page for Australian customers?

Usually because the page is hard to reach or does not match the question. Perplexity searches for pages that answer the question, and cites the ones it finds. Common causes:

• Payment methods appear only at checkout, which crawlers never reach.
• One global payments page lists methods by country inside collapsed sections or a script-driven selector.
• The Australian page is not linked from Australian product pages, the footer or the sitemap.
• A general FAQ answers first. "We accept Visa, Mastercard and PayPal" on your global FAQ matches the question well enough to be cited instead.
• Crawler access. If robots.txt or bot protection blocks Perplexity's crawler, its index may lack your pages.

Publish a payment methods page for Australia at its own URL, in text. List every method, including buy now, pay later services and bank transfer options, with any conditions. Link it from Australian product pages, the checkout help text and the footer, include it in your sitemap, and link it to other country versions with hreflang. Then ask Perplexity "Can I pay with [method] at [store] in Australia?" and see whether the page is cited. Where Perplexity keeps giving the wrong answer, the steps in how to report an inaccurate Perplexity answer about your business apply.

How do you test what assistants say?

Ask Google's AI features, ChatGPT, Gemini and Perplexity, from each market where possible, several times each:

• "How much is [product] in Australia?"
• "[Product] price UK"
• "Does [store] price include GST?"
• "What payment methods does [store] accept in Australia?"
• "Does [store] ship to [country] and in what currency?"

Record the currency, the price, whether tax is described correctly, and the cited URL. A cited URL from the wrong country version shows where the fix is needed.

What might an illustrative case look like?

Consider an illustrative homeware brand with UK and Australian stores on the same domain, redirected by IP address. AI Overviews quoted UK prices in pounds to Australian searchers, and ChatGPT converted them to Australian dollars at an old rate. Perplexity said the brand accepted "cards and PayPal" and never mentioned its buy now, pay later option, which appeared only at checkout. The brand removed the automatic redirect in favour of a country banner, and gave each store its own path with hreflang. It added "Prices in AUD include GST" to every Australian page and submitted an AUD feed. It also published an Australian payment methods page. Two months later, most Australian answers quoted AUD prices, and Perplexity cited the new payments page.

What do people ask about currency and AI answers?

Should we show prices in several currencies on one page?

It can help visitors, but give each country its own page with its own currency as the main price, so assistants have one clear figure per market.

Do we need translated pages for English-speaking countries?

No, but each country page needs genuinely local details, such as currency, tax, delivery and payment methods.

Will fixing the feed fix chat answers too?

It fixes shopping features that read the feed. Chat answers also read your pages, so fix both.