International SEO:
A Practical Guide

International SEO is the practice of improving a website’s visibility for searches across languages or countries. It combines local keyword research, content localization, distinct page URLs, and signals that identify equivalent versions. The steps below cover how to choose the pages to publish, connect their language and regional versions, and measure their performance in Google Search.

Separate language targeting from country targeting#

Google distinguishes multilingual sites from multiregional sites: multilingual sites offer multiple languages, while multiregional sites target different countries. A website can do both.

Define these requirements separately. Record the language needed for each page and any country-specific information it must contain. Then decide whether the content needs a language version, a regional version, or both. Create a regional variant where it has a clear purpose, and assign responsibility for keeping that version accurate.

Research searches in each target market#

Research keywords for each intended language and country before selecting pages for localization. In Keyword Planner’s targeting settings, location and language are separate choices. Set both deliberately rather than relying on a global keyword list.

Google’s Keyword Planner documentation describes keyword suggestions and monthly search estimates. Treat those estimates as research inputs, and evaluate prospective organic visits separately from paid campaign forecasts.

Google’s SEO Starter Guide recommends considering the different terms people use to search. Apply that principle to local research: review relevant search results, identify the question each query asks, and decide whether the answer needs an article, category page, product page, or another format.

Build a page map that records the target query, language, country where relevant, search intent, and intended URL. Use it to prioritize content that can answer the search completely. Before including a commercial page, confirm that its stated availability and next steps apply in the intended market.

Localize the content and its next steps#

Google determines page language from visible text, rather than URL labels or HTML language attributes. Localize the main content and navigation together.

Review each version as a complete page:

• Check terminology, grammar, and the clarity of the explanation with a reviewer fluent in the language.
• Adapt units, dates, currencies, availability, and contact information where the subject requires regional differences.
• Check labels, forms, error messages, and linked instructions along the next step offered by the page.
• Remove claims or destinations that the localized version cannot support.

Write page titles and descriptions that accurately summarize the localized content, following Google’s guidance for titles and snippets. Review them alongside the body rather than translating them in isolation.

Choose a URL structure and keep each version accessible#

Google’s URL comparison describes these main options:

Choose the structure that fits the site’s hosting, ownership, and publishing requirements. Document one permanent URL for every localized page.

Google warns that locale-adaptive pages, which change content according to a visitor’s perceived language or location, may leave some versions uncrawled. Googlebot requests do not include an Accept-Language header, and its default IP addresses appear US-based, although it also crawls from other countries.

Publish separate locale URLs. Keep a directly requested version accessible and offer visible language or region links so visitors can choose another version. Link to the corresponding page when it exists, preserving the subject of the visit.

Include localized pages in ordinary site navigation. Google’s discovery guidance explains that it primarily finds pages through links from pages it has already crawled. Check that the localized section has working navigation and links to its important pages.

Connect equivalent versions with hreflang#

Hreflang identifies localized versions of the same content. Google accepts HTML tags, HTTP headers, or XML sitemap annotations as equivalent methods. Choose one implementation that the publishing system can maintain.

Follow Google’s annotation rules:

• List the current page and its alternates on every version.
• Use fully qualified URLs, including https://.
• Keep links reciprocal: each paired page must reference the other.
• Use a language code such as en, optionally followed by a country code such as en-GB. For the United Kingdom, use GB, not UK.
• Use x-default for an unmatched-language fallback, such as a language selector.

Minimal HTML syntax for English and French versions:

<link rel="alternate" hreflang="en" href="https://example.com/en/guide" />
<link rel="alternate" hreflang="fr" href="https://example.com/fr/guide" />

Put both annotations in each corresponding page’s HTML head, using real URLs. Pair equivalent pages rather than unrelated homepages.

Align canonical URLs with the localized pages#

A canonical declaration identifies a preferred URL among duplicate or very similar pages. Google describes rel="canonical" as a strong canonicalization signal and recommends same-language canonical targets when using hreflang. Google ultimately selects the canonical URL.

Translated main content is not considered duplicate content under Google’s localized-page guidance. Do not automatically canonicalize every translation to the original language page.

For a distinct translation, keep its preferred URL consistent with the version named in hreflang. Google’s canonical best practices also recommend a self-referencing canonical on the preferred page and consistent internal links. Align sitemap entries with that same preference.

Review near-identical regional pages separately. Identify which URLs should represent the content before generating canonical and alternate declarations. Check these choices whenever a page moves or its regional scope changes.

Check access and indexing before assessing rankings#

Every localized page must meet Google’s minimum technical requirements: Googlebot can access it, the server returns HTTP 200, and it contains indexable content. Meeting these requirements does not guarantee indexing.

Check the pages intended for search visibility for login restrictions, crawler blocks, and unintended noindex directives. Google’s technical guidance distinguishes blocking crawling with robots.txt from preventing indexing with noindex.

Use URL Inspection in Search Console to inspect the indexed version, test the live URL, and view rendered content. The indexed report can show Google’s selected canonical; the live test cannot predict that choice.

When investigating a missing version, inspect its actual URL and rendered content before changing annotations. Then review its declared counterparts and canonical target. Retest after fixing the specific access, content, or URL relationship at issue.

Measure each language and country separately#

Search Console’s Performance report provides clicks, impressions, click-through rate, and average position, with dimensions including queries, pages, and countries.

Review each localized URL group and target country over time. Check which queries bring impressions and visits, whether those searches match the intended page purpose, and which pages need clearer content or search-result descriptions. Treat country as a geographic segment; use the page groups to examine language versions separately.

Keep on-site outcomes, such as completed purchases or forms, alongside search metrics when those actions are relevant. Choose the outcome appropriate to the page, and document any gaps in measurement before drawing conclusions.

A manual search is only one observation. Google’s report documentation notes that individual results depend on time, place, device, and recent search history. Use repeated observations and page-level evidence when investigating an unexpected result.

Maintain the localized page map#

Keep the query, language, region, URL, alternate relationships, and maintenance owner in the same record. Review related versions when shared information changes. When moving or retiring a page, update the navigation, sitemap, canonical declarations, and hreflang references that point to it.

Before expanding to another locale, repeat the research and content review for that audience. Publish the versions that can provide a complete answer and remain accurate, then assess their search visibility and relevant on-site outcomes before extending coverage further.