13 International SEO Mistakes We Find in Audits (and How to Fix Them)

International SEO mistakes rarely announce themselves. A French or German site goes live, the hreflang validator shows green, and the market simply never grows. When we audit these sites at Flying Cat, the cause is usually one of the thirteen mistakes below. Some are strategy errors made before launch. Others are technical faults that only show up when you crawl the site the way Googlebot sees it.

We have run international programs in English, French, German, Italian and Spanish for B2B SaaS companies for over a decade. This list combines the classic errors every guide covers with the ones we keep finding in client audits in 2025 and 2026, including how each market shows up in AI answers from ChatGPT, Perplexity, Gemini and Google AI Mode.

International SEO mistakes at a glance

1. Incorrectly using hreflang tags

Hreflang tags tell search engines which language and region each version of a page serves. Google uses them to show a searcher in Lyon the French page and a searcher in Toronto the Canadian English page. When the annotations break, the wrong version ranks, or Google ignores the cluster entirely.

The hreflang errors we find in audits fall into four groups.

• Missing return links. Every version must point to every other version, and to itself. Google states that if two pages do not point to each other, it ignores the tags.
• Invalid codes. A region code on its own is invalid. Codes like "UK" or "EU" are reserved, so Google ignores that part of the annotation. The correct code for the United Kingdom is "en-gb".
• Hreflang pointing at non-canonical URLs. Annotations that point at redirected, noindexed or canonicalized URLs send mixed signals.
• No x-default. Without it, searchers whose language you do not serve get whichever version Google picks.

Our hreflang tags guide covers syntax, code examples for HTML, HTTP headers and sitemaps, and a step-by-step Screaming Frog audit. The short version is that hreflang only works on top of a sound URL structure. The next three mistakes break that structure.

2. Not having specific URLs for each international site

Each language or country version of your site needs its own URL so Google can crawl, index and rank it separately. Some sites instead serve different content on a single URL based on the visitor's browser language or location. Google calls these locale-adaptive pages.

Locale-adaptive pages create two problems.

The user experience suffers. Visitors cannot share or bookmark a specific language version, because the URL stays the same. The setup also assumes everyone in a country wants the local language. An English-speaking buyer in Madrid or a French speaker in Montreal may get the wrong version with no easy way out.

Googlebot may never see your other languages. Google warns that it might not crawl, index or rank all content on locale-adaptive pages, because Googlebot's default IP addresses appear to be in the US. Googlebot also crawls without an Accept-Language header, so language-based switching shows it one version only.

The fix is a distinct URL for each locale, such as example.com/fr/ and example.com/de/, connected with hreflang.

3. Automatically redirecting to localized versions by IP address

Many sites redirect visitors to a local version based on their IP address. This creates the same two problems as locale-adaptive pages, plus a third. Visitors who land on the version they wanted get bounced away from it.

Google's guidance on multi-regional sites is direct. It advises site owners to avoid automatically redirecting users from one language version to another and to avoid adapting content by IP analysis. Googlebot crawls mostly from US IP addresses, so an IP redirect can send the crawler to the US pages every time.

Keep both visitors and Googlebot on the URL they requested. Use the visitor's location to suggest a local version in a banner, and give every page a visible language switcher that links to the alternates with plain HTML links.

In this example, Adobe used the visitor's location to suggest a local site in a banner. The requested page stayed in place for users and for Googlebot.

4. Choosing a domain that is already tied to one country

Country-code top-level domains (ccTLDs) such as .de, .fr or .ca signal one country. Google treats a ccTLD as a strong geotargeting signal and lists it as one of the main ways to make regional variants explicit. That strength becomes a constraint when you expand. A .es domain with /fr/ and /de/ subfolders tells Google the whole site targets Spain.

You have two clean options.

• A generic domain (.com, .io) with subfolders or subdomains, such as example.com/fr/ or fr.example.com. Subfolders share the main domain's authority and run on one CMS, which is why we recommend them for B2B SaaS companies that run one CMS with one web team.
• One ccTLD per country, such as example.de and example.fr. Each domain sends a clear country signal, but each one also builds authority from zero and needs its own hosting and maintenance.

Inside a single country with more than one language, add language subfolders. IKEA does this in Canada with ikea.ca/en/ for English and ikea.ca/fr/ for French.

IKEA uses a Canadian ccTLD with separate English and French subfolders.

5. Relying on Google Search Console for country targeting

Older guides, including an earlier version of this page, told readers to set a target country for each subfolder or subdomain in Google Search Console. That setting no longer exists. Google announced in August 2022 that it was deprecating the International Targeting report, and stated that country targeting through Search Console had little value and is no longer supported. Search Engine Land reported the removal date as September 22, 2022.

