Translation vs. Localization for SEO

TL;DR — Translation changes your words into another language. LocalizationLocalization is adapting content for a specific target market — not just translating the words, but adjusting currency, formats, idioms, cultural references, local search terms, and trust signals so the experience feels native. changes the whole experience for a market — currency, dates, idioms, examples, and the actual terms people there search for. Most sites that go global translate and then wonder why they don’t rank. The answer is almost always: they translated, but they didn’t localize.

The one-sentence difference

Translation asks: “What does this say in Spanish?”

Localization asks: “What should we say to Spanish-speaking shoppers in Mexico to actually serve them?”

Translation is a linguistic act — words in, words out, meaning preserved. Localization is a market act — you adapt everything around the words so the page feels like it was made for that audience in the first place.

What localization changes that translation doesn’t

A pure translation swaps the language and stops. Localization also adjusts:

• Currency, dates, units — $ vs. €, MM/DD vs. DD/MM, miles vs. kilometers.
• Idioms and cultural references — jokes, examples, and analogies that land locally instead of reading like a dubbed movie.
• Imagery and design — photos, colors, and symbols carry different meaning in different cultures.
• The actual search terms — and this is the big one for SEO.

Why this matters for search

Search engines rank pages for the words people type. People in different markets don’t type translated versions of your keywords — they type their own words.

The classic trap is translating your keyword list. “Pants” in the US means trousers; in the UK it means underwear. Translate a keyword literally and you can end up optimizing for the wrong thing, or for a term nobody local actually searches. Sometimes there’s more search volume under a phrase you’d never guess, and sometimes the obvious translation has basically none.

Intent shifts too. The same query can be informational in one country and transactional in another. So keyword research for a market has to be done in that market — from local data and, ideally, with a native speaker — not by running your English list through a translator.

The thing most people get wrong

Adding hreflang tagsHreflang is an annotation (in HTML, HTTP headers, or XML sitemaps) that tells search engines which language and optional region a page targets, and which alternate versions exist. It only works when every page in the cluster references all the others. is not localization. HreflangHreflang is an annotation (in HTML, HTTP headers, or XML sitemaps) that tells search engines which language and optional region a page targets, and which alternate versions exist. It only works when every page in the cluster references all the others. is a signal that tells Google which version is for whom. It doesn’t make the content good. If all you’ve done is auto-translate the words and bolt on hreflang, you’ve built a cluster of thin pagesThin content is web content that provides little or no value to users. Google's spam policies name it 'thin content with little or no added value' — and it's about value per page, not word count. pointing at each other — and that’s not what wins in a competitive local market.

Want the deep version — Google’s actual policy on AI translation, the traffic Google quietly takes when you don’t localize, and when machine translation is genuinely good enough? Switch to the Advanced tab.

Test yourself: Translation vs. localization

TL;DR — Translation is linguistic conversion; localizationLocalization is adapting content for a specific target market — not just translating the words, but adjusting currency, formats, idioms, cultural references, local search terms, and trust signals so the experience feels native. adapts content, keywords, and trust signals to a market. Google evaluates scaled or automated content by whether it helps users rather than by translation technology alone. The quality bar still applies, and language is not the same as country targeting. The pragmatic stack: triage markets, do real local keyword research, localize the ones that matter, and use MTPEMachine translation (MT) is using automated systems — Google Translate, DeepL, Microsoft Translator, or an LLM — to translate a site's content into other languages. It isn't banned for SEO; publishing raw, unreviewed MT in bulk purely to rank is what Google's scaled content abuse policy targets. MT reviewed and edited by a human (MTPE) is standard practice at scale. to scale without shipping junk.

Translation is a step. Localization is a system.

I’ll borrow a framing I like from the Ahrefs localization research: translation is a step, localization is a system. Translation is the narrow linguistic task — turn these words into those words. Localization is everything around it: local keyword research, currency and formats, cultural references, imagery, legal compliance, local pricing and availability, and the local trust signals that make a page credible in a market it wasn’t born in. Transcreation sits one level beyond — recreating tone and emotion for cultural resonance — and it’s mostly a brand-copy and advertising concern, not an informational-page one.

The reason this distinction earns its own article is that almost every “our international pages don’t rank” problem traces back to it. The site translated and called it localization.

Search intent diverges by market — so keyword research can’t be translated

