The problem: growth abroad that the site was never built for
International SEO problems rarely announce themselves. A UK retailer notices its .co.uk pages ranking in Australia, where pricing and shipping are wrong and conversion rates collapse. A SaaS company launches German and French versions, translated word for word, and finds that they rank for nothing because German buyers search with different terms than the ones an English keyword list suggested. A US company sets up separate country domains and watches each one struggle, because the authority that made the main site rank is now divided five ways.
Each of these is a structural decision that was made without an SEO consequence in mind, and each is far more expensive to reverse than to get right at the start. International SEO is the discipline of making those decisions deliberately.
What international SEO covers
International SEO is the set of technical and content decisions that let one business rank appropriately in multiple countries or languages. It has three layers. The structural layer is how markets are separated: country-code domains (ccTLDs), subfolders on one domain, or subdomains. The signalling layer tells search engines which version belongs to which audience: hreflang annotations, geo-targeting settings in Search Console, local currency, addresses and language declarations. The content layer is localization: adapting pages so they match the vocabulary, products, regulations and search behaviour of each market rather than merely translating them.
Who this service is for
Businesses already selling in more than one country and getting less organic traffic abroad than at home. Companies planning expansion into markets such as the United States, United Kingdom, Canada, Australia, India or continental Europe and wanting the site structure decided before development starts. E-commerce brands managing regional catalogues, currencies and shipping. SaaS companies localizing product and content in several languages. Travel businesses where the same destination is searched differently by source market. If you sell in one country and one language, you do not need this yet, and we will say so.
What Axoria does
Market prioritization
Search demand, competition, commercial readiness (payments, shipping, support, legal) and existing traction scored per market so investment goes where it can pay back, rather than launching ten markets thinly.
URL structure strategy
A documented recommendation on ccTLD, subfolder or subdomain, with the reasoning, the migration path from your current setup and the implications for authority, hosting and CMS.
Hreflang implementation
Full annotation set (including x-default and self-references) generated and validated across HTML, sitemaps or HTTP headers, whichever suits your platform, with ongoing error monitoring.
Geo-targeting and signals
Search Console international targeting, local currency and contact details, language attributes, structured data with country-specific properties, and consistency between all of them.
Localized keyword research
Native-language research for each market, because direct translation of a keyword list misses how people actually search. Delivered as market-specific intent maps.
Localization quality control
Briefs and review checklists so translated pages are adapted for market-specific products, units, regulation and cultural references, with unique titles and metadata per market.
ccTLD, subfolder or subdomain: how we decide
This is the decision most clients come to us for, and there is no universal answer. Subfolders (example.com/de/) keep all authority on one domain, are cheapest to run and are our default recommendation for most businesses. ccTLDs (example.de) give the strongest geographic signal and can matter for consumer trust in some markets, but each domain must earn its own authority and the operational cost multiplies. Subdomains (de.example.com) sit awkwardly between the two and are usually only justified by infrastructure constraints.
| Structure | Strengths | Trade-offs | Usually right for |
|---|---|---|---|
| Subfolder | Consolidated authority, one CMS, simple hreflang | Weaker geo signal; relies on hreflang and content to target | Most SaaS, B2B and e-commerce sites |
| ccTLD | Strongest country signal, local trust | Authority split, separate hosting and maintenance per domain | Established brands with dedicated market teams and budgets |
| Subdomain | Separate infrastructure possible | Treated partly as a separate site; authority partially split | Cases where a subfolder is technically impossible |
We also distinguish between language targeting and country targeting. A Spanish-language page can serve Spain, Mexico and Argentina if pricing and product are the same, using hreflang=”es” plus country-specific variants only where content genuinely differs. Creating a separate near-identical page per country creates duplicate content and dilutes the pages that matter.
Hreflang without the usual errors
Hreflang is easy to describe and easy to get wrong. The most common errors we find in audits are missing return links (page A references page B but B does not reference A, which invalidates the pair), missing self-referencing tags, invalid language or region codes such as “en-UK” instead of “en-GB”, annotations pointing at redirected or non-canonical URLs, and no x-default for users outside the targeted markets. On a site with 20,000 pages across eight markets, that is 160,000 URLs that need consistent annotations, which is why we generate them from the CMS or sitemap rather than by hand and validate the full set with a crawler before and after release.
Expert note: hreflang does not fix duplicate content across markets
Hreflang tells Google which version to show to which audience; it does not merge signals or excuse identical pages. If your Canadian and US English pages differ only by currency symbol, expect Google to consolidate them and pick one. Give each market variant genuinely different value (pricing, availability, local terms, shipping, regulations) or serve one page with hreflang for the language only.
Localization versus translation
Translation produces a page that is grammatically correct in the target language. Localization produces a page that ranks and converts there. The difference shows in keyword research: a British “estate agent” is an American “realtor”; the German market searches for “Autoversicherung” in ways that do not map to the English “car insurance” cluster; a product measured in ounces needs metric units in most markets. We run native keyword research per market, brief translators with the target terms and intent, and review the results for search fit as well as language quality. Titles and meta descriptions are written fresh for each market, never machine-translated.
Our international SEO process
International audit
Current market performance from Search Console by country, existing hreflang validity, duplicate content between markets, geo-targeting settings and technical setup per market.
Market and structure strategy
Prioritized market list with demand and competition data, the URL structure recommendation and a migration or build plan agreed with your developers.
Technical implementation
Hreflang generation, sitemap structure, Search Console properties per market, canonical rules and language and currency handling specified as developer tickets and validated on staging.
Localized content
Per-market keyword research, page-level briefs and localization QA, starting with the commercial pages that carry the most demand.
Market-level monitoring
Reporting by country and language, hreflang error monitoring and quarterly review of which markets earn further investment.
Tools we typically work with
Google Search Console (one property per market or subfolder) for country-level performance and hreflang error reports, Screaming Frog for site-wide hreflang validation, Ahrefs and Semrush with country-specific databases for localized keyword research, and Looker Studio for market-by-market reporting. For markets where Google is not dominant, such as parts of Asia and Russia, we adapt the approach to the relevant engine and will be honest about the limits of our coverage there.
How international SEO results are measured
Everything is reported by market: organic sessions, conversions and revenue per country and language, the share of impressions where the correct market version ranked (a direct measure of whether hreflang is working), hreflang error counts, and indexation per market subfolder or domain. We compare market growth against the prioritization scores so you can see whether the investment is landing where the plan said it would. Conversion tracking per market is set up through our analytics and tracking service so currency and regional attribution are correct from the start.
What to expect
Fixing hreflang and geo-targeting on an existing site often corrects wrong-market rankings within a few weeks of recrawl. Building organic visibility in a genuinely new market takes as long as it would for a new site, typically six to twelve months for competitive terms, because authority in that market has to be earned through local link building and content. Restructuring from ccTLDs to subfolders (or the reverse) is a migration and carries migration risk; we run it with the same benchmarking and redirect discipline as any other under our technical SEO service.
International SEO works best alongside a broader programme, so it is usually scoped as part of our full SEO services. Where paid search is running in the same markets, we coordinate with our PPC team so keyword and landing page decisions are consistent across channels.