Satelo / Indexing / Hreflang Tags for Small Bilingual Sites: A Setup Guide From Our Own EN/RU Build
Indexing

Hreflang Tags for Small Bilingual Sites: A Setup Guide From Our Own EN/RU Build

Hreflang tags tell search engines that two URLs are the same page in different languages, so a Russian speaker gets your Russian version and everyone else gets English. For a small bilingual site the whole job is three link tags per translated page, a decision about x-default, and a rule for pages that exist in one language only. Below is the setup we run on satelo.io (English plus Russian), the official rules from Google and Yandex behind each choice, and the mistakes that silently break it.

Published: 2026-11-06 · 7 min read · Satelo

Hreflang Tags for Small Bilingual Sites: A Setup Guide From Our Own EN/RU Build

What hreflang does and doesn't do

Google's documentation on localized versions of your pages frames hreflang as a way to help Google point users to the most appropriate version of a page by language or region. Yandex says the same in its help article on localized pages: choosing the right version helps show a suitable result in search.

What it doesn't do:

If your site has only one language, you don't need hreflang at all.

The markup: three tags per translated page

For a page that exists in English and Russian, both versions carry the same block in <head>:

<link rel="alternate" hreflang="en" href="https://example.com/blog/post/">
<link rel="alternate" hreflang="ru" href="https://example.com/ru/blog/post/">
<link rel="alternate" hreflang="x-default" href="https://example.com/blog/post/">

The rules that make it valid, all from Google's documentation:

Yandex asks for the same structure: on each version, list links to all its alternates, with language codes in ISO 639-1 and regions in ISO 3166-1 Alpha-2 (or ISO 3166-2:RU for Russian regions).

Head, HTTP header or sitemap? For EN/RU, pick the head

Google accepts three equivalent methods: HTML link tags, HTTP Link headers and XML sitemaps. It also says using more than one gives no benefit in Search and makes maintenance harder.

Yandex is stricter. Its help page says Yandex no longer supports sitemaps for language versions and recommends markup in the page <head>; HTTP headers aren't described as an option.

MethodGoogleYandexVerdict for an EN/RU site
<link> in headSupportedSupported (the recommended way)Use this
HTTP Link headerSupportedNot describedOnly for PDFs and other non-HTML files
XML sitemapSupportedNo longer supported for language versionsOptional extra for Google; never the only method

If your audience includes Russian speakers who search on Yandex, a sitemap-only setup leaves Yandex with nothing to read.

Where x-default should point on a two-language site

Google says x-default is the fallback for users whose language matches none of your versions and that it was designed for language selector pages. Yandex suggests x-default when the language is picked automatically (by IP or the Accept-Language header) or chosen by the visitor on the page.

Most small bilingual sites have no separate selector page, so the practical choice is: point x-default at the version that serves the widest audience. For us that's English, because a visitor searching in German or Spanish is more likely to read English than Russian. If your site is Russian-first with an English translation for a few pages, x-default can just as well point at Russian. What matters is that it's the same choice on every version of the page.

Pages that exist in one language only

This is where small sites go wrong. Many posts on a bilingual blog exist only in English or only in Russian. The rules:

The rule we built into our generator: the alternate block is printed only when both locales of a post exist in the content source, so a missing translation can never produce a broken pair.

Canonical and hreflang together

Each language version should canonicalize to itself. Google's guide to consolidating duplicate URLs says that when you use hreflang, you should specify a canonical page in the same language (or the best substitute language if none exists). The same guide notes that rel="canonical" annotations carrying hreflang attributes are not used for canonicalization; use rel="alternate" for language versions.

The classic mistake is a Russian page whose canonical points to the English one. That tells Google the Russian URL is a duplicate, and the hreflang pair collapses. If your plugin or theme sets canonicals globally, check one translated page by hand.

Our setup on satelo.io, as a template

Page typeHead tagsSitemap
Homepage and pages in both languagesen + ru + x-default → English URL; self-canonical; <html lang> set per versionxhtml:link alternates for en and ru
English-only postSelf en + x-default → itselfPlain URL, no alternates
Russian-only postSelf ru + x-default → itselfPlain URL, no alternates

One honest note on our own build: we also list alternates in the sitemap. By Google's own documentation that adds nothing over the head tags, and Yandex ignores it. We keep it because both are generated from the same data and can't drift apart. If you maintain tags by hand, keep one method, the head.

