NeovaAdvanced SEO Platform

International SEO Checklist: Every Check for a Multilingual or Multi-Country Site

Going international multiplies everything: every template, every redirect rule, every title now exists in several languages, and one wrong setting repeats across all of them. This international SEO checklist goes from picking markets to checking the last hreflang tag, with Google's own guidance linked at each step.

International SEOinternational seo checklistUpdated November 21, 2026By the Neova team

Start With Markets, Not Just Languages

Before any tag or folder, write down who each version is for. A version can target a language, a country, or a language in a country, and each needs a different code:

TargetExamplehreflang code
A language anywhereGerman speakersde
A language in one countryGerman in Austriade-at
One script of a languageTraditional Chinesezh-Hant
Everyone elseLanguage picker pagex-default
A country aloneAustria– Not valid

Google's localized versions guide lists the formats: the language in ISO 639-1, an optional region in ISO 3166-1 Alpha 2. Only make a country version if it differs: prices, currency, delivery, legal text. Two identical English pages for the US and the UK compete with each other unless hreflang tells them apart.

The International SEO Checklist at a Glance

CheckAreaPriority
One URL per language versionStructureMust
ccTLD, subdomain or subfolder chosenStructureMust
No language by cookie or parameterStructureMust
Valid hreflang codesHreflangMust
Self-reference and return linksHreflangMust
Targets answer 200, self-canonicalHreflangMust
x-default on picker pagesHreflangShould
Main content fully translatedContentMust
Titles, descriptions localizedContentMust
Currency, units, addresses localContentShould
html lang matches the textContentShould
No automatic redirect by IPTechnicalMust
Visible links between versionsTechnicalMust
Canonical stays in its languageTechnicalMust
Every version in a sitemapTechnicalShould
Results tracked per marketMeasurementShould

The sections below explain each one, with the source.

Structure: One URL per Version

Google's guide to managing multi-regional and multilingual sites asks for a separate URL for each language version, rather than cookies or browser settings that change the language on one URL. Googlebot sees one version per URL, so a version that only exists behind a cookie is a version it never indexes.

Then pick where the versions live:

  • ccTLD, such as example.de: the clearest country signal, and a separate site to run for each country.
  • Subdomain, such as de.example.com: easy to set up, may be hosted elsewhere.
  • Subfolder, such as example.com/de/: easy to set up and maintain on one host.
  • URL parameters, such as ?loc=de: Google does not recommend them.

The international site structure guide compares the three in one table and helps you choose.

Hreflang: Tell Search Engines Which Version Is Which

hreflang connects the versions so search results show the right one. Declare it in the HTML head, the HTTP Link header or the XML Sitemap, and pick one method per set. The rules that break most often:

  • Every version lists itself and all the others. The same list goes on every page of the set.
  • Return links. If page A names page B, B must name A. Google's guide says tags that do not point both ways may be ignored.
  • Full URLs, with https and the host, never relative paths.
  • Healthy targets. Each target answers 200, is indexable and is its own canonical.
  • The equivalent page, not the home page of the other language.
  • Right codes. en-gb, not en-uk; never a country alone.
<link rel="alternate" hreflang="en" href="https://example.com/en/pricing/" />
<link rel="alternate" hreflang="de" href="https://example.com/de/preise/" />
<link rel="alternate" hreflang="x-default" href="https://example.com/pricing/" />

The hreflang checker guide covers every error with its fix. SEO ProCheck's hreflang and international SEO FAQ answers the edge cases.

Content: Localize, Not Just Translate

  • Translate the main content. Google warns against translating only the navigation and footer while the main text stays in one language. Keep each page in one language, without side-by-side translations.
  • Localize titles and meta descriptions. They are what people see in results. German and French text often runs longer than English, so check lengths per language.
  • Local details. Currency, prices, units, date formats, addresses and phone numbers. Google lists local addresses, phone numbers, language and currency among the signals it uses to understand a page's audience. SEO ProCheck has a check page on currency that is not localized.
  • Set html lang correctly. Google says it uses the visible text, not the lang attribute, to decide a page's language, but screen readers, browsers and other search engines read it. Make it match.
  • Local search demand. Research keywords per market. The words people search are not always the translation of your English keyword.