This is the part competitor articles wave at and rarely demonstrate. Same words, different meaning: “pants” (US trousers / UK underwear), “purse” (US handbag / UK wallet). Same concept, different volume: a term like “heated tobacco” can have effectively zero volume in one language while the locally natural phrasing pulls real search demand. Same query, different intent: informational in one country, transactional in another.

There’s even a meta-trap. Translate “SEO localization” into Spanish and you drift toward localización SEO — which a lot of people will read as local SEO, a different topic. Direct keyword translation doesn’t just lose nuance; it can land you on the wrong topic entirely.

The operational takeaway: never translate your keyword list. Research each market from its own data — per-country volumes in your keyword tool, Search ConsoleA free Google service that reports how a site performs in Google Search and surfaces problems with how Google crawls, indexes, and serves it. It's first-party data straight from Google — but you don't need it to appear in results. data segmented by country — and validate with someone who actually searches that way. Localization is keyword research from scratch, not a find-and-replace.

Google’s actual stance on AI translation (it changed)

The single most outdated thing in competitor content is the claim that machine-translated content is automatically spam. As of 2025, that’s not Google’s position.

When questions came up about Reddit scaling AI translations across 20-plus languages and millions of URLs — and seeing ranking gains after the March 2025 core update — a Google spokesperson said plainly that “our policies do not strictly define content that has been translated by AI as spam.” The scaled content abuseScaled content abuse is Google's spam policy (introduced March 2024) for generating many low-value pages primarily to manipulate search rankings rather than help users — and it applies no matter how the content is created: AI, automation, or human writers. policy does name “automated transformations” including translation, but the trigger is value, not method: it’s aimed at “creating large amounts of unoriginal content that provides little to no value to users.” High-quality AI translation and bulk junk translation are treated differently because the policy was never about the tool.

Two corroborating moves:

• The robots.txtA plain-text file at the root of a host that tells crawlers which URLs they may and may not request. It controls crawling, not indexing — a blocked URL can still be indexed if it's linked from elsewhere. guidance removal (2025). Google removed its longstanding advice to block auto-translated pages via robots.txt, calling it a docs-only change with no behavior change. The old advice predated the scaled-content-abuse framing; once policy evaluates content by user value rather than creation method, “block all machine-translated pages” stopped being the right blanket rule. The right tool for a specific low-quality translated page is page-level noindex, not a sitewide robots.txt block.
• The Quality Rater Guidelines don’t treat machine translation as categorically low quality either — they explicitly recognize effort can go into “building systems that power a webpage, such as the creation of a page that offers machine translation as a service to users.” But the broader E-E-A-T framework still applies: translated content with no local experience or authority signals scores lower.

Here’s my contrarian caveat, and it’s the one that actually matters in practice: the policy permits good AI translation, but site owners systematically overrate their own content. “AI translation is allowed” is not “my AI-translated pages are good.” Glenn Gabe’s reporting on the Reddit case lands on the same nuance — scaling genuinely helpful content with AI appears fine; scaling mediocre content with AI is still a spam risk you’ve just made cheaper to commit. The policy didn’t lower the quality bar; it moved the judgment from how you made the page to whether it’s worth indexingStoring a crawled page in the search index so it can appear in results. Crawled is not the same as indexed — Google selects what to keep, and indexing isn't guaranteed..

Quality is the gate Google’s people keep pointing at

The reps have been consistent that the bar is helpfulness, not the translation method. John Mueller has framed the goal as a good localization being “much more than just a translation of words and sentences” and pushed site owners to have a native reviewer make sure the content is actually helpful. Martin Splitt put the warning more bluntly: instead of “lackluster translated pages,” build content that’s genuinely useful to each audience — and don’t over-internationalize into markets you can’t support properly.

That last point is strategy, not just quality: pick the locales that matter and do them well, rather than auto-spraying 30 languages thin.

Language is not country targeting

A trap worth calling out explicitly: translating into a language does not target a country. Gary Illyes said it directly — “the language is absolutely not a tell for what country you are targeting.” Spanish doesn’t mean Spain, or Mexico, or Colombia. If you need market-level targeting, that’s hreflangHreflang is an annotation (in HTML, HTTP headers, or XML sitemaps) that tells search engines which language and optional region a page targets, and which alternate versions exist. It only works when every page in the cluster references all the others. language+country (es-mx vs. es-es), on-page signals like local currency and addresses, and local links — not the language alone. Google also determines a page’s language from its visible content, not the lang attribute or the URL, so half-translated boilerplate-only pages confuse it (and Google explicitly warns that translating only boilerplate while leaving the body in one language creates a bad experience).

