Chapter 20 — Key Takeaways
A one-page reference. If you remember nothing else: most sites don't need this chapter; for the ones that do,
hreflang correctness lives in the relationships between pages, and localization — not translation — is what
earns the ranking.
The one idea
International SEO shows the right language and country version of your content to the right searcher. It is powerful for the sites that genuinely serve multiple markets and can maintain them — and a costly, fragile mistake for everyone else. The advanced skill is knowing which you are.
First, the honest test (§20.1)
You need international SEO only if both are true:
- Real, evidenced demand in more than one country or language, and
- You can genuinely localize and maintain a full version for each — and actually serve those customers.
Missing either → the correct deliverable is one sentence: "International SEO does not apply to us, because ___." A half-built, stale, or unserved locale is worse than none.
The two axes (don't confuse them)
| Axis | Question | Tool |
|---|---|---|
| Language | Which language does this searcher want? | hreflang (language, e.g. es) |
| Country | Which country's experience (currency, law, shipping)? | ccTLD, hreflang region (e.g. en-gb), local signals |
URL structures — one decision, expensive to reverse (§20.2)
| Structure | Example | Geo signal | Authority | Best when |
|---|---|---|---|---|
| ccTLD | example.fr |
Strongest | Split across domains (from zero each) | Real per-country presence + budget |
| Subdomain | fr.example.com |
Moderate | Somewhat separate | Infra/org reasons, not SEO |
| Subdirectory | example.com/fr/ |
Weakest (leans on hreflang) |
Consolidated on one domain | Language expansion; keep authority in one pot |
Reversing a structure later = a full migration (Ch 21). Measure twice.
hreflang — the rules that actually break people (§20.3, §20.5)
- What it does: routes the right existing version to the right searcher. What it can't: boost rankings, or rescue thin/badly-localized content. It's a routing signal, not a ranking one.
- Value format: ISO 639-1 language + optional ISO 3166-1 region, hyphen-joined (
en,en-gb,es-mx). Language-only is allowed; region-only is not. The UK isGB, neveren-uk. x-default: the fallback for unmatched searchers (a selector or global homepage).- The return-tag rule: every version references every version and itself, and every reference must be returned. Miss one → Google may ignore the pairing. It's an all-or-nothing set, not a per-page tweak.
The failure modes (memorize the fatal two)
| Failure | Fix |
|---|---|
| Canonical conflict — a version canonicals to another language → dropped from the index | Every version's canonical is self-referential |
| Missing return tag — A names B, B doesn't name A | Every version references every version + itself |
| No self-reference | Add the self-referential tag |
Invalid codes (en-uk, fr_FR, "German") |
Valid ISO codes, hyphen-joined |
href to a redirect / http:// / 404 |
Absolute, canonical, https, 200 OK URLs |
Language mismatch (tagged es, written in English) |
Tag the language the page is really in |
hreflang points across versions; canonical points at itself. Never cross the streams.
Localization ≠ translation (§20.4)
- Translation = the words. Localization = words + currency, units, examples, culture, and the local terms people actually search (fresh keyword research per market — Ch 7).
- Myth: "Just machine-translate and publish." → low quality, missed local keywords, eroded trust; Google discourages raw unreviewed output. Machine translation is a draft for a human localizer, not a product.
Geotargeting is no longer a setting (§20.6)
- The Search Console country-target setting was retired (with the International Targeting report, in 2022). A lot of still-circulating advice tells you to use a button that no longer exists.
- Country is now inferred: ccTLD >
hreflangregion > on-page/business signals (currency, address) > links. Server/IP location is essentially moot (CDNs made it uninformative).
Duplicate content across locales is (mostly) a myth (§20.7)
- Different languages ≠ duplicates — no issue at all. And duplicates are filtered, not penalized.
- Same-language regional variants (US/UK/AU English) are the only real case → fix with
hreflang+ self-referential canonicals + genuine localization. Never merge or canonicalize them together.
Rules of thumb
- Most sites should skip this chapter. Saying so is the expert move.
- hreflang is relational — validate the set with a crawler, never a single page by eye.
- Never let a plugin canonical your locales to the "main" language — it deletes them.
- Localize, don't translate. The ranking value is in the local adaptation.
- Don't chase demand you can't serve. Leads in a language you can't answer aren't a win.
What you can do today
Run the §20.1 decision tree on your site. If you don't need international SEO, write the one honest sentence
that says so and move on — you just saved months. If you do, inspect one competitor's hreflang (view-source)
and note whether it's self-referential and reciprocal; then crawl your own set with Screaming Frog (free)
and check for missing return tags and canonical conflicts.
Where this goes next
→ Chapter 21 takes on site migrations — the most dangerous operation in SEO, and the thing an international restructure becomes if you get the URL-structure decision wrong. Redirect discipline is the difference between a temporary dip and a catastrophe.