Corporate websites and landing pages

Multilingual Sites: i18n and hreflang

A multilingual website needs separate indexable versions with clear URLs and hreflang relationships, not an automatic…

Discuss this directionContact form

Tell me the goal, stack constraints, and timeline — I reply on Telegram.

A multilingual website needs separate indexable versions with clear URLs and hreflang relationships, not an automatic translator over one page. I configure routing, templates, and editorial workflow for the correct language.

Scope includes localised URLs, a language switcher, hreflang, canonical, sitemap, date formats, and key-completeness checks. Translation itself belongs to an editor or translator. Acceptance verifies reciprocal hreflang, no redirect loops, preservation of the current page when switching languages, and honest handling of missing versions.

Acceptance criteria

Done when

  • Key templates render full HTML and pass agreed CWV checks
  • Canonical, sitemap, and basic meta are in place
  • Forms submit and notify as specified

Deliverables

  • Deployed site + CMS/editor access if used
  • Redirect / SEO checklist

Out of scope

  • Ongoing SEO retainers and link building
  • Stock photography purchases

The final acceptance checklist is confirmed in the brief or contract; the list above is a scope alignment guide.

Ballpark estimate

Scope size
Extras

FAQ

Tap a question to expand the answer.

Does every language need its own domain?

No. Subdirectories are generally easier to maintain. Separate domains suit independent markets, teams, or legal requirements.

Can languages launch at different times?

Yes, provided missing URLs do not pretend to be translations and hreflang lists only versions that actually exist.

Discuss this directionContact form

Tell me the goal, stack constraints, and timeline — I reply on Telegram.

View full service page