The traffic threat most people aren’t thinking about

Here’s the angle almost nobody covers, and it’s the one I’d lead with if I were trying to scare a stakeholder into funding localization: if you don’t create local-language pages, Google may auto-translate your content onto its own translate.goog subdomain and serve that to international users — capturing the search traffic that should’ve been yours. Ahrefs’ analysis put an estimated 377M monthly organic visits flowing through that subdomain, with markets like India, Indonesia, and Brazil most affected.

My take on it, which I’ll stand behind: Google has talked about improving the hreflangHreflang is an annotation (in HTML, HTTP headers, or XML sitemaps) that tells search engines which language and optional region a page targets, and which alternate versions exist. It only works when every page in the cluster references all the others. system for years; instead of continuing to help creators translate and localize, it has effectively decided to claim a chunk of that traffic as its own. You don’t beat that by hoping — you beat it by shipping genuine native-language pages (even a lean 300-word MVP is a start) with proper hreflang so your URLs are the ones indexed for the market.

Machine translation, MTPE, and human translation

For SEO content meant to rank, the three tiers trade quality, speed, and cost:

• Raw machine translation (DeepL, Google Translate) — fastest and cheapest, highest quality risk. DeepL tends to edge out Google Translate on European language pairs; Google Translate covers more languages, and its 2025 Gemini integration improved idiom and context handling. Both got dramatically better, and neither is publish-ready for competitive SEO on its own.
• MTPE — machine translation post-editing — the middle path most language service companies actually run. Machine translation produces the first draft; a human linguist reviews and corrects it. Light MTPE fixes readability and obvious errors; full MTPE brings it up to human-translation quality. This is how you scale across markets without shipping the “lackluster translated pages” Splitt warned about.
• Human translation (or transcreation) — highest quality, slowest, most expensive. Reserve it for your highest-value pages and brand-critical copy.

Important: none of these tiers, on their own, localizes. MTPE still translates your existing keywords and examples. Real localization layers local keyword research, local examples, and local trust signals on top — the translation tier just decides how you produce the words once you know what the words should be.

How much human review any of this needs isn’t just a function of page value — scale it to risk. Factual claims (numbers, medical, financial), legal or regulatory language, brand-critical copy, culturally sensitive topics, and anything that could cause real harm to a user if mistranslated all deserve human review regardless of which tier you’re running; low-stakes reference content can tolerate a lighter touch. And none of this — not even full human translation — is a substitute for jurisdiction-specific legal review where consumer-protection, accessibilityWeb accessibility means designing sites so people with disabilities can use them, per the W3C's WCAG guidelines. It overlaps with SEO in specific, checkable ways — alt text, heading structure, descriptive link text, captions, and page speed all serve both audiences — but Google has said accessibility itself is not a ranking factor, and most WCAG success criteria (keyboard focus order, ARIA live regions, form labels) have no SEO effect at all., labeling, or privacy rules are in play. That’s outside SEO entirely and needs its own sign-off; a clean translation of non-compliant legal copy is still non-compliant.

Local E-E-A-T: authority doesn’t travel

A strong global brand does not automatically rank in a new market. Motoko Hunt’s work on the “global E-E-A-T gap” is the clearest framing I’ve seen: global reputation doesn’t equal local trust. A domestic competitor with local media backlinks, region-specific certifications, local reviews, and consistent local schema can beat a much larger global brand whose international pages show only US reviews and a translated template. Localization, done right, includes building those local signals — bylines from local authors, links from local authoritative sources, and structured dataStructured data is a standardized way of labeling page content (using the schema.org vocabulary in JSON-LD, Microdata, or RDFa) so search engines can understand its meaning. It's not a direct ranking factor — its value is rich results and entity understanding. that reflects the market — not just translating the body copy.

What “translation-only” is actually fine for

I’m not arguing you must fully localize everything. Translation-only is a reasonable starting point for very low-traffic target markets, purely informational/reference content with little local nuance, content you can clearly mark as machine-translated, or as a temporary bridge while you stand up a real localization workflow. The mistake isn’t translating — it’s translating and calling it done.

Where this fits

