How to Target International Visitors to Your Website

Targeting international visitors is one of the highest-leverage SEO plays for a growing business, and one of the easiest to implement incorrectly. The mechanics have shifted since 2018: Google removed the International Targeting report from Search Console in September 2022, CDNs handle things that used to require ccTLDs, and modern frameworks bake in multilingual routing that used to be a custom build. This guide covers how international SEO actually works in 2026 — domain strategy, hreflang, and the localization details that matter beyond translation.

International SEO in 2026: What Changed

Three shifts matter if you are updating an older international SEO playbook:

• Google removed the International Targeting report from Search Console on September 22, 2022. That report was the primary way to view hreflang errors and set a site-wide country target. Both functions are gone — Google now relies entirely on automatic detection, hreflang tags on your pages, and signals like ccTLD, server location, and backlinks.
• Bing still supports hreflang and provides geo-targeting through Bing Webmaster Tools. If international traffic from Bing matters (Microsoft search powers parts of Apple and DuckDuckGo), keep it configured there.
• AI Overviews and answer engines are multilingual. Content in the target language, on the target-region domain structure, is increasingly cited in AI responses as well as organic results. The hreflang signals that help Google rank you correctly also help AI systems surface you to the right audience.

Multilingual vs Multi-Regional vs Both

Three distinct scenarios, each with different SEO implications:

• Multilingual: same content, multiple languages, one market. Example: a Canadian SaaS with English and French versions for the Canadian bilingual market.
• Multi-regional: same language, multiple countries. Example: a US ecommerce brand with US, UK, and Australian sites — all English, but priced in local currency with local shipping.
• Both: multiple languages across multiple regions. Example: a global SaaS with US English, UK English, French French, Canadian French, German German, etc. This is the hardest case and the one where hreflang earns its keep.

Decide which pattern fits before you pick a domain strategy. Mixing them without a plan produces the sprawling URL structures that are the source of most international-SEO pain.

Choose a Domain Strategy

Three options, none of them obviously best. Pick based on your team size, infrastructure, and how differentiated the regional experience needs to be.

ccTLDs (example.fr, example.de, example.co.uk)

Pros: clearest geo-targeting signal; users trust local domains; each site can be hosted, legally registered, and operated locally. Cons: each ccTLD is a fresh domain for SEO — no inherited authority from your main site; expensive to register, maintain, and rank. Right for large brands with genuine country-level operations.

Subdomains (fr.example.com, de.example.com)

Pros: easier to set up than ccTLDs; can be hosted on different infrastructure; clear separation. Cons: Google treats subdomains as somewhat separate from the root domain, so they do not inherit all the authority of the main site. Right for mid-size teams that want separation without buying ccTLDs.

Subfolders (example.com/fr/, example.com/de/)

Pros: consolidates all SEO authority on one root domain; simplest to manage; works well with a single CMS. Cons: weaker geo-targeting signal than ccTLDs; harder to host region-specific infrastructure. Right for most small-to-mid companies, especially those where one team manages all regions. Subfolders on an established root domain usually rank fastest.

A detailed treatment of the subfolder-vs-subdomain question — including how it plays into overall site architecture — lives in our best URL structure for SEO guide.

Implement hreflang Correctly

hreflang tells search engines which language and region each URL targets, and which alternate versions exist. It is the closest thing to a universal international-SEO standard and is still supported by Google, Bing, and Yandex.

Three implementation options:

• HTML head tags — easiest for small sites, added to every page:

<link rel="alternate" hreflang="en-us" href="https://example.com/">
<link rel="alternate" hreflang="en-gb" href="https://example.com/uk/">
<link rel="alternate" hreflang="fr-fr" href="https://example.com/fr/">
<link rel="alternate" hreflang="x-default" href="https://example.com/">

• XML sitemap entries — better for large sites; one sitemap lists all regional variants of every URL. Keeps markup out of individual page templates.
• HTTP headers — the only option for non-HTML files (PDFs, images).

Four rules to follow:

1. Every page in the hreflang group must list every variant, including itself. Missing self-references is the most common hreflang error.
2. References must be bidirectional. If /fr/ points at /en/ as an alternate, /en/ must point back at /fr/. Asymmetric references are ignored.
3. Use ISO 639-1 language codes and ISO 3166-1 alpha-2 country codes (lowercase language, uppercase country — though Google is forgiving on case). Common valid examples: en, en-US, en-GB, fr-FR, fr-CA, zh-CN, zh-TW, pt-BR, pt-PT.
4. Include an x-default fallback pointing at the version to serve when no other match applies. Usually this is your English or primary-market homepage.

