UI Localization Update

Changes

• Navigation labels are now consistently translated (header, footer, and breadcrumbs).
• On-page section navigation uses i18n keys and better active-state logic near the bottom of pages.
• Sitemaps and robots directives include all locales, helping crawlers discover localized tool pages faster.

Routing + hreflang

All content is served under language-prefixed paths (/en/, /tr/) with proper canonical URLs and alternates. This reduces duplicate-content confusion and improves targeting for search engines.

Why this matters

Clear language targeting reduces duplicate content signals, improves user trust, and makes it easier for search engines to index the right version of each page.

Languages we actively serve

Omnvert is now fully localized in English and Turkish, and these are treated as first-class locales rather than machine-translated afterthoughts. Every tool page has a hand-checked counterpart in each language, so the interface, helper text, and supporting copy all read naturally instead of switching back to English halfway down the page.

• Chrome elements: header, footer, breadcrumbs, and on-page section navigation.
• Tool UI strings: buttons, field labels, placeholders, and empty/error states.
• SEO surfaces: page titles, meta descriptions, FAQ blocks, and the structured data behind them.

How language is detected and switched

The path prefix is the single source of truth, so the URL — not a guessed cookie or browser header — decides which language you see. When you switch locale, we keep you on the same page through its declared alternates instead of dropping you back on the home page, and bookmarks stay stable because each page has one canonical address per language.

12345/en/tools/png-svg-to-stl   ← English
/tr/tools/png-svg-to-stl   ← Türkçe

# language switch keeps the same page:
/en/news/ui-localization-update  ⇄  /tr/news/ui-localization-update

hreflang and canonical, in practice

Each localized page now emits a self-referencing canonical plus hreflang alternates for every active language and an x-default fallback. In plain terms: search engines are told these pages are translations of one another, not duplicates competing for the same query, so the right language version surfaces for the right audience.