Technical: Redirects, Crawling and Locale-Adaptive Pages

Google documents how Googlebot meets international sites, and the facts decide several checklist items:

FactSo do this
Googlebot usually crawls from the USANo redirect by IP
It sends no Accept-Language headerNo content by browser language
It does not vary its locationDeclare every version
Auto-redirects hide versionsVisible language links
Server location is a weak signalA CDN is fine
Geo meta tags are ignoredSkip them

All six come from Google's multi-regional sites guide. Beyond those:

  • Canonicals stay within a language. A German page that names the English page as canonical tells search engines it is a duplicate, which cancels its hreflang.
  • robots.txt per host. Each subdomain and ccTLD needs its own file; the robots.txt tester guide explains why.
  • Sitemaps list every version. One sitemap per language or one with all of them; the XML sitemap checker guide has the limits.
  • Internal links per version. Each language version needs its own navigation, so its pages are not orphans reached only through hreflang.

Measurement: Track Each Market

Search Console's International Targeting report, with its country setting, was deprecated in 2022. Measure per market instead:

  • Add a Search Console property per subfolder, subdomain or ccTLD, so each market has its own reports.
  • Filter the Performance report by country, and compare clicks with the version meant for that country.
  • Watch for the wrong version ranking: French pages getting clicks in Canada while the fr-ca pages get none is a hreflang signal worth reading.
  • Compare each version's indexed page count with its sitemap.

What We Check on Our Own Site

neova.app runs in 15 languages, one subfolder each, such as /fr, /de and /pt-br, with English at the root and an x-default. Our own SEO pass on November 20, 2026 measured:

neova.app, November 20, 2026Result
Languages15
URLs in the XML Sitemaps1,358
Hreflang return links✓ Fully reciprocal
Meta descriptions cut to 160 or less1,354 pages
http:// to https://200, fixed to 301
Unknown addresses503, fixed to 404

Two lessons from it. Every hreflang tag comes from one shared list, so the return links cannot drift. And description length is a per-language job: a description that fits in English can run long once translated, so the cut had to be checked in all 15 languages.

Run the Checklist With Neova

A crawl checks most of this list at once. Neova's International category has 41 checks and reads hreflang from the HTML head and the HTTP Link header; hreflang in XML Sitemaps is not read. Crawl Subdomains Too adds the language subdomains to the same crawl. The checks behind the list:

Each flag says why it matters, how to fix it and its source. The Free plan runs every check on up to 1,000 URLs a crawl; see Features or download Neova.

Questions

What should an international SEO checklist include?

One URL per language version, a chosen structure (ccTLD, subdomain or subfolder), valid and reciprocal hreflang, fully localized content and metadata, no automatic redirects by IP, canonicals within each language, sitemaps for every version and results tracked per market.

Do I need hreflang if each country has its own ccTLD?

It still helps when two versions share a language, such as English for the US and the UK. The ccTLD tells Google the country; hreflang tells it which page replaces which.

Should I redirect visitors to their language automatically?

Google advises against it. Googlebot usually crawls from the USA without an Accept-Language header, so automatic redirects can hide versions from it. Show visible links to the other versions instead.

Does Google use the html lang attribute?

Not to decide a page's language: Google says it reads the visible text. Set html lang correctly anyway, for browsers, screen readers and other search engines.

Can I still set a target country in Search Console?

No. The International Targeting report and its country setting were deprecated in 2022. Use a ccTLD, hreflang and local content to signal the country.

Take this with you

The assistant links open with a question about this page already written.

Crawl your site with NeovaThe Free plan runs every check on Mac, Windows and Linux. No credit card required.

Keep Reading