Chapter 20 — Quiz

Twenty-four self-check questions: sixteen multiple choice, then eight short answer. Answer them before you open the key at the bottom. This quiz tests the "do you need it?" judgment, the URL-structure trade-offs, the return-tag rule, and the failure modes that make hreflang break silently.

Part 1 — Multiple choice

Q1. International SEO addresses two independent axes. They are: - A. Speed and stability - B. Language and country - C. Links and content - D. Crawling and indexing

Q2. Which URL structure gives the strongest geographic signal but splits your authority across separate domains? - A. Subdirectory (example.com/fr/) - B. Subdomain (fr.example.com) - C. ccTLD (example.fr) - D. URL parameter (example.com?lang=fr)

Q3. Which structure consolidates authority on one domain but relies on hreflang for its geographic signal? - A. ccTLD - B. Subdomain - C. Subdirectory - D. Separate domain per language

Q4. hreflang is best described as: - A. A ranking booster that lifts you into new markets - B. A routing signal that shows the right existing version to the right searcher - C. A way to avoid a duplicate-content penalty - D. A Google Search Console setting

Q5. The return-tag rule says: - A. Every page must link back to the homepage - B. If page A references page B via hreflang, page B must reference A — and every page references itself - C. You must return to Search Console monthly to renew hreflang - D. Only the x-default page needs reciprocal tags

Q6. In hreflang="en-gb", gb is: - A. A language code - B. The region code (ISO 3166-1) for the United Kingdom - C. An invalid value — it should be uk - D. A currency code

Q7. The common error en-uk is wrong because: - A. en is not a valid language code - B. The region code for the United Kingdom is GB, not UK - C. You cannot combine a language and a region - D. It should use an underscore: en_uk

Q8. x-default marks: - A. The default language of the whole internet - B. The fallback page shown when no language/region version is a good match - C. The page Google ranks first - D. A page that should not be indexed

Q9. The deadliest hreflang failure — the one that can remove a locale from the index entirely — is: - A. A missing x-default - B. Using HTML tags instead of a sitemap - C. A canonical tag pointing to a different language version - D. Listing versions in the wrong order

Q10. In a correct hreflang set, each version's canonical tag should point to: - A. The main/English version - B. The x-default page - C. Itself (self-referential) - D. The homepage

Q11. Localization differs from translation in that it also adapts: - A. Only the grammar - B. Currency, units, examples, local search terms, and cultural context — not just the words - C. Nothing; they are synonyms - D. Only the page title

Q12. Publishing raw, unreviewed machine-translated pages is discouraged mainly because: - A. It is illegal - B. It produces low-quality content that misses local search terms and undermines trust - C. Google cannot read translated text - D. It always triggers a manual action

Q13. How do you now set a target country for a generic (.com) site in Google Search Console? - A. In the International Targeting report - B. In the Sitemaps report - C. You can't — that setting was retired; Google infers country from other signals - D. In the URL Inspection tool

Q14. Which is no longer a meaningful geotargeting signal, according to the chapter? - A. ccTLD - B. hreflang region annotations - C. Server / IP location - D. Local currency and address on the page

Q15. Two different languages (e.g., German and French versions) of the same page are, to Google: - A. Duplicate content that risks a penalty - B. Entirely different content — not a duplicate-content issue at all - C. Automatically merged into one - D. Ignored unless you disavow one

Q16. For same-language regional variants (US/UK/AU English) with near-identical text, the correct approach is to: - A. Canonicalize them all to one master page - B. Delete all but one - C. Use hreflang + self-referential canonicals, and genuinely localize each - D. Block the duplicates in robots.txt

Part 2 — Short answer

Q17. Give the honest test from §20.1 for whether a site needs international SEO at all. Name the two conditions that both have to be true.

Q18. State what hreflang can do and what it cannot do, in one sentence each.

Q19. Explain the return-tag rule and why it makes hreflang an "all-or-nothing set" rather than a per-page tweak.

Q20. A team translated its site into Spanish, added correct hreflang, and got almost no Spanish traffic. Give two reasons rooted in localization (not hreflang) that could explain it.

Q21. Explain the canonical conflict: what two signals contradict each other, which one usually wins, and what happens to the page as a result.

Q22. Why is "just host your site on a server in the target country to rank there" outdated advice?

