Hreflang: connect the right language and regional pages

What is hreflang?

Hreflang identifies alternate language or regional versions of a page. It helps Google select a suitable version for a searcher. It does not translate content, force indexing, or replace the document's language declaration.

Use it where real alternatives exist

A Lithuanian service page and its English translation are good candidates. A single-language site does not need invented alternate pages to pass a presence check. Treat missing hreflang as an opportunity to inspect your publishing model, not a universal SEO failure.

Build a topic-to-URL table

For each translated topic, record the live URL for every language. Use a stable content key to connect the records; do not translate slugs by string replacement or send every alternate to the home page. If a translation does not exist yet, leave it out of the cluster.

Choose one manageable implementation: HTML links, HTTP headers or sitemap annotations. Multiple methods can work, but maintaining inconsistent copies creates avoidable errors.

1. Validate language and optional region codes

Use a supported language code such as en or lt, with an optional region when the content really targets that region. A country code alone is not a language. Do not use made-up labels such as en-UK; Great Britain uses GB in a language-region pair.

2. Link the complete reciprocal set

On each equivalent page, include itself and the other available versions with fully qualified URLs. Check that each version links back. Avoid assigning the same language label to competing targets, and open every target to confirm its content, protocol and availability.

3. Keep canonical and language decisions aligned

A genuine translation normally identifies its own preferred URL, rather than canonicalizing to a different-language version. Within duplicate same-language variants, decide which canonical page should participate in the alternate set. Check final URLs after redirects.

4. Decide whether a fallback is useful

Use x-default for an appropriate fallback, such as a language selector or your chosen default page. It is not compulsory for every multilingual site. Make sure the fallback gives visitors a sensible next step instead of repeatedly redirecting them.

5. Verify both sides after publication

Inspect the head on each version, not only the page that triggered the audit. Test the language switcher too. A single-page check cannot prove that remote pages return reciprocal annotations or are equivalent translations.

Example: different slugs for the same topic

Use the same set on both pages. The optional default points to English here because that is this example site's chosen fallback.

<link rel="alternate" hreflang="en" href="https://example.com/bicycle-repair">
<link rel="alternate" hreflang="lt" href="https://example.com/lt/dviraciu-remontas">
<link rel="alternate" hreflang="x-default" href="https://example.com/bicycle-repair">