Translation changes language. Localisation adapts an experience to a market. SEO requires the second decision before the first: is there a defined audience the organisation can serve, and what must change for the page to be accurate and useful there?

More language versions are not automatically more opportunity. Every version creates research, legal, product, support and maintenance obligations.

Decide whether the market is real

Before translating, verify:

  • relevant demand in the target language and country;
  • product, service or public-information availability;
  • local terminology and competing solutions;
  • pricing, currency, tax and delivery differences;
  • legal, regulatory or accessibility requirements;
  • local support and customer-service capability;
  • the organisation’s ability to maintain the content.

Search volume alone is insufficient. A global software company may be able to serve Spanish-speaking customers in several countries, while a regulated service may need a separate experience for each jurisdiction.

Choose among translation, localisation and new creation

Translate

Use a faithful translation when the task, facts, product and audience expectations are materially equivalent. Examples may include stable documentation or a universal product feature.

Localize

Adapt the page when terminology, examples, proof, units, currency, imagery, support routes or decision factors change. Most commercial landing pages require this level.

Create a new page

Create market-specific content when the underlying task, regulation, offering or search landscape is different. Forcing a translation can produce an inaccurate equivalent.

Do not publish

Do not create a version when the organisation cannot serve the market, verify the claims or maintain the page. A language selector is a commitment, not a design feature.

Research language in context

Native speakers use different terminology across countries and industries. Research store, site and search data by locale. Interview local sales, support or subject experts. Review result pages and customer questions.

Create a terminology guide that records:

  • preferred product and category names;
  • prohibited or misleading terms;
  • formal and informal variants;
  • local units, date and number formats;
  • legal phrases that require exact review;
  • brand terms that should not be translated;
  • approved calls to action.

Machine translation can accelerate a draft, but it does not decide market fit or verify legal and product accuracy. A qualified reviewer needs context, not just a spreadsheet of isolated strings.

Use separate, stable URLs

Google recommends different URLs for different language versions and advises against automatically redirecting people based only on language assumptions. Its international guidance also recommends making the language obvious in visible content rather than relying on code-level attributes alone. Review Google’s multi-regional and multilingual site guidance.

Common URL patterns include:

  • country-code domains, such as brand.fr;
  • subdomains, such as fr.brand.test;
  • subdirectories, such as brand.test/fr/.

The best structure is the one the organisation can operate consistently. Subdirectories often make shared governance easier, while country domains can provide clear market separation but increase operating overhead.

Avoid changing language at the same URL based solely on cookies or browser settings. Search systems and users need stable addresses they can link to, revisit and share.

Implement hreflang for true equivalents

Hreflang helps search systems understand alternate language or regional versions. It does not improve weak content and does not replace localisation.

Each equivalent set should:

  • use valid language or language-region codes;
  • reference every alternate, including itself;
  • be reciprocal across the set;
  • point only to canonical, indexable, successful URLs;
  • remain consistent across HTML, sitemap or header implementation;
  • use x-default only when a real default or selector page exists.

Google’s localized-version documentation explains the supported methods and return-link requirement.

Do not place pages in the same hreflang cluster merely because they are related. They should serve substantially the same purpose for different audiences.

Use canonicals within the locale

An indexable translated or localized page normally uses a self-referencing canonical. Canonicalizing every language page to the English version asks search systems to treat the local pages as duplicates and can undermine their discovery.

Canonicals and hreflang solve different problems:

  • canonical signals the preferred URL among duplicate or near-duplicate candidates;
  • hreflang signals equivalent versions for language or regional audiences.

When regional pages use the same language and are nearly identical, canonical strategy needs particular care. Consolidate pages that have no material market difference instead of maintaining artificial variants.

Localize the whole decision path

A translated article that sends users to an English-only checkout or unsupported contact team creates a broken journey. Review:

  • navigation and internal links;
  • product availability and inventory;
  • prices, payments and taxes;
  • forms and validation messages;
  • account and checkout flows;
  • documentation and support;
  • legal and privacy notices;
  • confirmation emails and transactional messages.

Make the language switcher easy to find and keep users on the equivalent page when one exists. If there is no equivalent, explain the fallback rather than silently sending everyone to the homepage.

Measure each market separately

Track:

  • relevant discovery by locale and country;
  • landing-page and query groups;
  • completion or conversion rate;
  • use of language switching;
  • support and quality issues;
  • untranslated or inconsistent interface strings;
  • hreflang and canonical errors;
  • content awaiting local review;
  • revenue, qualified demand or service outcomes.

Compare markets against their own seasonality, maturity and product capability. Do not expect a new locale to reproduce the established market’s performance immediately.

Build a maintenance agreement

For every language or market, assign:

  • business owner;
  • language and subject reviewer;
  • source page or content relationship;
  • update triggers;
  • service-level expectation for critical changes;
  • process for retirement or consolidation.

When the source page changes, decide whether the local version needs translation, a market-specific adaptation or no change. Blind synchronization can overwrite important local differences.

The correct international SEO question is not “Can this page be translated?” It is “Can we maintain a trustworthy local experience for an audience we are prepared to serve?”