Q23. State the myth this chapter is required to bust about duplicate content across locales, and give the one place the concern has a grain of truth.

Q24. Rivertown serves one metro and must reach every customer by truck. In two sentences, explain why international SEO does not apply — and name the one narrow exception and how you would handle it.

Answer key (try every question first) **Part 1 — Multiple choice** 1. **B** — Language and country are the two independent axes. 2. **C** — A ccTLD is the strongest geo signal but splits authority across separate domains. 3. **C** — A subdirectory consolidates authority on one domain and relies on `hreflang` for geo. 4. **B** — `hreflang` routes the right existing version to the right searcher; it is not a ranking booster. 5. **B** — Reciprocal references, and every page references itself. 6. **B** — `gb` is the ISO 3166-1 region code for the United Kingdom. 7. **B** — The UK's region code is `GB`; `en-uk` is a silent, invalid error. 8. **B** — The fallback shown when no language/region version matches (often a selector or global homepage). 9. **C** — A canonical pointing to a different language version tells Google the page is a duplicate to drop. 10. **C** — Self-referential; each version is the master of its own content. 11. **B** — Currency, units, examples, local search terms, culture — the whole experience, not just words. 12. **B** — Low quality, missed local search terms, and eroded trust (and Google's guidance discourages it). 13. **C** — The setting was retired (with the International Targeting report, in 2022); Google now infers it. 14. **C** — Server/IP location is now largely moot (global CDNs made it uninformative). 15. **B** — Different languages are different content; no duplicate-content issue exists between them. 16. **C** — `hreflang` + self-referential canonicals + real localization; never merge or block them. **Part 2 — Short answer** 17. You need international SEO only if **both** are true: (1) you have real customers or clear, evidenced **demand** in more than one country or language, **and** (2) you can genuinely **localize and maintain** a full version for each (translate well, keep it current, and actually serve those customers). Missing either, the honest answer is "not yet," because a half-built, stale, or unserved locale is worse than none. 18. **Can:** get the correct existing language/region version of your page shown to the right searcher (right currency, right language), reducing wrong-version bounces. **Cannot:** make you rank where you otherwise wouldn't — it routes among your own alternates and cannot rescue thin or badly localized content. 19. Every version must reference every other version *and itself*, and every reference must be *returned* by the page it points to; a missing return tag means Google may discard that pairing. Because the correctness lives in the *relationships*, adding or changing one locale means updating *every* page in the set — one forgotten return tag breaks a pair, so it is all-or-nothing, not a per-page edit. 20. (1) **No local keyword research** — the pages target literal translations of English keywords, not the phrases Spanish speakers actually search, so they may chase terms with little demand. (2) **Quality/trust** — unreviewed machine translation reads as unnatural to native speakers and can be treated as thin, low-value content that neither engages nor deserves to rank. `hreflang` only routes; it can't make a bad page deserve to rank. 21. The **`hreflang`** annotation says "I am a distinct version, show me to my audience," while a **canonical** pointing at another language says "I am a duplicate of that page, index it instead." They contradict; the **canonical usually wins**, so the localized page is dropped from the index and shown to no one. Fix: self-referential canonical on every version. 22. Because content delivery networks (CDNs) now serve sites from servers all over the world, so physical server location tells Google almost nothing about who the content is *for*; Google has said it does not rely on it, and geotargeting comes from ccTLD, `hreflang`, on-page/business signals, and links instead. 23. Myth: **"Publishing similar content across languages/regions causes a duplicate-content penalty."** It is entirely unfounded between *different languages* (they aren't duplicates) and there is no punitive penalty anyway (duplicates are *filtered*, not penalized). The grain of truth is *same-language regional variants* (US/UK/AU English) with near-identical text, which can be filtered — remedied by `hreflang` + self- referential canonicals + genuine localization, never by merging them. 24. Rivertown's customers must be within truck range of one metro, so there is no second country (or second-country customer it could serve) — the geographic machinery of international SEO has nothing to target. The one narrow exception is *language*: if a meaningful share of the **local** market preferred Spanish, the lightest correct response is Spanish versions of the top pages in a `/es/` subdirectory with `es`/`en` `hreflang`, self-referential canonicals, and human localization by a bilingual technician — only if call-log evidence shows the demand is real.