This is the fundamentals piece on the why. The how — URL structureURL structure is how the parts of a web address — scheme, domain, path, query string, and fragment — are organized and formatted. It mostly affects crawling, usability, and how engines understand a page, not rankings directly. (ccTLDCountry-code top-level domain like .de or .co.uk — a strong geotargeting signal. vs. subdomain vs. subdirectory), hreflang mechanics and language-vs-country targeting, and avoiding IP/cookie redirectsA redirect sends browsers and crawlers from a requested URL to a different one. An HTTP redirect specifically is a 3xx status code paired with a Location header; meta refresh and JavaScript redirects achieve a similar navigation without being a 3xx response themselves. Permanent redirects (301/308) are Google's signal the target should be canonical; temporary ones (302/303/307) aren't. that hide localized content from bots — lives in the rest of the international SEOInternational SEO is the practice of optimizing a site so search engines understand which countries and/or languages it targets, and serve the right version to each user. It spans URL structure, hreflang, and on-page localization. cluster.

AI summary

A condensed take on the Advanced version:

• Translation ≠ localizationLocalization is adapting content for a specific target market — not just translating the words, but adjusting currency, formats, idioms, cultural references, local search terms, and trust signals so the experience feels native.. Translation converts words; localization adapts the whole experience — keywords, currency/formats, culture, imagery, and local trust signals — for a market. “Translation is a step; localization is a system.”
• Keyword research can’t be translated. Same words mean different things by market (“pants,” “purse”), volume shifts, and intent flips (informational vs. transactional). Research each market from its own data, with a native speaker.
• AI translation isn’t categorically spam (Google, 2025). The scaled content abuse policy targets value, not method. Google also removed its old robots.txtA plain-text file at the root of a host that tells crawlers which URLs they may and may not request. It controls crawling, not indexing — a blocked URL can still be indexed if it's linked from elsewhere. advice to block auto-translated pages. Caveat: owners overrate their own content, so “allowed” ≠ “good.”
• Quality is the gate. Mueller: a good localization is “much more than just a translation.” Splitt: avoid “lackluster translated pages,” and don’t over-internationalize.
• Language ≠ country targeting (Illyes). Spanish doesn’t mean Spain — use hreflangHreflang is an annotation (in HTML, HTTP headers, or XML sitemaps) that tells search engines which language and optional region a page targets, and which alternate versions exist. It only works when every page in the cluster references all the others. language+country, local on-page signals, and local links.
• The traffic threat: if you don’t localize, Google may auto-translate your pages onto translate.goog and keep the traffic (~377M monthly visits flow through it). Counter it with native pages + hreflangHreflang is an annotation (in HTML, HTTP headers, or XML sitemaps) that tells search engines which language and optional region a page targets, and which alternate versions exist. It only works when every page in the cluster references all the others..
• Production tiers: raw MT (fast, risky) → MTPEMachine translation (MT) is using automated systems — Google Translate, DeepL, Microsoft Translator, or an LLM — to translate a site's content into other languages. It isn't banned for SEO; publishing raw, unreviewed MT in bulk purely to rank is what Google's scaled content abuse policy targets. MT reviewed and edited by a human (MTPE) is standard practice at scale. (scalable middle path) → human translation/transcreation (highest value pages). None of them localize on their own.
• Authority doesn’t travel. Local E-E-A-T — local authors, links, reviews, certifications, schema — is part of localization, not an afterthought.

Official documentation

Primary-source documentation on translated and localized content.

Google

• Spam policies for Google web search — the scaled content abuseScaled content abuse is Google's spam policy (introduced March 2024) for generating many low-value pages primarily to manipulate search rankings rather than help users — and it applies no matter how the content is created: AI, automation, or human writers. section names “automated transformations like synonymizing, translating, or other obfuscation techniques” where “little value is provided to users.” The judgment is value, not method.
• Using AI-generated content — Google’s helpful-content-first stance, which the translation guidance now mirrors.
• Managing multi-regional and multilingual sites — warns against translating only boilerplate, and notes Google uses visible content (not lang attributes or the URL) to detect language.
• International SEO overview — locale-adaptive pages and how Google may not crawl/indexStoring a crawled page in the search index so it can appear in results. Crawled is not the same as indexed — Google selects what to keep, and indexing isn't guaranteed./rank all locale variants.
• Localized versions of your pages — hreflangHreflang is an annotation (in HTML, HTTP headers, or XML sitemaps) that tells search engines which language and optional region a page targets, and which alternate versions exist. It only works when every page in the cluster references all the others. implementation for language/region variants.
• Search Quality Rater Guidelines (PDF) — recognizes effort in translation and in “building systems that power a webpage, such as … machine translation as a service”; E-E-A-T still applies.