Google still supports hreflang. It also reads other local signals, which it lists in its multi-regional guidance as ccTLDs, local addresses and phone numbers, local currency and language, and links from local sites. An international plan in 2026 should build on those signals and drop any step that depends on a Search Console country setting.

Search Console remains useful for reporting. Filter the Performance report by country and by folder to track each market separately.

6. Machine-translating pages without local keyword research

Translating your English keyword list gives you the words a translator would use. It rarely gives you the words local buyers type. German buyers searching for email consent rules use "DSGVO double opt in", for example, which no direct translation of the English term would produce.

We saw the cost of this at an ecommerce marketing platform. Its translated pages sat in the mid-20s in France. Native writers rebuilt each market from scratch around local search habits, retail calendars, regulations and customer examples, on a budget of about two articles per market per month. The client tripled its top-3 keyword rankings in France within six months. Organic conversions in France grew 60% in year one. Later, its core French term "email marketing" climbed from rank 48 to rank 1.

Unreviewed machine translation also carries policy risk, which is why the multilingual SEO agencies worth hiring put a native writer on every page. Google's spam policies name automated translation that adds little value as an example of scaled content abuse. Our international keyword research guide covers how we build a keyword set for each market with native linguists.

7. Overlooking local content and language nuances

Correct keywords still fail if the page reads like a foreign company talking to a local buyer. Content has to reflect local buying behavior, regulations and terminology, even between markets that share a language.

Two examples from our own client work show how specific this gets. For a vertical SaaS client in veterinary software, burnout messaging that works in North America does not land the same way in France. The term "SOAP notes" is also less universal than US teams assume, because UK and European vets more often say "medical records". For an enterprise learning platform, content written around local regulations in India grew clicks 76.5% in one reporting period, while generic content for Latin America declined.

ActiveCampaign shows what happens when localization is done at scale. We localized its best English pages and wrote about twenty new bottom- and mid-funnel pages per language each month for its French, Italian, German and Spanish sites. Those sites gained 83,000+ more non-branded clicks and 4.1M+ more impressions in eight months. Our multilingual SEO guide explains the glossary, writing and in-market review workflow behind that kind of program.

8. Canonicalizing regional versions to a single page

Teams worried about duplicate content often point the canonical tag on every regional page to the US or global version. That tells Google the regional pages are copies, so they drop out of the index in their own markets.

Google's rules are specific here.

• Translated pages are only duplicates when the main content stays untranslated, per Google's localized versions documentation.
• Same-language regional pages, such as US and UK English, can count as duplicates. Google's guidance is to specify a canonical in the same language and to prefer URLs that sit in an hreflang cluster.

In practice, give every localized page a self-referencing canonical and connect the versions with hreflang. Then make the regional versions different where buyers notice, such as pricing currency, spelling, local customers and legal terms.

9. Hiding localized pages behind client-side redirects

This mistake passes every standard check. During a content audit for an AI tax research platform for accountants, we noticed its Canada and UK sections drew almost no traffic. The pages returned a 200 status code and carried valid hreflang tags.

A crawl with JavaScript rendering turned on told a different story. 99.9% of the Canadian answer pages redirected client-side to their US versions. Visitors and Googlebot who requested a Canadian URL ended up on the US page. A plain HTML crawl would have reported those pages as healthy.

Any site built on a JavaScript framework needs a rendered crawl alongside a text-only crawl. In Screaming Frog, compare the two and check the JavaScript redirect report for localized folders.

10. Serving localized pages as empty shells after a re-platform

Migrations and re-platforms break international sites more often than anything else we see. After a vertical SaaS client in veterinary software moved its site to a JavaScript app, we checked every French page we had published. Every one served Googlebot the same empty shell with an English title, so Google could not see any of the French content.

The pages were already losing clicks when we caught it. Before the re-platform, the French site had doubled its clicks and nearly tripled its impressions soon after we started publishing French pages. In July, two months after the audit, French clicks rose 53% month over month with a 70% engagement rate.

Check the rendered HTML of a sample of pages in every language before and after any migration. The URL Inspection tool in Search Console shows the HTML Google rendered for a specific URL. Our technical SEO service includes this check on every re-platform.

11. Letting www and non-www hosts split ranking signals

The same veterinary software audit found a second problem. The site answered on both www and non-www hosts. Its canonical tags pointed at URLs that redirected. Google received conflicting signals about which host to rank, so the two versions split the ranking signals between them.

