Skip to content
PROOF48
All answers
seo

What hreflang actually does for a Romanian-English website

Hreflang tells Google that a Romanian page and an English page are the same page in two languages, so it can point each searcher to the version in their language. Google's documentation does not describe it as a ranking boost. It works only when each page lists itself and the other version. PROOF48's own sitemap does this for every page in en and ro.

Founder, PROOF485 min read

01What hreflang tells Google, and what it does not

Hreflang is a set of annotations that tells Google your Romanian and English URLs are localized variations of the same content. Google's documentation says the aim is to help Search 'point users to the most appropriate version of your page by language or region'. It does not describe hreflang as a ranking boost, and we do not claim one. It translates nothing. It does not tell Google what language a page is written in either: the same page says Google does not use hreflang or the HTML lang attribute for that, and works the language out with its own algorithms. It also says nothing about getting a page indexed, which is a separate step. Even without annotations Google might find your alternate versions on its own, but marking them is usually best.

  • It does: link a Romanian URL to its English twin so Google can serve the right one
  • It does not: translate, set the page's language or promise a position
  • It does not get a page indexed, so check each URL separately in Search Console
  • Source: Google Search Central, localized versions (developers.google.com/search/docs/specialty/international/localized-versions)

02The rules that make the tags count

Google's page sets out four conditions. Each language version must list itself as well as all the others, so the Romanian page carries one tag for ro and one for en. The tags must be reciprocal: if two pages do not both point to each other, the tags will be ignored. URLs must be fully qualified, with https and the domain. Language codes must come from ISO 639-1 and region codes from ISO 3166-1 Alpha 2, so ro and en are valid, and a region code on its own is not. A reserved value, x-default, covers visitors whose browser language matches none of your versions and suits a fallback or language-picker page. On a Romanian-English site we use language-only codes, ro and en, with x-default pointing at the English page. That last part is our practice, not a Google requirement.

  • Each page lists itself and the other language version
  • Both pages point to each other, or the tags are ignored
  • Full URLs with https, not relative paths
  • ro and en are valid codes; x-default marks the fallback (ours points at English)

03Where the tags go, and what else Google's pages ask for

You can declare the tags three ways: link elements in the head of each page, a Link header in the HTTP response, or entries in the sitemap. Google says the three methods are equivalent from its side, so pick the one your site can keep correct. We use the sitemap, because one file lists every pair and is easy to check. Google's guidance on multi-regional sites adds the parts that are easy to get wrong. Give each language its own URL instead of switching by cookie or browser setting. Avoid automatically redirecting visitors from one language version to another, because that can stop users and search engines from seeing every version. Keep one language per page, with no side-by-side translations, and do not translate only the menu while the body stays in one language. Link visibly to the other language. A Romanian page and its English version are not duplicates: Google treats localized versions as duplicates only if the main content stays untranslated.

  • Pick one method: head links, an HTTP header or the sitemap (equivalent to Google)
  • One URL per language, such as /ro/... and /en/..., never a cookie switch
  • No automatic redirect by browser language; offer a visible link to the other language
  • One language per page, with the whole text written in that language, not only the menu

04Where PROOF48 is the wrong choice

If your site has one language, you need no hreflang: there is nothing to point to. If your platform already writes the tags correctly, leave it alone and check them instead of paying for a rebuild. Hreflang does not repair weak copy. A machine-translated Romanian page is still a weak Romanian page, and we write each language in its own idiom rather than translating. We promise no Google position, because nobody controls one. PROOF48's FOUND plan costs 297 EUR a month and includes Google Business Profile management, local SEO for 5 target keywords, schema and a monthly ranking report. For a five-page site with a handful of local customers it may be more than you need, and the free technical audit described on our SEO page is the cheaper first step. A bilingual build has its own timeline, covered in our post on why a two-language site takes longer. Stores and apps are separate builds.

  • One language only: no hreflang needed
  • Your platform already writes correct tags: check them, do not rebuild
  • Weak or machine-translated Romanian: fix the copy first
  • A guaranteed position from anyone: nobody controls Google's rankings
  • A bilingual build gets its own scope and timeline, see our post on two-language sites
From a build we shipped

A bilingual membership site: what its live sitemap shows

SunVolt Club is the membership platform we built for SunVolt Energy UAB, with a public membership page in Romanian and English. We opened its live sitemap on 16 November 2026 for this post. It lists each page under four language prefixes (ro, en, it and es), and every URL carries hreflang entries for all four versions, itself included, plus x-default pointing at the Romanian page. The case study describes Romanian and English only, and we did not check the Italian and Spanish content, so we say nothing about it. The case study records no rankings or traffic, and we publish none.

See the build: SunVolt Club

Questions, answered

Do I need hreflang if my site is only in Romanian?

No. Hreflang links variants of the same page in different languages or regions, and a one-language site has no variants. It becomes relevant when you add a second language on its own URLs.

Will hreflang make my English page rank in Romania?

Google's documentation describes it as a way to point users to the most appropriate version, not as a ranking boost. We promise no position.

Can I redirect visitors to the language of their browser?

Google's guidance says to avoid automatically redirecting users between language versions, because it can keep users and search engines from seeing all of them. Offer a visible link to the other language instead.

Is a Romanian page and its English version duplicate content?

Not when the text is really translated. Google says localized versions are considered duplicates only if the main content remains untranslated.

Where PROOF48 fits

Hreflang tells Google that a Romanian page and an English page are the same page in two languages, and the tags count only when each page lists itself and the other. It does not translate, index or promise a position. PROOF48 declares its own language versions in the sitemap, starts SEO work with a free technical audit and promises no Google position.

· Founder, PROOF48

Cosmin has worked in online marketing and software development since 2018, and has built with AI every day since January 2023. He still writes code from scratch daily, in Python, React, Rust and C#. PROOF48 ships business websites in 48 hours and invoices afterwards, so every opinion on this blog was paid for in real builds, not in theory.

Related articles