Discussion
  • International SEO

Separate URLs per currency, or one URL with geo-pricing? What has worked for both Merchant Center and organic rankings?

Published 1 reply

Discussion starter: an international SEO question, posted with an answer from Niraj Raut to open the thread. If you have dealt with this on a site, reply with what you saw, especially where it differs.

Disclosure: Niraj Raut, who posted this answer, runs the SEO consultancy linked at the end of it.

1 reply

  • admin
    Admin
    Original poster

    If “geo-pricing” means one URL whose currency switches with the visitor’s IP address, that is the setup that suits neither system. Google Search and Merchant Center both judge the page by what your server shows Google’s crawlers, and Google’s own documentation says most of its crawling comes from US addresses, not from your customers’ locations. What works for both is letting the URL, not the visitor’s location, decide which currency renders by default. That can mean fully separate market URLs, or one indexable URL plus currency-specific landing URLs used only in your feeds.

    The choice between those two comes down to whether a market needs a page that differs in more than currency. If shipping, returns, tax display, spelling or range differ and there is real local search demand, separate market URLs earn their cost. If only the currency differs, separate URLs mostly produce near-duplicates that Google may fold together, and the lighter setup serves Merchant Center just as well.

    What each system is documented to need

    Google’s guide to managing multi-regional and multilingual sites (last updated December 2025) is direct about IP-based adaptation. It advises against using IP analysis to adapt content and warns that Google may not be able to crawl the variations properly. It says most, but not all, Google crawls originate from the US, that the crawler sends requests without an Accept-Language header, and that Google does not vary the crawl location to detect variations. The same page lists URL parameters as a not-recommended way to structure locale-specific URLs, and includes the use of local language and currency among the signals Google can use to identify a site’s intended audience.

    Merchant Center’s rule is narrower. Its help page on inconsistent currency between your product data and your website says the currency in your product data and on your landing page need to match, and tells you to change one or the other. It allows several currencies on the landing page, provided the product data’s currency is the default, prominently listed one, and several at checkout, provided shoppers can easily select the product data’s currency for at least one payment method. It also suggests currency conversion as a way to reach more countries.

    Put those side by side and the conflict with IP-based switching is plain. The “default” currency on such a page is whatever the request’s location implies. Googlebot, arriving mostly from US addresses, indexes the US version, and the price in your product results reflects that version. Merchant Center then checks an Australian item priced in AUD against a page whose default currency is decided by where the check comes from, which you do not control.

    Think of Google’s crawlers as a mystery shopper who walks in through the same door almost every time. If your shop changes its price tags depending on which door a customer used, the mystery shopper keeps reporting the same set of tags, and it may not be the set your local customers see. Technically, one URL gets one indexed version. The IP-based variants only reach Google if it happens to crawl from that country, and Google says it does not try to.

    On rankings specifically, a separate currency URL is not a ranking lever in itself. Google lists local currency as one audience signal among several and does not document its weight. The benefit to look for is in which URL and which price a country’s searchers see, and so in click-through and conversion. Any ranking gain comes from the version being a better fit for that market, not from the currency code.

    Three setups that satisfy both systems

    Setup What Search indexes What Merchant Center checks Costs and risks
    1. Separate market URLs (subfolders or ccTLDs), local prices rendered on the server, hreflang and self-canonicals, one feed per country pointing at that market’s URLs One version per market, each showing its own currency, which Google lists as an audience signal Each country’s items land on a page that defaults to that country’s currency Price lists, feeds and structured data to keep in sync per market. If versions differ only in currency, Google may cluster them, and Search Console reports the rest as “Duplicate, Google chose different canonical than user”
    2. One indexable URL plus feed landing URLs that fix the currency (for example ?currency=AUD, rendered on the server) and canonicalise to the main URL One version, in your base currency, with no duplicate cluster to manage Each country’s items land on a URL that defaults to the right currency Organic results show your base currency in every market. The feed URLs must stay crawlable. This is a practitioner workaround rather than a recipe Google documents
    3. One URL in one currency, plus Merchant Center currency conversion for other countries One version Products can reach more countries without re-pricing (check eligibility per country and how converted prices display) Shoppers meet a foreign currency on your page, which can cost conversions in price-sensitive categories

    One nuance for setup 1: hreflang describes language and region, not currency. When two markets share a language, the region code is doing all the work, and Google’s guide says that where similar content in the same language sits on different URLs, you should pick a preferred version and use canonical and hreflang so the right regional URL is served. A version that differs only by currency gives Google little reason to keep it separate.

    Choose per market, not per site

    Condition Lean towards separate market URLs Lean towards one URL plus feed landing URLs
    Local search demand Meaningful category and product demand, with local competitors ranking Small market, or one served mainly through Shopping
    What differs besides currency Shipping promise, returns, tax display, spelling, range Only the currency
    Pricing strategy Local price points set deliberately (A$49 rather than a converted A$47.83) Converted prices are acceptable
    Engineering capacity Can keep several price lists, feeds and structured data in sync One price list, converted at render
    Reversibility Harder to unwind once indexed and linked Easy to upgrade a market later

    Mixing both is a sound position: separate URLs for the two or three markets that justify localisation, one URL plus feed landing URLs for the rest, and a rule for when a market graduates, such as organic demand or revenue passing a threshold you set in advance.

    Hypothetical example:

    A UK skincare brand sells to the UK, Ireland, Australia and the US from one.com that switches currency by IP. Merchant Center flags currency issues on Australian items, and Australian searchers see US-dollar prices in organic results because that is what Googlebot was served. The brand moves Australia and the US to subfolders with local prices, delivery and returns terms, keeps Ireland on the main URLs with a euro feed landing URL, and makes pounds the fixed default everywhere else. Irish items stop failing the currency check without a new site section, and organic effort goes only where a local page has something local to say.

    Where these setups break in practice

    • Client-side currency swaps. If the HTML carries one currency and JavaScript swaps it after an IP lookup, the currency Google renders is decided by Google’s own IP. Render the market’s currency on the server for every URL that should carry it.
    • Cookie-based selectors. Google’s crawlers generally do not keep cookies between page loads, so a currency chosen through a cookie does not reach them. The URL has to carry the choice.
    • Structured data in the wrong currency. A theme or app that hard-codes the base currency in JSON-LD produces pages whose markup disagrees with the visible price. Each version’s priceCurrency should match the price the page shows.
    • Automatic redirects. Google’s guide advises against automatically redirecting users between language versions, and the same logic applies to currency versions: if US-located requests are redirected to the US version, the other markets become hard to crawl. A banner with a country selector keeps every URL reachable.
    • Feed landing URLs leaking into the index. Keep currency parameters out of internal links and XML sitemaps, and do not block them in robots.txt, so they exist for Merchant Center without competing with the canonical URL.

    How to check what Google actually sees

    1. URL Inspection. Run a live test on a product URL for each setup and check the visible price and the JSON-LD currency in the tested page’s HTML.
    2. Server logs. For requests from verified Googlebot and Storebot-Google addresses, log which currency was served. A currency field in each log line makes this a quick query.
    3. Merchant Center diagnostics by country. Review currency and price mismatch issues after each feed update, split by target country.
    4. Results by location. Use a SERP tool set to each market and look at the price shown in your product results.
    5. Canonical choice for market URLs. If you run separate market URLs, compare user-declared and Google-selected canonicals in URL Inspection for a sample, and use Search Console Performance filtered by country to see whether each country’s impressions go to its own URLs.

    A fast experiment before restructuring anything

    Take one secondary market that currently relies on IP switching. Point that country’s feed at currency-fixed landing URLs and change nothing else. The primary metric is the number of currency and price mismatch issues for that country in Merchant Center; the secondary metrics are Shopping and free listing clicks and conversion rate from that country. Merchant Center reprocesses items after feed fetches and recrawls, so this should read out far faster than any organic test.

    The organic question needs a slower test. Launch a market subfolder for a handful of top categories, with local prices, delivery and returns, and track two things: the share of sampled URLs where Google selects the market URL as canonical, and the share of that country’s organic landings that reach market URLs. On a large catalogue, recrawling and re-clustering can take months, so judge the pilot on crawl coverage (logs showing the pilot URLs recrawled) rather than a fixed date.

    What would change the decision: if the feed-only fix clears the Merchant Center issues and Shopping conversion recovers, that market may not need its own organic section yet. If the pilot URLs keep being folded into the base version and local searchers keep landing on base URLs, the market is not differentiated enough, and more currency-only URLs will not fix that.

    If this were my store, I would remove IP-based currency switching from every URL Google sees, give each country’s feed a landing URL that fixes the currency, and create separate market URLs only where the page would genuinely differ. Currency on its own is a weak reason for a separate URL, but a strong reason to make sure Google never has to guess which price you meant.

    Need help with this on your own site?

    Niraj Raut works with businesses in Nepal, Australia, the UK, Europe and the US on technical SEO, ecommerce SEO, local SEO and AI search.

    See SEO services

Add a reply

Replies are open to approved members. Log in or apply to join.