Supporting Details That Still Matter

hreflang does most of the heavy lifting, but these details make the difference between a site that ranks in a region and one that merely exists there:

• lang attribute on <html>. <html lang="en-GB"> tells browsers, screen readers, and spell-checkers what language the page is in. Required for accessibility compliance and a quiet ranking signal.
• Content-Language HTTP header. Optional but useful for non-HTML resources.
• Canonical tags within each language. Every page points to itself as canonical. Do not canonicalize a French page to its English equivalent — that removes the French version from the index.
• Local currency, date, and address formats. A UK site showing USD prices and mm/dd/yyyy dates feels translated, not localized.
• Right-to-left (RTL) language support. Arabic, Hebrew, Urdu, and Persian need dir="rtl" on the root element and RTL-aware CSS (flexbox directions, text alignment, logo positioning).

Don’t Auto-Redirect Based on IP or Browser Locale

The single most damaging mistake in international SEO is automatically redirecting users (and crawlers) to “their” language based on IP address or browser Accept-Language header. Three reasons:

• Googlebot mostly crawls from US IPs. If your site auto-redirects US IPs to the US version, Google never sees the non-US variants and they do not get indexed.
• Users travel and use VPNs. A French speaker in Germany should be able to read your French site without fighting a redirect loop.
• Users explicitly choose. Manually clicking through to the UK site from a Google UK result should not bounce them back to the US version.

Instead, serve every language version at its own URL and offer a prominent language/region switcher (in the header or footer). Show a gentle suggestion banner at the top (“Looks like you are in France — switch to fr.example.com?”) if you want, but let users dismiss it and stay on the page they chose.

Auditing hreflang Without Search Console

Since the International Targeting report is gone, hreflang auditing now happens in third-party tools. The reliable options:

• Screaming Frog SEO Spider — crawl your site and use the hreflang report to surface missing return tags, invalid language codes, and mismatched self-references.
• Sitebulb, Ahrefs Site Audit, Semrush Site Audit — all include hreflang validation in their standard crawls.
• Hreflang Tags Testing Tool (Merkle/Aleyda Solis) — free web-based validator for spot-checking individual URLs.
• Google Search Console’s URL Inspection tool — shows the canonical and any hreflang Google detected for a specific URL, which is the closest remaining Search Console equivalent to the old report.

Localization Beyond Translation

A well-optimized international site treats translation as the first step, not the whole job:

• Translate with native speakers or a qualified agency — not machine translation alone. Google’s Helpful Content system demotes content that reads as machine-produced, and users bounce fast from obviously automated translations.
• Localize images, units, and currency. A photo of US outlets on a UK product page is a visible failure. Price in £, not $.
• Use local examples in content. A blog post that references American sports leagues will not land with a French audience. Swap in examples that resonate.
• Earn local backlinks. Links from .fr publications matter more for ranking in France than links from .com sites. Local press, local partnerships, local industry directories.
• Host close to the audience or use a CDN. Server latency affects Core Web Vitals, which are measured at the user. A CDN with edge locations in the target region solves this more cheaply than regional hosting.

Frequently Asked Questions

Is hreflang still supported by Google?

Yes. Google removed the International Targeting report from Search Console in September 2022, but hreflang tags on pages and sitemaps remain a core signal Google uses for international ranking. Bing and Yandex also support hreflang.

Should I use ccTLDs, subdomains, or subfolders for international sites?

Subfolders for most small-to-mid businesses (simplest, inherits root-domain authority), subdomains when you need infrastructure separation, and ccTLDs only when you have genuine country-level operations that justify the overhead and lost authority inheritance.

Can I auto-redirect users to their local version based on IP?

No. Googlebot crawls mostly from US IPs, so auto-redirecting by IP can hide non-US variants from Google’s index entirely. Offer a language/region switcher instead and show a dismissible suggestion banner at most.

Do I need to translate my content or can I use machine translation?

Machine translation alone is not enough in 2026. Google’s Helpful Content system demotes content that reads as auto-translated, and user bounce rates on machine-translated pages are high. Use human translators or a qualified localization agency, and treat machine translation as a draft-assist at best.

Bottom Line

International SEO in 2026 is less about configuring a Search Console setting and more about getting the basics right: pick a coherent domain strategy, implement hreflang correctly (bidirectional, self-referencing, with an x-default), localize beyond translation, and never auto-redirect by IP. Google’s International Targeting report is gone, but hreflang tags and ccTLD signals still do the job — the tooling just lives in third-party crawlers now.