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…

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.

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.

Selected portfolio work

stuzhuk.page

stuzhuk.page is a personal portfolio and product site on Astro SSR with AISO stack (AI Readiness 84): llms.txt, AI crawler rules, JSON-LD, hreflang, related …

lagrant.com.ua

Marketing site for grant-related services on Astro and TypeScript with Tailwind styling. Emphasis on fast static delivery and maintainable content sections.

hiddenlogic-website

Brand website for Hidden Logic built on Astro with TypeScript and Tailwind. Component-driven layout with performance-focused static generation.

Discuss this direction Contact form

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

View full service page