Hreflang for Finnish and English Websites

Hreflang is a small piece of code that tells Google which language a page is written in and which audience it is meant for. If your business publishes the same content in both Finnish and English, hreflang is what stops Google from showing the wrong version to the wrong reader — and what stops it from treating your two language versions as duplicate content. This guide explains what hreflang does, how to set it up correctly for a bilingual Finnish and English site, the mistakes that quietly break it, and why the old google.fi domain no longer works the way many people still assume.

What hreflang actually does

Hreflang is an HTML attribute that lists all the language and regional versions of a page so search engines can serve the right one to each user. It does not translate anything, and it is not a ranking booster — it simply describes the relationship between pages that say the same thing in different languages.

When you have a Finnish page and an English page covering the same topic, Google needs to understand that they are alternates of each other rather than competing duplicates. Hreflang provides that map. A searcher using Finnish is then more likely to be shown the Finnish URL, while an English-language searcher is shown the English URL — even though both pages target the same subject.

Without these signals, two things tend to go wrong. Google may show the English version to a Finnish reader (or the reverse), and it may consolidate your two versions and largely ignore one of them, wasting the effort you put into translation.

Why hreflang matters for Finnish and English sites

Finnish and English are genuinely different languages, but their audiences overlap heavily, which is exactly why hreflang is worth getting right. Finland has a highly bilingual population, so many of your Finnish visitors could plausibly be served either version — and Google will guess unless you tell it what you intend.

A typical setup is an English site for international readers plus a Finnish site (or subfolder) for the domestic market. Hreflang keeps those two streams separated in search results, so your carefully localised Finnish pages actually reach Finnish searchers instead of losing visibility to the English originals.

The bilingual-audience trap

Because so many Finns read English comfortably, Google sometimes surfaces an English page for a Finnish query when both exist. That is not necessarily wrong from Google’s point of view, but it usually is from yours: the Finnish page is the one with local phrasing, local examples and local trust signals. Correct hreflang tells Google that a Finnish speaker in Finland should get the fi version first. If your localisation strategy relies on this, it is worth reading up on how Finnish content localisation differs from plain translation before you wire up the tags.

Does google.fi still matter?

Targeting Finnish searchers has essentially nothing to do with the google.fi domain anymore. This surprises people who remember when the country-code domain (ccTLD) seemed to control which country’s results you saw.

Two changes settled this. In 2017 Google moved to serving results based on the user’s location rather than the Google domain they typed — so someone in Helsinki got Finnish results whether they visited google.fi or google.com. Then in April 2025 Google began phasing out country-code domains entirely, redirecting google.fi and the others to google.com over the following months.

Crucially, Google’s John Mueller confirmed that this domain change does not affect international SEO. Your country and language targeting still come from signals on your own site — the language of the content, your server location and other cues, and, for language, hreflang. So the practical takeaway is simple: do not rely on a domain to reach Finnish users. Use hreflang and genuinely localised content instead. If you are planning a wider Nordic rollout, the same logic extends across the region, which is covered in this overview of Nordic link building.

Choosing the right language and region codes

Hreflang codes always start with a language code, optionally followed by a region code. Getting the format right is the single most important step, because an invalid code makes Google ignore the tag.

• Language code: ISO 639-1 format — fi for Finnish, en for English.
• Region code (optional): ISO 3166-1 Alpha-2 format — FI for Finland, GB for the United Kingdom, US for the United States.
• Separator: always a hyphen, never an underscore. It is en-GB, not en_GB.

The region part is optional, and for most Finnish and English sites you do not need it. Plain fi and en cover the vast majority of cases: Finnish is used almost exclusively in Finland, and a single English version usually serves your international audience well.

Do you need fi-FI and en-FI?

Usually not. Add a region code only when you have genuinely different content for different countries — for example a separate en-US page with US pricing and an en-GB page with UK pricing. If you only have one English page, use plain en and let it serve everyone. Splitting into regional variants you cannot actually maintain creates more problems than it solves.

Three ways to implement hreflang

Google accepts three implementation methods, and they are equivalent — you only need one, so pick the one that fits your platform. Whichever you choose, every version must list every other version, including itself.

Method 1: HTML link tags in the head

This is the most common method: you add a link element for each version inside the <head> of every page. For a Finnish and English page pair it looks like this (shown as text):

<link rel=”alternate” hreflang=”fi” href=”https://example.com/fi/” />
<link rel=”alternate” hreflang=”en” href=”https://example.com/en/” />
<link rel=”alternate” hreflang=”x-default” href=”https://example.com/en/” />

Both the Finnish page and the English page carry the exact same block. It works well for small and medium sites but adds markup to every page, which can get heavy at scale.

Method 2: HTTP headers

For non-HTML files such as PDFs, you cannot add a link tag, so you send the same information in an HTTP Link header instead. The server returns each alternate as <url>; rel=”alternate”; hreflang=”code”. This method is rarely needed for ordinary web pages but is the correct choice for downloadable documents you want to internationalise.

Method 3: XML sitemap

For large sites, listing the alternates in your XML sitemap keeps the page markup clean and centralises everything in one file. Each URL entry gains an xhtml:link child element for every language version. It is more work to set up but far easier to audit and update once you have hundreds of pages.

