NULLEX WEBGet a project estimate

NULLEXWEB / Blog

Multilingual website SEO: URLs, hreflang and useful content

A translation needs stable URLs, a clear language choice and useful local context. Adding country names to the same text is not an international strategy.

A real URL for every version

Use stable language or market URLs and link between equivalent pages. Let visitors choose a version themselves. Translate titles, descriptions, navigation, form labels, success and failure states and legal information. A translated hero above an untranslated form leaves the journey incomplete. Language and country are different: English versions for Ireland and the UK can use different currency and service context without inventing local offices.

Connect equivalent pages accurately

Canonical identifies a preferred page URL; hreflang connects language or regional equivalents. Check that alternate pages exist, are indexable and link back. Keep intended public URLs in a valid sitemap without duplicates. An article language switch should reach the matching article when one exists. When a translation is not ready, an honest fallback is preferable to a thin page created just to complete a list of country codes.

Translate the customer decision

Explain scope, contact, enquiry handling and ongoing costs in the chosen language. Local phone support, registration and locations must be real. Use currency only when a genuine estimate supports it. Helpful articles should offer checklists, limitations, an identified author and sources. No fixed word count, automated translation or number of pages guarantees indexing. Avoid near-identical city pages without distinct service information. After publication, use Search Console evidence and update content when the offer changes.

Technical review

  • One H1 and distinct title and description.
  • Self canonical and reciprocal hreflang.
  • Working equivalent article links.
  • Translated form and legal information.
  • Readable mobile layout and keyboard access.
  • Valid sitemap and a tested contact journey.

Sources & further reading

More guides

Contact

Send a project enquiry

Review the structure before development. Confirm content, contact routes and costs in writing. Test the agreed pages before handover.

  1. 1Project
  2. 2Contact
  3. 3Review

An ordinary enquiry does not require an Upwork account. If you found me on Upwork, please message me there before starting a contract. Message me on Upwork ↗

Your goal, required features, available materials and preferred timing. 20–2,500 characters.

Cookies & storage ↗