Language and market are two different axes. Most international sites only model one.
Arabic in Cairo and Arabic in Riyadh are one language and two markets. English in Dubai and English in London are one language and two markets. Structures that treat language as a proxy for market are why multi-country sites underperform in every country except the one they were built for.
Review our international structure-
Structure
- Subdirectories, subdomains or country domains, decided on the actual trade-off rather than a default.
-
Hreflang
- Reciprocal, self-referencing, and with region codes used properly. Most implementations we inherit fail at least one of those.
-
Real localization
- Prices, payment methods, delivery, legal text and support hours. The parts that decide conversion, not just translation.
-
Consolidate or split
- Some clients need five sites merged. Some need one site split. We will tell you which, including when the answer is neither.
The structural decision
Subdirectories, subdomains or country domains
Expensive to reverse. Worth an hour of argument before anyone builds anything.
Subdomains sit between the two and usually inherit the disadvantages of both. We recommend them rarely and always with a stated reason.
How an international engagement runs
-
Market and structure audit
Weeks 1 to 3
- Every market, language and URL variant currently live, mapped
- Hreflang validated pair by pair, including reciprocity and self-reference
- Canonical conflicts between language versions, which is the common fault
- Traffic and conversion split by market rather than pooled into one number
-
Structure decision
Weeks 3 to 4
- A recommendation with the trade-off written down, not a default
- Migration scope and risk if a change is warranted
- Explicit statement if the answer is that your current structure is fine
- Agreed with your engineering and legal teams before anything moves
-
Implementation
Weeks 4 onward
- Hreflang built correctly and monitored, not set once
- Local content beyond translation: pricing, payment, delivery, legal, support
- Local entity signals per market so each one resolves independently
- Per-market internal linking rather than everything pointing home
-
Reporting
Monthly
- Rankings, traffic and conversion per market and per language, never blended
- Hreflang errors caught as they appear rather than at the next audit
- Market-by-market share of the queries that matter
- In the portal, with each market on its own view
How we report it
The clients behind the claims on this page
Multi-market engagements with published numbers, plus the per-engine citation data that shows why one blended score never describes a multi-market brand.
Delta Medical Labs
5,570 pages cited across AI assistants, July 2026
Eduverse
171 pages cited across AI assistants, August 2026
- 89.1%of the sites ChatGPT cites, Perplexity never touches for the same questionWellows, 804,058 answers, Sept 2025 to May 2026
- 79.6%of sources appear on one engine only22.7M citations across 1,146,483 questions, 2026
- 46xgap in brand citation rate between ChatGPT at 0.59% and Perplexity at 13.05%Study of 34,234 AI responses, 2026
Delta’s AI Overview count is 27 times its ChatGPT count. Eduverse’s top and bottom engines sit 18 pages apart. Same agency, same method, opposite shapes. Any single score we quoted you would have described neither.
Review our international structureClient reviews
All reviewsWhat we inherit
Three structural mistakes on multi-market sites
All three are expensive to reverse, which is why they are worth naming before anyone builds anything.
Language used as a proxy for market
One Arabic version for Egypt and the Gulf, or one English version for the UAE and the UK. It looks efficient on a budget line.
Model language and market as two axes. Shared content stays shared, commercial pages split by market.
Arabic pages canonicalised to English
A plugin default nobody revisited. It tells Google to ignore the Arabic version entirely and it is invisible in normal reporting.
Reciprocal hreflang pairs and self-referencing canonicals, verified per template.
Translation without localisation
Prices, payment methods, delivery expectations and phone formats left as the home market. The page ranks and does not convert.
Localise what decides conversion, not just what decides ranking.
Questions about international SEO
Subdirectories for most companies, because authority is shared and the running cost is one site. Country domains when you need genuine legal or brand separation, or when a local domain is a trust requirement in that market. The reasoning gets written down either way.
Often, yes. It is one language and several markets with different currencies, competitors and sometimes different products. Whether it justifies separate versions depends on how much actually differs, and we will tell you if it does not.
Send us the URL. The three faults we find most are missing self-references, non-reciprocal pairs, and Arabic pages canonicalised to their English twins. The last one is invisible in normal reporting and it suppresses the Arabic market entirely.
Translate what is worth ranking in that market, and localize what decides conversion. A translated page with the home market’s currency, payment methods and phone format is a page that ranks and does not convert.
Common, and usually the right answer is consolidation. It is a real migration with real risk, so it gets planned properly. Our SEO migration page covers how we run that kind of move.
Yes. Assistants answer differently by market and language from different source pools. A brand strong in English and absent in Arabic reads as two different companies to an engine.