Bing / Microsoft

• Going international: considerations for your global site — Bing’s international signals (ccTLDCountry-code top-level domain like .de or .co.uk — a strong geotargeting signal., host location, body-text language, locale of linking pages) and its warnings against cookie/JS/HTTP_ACCEPT_LANGUAGE-based localizationLocalization is adapting content for a specific target market — not just translating the words, but adjusting currency, formats, idioms, cultural references, local search terms, and trust signals so the experience feels native. that crawlersA crawler — also called a spider or bot — is an automated program that fetches web pages, extracts their links, and queues new URLs to visit. Search engines use crawlers to discover and download content for their index. can’t see.
• Bing Webmaster Guidelines — Bing’s general content-quality expectations, which auto-translated contentMachine translation (MT) is using automated systems — Google Translate, DeepL, Microsoft Translator, or an LLM — to translate a site's content into other languages. It isn't banned for SEO; publishing raw, unreviewed MT in bulk purely to rank is what Google's scaled content abuse policy targets. MT reviewed and edited by a human (MTPE) is standard practice at scale. without human review can fall foul of.

Quotes from the source

On-the-record statements from Google. Where a quote reached me through secondary reporting rather than a directly checkable source page, that’s noted.

Google — AI translation is not categorically spam

• “While we don’t comment on the status of specific sites or pages, our policies do not strictly define content that has been translated by AI as spam. Our scaled content abuse policyScaled content abuse is Google's spam policy (introduced March 2024) for generating many low-value pages primarily to manipulate search rankings rather than help users — and it applies no matter how the content is created: AI, automation, or human writers. mentions automated transformations, including translations, as part of the overall warning against creating large amounts of unoriginal content that provides little to no value to users.” — Google spokesperson, June 2025. Read the coverage

Google — the scaled content abuseScaled content abuse is Google's spam policy (introduced March 2024) for generating many low-value pages primarily to manipulate search rankings rather than help users — and it applies no matter how the content is created: AI, automation, or human writers. policy

• “Scraping feeds, search results, or other content to generate many pages (including through automated transformations like synonymizing, translating, or other obfuscation techniques), where little value is provided to users.” — Google Search Central docs. Jump to quote

John Mueller, Google — localizationLocalization is adapting content for a specific target market — not just translating the words, but adjusting currency, formats, idioms, cultural references, local search terms, and trust signals so the experience feels native. is more than translation

• “A good localization is much more than just a translation of words and sentences, so I would definitely encourage you to go beyond the minimal bar if you want users in other regions to cherish your site.” Read the coverage
• “You should ensure that a human native in those languages reviews (and perhaps fixes) the translations to ensure that the content is actually helpful for users.” Read the coverage

Martin Splitt, Google — avoid lackluster translated pages

• “Instead of lackluster translated pages, make sure you have content that is useful to the different audiences in the countries you care about and make sure they have a great experience on each of your language variations.” Read the coverage

Gary Illyes, Google — language is not country targeting

• “The language is absolutely not a tell for what country you are targeting.” Read the coverage

Should you translate, localize, or transcreate?

The question isn’t “translation or localizationLocalization is adapting content for a specific target market — not just translating the words, but adjusting currency, formats, idioms, cultural references, local search terms, and trust signals so the experience feels native.?” in the abstract — it’s “how much adaptation does this content, in this market, justify?” Work it in this order:

1. Content type — what is the page for? Reference/informational content with little local nuance tolerates lighter adaptation. Money pages (commercial, conversion-critical) and brand copy demand the most.

2. Market priority — does this market matter? Triage hard. Splitt’s advice — don’t over-internationalize — is the rule here. Rank markets on real signals (revenue/billing, interface-language usage, brand search, market size, competition) and only invest where you’ll commit. A long tail of thin, auto-translated markets is a liability, not coverage.

3. Budget and scale — how many pages, how fast? This decides your production tier, not whether to localize. Localization strategy (local keywords, local signals) is separate from how you generate the words.

4. Quality tier — pick the production method. Match the method to the value of the page and market, then layer localization on top regardless of tier.

