hreflang the right way
Most international setups have broken hreflang. We diff your declarations against your sitemaps, fix the templates, and verify in Search Console. A boring fix that quietly recovers 10–30% of misindexed traffic.
Service · 06 / 06
SEO for brands expanding market by market.
Three or more markets, hreflang done right, ccTLD/subdomain/subfolder decisions made transparently, content localised by named editors per language. Country-level reporting, not a global line going up.
Editors per language · in-house
- 🇺🇸EnglishENUS / UK / International
- 🇪🇸EspañolESES / MX / LatAm
- 🇧🇷PortuguêsPTBrazil + EU
- 🇩🇪DeutschDEDACH region
- 🇫🇷FrançaisFRFrance + FR-Africa
- 🇯🇵日本語JAJapan
What an international engagement covers
Six disciplines. All required if the work is going to last.
ccTLD vs. subfolder
The decision matters more than people think and rarely gets revisited. We walk you through the trade-offs for your business — search authority transfer, ops complexity, marketing-domain story — and give a clear recommendation.
Localisation, not translation
Google Translate is the cheapest way to lose a market. We work with native-language editors per language, briefed from the original strategy. Same intent, locale-native voice, in-market keyword research underneath.
In-market KW research
Direct keyword translation rarely matches local search behaviour. Spanish in Mexico ≠ Spanish in Spain. We rebuild the keyword set per language using local SERPs, not a Google Translate of the EN list.
Multilingual content production
We ship in six languages with named editors per language. EN, ES, PT, DE, FR, JA. Adding a language is a conversation, not a rebuild.
Country-level reporting
Performance by country and language, not just a global line going up. Forecasts per market. We tell you which expansions to double down on and which to pause.
FAQ
The international SEO questions worth asking.
- We tried machine translation before and it didn't rank. Why now?
- Because machine translation is a different problem than what you tried in 2020. We don't lead with translation — we lead with localisation, which means a native-language editor working from the strategy, not from your English copy. Translation is one input, not the entire workflow. The pages that result rank because they're answering the local search, not because a machine rewrote your blog post.
- Do you handle the technical migration to a new structure?
- Yes — and we'd prefer to. Switching from a subdomain setup to a subfolder one (or vice versa) is a migration with all the usual risks, plus hreflang complications. Our technical SEO team owns this end to end if you want them to.
- What if our target market is on this list but the language is dialected (e.g. Quebec French)?
- We work with editors per dialect when the buyer demands it. FR-CA is materially different from FR-FR; PT-BR is the default but PT-PT is available. Tell us on the scoping call — we'll either confirm the editor capacity or refer you to a partner.
- Languages outside the six?
- Italian, Dutch, Polish, and Russian are doable on request — we have editorial partners for each. Languages we don't currently offer: Arabic, Mandarin, Korean, Hindi. We won't fake capacity we don't have.
Send us your current structure and the next three markets you're planning. We'll come back with a recommended structure and a 90-day kickoff plan.
Scope an expansion