Why Google Shows the Wrong Country Version of Your Website

The customer arrived. The page went abroad.

Imagine a buyer in Manchester searching for a commercial coffee machine. Your company appears. The product looks right, the description is in English, and the buyer clicks.

Then the doubts begin. Prices are in US dollars. Delivery information refers to American states. The service number is across the Atlantic.

You have a UK page with the answers they need. They have landed on the US version.

Your website has turned a promising enquiry into a geography quiz.

That is the business problem behind a technical term you may have heard: hreflang. It helps Google understand which versions of a page are intended for different languages or regions. The point is to help a potential customer reach the page that makes sense for them.

Before changing anything, though, separate two questions: does the right page exist, and are you giving Google clear information about it?

The same language can serve different markets

English tells you how someone reads. It tells you much less about where you can deliver, which products they can buy, or who will service the equipment afterwards.

For our imaginary coffee-machine supplier, regional pages might answer these questions differently:

Illustrative example, not a client case study.

These are useful differences. They give each page a reason to exist. If your offer and information are identical everywhere, do not create a separate country page just because another flag would look nice in the menu.

Where regional versions are useful, give each one a stable URL. For example, example.com/uk/coffee-machines/ and example.com/us/coffee-machines/. Google recommends distinct URLs for different language versions, and supports regional variations of similar content. See Google's international-site guidance.

Keep a visible country or language selector, too. A buyer travelling abroad may still need their home market. Let people choose; avoid forcing them into a version based on an assumed location or language.

Hreflang handles the introductions

Hreflang sounds like something a developer dropped on a keyboard. Its basic job is fairly simple: label the alternative versions of a page.

For our example, en-GB identifies English for the UK; en-US identifies English for the US. A general English version can use en. These labels help Google select an appropriate search result. They do not translate the content or redirect the visitor.

The implementation needs a few careful introductions:

• Connect equivalent pages. A UK product page should identify the corresponding US product page as its alternative.
• Make the relationship mutual. Each alternative should point back. Google can ignore a relationship without the return link.
• Include the page itself. Each version lists itself alongside its alternatives.
• Use valid codes and complete URLs. For the UK, use en-GB. Use complete web addresses in the annotations.

These are established implementation rules, detailed in Google's hreflang documentation.

You can also specify an x-default fallback, such as a country-selection page, for users whose language or region does not match a listed version. It is an optional recommendation, explained in Google's x-default guide.

Hreflang helps with selection. It does not guarantee a particular result for every searcher. Google still has to interpret the pages and decide what to show.

The canonical question deserves its own answer

Now for the detail that can make an apparently tidy setup confusing: two regional pages may still contain very similar content.

That does not automatically mean a penalty. Google generally does not treat duplicate content as a spam-policy violation, as its crawling and indexing FAQ explains.

It does mean Google may choose a representative URL, called the canonical, from a group of duplicate or very similar pages.

A canonical tag states your preferred representative. Hreflang identifies language or regional alternatives. Both matter, but they answer different questions. Google treats canonical tags as a strong signal, rather than an instruction it must always follow, per its canonical guidance.

For similar pages in the same language aimed at different regions, Google recommends considering canonical and hreflang together. A preferred canonical and a regional alternative can be part of the same setup. The right arrangement depends on how the content differs and what the pages are for. See the regional duplicate-content guidance.

This is where a blanket rule can cause trouble. Pointing every international page to the homepage is not a substitute for deciding which pages are genuinely equivalent.

Make the right page worth landing on

Return to our buyer in Manchester. This time, they reach the UK page. The currency makes sense. The delivery information answers their question.

Then the product image takes ages to appear, a button ignores their first tap, and a late-loading banner pushes the contact link out of reach.

The regional setup has done its job. The page experience still needs work.

Google's Core Web Vitals measure three parts of that experience: loading, responsiveness and visual stability. These are the thresholds for a good result, from the Web Vitals overview.

Source: Google web.dev. Good Core Web Vitals thresholds, checked September 2026. CLS is a unitless score.

LCP tracks when the largest eligible visible content, such as a product image, is rendered. INP assesses the delay between a click, tap or keyboard interaction and the next paint, using the longest interaction with an allowance for outliers. CLS captures unexpected layout shifts: the familiar experience of a page moving just as you try to press something. The details live in the LCP, INP and CLS guides.

Aim to meet each threshold for at least 75% of page visits, assessed separately on mobile and desktop. This is a real-user performance target, not a percentage improvement in sales, per Google's measurement guidance.

Good scores support a better experience. They do not guarantee top rankings, and speed plus hreflang cannot make a website immune to Google updates. Google explicitly warns against treating good Core Web Vitals as a ranking guarantee in its page experience guidance.

Our buyer would settle for a page that loads, makes sense and lets them ask for a quote.

Check the journey, then measure what changes

Start with one commercially important page in each market. Open it on your phone and follow the route a new customer would take.

Check the currency, availability, delivery information and contact details. Switch markets. Do you stay on the equivalent product, or get dropped at the homepage and have to start again?

Then ask whoever manages the site to verify the technical relationship: the intended URLs are reachable, the hreflang links match, return links are present, and canonical choices fit the content.

In Search Console, use URL Inspection to examine Google's selected canonical. A “Duplicate without user-selected canonical” status can describe expected behaviour; it needs interpretation, not an automatic promise to make the report greener. The page indexing report guidance covers the statuses.

After changes, look at search performance by country alongside your analytics and enquiries. Read those results with the indexing information. A rise in clicks alone will not tell you whether people found the correct delivery terms or reached the right sales team.

Useful outcomes are concrete: visitors can find the regional information they need, and suitable enquiries reach someone who can handle them. Any change in conversion rate still needs measurement. The price, offer, content and follow-up matter too.

Your customer should be comparing suppliers, not decoding your website.

For the broader work behind entering a new market, our guide to what multi-language SEO actually takes covers site structure, local keyword research and measurement.