Quality tier alone doesn’t decide whether a page ranks — it just decides whether the words clear the bar. A perfect human translation of the wrong keywords, or one Google can’t discover because of a canonical or hreflangHreflang is an annotation (in HTML, HTTP headers, or XML sitemaps) that tells search engines which language and optional region a page targets, and which alternate versions exist. It only works when every page in the cluster references all the others. mistake, still won’t rank. Ranking also needs the local keyword research from the section above and the technical setup (separate crawlable URLs, correct canonical/indexability, reciprocal hreflangIf page A lists page B as an alternate, B must list A back — or Google ignores the pair., and a way for users to switch) covered in the rest of the international SEOInternational SEO is the practice of optimizing a site so search engines understand which countries and/or languages it targets, and serve the right version to each user. It spans URL structure, hreflang, and on-page localization. cluster.

Is machine translation “good enough”? Yes — as a draft. Google’s policy permits AI-translated content judged on value, so raw MT is a legitimate starting point. It’s “good enough” to ship only when (a) the market is low-priority, (b) the content has little local nuance, and (c) you’re honest that owners overrate their own output. For anything you actually want to compete in a competitive market, MTPE is the production floor — and real localization (local keywords + local signals + correct technical setup) sits on top of whichever tier you chose.

Transcreation vs. localization vs. translation at a glance

Localization cheat sheet — what actually changes

Translation changes the words. LocalizationLocalization is adapting content for a specific target market — not just translating the words, but adjusting currency, formats, idioms, cultural references, local search terms, and trust signals so the experience feels native. changes all of this:

Policy quick facts (2025–2026)

• AI-translated content is not categorically spam — judged on user value (Google, 2025).
• Google removed its old robots.txtA plain-text file at the root of a host that tells crawlers which URLs they may and may not request. It controls crawling, not indexing — a blocked URL can still be indexed if it's linked from elsewhere. advice to block auto-translated pages — use page-level noindex for specific low-quality pages instead.
• Translated content is not duplicate contentThe same or very similar primary content reachable at more than one URL. There's no general duplicate content penalty — the real costs are possible signal dilution, the wrong URL getting chosen, and less-efficient crawling. — it’s different words; hreflangHreflang is an annotation (in HTML, HTTP headers, or XML sitemaps) that tells search engines which language and optional region a page targets, and which alternate versions exist. It only works when every page in the cluster references all the others. marks the variants.
• Language ≠ country. Spanish doesn’t target Spain; use hreflangHreflang is an annotation (in HTML, HTTP headers, or XML sitemaps) that tells search engines which language and optional region a page targets, and which alternate versions exist. It only works when every page in the cluster references all the others. language+country and local signals.
• Google detects page language from visible content, not the lang attribute or URL.
• If you don’t localize, Google may auto-translate your pages onto translate.goog and keep the traffic (~377M monthly visits flow through it).

Production tiers, shortest version: raw MT (draft) → light MTPEMachine translation (MT) is using automated systems — Google Translate, DeepL, Microsoft Translator, or an LLM — to translate a site's content into other languages. It isn't banned for SEO; publishing raw, unreviewed MT in bulk purely to rank is what Google's scaled content abuse policy targets. MT reviewed and edited by a human (MTPE) is standard practice at scale. → full MTPE → human translation → transcreation. Pick by page value; localize on top regardless.

Localization

Localization is adapting content for a specific target market — not just translating the words, but adjusting currency, formats, idioms, cultural references, local search terms, and trust signals so the experience feels native.

Related: Multilingual SEO, International SEO, Hreflang

Localization

LocalizationLocalization is adapting content for a specific target market — not just translating the words, but adjusting currency, formats, idioms, cultural references, local search terms, and trust signals so the experience feels native. is the process of adapting content and the surrounding experience for a particular target market. Translation converts text from one language to another — words in, words out. Localization goes further: it adjusts currency, date and number formats, units, imagery, cultural references, idioms, legal requirements, and — critically for SEO — the actual terms local people search for. The working shorthand is that translation is a step and localization is a system.

The difference matters because search behavior shifts by market even within the same language. A direct keyword translation often misses how locals search, and the same query can carry different intent (or a different meaning entirely) in another country. Localized content also carries local E-E-A-T signals — native authors, regional reviews, local links and certifications — that a translated-only page lacks.

A related concept, transcreation, goes one step beyond localization: it recreates the tone, emotion, and intent of content for cultural resonance, and is usually reserved for brand copy and advertising rather than informational pages.

Related: Multilingual SEO, International SEO, Hreflang

Changelog