Global SEO: International Checklist, Hreflang, and Multi-Market Targeting

Global SEO is the practice of making a website rank in more than one country or language. It covers three decisions: which markets to target, how to structure URLs for them, and how to tell search engines which version belongs to which audience. Hreflang handles the last part.

Most of the international SEO work I get asked to fix traces back to a company that translated its site into six languages before checking whether anyone in those markets was searching.

Key takeaways

• Pick markets on search demand: existing customers found you anyway. Demand tells you where new ones are looking.
• Subdirectories beat subdomains and ccTLDs for most SaaS: they inherit the authority you have already built.
• Hreflang must be reciprocal: if page A points to page B, page B has to point back, or search engines ignore both.
• Research keywords natively in each market: literal translations of your English terms tend to rank for phrases nobody uses.
• Translation cost is the usual blocker: we built a WordPress plugin that lets WPML run against a cheaper translation API, which changes the economics of multi-language sites.
• Audit before expanding: a broken hreflang setup across six languages is six times the problem.

What global SEO is

Global SEO covers two related problems that people often merge. International SEO targets countries, multilingual SEO targets languages.

They overlap, and each needs its own decisions.

A company selling into Germany, Austria and Switzerland has one language and three markets. A company selling into Canada has one market and two languages.

Getting this distinction right early determines your URL structure, and URL structure is the decision that is expensive to reverse.

Choosing a URL structure

You have three options and the choice is mostly settled for SaaS.

• Subdirectories (example.com/de/): inherit your existing domain authority, simplest to maintain, and the default recommendation for almost every SaaS company.
• Subdomains (de.example.com): treated as more separate, so authority transfers less readily. Worth it when markets need genuinely separate infrastructure.
• ccTLDs (example.de): strongest local signal and the most expensive path, because each domain builds authority from zero. Justified when local trust genuinely drives conversion, which is rarer in B2B software than in retail.

Unless you have a specific reason, use subdirectories. The authority argument is decisive for companies that have spent years building one domain.

The international SEO checklist

• Validate demand per market: search volume in the local language for your category, researched natively.
• Choose the structure once: subdirectory, subdomain or ccTLD, and commit.
• Implement reciprocal hreflang across every language version including a self-reference.
• Add an x-default for users whose language you do not serve.
• Localise keywords natively rather than translating the English set.
• Keep canonical tags self-referencing within each language version, never pointing across languages.
• Avoid automatic IP redirects: they block crawlers and frustrate users. Offer a language switcher instead.
• Build local links in each market, because authority is partly market-specific.

How to set up hreflang

Hreflang tags tell search engines which language and region each version of a page serves, so the right one appears in the right market.

You can implement it three ways: link tags in the head, HTTP headers for non-HTML files, or an XML sitemap. The sitemap method scales best on large multi-language sites and keeps the markup out of your templates.

The format is language code, optionally a region code: en, en-GB, de-CH. Language is required, region is optional, and the order is not interchangeable.

Four mistakes cause most broken implementations:

• Missing return tags: every page in the set must reference every other page and itself. One-directional hreflang is ignored entirely.
• Wrong codes: using uk for the United Kingdom rather than gb, or jp instead of ja for Japanese.
• Conflicting canonicals: pointing the German page’s canonical at the English version cancels the hreflang.
• Pointing at redirects or 404s: every URL in the set must return a 200.

Search Console’s International Targeting report surfaces most of these, and it is the first place I look on an inherited setup.

Running WPML without the translation bill

WPML is the standard multilingual plugin for WordPress, and for most sites it works well. The cost problem is the per-word translation credits on top of it once you are maintaining several languages across a content library that keeps growing.

We built a WordPress plugin that lets WPML run against a cheaper translation API instead of the default options, which changes the running cost of a multi-language site substantially.

The quality tradeoff is smaller than people expect for documentation and knowledge base content, and larger than people expect for landing pages, where the copy is doing persuasion rather than explanation.

The approach I recommend is machine translation for the long tail, human review for the pages that convert.

International keyword research

Keywords do not translate. The literal translation of your best English term is frequently not what people in that market type.

Research each market in its own language: pull the local search volumes, check what the local competitors rank for, and confirm the term with someone who speaks it natively.

English loanwords complicate this in technical categories. German developers often search the English term. Your German keyword set may be half English, and translating it fully would lose you the traffic.

This is the step that gets skipped when translation is handed to a vendor with no SEO brief.

Running an international SEO audit

An international audit adds four checks to a standard one.

• Hreflang validity: reciprocity, correct codes, 200 status on every referenced URL, self-reference present.
• Indexation per market: how many pages are indexed in each language version, which surfaces structural problems quickly.
• Cannibalisation across languages: the English page ranking in a market where a local version exists, usually a canonical or hreflang conflict.
• Local performance: rankings and traffic per country, since a version can be technically perfect and commercially pointless.

Start with indexation. If the German subdirectory has forty pages indexed out of four hundred, nothing downstream matters until that is fixed.

Cross-cultural considerations

The technical layer gets a page shown. Whether it converts depends on things hreflang cannot express.

Currency, date formats, payment methods, legal and compliance references, and the level of directness expected in sales copy all vary by market. A German B2B buyer expects more specification detail than a US one. A Japanese landing page that mirrors US urgency reads as aggressive.

These factors decide whether the rankings are worth having.

Final thoughts

International SEO fails commercially far more often than it fails technically.

Validate demand before translating anything, choose subdirectories unless you have a specific reason not to, get hreflang reciprocal, and spend your translation budget on the pages that convert rather than spreading it evenly.

A site in three languages that all earn is worth more than one in nine that do not.