The x-default tag

The x-default value tells Google which page to show when none of your declared languages matches the user. It is a fallback, not a language: it is meant for visitors whose settings do not match Finnish or English at all, and it is also the right choice for a language-selector or gateway page.

You do not have to use x-default, but Google recommends it, and there should only ever be one per set. On a Finnish and English site, pointing x-default at your English page is a sensible default, because English reaches the widest international audience.

A complete example for a Finnish and English site

Putting it together, here is the full hreflang block that belongs in the head of both the Finnish and the English version of a page. Note that every URL is absolute (it includes https://), each version references itself, and the two pages carry identical tags:

<link rel=”alternate” hreflang=”fi” href=”https://example.com/fi/tuote/” />
<link rel=”alternate” hreflang=”en” href=”https://example.com/en/product/” />
<link rel=”alternate” hreflang=”x-default” href=”https://example.com/en/product/” />

That is the whole pattern. Reciprocity (each page links back to the others) and self-reference (each page lists itself) are what make it valid — miss either and Google may quietly ignore the annotations.

Common hreflang mistakes

Most hreflang problems come from a handful of recurring errors. These are the ones to check first, because Google will often disregard the whole set when one of them is present.

• Missing return tags: if the Finnish page links to the English page, the English page must link back. Broken reciprocity is the most common reason hreflang is ignored.
• No self-reference: each page must list its own URL as well as the others. Leaving the page out of its own set is easy to do and breaks the mapping.
• Wrong codes: en-UK is invalid (the correct region code is en-GB), and codes like EU or UK are not valid regions. Never use a country code where a language code belongs.
• Underscore instead of hyphen: use en-GB, not en_GB.
• Relative URLs: hreflang URLs must be fully qualified, including https://. Relative paths are not accepted.
• Conflicting canonical tags: each language version should have a self-referencing canonical. Pointing the Finnish page’s canonical at the English URL tells Google to drop the Finnish page — the opposite of what hreflang is meant to achieve.
• Tagging only some pages: hreflang works page by page. Add it to every page that has alternates, not just the homepage.
• Confusing Finnish and Swedish: Finland is officially bilingual, and Swedish content is sv, not fi. Do not label Swedish-language pages as Finnish.

Several of these overlap with the wider technical errors that hurt international sites; there is a broader rundown in this guide to common link building and SEO mistakes in Finland.

How to test your hreflang setup

Google Search Console no longer flags hreflang problems for you — the International Targeting report was removed in September 2022 — so testing now relies on your own checks. The good news is that verification is straightforward.

• Crawl the site: a crawler such as Screaming Frog can extract every hreflang tag and flag missing return links or invalid codes across your whole site at once.
• Inspect individual URLs: the URL Inspection tool in Search Console shows how Google sees a specific page, which helps confirm the tags are present and indexed.
• Use a validator: several free hreflang validators check reciprocity and code format for a single URL, which is handy for spot checks after a change.

Run a check whenever you add a new language version or restructure URLs, since those are the moments hreflang most often breaks.

Hreflang, canonicals and rankings

Hreflang does not improve your rankings directly — it improves which of your existing pages is shown to which audience. That distinction matters, because teams sometimes expect a traffic jump from hreflang alone and are disappointed. The real benefit is that each language version can rank for its own audience without cannibalising the other, and users land on the version written for them.

It also works alongside, not instead of, other international-SEO fundamentals: a clean site structure, genuinely localised content, and relevant local links. If your goal is stronger visibility in Finland specifically, hreflang is one layer on top of a solid foundation in SEO for the Finnish market, and it pairs naturally with the localisation work described in the difference between translation and localisation for Finnish. For online stores in particular, hreflang and structured localisation go hand in hand, as covered in this guide to e-commerce SEO in Finland.

Frequently Asked Questions (FAQ)

Do I need both fi and en hreflang tags, or just one?

You need a full set on every page that has alternates. Both the Finnish and the English version must list each other and themselves, so a two-language page carries an fi tag, an en tag and usually an x-default tag. A single one-directional tag will normally be ignored, because hreflang has to be reciprocal to work.

Should I use fi-FI or just fi for a Finnish site?

Plain fi is usually the better choice. Finnish is used almost exclusively in Finland, so the region code adds nothing in most cases. Only reach for fi-FI if you have a specific reason to distinguish Finnish content by country, which is rare.

Does google.fi still affect my rankings in Finland?

No. Since 2017 Google has served results based on the user’s location rather than the domain they visit, and in 2025 it began redirecting google.fi to google.com. Your visibility in Finland comes from your content, its language, hreflang and local signals — not from any country-code domain.

Will hreflang help my pages rank higher?

Not directly. Hreflang controls which version of a page is shown to which audience; it does not raise your position in the results. Its value is preventing duplicate-content confusion between your language versions and making sure the right reader gets the right page.

How do I check whether my hreflang is set up correctly?

Because Google Search Console removed its International Targeting report in 2022, use a crawler such as Screaming Frog to check every page at once, inspect individual URLs with the URL Inspection tool, or run a dedicated hreflang validator. Re-check after adding a language or changing URLs, since those changes most often break the tags.