Skip to content

International SEO

International targeting in Google Search Console

The old International Targeting report and its country setting are gone. International SEO now depends on locale-specific URLs, visible localized content and correct hreflang annotations.

✓ Checked against Google Search Central · October 2026

The old International Targeting report and its country setting are gone. Google has deprecated the report: country targeting in Search Console is no longer supported, while Google continues to support and use hreflang (Google’s official notice). International SEO now depends on locale-specific URLs, visible localized content and correct hreflang annotations.

What changed in Search Console

Two different features disappeared with the old report, and their replacements are not another Search Console screen. First, country targeting was removed: you can no longer choose a target country for a generic domain in Search Console. Second, the hreflang error report disappeared: Search Console no longer provides the old site-wide Language tab. Hreflang itself was not deprecated; only that reporting interface went away.

What to use instead

Google’s current guidance focuses on page and URL signals rather than a manual country switch (localized versions of your pages). Give each language or regional version its own crawlable URL, such as /en-gb/ and /en-us/, and do not depend on cookies or browser-language swaps. Declare alternates with hreflang using HTML tags, HTTP headers or an XML sitemap; Google treats the three methods as equivalent and says there is no Search benefit in maintaining all three. Keep every cluster reciprocal: each localized page must list itself and every alternate, so if page A points to page B, page B must point back to page A. And let users switch locale with visible language or region links, because Google advises against adapting content solely through IP detection, since crawling may miss variants (managing multi-regional and multilingual sites).

A minimal hreflang cluster

The same set belongs on every version of the page. Use fully qualified URLs and a language code with an optional region code.

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

Use x-default for a fallback page when no listed language or region is the right match.

How to validate it now

Search Console no longer supplies the old site-wide error list, so validate the implementation at page and crawl level. Check that every alternate points back to every other member of the cluster, and that each page includes its own URL in the hreflang set. Use ISO 639-1 language codes and optional ISO 3166-1 Alpha 2 region codes; a country code by itself is invalid. Alternate URLs must resolve successfully, be crawlable and not be blocked from indexing. Each localized page normally canonicalizes to itself rather than collapsing the whole cluster into one locale. And HTML, headers or sitemap entries must not disagree about which URLs belong together.

People search for this under several names: Google Search Console international targeting, Search Console international targeting, Google Search Console country targeting and hreflang Google Search Console now all point to the same answer. The report is retired, but international SEO signals still work. To check what the workspace can tell you about crawling and indexing, see the Page indexing article.

Go further

Indexing and technical SEO: Sitemaps, URL Inspection and indexing signals. Data and metrics: Clicks, impressions and reporting differences. Account and access: Roles and Google account permissions.

Official sources

  1. International Targeting report is deprecated ↗
  2. Tell Google about localized versions ↗
  3. Managing multi-regional and multilingual sites ↗
SEOKIT · GROQ

SEOKit assistant

0 / 1000

Data at Groq