International SEO Across Multiple Countries and Languages
A company expanding into new countries found Google serving the wrong regional pages to searchers. Meek Media rebuilt the international setup as one system: hreflang, a clear country structure, localized content, market-specific currencies, regional keyword research and duplicate-content controls, so each audience lands on the version written for it.
- Client
- Company expanding internationally
- Services
- Technical SEO Services, SEO Services
- Privacy
- Client name withheld
How do you fix Google showing the wrong country page?
Give Google unambiguous signals for every regional version. That means a consistent country and language URL structure, reciprocal hreflang with self-references and an x-default, self-referencing canonicals, and genuinely localized content and currencies so near-identical versions stop competing. Meek Media applied all of these together on this project instead of patching tags one at a time.
Why was Google showing the wrong regional pages?
The company was growing into new international markets, but its search visibility was not keeping up with the plan. Searchers in one country were being shown pages built for another region. That meant the wrong currency, the wrong regional details and messaging that did not fit the local audience. Every mismatched result either started a visit with friction or sent the click to a competitor that showed the right local page.
This pattern almost always comes from mixed signals. When regional versions share largely identical copy, Google may treat them as duplicates and choose one of them as the canonical for all. Missing hreflang return links, a URL structure that does not clearly separate countries and languages, and content that has not been adapted for each market all make the confusion worse. None of these issues can be solved in isolation. Fixing the problem meant addressing structure, annotations, localized content, currency and keyword targeting together, so that every signal Google received pointed at the same answer for each market.
What we found
- Google was ranking regional pages in countries they were not built for
- Regional versions were similar enough to be treated as duplicates
- The country and language structure sent unclear signals to search engines
- Hreflang needed to be implemented and validated across every regional version
- Currencies had to match the market each page was serving
- Keyword targeting had not been researched market by market
How did Meek Media get the right page in front of each market?
We treated international SEO as one connected system rather than a tagging exercise. Structure came first, because hreflang and localization only work on a foundation search engines can read clearly. On top of that we layered annotations, localized content, currency handling and regional keyword targeting, then closed the duplicate-content paths that had let one market's page win everywhere.
-
1
Settle the country and language structure
We mapped every market the company served and defined one consistent URL pattern for each country and language combination. The goal is simple: any URL should tell users and crawlers exactly which audience it serves. Mixed or inconsistent patterns are a common cause of regional confusion, so every existing page was assigned a clear home in the structure before any tags were touched.
-
2
Implement and validate hreflang clusters
Each regional page received hreflang annotations listing every alternate version, including itself, with valid language and region codes and an x-default for visitors who match no specific market. Hreflang only works when links are reciprocal, so each cluster was validated for missing return tags, invalid codes, and alternates pointing to redirected or non-canonical URLs, all of which cause Google to ignore the annotations.
-
3
Localize content beyond translation
Pages that differed by little more than a flag were reworked so each market version reflects local terminology, regional details and the expectations of that audience. Genuine localization gives Google a reason to treat versions as distinct pages and gives visitors content that feels written for them. Where two markets shared a language, local wording and regional specifics were used to separate the versions meaningfully.
-
4
Align currencies with each market
Every regional version shows prices in the currency of the market it targets, consistently across the page. Rather than silently redirecting or swapping content based on a visitor's IP address, the setup keeps every regional version crawlable, because Googlebot crawls mostly from one location and can miss versions it is redirected away from. Visitors can still be offered a switch to their own region.
-
5
Research keywords region by region
Search behaviour differs between countries, even when they share a language, so keyword research was carried out separately for each market instead of translating a single master list. That surfaced different terms, phrasing and priorities per region. Each regional page was then mapped to the queries its own audience actually uses, strengthening relevance and reducing the chance of one version outranking another outside its market.
-
6
Control duplicate content across regions
Every regional page carries a self-referencing canonical and never points to a different country, because a cross-regional canonical tells Google to drop the version you want shown. Duplicate variants of regional pages were consolidated, sitemaps were limited to canonical regional URLs, and indexing was reviewed market by market to confirm Google was selecting the right version for each audience.
What We Delivered
- Country and language URL structure plan
- Hreflang implementation with x-default for every regional cluster
- Hreflang validation and error fixes
- Localized content for each target market
- Market-specific currency handling
- Regional keyword research and page-to-query mapping
- Canonical and duplicate-content rules for international pages
What Other Teams Can Learn From This
Hreflang is a signal, not a cure
Hreflang tells Google which version suits which audience, but it cannot rescue pages that are otherwise duplicates or that canonicalize to another region. Treat it as the final layer on top of a clean structure and real localization. If annotations are the only thing separating your regional pages, expect Google to keep making the choice for you.
Translate less, localize more
A translated page answers the question of language. A localized page answers the questions a specific market actually asks, in its own terms, with its own currency and details. The second is what earns rankings and conversions. Budget regional expansion around localization and market research, not just translation, or the new pages will struggle to compete with local sites.
Audit clusters, not single pages
Most hreflang failures live in the relationships between pages: a missing return link, a redirected alternate, a region code that does not exist. Checking one URL at a time misses them. Validate every cluster as a set whenever pages are added, moved or retired, because international setups tend to break quietly as a site grows.
Frequently Asked Questions
What is hreflang and does an international site need it?
Hreflang is an annotation that tells search engines which language or regional version of a page to show a given user. Any site with multiple versions of the same content for different languages or countries benefits from it. It must be reciprocal across every version, include a self-reference, and point only to canonical, indexable URLs to be honoured.
Should international sites use subdirectories, subdomains or country domains?
All three can work in Google. Country-code domains send the strongest geographic signal but split authority across sites. Subdirectories keep authority on one domain and are easiest to manage. Subdomains sit in between. The right choice depends on business structure and resources, but consistency matters more than the option chosen.
Can translated or regional pages count as duplicate content?
Translations are not treated as duplicates, but same-language pages for different countries often are when the copy is nearly identical. Google may then pick one as canonical and show it everywhere. Localizing content, currency and regional details, combined with correct hreflang, helps Google keep each version for its intended market.
Should we automatically redirect visitors based on their location?
Google advises against forcing automatic redirects by location because they can stop crawlers and users from reaching other versions. Googlebot crawls mostly from one country, so redirected versions may never be seen. A better pattern is to keep every version accessible and show a clear, dismissible prompt suggesting the visitor's local version.
Related Case Studies
Rebuilding a 10,000+ Page Website Without Losing SEO
A website with more than 10,000 pages needed a complete redesign, and thousands of those pages were indexed and ranking. Meek Media planned the rebuild so search value carried across: URL architecture, page templates, metadata migration, redirects, structured data, internal linking and a structured launch QA process that checked the new site before and after it went live.
Read the case study →
Recovering a Website After a Google Algorithm Traffic Collapse
After a major Google update, this site lost 60–80% of its organic traffic. Meek Media audited everything that shapes how Google judges a site: content quality, backlinks, site architecture, duplicate pages, search intent and technical SEO. We then rebuilt the organic strategy around the pages that deserved to rank, rather than chasing the update itself.
Read the case study →
Core Web Vitals Rescue for a High-Traffic Website
This website had strong traffic but failed Core Web Vitals. Heavy scripts, large images, layout shifts, slow server responses and third-party integrations were all dragging down the experience. Meek Media tackled the problem on two fronts, optimising the front-end architecture and the server infrastructure behind it, so pages loaded faster, responded quicker and stayed visually stable.
Read the case study →
Facing a similar problem?
Every engagement starts with a free audit. We find what is holding your site back, show you the fix, and scope the work to your goals before you commit.