The fix has three parts. Pick one host and 301 redirect the other to it. Make every canonical tag and every hreflang annotation point at a URL that returns a 200. Update internal links to the chosen host, so they no longer pass through redirects. The client's team replaced hundreds of internal www links in the first pass.

12. Leaving localized pages without localized internal links

Localized pages need internal links from other pages in the same language. Many international sites link every local page from the English navigation and nowhere else. Their French blog posts link to English product pages, and new local articles have no links at all.

After the www fix, the same veterinary software client found and fixed hundreds more links across dozens of posts. Some of those posts were orphaned, so the crawl could not reach them at all.

We build internal linking into every localized page. Local blog posts link to local product and solution pages. Navigation and footers point to the local versions. Each new local article gets links from older local pages that already rank.

13. Ignoring AI visibility in each market

International SEO now includes AI answers. Google expanded AI Mode to over 200 countries and territories and more than 35 new languages in October 2025. Buyers in Paris, Munich and Madrid ask ChatGPT, Perplexity, Gemini and AI Mode the same vendor questions US buyers ask.

AI assistants do not research every language in the same way. Peec AI analyzed more than 20 million ChatGPT fan-out searches and found that 43% of the background searches for non-English prompts ran on the English-language web. English vendor lists can therefore shape the answer a German buyer reads. A brand that tracks AI visibility only in English misses what local buyers see.

Rankings still feed AI citations. In Maeva's own research for The Search Spot, 76% of product pages with five or more top-10 keywords reached 10+ AI citations, against 10% of pages below that threshold. A localized page that Google cannot render or index is unlikely to be cited in that market either.

The payoff from tracking each market is large. Over three months to May 2026, AI referral users at the ecommerce marketing platform grew 522% in France and 281% in Spain. The veterinary software client now ranks first in French AI share of voice, at about twice its nearest competitor. We track these numbers with a native-language prompt set for each market, run from that country, as part of our GEO and AEO service.

How Flying Cat audits an international site

Every international engagement starts with the same audit. Our founder, Maeva Cifuentes, leads the strategy and works with native-speaking specialists for each market. These are the checks we run, in order, and the template you can copy for your own site.

1. Market performance baseline. We pull Search Console clicks, impressions and conversions by country and by language folder, so each market has its own starting point.
2. URL and domain map. We list every locale, its URL pattern and its hreflang code in one spreadsheet, with one row per page and one column per market.
3. Two crawls. We run a text-only crawl and a JavaScript-rendered crawl in Screaming Frog, then compare titles, word counts, status codes and redirects per language folder.
4. Redirect and host checks. We test IP and language redirects from several countries, confirm a single host, and check that canonicals and hreflang point at URLs that return a 200.
5. Hreflang validation. We check return links, codes, x-default and canonical conflicts for every cluster.
6. Keyword and content review. Native linguists compare each market's pages with local search demand and local competitors.
7. Internal link review. We count internal links into every localized page from pages in the same language and flag orphans.
8. AI visibility per market. We run native prompts in each market and record presence, citations and the third-party sources AI assistants cite locally.

Each finding becomes a ticket with a severity, an estimate of traffic impact, an owner and a verification step. On the AI tax research platform, that audit format let the client's team verify two-thirds of the technical tickets as complete within about six weeks.

Fixing these mistakes is only half of an international program. Our guide to international SEO strategy covers how to choose markets, sequence launches and build a business case for each one. If you want us to run this audit on your site, our international SEO service starts with it, and you can book a call to talk through your markets.

Frequently asked questions about international SEO mistakes

What is the most common international SEO mistake?

No public dataset ranks international SEO mistakes by how often they occur. In our audits, hreflang errors are what SEO tools flag first. Yet the more expensive problems sit next to the hreflang code. Client-side redirects, empty JavaScript shells and pages canonicalized to the main market can all leave valid hreflang pointing at content Google cannot index.

Can I still set a target country in Google Search Console?

You can no longer set one. Google deprecated the International Targeting report in 2022. Country targeting through Search Console is no longer supported. Use hreflang, a clear URL structure and local signals such as local currency, addresses and links from local sites.

Is translated content duplicate content?

Google treats translated pages as duplicates only when the main content stays untranslated. Same-language pages for different regions can count as duplicates, so give each one a self-referencing canonical, connect them with hreflang and make each version useful for its own market.

Should I redirect visitors to their local site automatically?

Google advises against it, because Googlebot crawls mostly from the US and may never reach your other versions. Show a banner that suggests the local version and keep a language switcher on every page.