International SEO
Rank in multiple countries and languages — hreflang, locale routing, and multilingual content strategy.
International SEO done right
International SEO is not just translating your content. It is hreflang implementation, locale-specific URL structures, country-specific content strategy, and technical signals that tell Google which page to show users in which country. Done wrong, it can cause duplicate content penalties. Done right, it multiplies your organic traffic.
Hreflang: the technical foundation
hreflang attributes tell Google that these two pages are the same content in different languages or for different regions. Every page in every locale must reference all other locale variants. I implement this as a server-generated sitemap and in-page head tags — both are required for maximum reliability.
Locale routing strategies
I implement three URL strategies depending on your requirements: subdirectories (example.com/en/, example.com/de/), subdomains (en.example.com, de.example.com), or ccTLDs (example.co.uk, example.de). Subdirectories are the most practical for most projects — they concentrate domain authority while clearly signalling locale.
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.
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.