Skip to content
International SEO · DE/EN · hreflang · mirrored URL structure

International SEO – visible in every market you sell in.

Multilingual and international websites are one of the most common SEO problem areas: hreflang errors, duplicate content between languages, faulty market-targeting setups. We build your international SEO so that every market gets its own visibility.

  • hreflang setup
  • Mirrored URL structure
  • Localization, not translation
  • x-default compliant
In brief

International SEO ensures that every language and country version of your website ranks in the right market, through correct hreflang markup, clean country targeting and localized rather than merely translated content.

Shown visually

The right country, the right language

With a clean hreflang setup and mirrored URL structure, Google shows each region the right version – without duplicate-content risk.

DE
de-DE
/de/
AT
de-AT
/at/
CH
de-CH
/ch/
GB
en-GB
/en/
US
en-US
/us/
hreflang in detail

What the tags look like for DE/EN/x-default

<!-- Add to every page version inside <head> -->
<link rel="alternate" hreflang="de" href="https://loomup.io/leistungen/seo/">
<link rel="alternate" hreflang="en" href="https://loomup.io/en/services/seo/">
<link rel="alternate" hreflang="x-default" href="https://loomup.io/leistungen/seo/">

// Plus optionally in the XML sitemap per URL:
<xhtml:link rel="alternate" hreflang="de" href="https://loomup.io/leistungen/seo/"/>
Subdirectory vs. subdomain vs. ccTLD

Which URL structure for which market

CriterionSubdirectory (/en/)Subdomain (en.)ccTLD (.com)
Domain authority inheritanceFullPartialNone
Setup effortLowMediumHigh
Hosting cost1–2×
Local targeting in Search ConsolePer country separatelyPer subdomainImplicit
Market trust (local)MediumMediumVery high
Ideal for2–4 languages, DE/ENTech brands, subdomain setupGlobal enterprises, market strategy
Three pillars of international SEO

What we watch for on every project

hreflang & market targeting

Correct hreflang tags for every language and market combination. x-default fallback. Search Console market setting per property.

Mirrored URL structure

Recommendation: language segment in the path (/en/), not a subdomain. Every German URL has its counterpart in every target language at the same depth.

Localization, not translation

Word-for-word translations fail on search intent. We localize: terms, examples, units of measure and tone adapted to each market.

~40%
of international multi-language websites have faulty hreflang tagsSource: Sistrix International SEO Study
×2.5
higher conversion rate for localized versus merely translated contentSource: CSA Research
76%
of buyers are more likely to buy in a language they understandSource: CSA Research
hreflang set correctly on every page version
Bidirectional linking (DE points to EN, EN to DE)
x-default fallback for languages not covered
A Search Console property per market
Localized title & meta data
Localized schema markup fields (currency, address)
Language switcher without automatic redirect
Local backlinks from every target market
Good to know

The key questions, answered briefly

What does hreflang do?

hreflang tells Google which language or country version of a page applies to which users. Implemented correctly, it stops versions from cannibalizing one another and ensures that, for example, German users see the DE page and British users the EN-GB page.

Is a translation enough for other markets?

No. Pure translation ignores local search terms, competition and cultural expectations. Successful international SEO localizes keywords, content and examples per market, otherwise the page won't rank in the target country.

Common mistakes

The typical hreflang mistakes, and how to avoid them

hreflang is powerful but error-prone. These are the mistakes we see most often:

Missing return reference: hreflang must be set reciprocally.
Wrong language/country codes (e.g. “en-UK” instead of “en-GB”).
No x-default for markets not covered.
hreflang pointing to non-indexable pages.
Inconsistency between sitemap and page markup.
Strategy

Does every country need a completely separate site?

A dedicated, localized version per language/market, yes, but not necessarily a separate domain. What matters is that content is genuinely localized (keywords, examples, tone) and correctly mapped via hreflang. Pure language duplicates without local adaptation won't rank in the target market, more on that under multilingual content.

Written & expert-reviewed by
Photo of Seth Iorio, Founder & Head of Visibility & Industries at Loomup

Seth Iorio

Founder & Head of Visibility & Industries at Loomup

Seth Iorio leads visibility across every channel at Loomup – SEO, GEO/AI visibility, local visibility, social and content – plus industry-specific strategy. His focus: making companies visible exactly where their customers search and decide.

FAQ

Frequently asked questions

Subdomain, subdirectory or cc-TLD, which is better?

For most mid-sized companies we recommend a subdirectory (loomup.io/en/), as it consolidates domain authority, is cheaper to maintain and is sufficient for DE/EN. cc-TLDs (loomup.de, loomup.com) only make sense if you run a separate marketing and local strategy per market.

How many languages can a website sensibly serve?

Up to 3–4 languages with a standard setup; beyond that, a dedicated localization system pays off. Important: two languages done really well beats eight done half-heartedly.

Do you handle the translations?

We localize, which goes beyond mere translation. We work with native-speaking editors and check search intent and terminology in the target market.

Get started

Ready to put this lever to work?

In the free visibility check we look together at whether and how this service fits your situation, including a concrete proposal for action.

Request an international SEO audit →
No obligation · Nationwide · Reply within one day