---
title: "Currency and language an AI agent can't misread"
description: "An agent that opens your product page from a data center abroad may see a different currency, a different language or a redirect."
source_url: "https://specoria.com/insights/currency-and-language-an-agent-cant-misread/"
lang: "en"
---

[Insights](https://specoria.com/insights/) Infrastructure

# Currency and language an agent can't misread: one URL, one price, one currency

An agent that opens your product page from a data center abroad may see a different currency, a different language or a redirect. Google's rules are clear: no price changes by IP, the same amount and currency on page and checkout, and hreflang that links both ways.

By [Specoria Team](https://specoria.com/about/) November 15, 2026 5 min read

![Cut-paper collage with plaster fragments, a stone arch, parcels and a paper browser frame holding two blank tags, with one violet paper key.](https://specoria.com/insights/img/currency-and-language-an-agent-cant-misread-1-ff80c663.jpg) One doorway, one honest price: the shop stands still while every visitor walks through the same door. Illustration: Specoria · generated with AI

In this article

- [Why location-based switching misleads agents](https://specoria.com/insights/currency-and-language-an-agent-cant-misread/#why-location-based-switching-misleads-agents)
- [What Google's rules say](https://specoria.com/insights/currency-and-language-an-agent-cant-misread/#what-google-s-rules-say)
- [Languages: hreflang that links both ways](https://specoria.com/insights/currency-and-language-an-agent-cant-misread/#languages-hreflang-that-links-both-ways)
- [A setup that works for agents](https://specoria.com/insights/currency-and-language-an-agent-cant-misread/#a-setup-that-works-for-agents)
- [Selling abroad from Turkey](https://specoria.com/insights/currency-and-language-an-agent-cant-misread/#selling-abroad-from-turkey)
- [A quick check](https://specoria.com/insights/currency-and-language-an-agent-cant-misread/#a-quick-check)
- [The bottom line](https://specoria.com/insights/currency-and-language-an-agent-cant-misread/#the-bottom-line)

A shopper in Istanbul asks an assistant for the price of a jacket on a Turkish store. The assistant's browser runs in a data center in Frankfurt. The store sees a German IP address, switches the page to euros and English, and the assistant reports a euro price the shopper will never pay. Nothing on the store was wrong for a person sitting in Turkey. For the agent, the store showed a different shop.

In this article, we look at how location-based switching confuses agents, what Google's rules say about currency and location, and how to set up languages and currencies so every visitor, human or not, sees the right price for the URL it asked for.

## Why location-based switching misleads agents

Agents rarely browse from where the shopper is. Their requests come from cloud regions chosen by the agent's provider. A store that decides currency, language or country site by IP address will show those agents whatever it shows visitors from that region. We listed geo-redirects among the common frictions in [what tires a shopping agent](https://specoria.com/insights/what-tires-a-shopping-agent/).

The result is one of three errors: a wrong currency, a wrong language, or a redirect away from the page the agent was asked to read.

## What Google's rules say

![Cut-paper collage of two paper envelopes with blank cards linked by a folded paper strip, two plaster hands reaching in, and a violet ribbon.](https://specoria.com/insights/img/currency-and-language-an-agent-cant-misread-2-705d3acb.jpg) Two paths that must point back to each other, so neither visitor is left wandering alone. Illustration: Specoria · generated with AI

![The same product URL opened from Istanbul and from a data center in Frankfurt: with IP-based switching the second visit gets euros, English and a redirect; with a fixed URL per market both visits see the same price and currency, and hreflang links the language versions](https://specoria.com/insights/fig/currency-and-language-an-agent-cant-misread-1.svg) One URL, one price, one currency: whoever asks, from wherever

Google's Merchant Center rules for the price attribute are direct:

- **Submit an amount and currency that match the price on your landing page and checkout pages.**
- **Show the price in the currency of your target country** prominently on the landing page and at checkout.
- **Don't change the price on your landing page based on a user's location.** Google says IP detection is against its guidelines and may interfere with the crawler. If prices really differ by region, it points to its regional pricing program.

For structured data, schema.org asks for the currency as an ISO 4217 code in `priceCurrency`, such as `TRY`, `EUR` or `USD`, instead of a symbol in the price.

## Languages: hreflang that links both ways

If you have language or country versions of a page, `hreflang` tells crawlers which version is for whom. Google's documentation stresses one rule above all: **return links**. If page X lists page Y as an alternate, page Y must list page X. If the links don't point both ways, Google may ignore them. Google also recommends an `x-default` version for visitors whose language doesn't match any version, such as a country selector or your main language.

## A setup that works for agents

- **One URL per market and language,** for example `/tr/` for Turkish in lira and `/en/` for English. The URL decides the language and currency, not the IP address.
- **No automatic redirects.** If you think a visitor is in the wrong place, offer a banner with a link to the other version, and let them stay.
- **The same amount and currency** in the page, the structured data, the feed and checkout for each URL.
- **`priceCurrency` as an ISO code** on every offer.
- **`hreflang` on every version,** listing all versions including itself, plus `x-default`.
- **A visible currency and language switcher** that changes the URL.

## Selling abroad from Turkey

Turkish stores that sell abroad often show foreign-currency prices next to lira. A few rules keep that honest for agents:

- **One currency per URL.** A page for euro buyers shows euros in the page, the markup and checkout; it doesn't convert on the fly by IP.
- **Update converted prices together.** If euro prices follow the exchange rate, update the page, the structured data and the feed in the same run.
- **Say what's included.** Taxes, duties and shipping to the destination country are part of the price a buyer compares. State them per market.
- **Keep the Turkish page Turkish.** A visitor from abroad who asked for `/tr/` should still get the Turkish page in lira, with a link to the other version.

## A quick check

- Open one product page through a VPN in another country, or ask a colleague abroad to open it.
- Confirm the URL, language, currency and price stay the same.
- View the source and find `priceCurrency` and the price in the structured data.
- Check that each language version lists the others in `hreflang`, and that they list it back.

## The bottom line

An agent sees your store from wherever its servers are, not from where the shopper is. A store that switches currency or language by IP shows it the wrong shop. Let the URL decide, keep the amount and currency identical from page to checkout, and link language versions both ways. Then any visitor, from anywhere, reads the price your shopper will actually pay.

Specoria checks whether currency and language are consistent on your pages, alongside price consistency between your page, your structured data and your feed. Start with a [free readiness test](https://specoria.com/#contact).

### Sources

- Google Merchant Center Help, [Price [price]](https://support.google.com/merchants/answer/6324371), accessed October 22, 2026.
- Google Search Central, [Localized versions of your pages](https://developers.google.com/search/docs/specialty/international/localized-versions), last updated September 21, 2026.
- Schema.org, [priceCurrency](https://schema.org/priceCurrency), accessed October 22, 2026.
- Specoria Insights, [What tires a shopping agent](https://specoria.com/insights/what-tires-a-shopping-agent/)

## Related

- [UCP for stores: one profile file and five capabilities, each tied to data you already run](https://specoria.com/insights/ucp-business-profile-and-capabilities/)
- [Buttons a browser agent can find: accessibility is how software sees your store](https://specoria.com/insights/accessible-buttons-for-browser-agents/)
- [A sitemap crawlers can trust: honest lastmod dates for a store that changes daily](https://specoria.com/insights/sitemaps-and-lastmod-for-agents/)
- [Currency and language](https://specoria.com/method/checks/market-match/) The check: how we measure it and how to fix it
- [Price, currency, availability and URL](https://specoria.com/method/checks/offer-complete/) The check: how we measure it and how to fix it
- [Agentic commerce statistics](https://specoria.com/agentic-commerce-statistics/) Sourced, dated figures you can cite
- [Agent Readiness Index 2027](https://specoria.com/index/) How the benchmarked stores scored, with open data

FREE TEST

## Is your store ready for shopping agents?

See in seconds how a shopping agent reads your store: free, instant, no email needed.

The free test runs in your browser and needs JavaScript. [Request the free deep audit by email instead →](https://specoria.com/#contact)

Your result opens on its own page. Want the full picture? The free deep audit and panel come next, by email.
