Skip to content
Now accepting Q2 projects — limited slots available. Get started →
Capability

Internationale SEO

Rank in meerdere landen en talen — hreflang, locale routing en meertalige contentstrategie.

Stack
Next.js i18nAstro i18nHreflangGoogle Search ConsoleAhrefsSupabase

International SEO correct uitgevoerd

International SEO is niet zomaar het vertalen van uw content. Het gaat om hreflang-implementatie, locale-specifieke URL-structuren, land-specifieke contentstrategie, en technische signalen die Google vertellen welke pagina aan gebruikers in welk land moet worden getoond. Fout gedaan, kan dit leiden tot penalties voor duplicate content. Correct gedaan, vermenigvuldigt het uw organische traffic.

Hreflang: de technische basis

hreflang-attributen vertellen Google dat deze twee pagina's dezelfde content in verschillende talen of voor verschillende regio's zijn. Elke pagina in elke locale moet verwijzen naar alle andere locale-varianten. Ik implementeer dit als een server-gegenereerde sitemap en in-page head tags — beide zijn vereist voor maximale betrouwbaarheid.

Locale routing-strategieën

Ik implementeer drie URL-strategieën, afhankelijk van uw vereisten: subdirectories (example.com/en/, example.com/de/), subdomains (en.example.com, de.example.com), of ccTLD's (example.co.uk, example.de). Subdirectories zijn voor de meeste projecten het meest praktisch — zij concentreren domain authority en geven duidelijk de locale aan.

FAQ

Common questions

What is hreflang and why does it matter?

Hreflang is an HTML attribute that tells Google which version of a page to show users in which language or country. Without it, Google may show the wrong language variant to users, or treat your translated pages as duplicate content. Correct hreflang implementation is the technical foundation of international SEO.

Should I use subdirectories, subdomains, or ccTLDs?

Subdirectories (example.com/en/) for most projects — they inherit domain authority and are easiest to manage. Subdomains (en.example.com) if you need separate hosting per locale. ccTLDs (example.de) for maximum local trust signal in specific markets, but only if you can manage separate domains.

How do you handle machine translation for multilingual sites?

Machine translation (DeepL, Google Translate) is a starting point, not an endpoint. I flag content for human review and prioritise high-traffic pages for native translation. For SEO purposes, unique translated content always outperforms direct machine translation.

What is the biggest mistake in international SEO?

Not implementing hreflang correctly — specifically not including the x-default tag, and not making hreflang bidirectional (both pages must reference each other). The second biggest mistake is translating content without adapting it for the target market''s search intent.

Can you implement international SEO on an existing Next.js site?

Yes. Next.js has built-in i18n routing. I add hreflang to the head, set up locale-specific sitemaps, and configure content delivery to serve the correct locale based on the URL or Accept-Language header.

Ready to get started?

Free consultation. No commitment. Just an honest conversation about your project.

Book a free call →
Get in touch

Let's build
something together.

Whether it's a migration, a new build, or an SEO challenge — the Social Animal team would love to hear from you.

Get in touch →