Setting it up on common platforms

Six mistakes that silently break hreflang

MistakeWhat happensFix
No return link from the other versionGoogle may ignore the pairGenerate both sides from one data source
Relative URLs in hrefInvalid annotationAlways print the full https:// URL
Region code without language, or en-UKTag has no effectUse en, en-GB, ru
Russian page canonicalized to EnglishTranslation treated as a duplicateSelf-canonical on every version
Hreflang only in the sitemapYandex sees nothingMove the tags into the head
Alternate points at a homepage or a 404Wrong page served, pair brokenPrint alternates only when the translation exists

Every row on this list comes from Google's and Yandex's documentation cited above, and every one can be caught by viewing the source of a single translated page. That's why the checklist below starts there.

Testing checklist

  1. View source on one translated page in each language: three tags, absolute URLs, codes valid.
  2. Open every hreflang URL: each returns 200, isn't noindexed, and canonicalizes to itself.
  3. Confirm the other version points back.
  4. Run a crawler over the site and filter for missing return links and non-200 alternates.
  5. In Google Search Console, inspect the Russian URL with URL Inspection and check that the Google-selected canonical is the Russian page itself.
  6. In Yandex Webmaster, make sure both language sections are indexed; if the Russian version is missing, start with indexing diagnostics before blaming hreflang.

What to do next

Hreflang is a routing layer; it only helps if both versions are indexed and worth showing. Fix the markup once with the checklist above, then spend your time on what makes each version earn its place: real translation, internal links within each language, and mentions from sites in each market. To see how your site looks from the outside, run the free Satelo site check: it shows your Quality Score with the evidence behind each number in about 30 seconds, built mostly from open data. For the rest of the technical basics, see our SEO checklist for a new site, and if a section isn't getting indexed at all, the guide to "Discovered, currently not indexed" is the next stop.

FAQ

What are hreflang tags?

Hreflang tags are link annotations that tell search engines which URLs are language or regional versions of the same page, so each searcher is shown the most appropriate version. They are added as rel="alternate" links in the page head, in HTTP headers or in a sitemap.

Do I need hreflang for a two-language site?

Yes, if pages are translated versions of each other. It helps Google and Yandex show the Russian page to Russian speakers and the English page to others. Single-language sites don't need it.

What does hreflang x-default mean?

x-default marks the fallback version for users whose language doesn't match any of your versions. Google says it was designed for language selector pages; on a small bilingual site it usually points at the version with the widest audience.

Should hreflang go in the sitemap or the head?

For sites that also target Yandex, use the head. Google treats head, HTTP header and sitemap as equivalent, but Yandex says it no longer supports sitemaps for language versions.

Does hreflang need a self-referencing tag?

Yes, on translated pages each version should list itself and all alternates. On a page that exists in one language only, a self-reference is optional because there is no pair to process.

Can a translated page canonicalize to the original language?

No. Google advises specifying a canonical page in the same language. A Russian page canonicalized to its English version is treated as a duplicate, which defeats the hreflang pair.

How do I test hreflang tags?

Check the page source for absolute URLs and valid codes, open every alternate to confirm a 200 status and self-canonical, verify return links, and use URL Inspection in Search Console to confirm Google selected each language page as its own canonical.

Satelo team
We build Satelo, a network where small websites promote each other. About us

Read next

"Indexed, Though Blocked by robots.txt": What It Means and the Right FixWhat "Indexed, though blocked by robots.txt" means in Search Console, a 2-question decision tree, and the exact fix: unblock it, or swap Disallow for noindex.
Bing Webmaster Tools: A Setup Guide for the AI Search EraSet up Bing Webmaster Tools in 5 minutes by importing from Search Console, then add IndexNow and read the AI Performance report for Copilot citations.
Screaming Frog Alternatives: Free Desktop, Cloud, and Open-Source CrawlersFree Screaming Frog alternatives compared: desktop, cloud, and open-source crawlers, with free URL limits from official pages and a pick for every site size.
"Crawled – Currently Not Indexed": What It Means and What We Did on a New SiteWhat "Crawled – currently not indexed" means in Google Search Console, how to diagnose it step by step, and the real indexing timeline of our new site.

Check your site's Quality Score

Free, no sign-up: a 0–100 score from mostly open data. Then add your site to Satelo and get partner articles from sites of your level.

Add my site