International SEO Technical Setup: hreflang, CDN, and Subdomain vs Subfolder Decisions

International SEO is the discipline of ensuring your website's correct pages rank in the correct countries and languages. Without proper technical setup, a business targeting India, the UAE, and the UK with separate localised content can end up with its Indian pages ranking in the UK, its UK pages receiving zero traffic anywhere, and Google consolidating authority onto a single URL that serves the wrong intent for every market. According to Google's John Mueller, hreflang implementation errors are among the most common technical SEO mistakes on international sites — and Ahrefs' 2025 site audit data shows that 68% of international sites have at least one hreflang error. For Indian businesses expanding internationally — particularly those targeting Gulf countries (UAE, Saudi Arabia, Qatar), the UK Indian diaspora, or US markets — getting the technical foundation right is the prerequisite for all international content investment.

The Three URL Structure Options: ccTLD, Subdomain, and Subfolder

The first technical decision in international SEO is how to structure your URLs for different countries and languages. Three options exist: country-code top-level domains (ccTLDs like example.co.uk or example.ae), subdomains (uk.example.com or ae.example.com), or subfolders (example.com/uk/ or example.com/ae/). Each has different implications for SEO, development effort, and authority distribution. ccTLDs are the strongest geographic targeting signal for Google — example.co.uk tells Google clearly that this domain is for the UK. However, each ccTLD is treated as a separate website by Google, meaning authority does not transfer between them. Building a new ccTLD from zero domain authority is a significant SEO investment. Subdomains (uk.example.com) send a moderate geographic signal and are treated as separate crawl units by Google, though Google has stated they give some credit to the main domain's authority. Subfolders (example.com/uk/) are typically the recommended choice for most businesses: they consolidate all authority under one domain, are easiest to maintain, and provide sufficient geo-targeting signal when combined with Google Search Console's country targeting feature. Ahrefs' internal research found that subfolder-based international sites average 48% more organic traffic than equivalent subdomain-based sites, largely because of consolidated domain authority.

ccTLD (example.co.uk): strongest geo signal but no authority transfer — best for large businesses with resources to build separate domains
Subdomain (uk.example.com): moderate geo signal, partial authority transfer — better than ccTLD for smaller businesses
Subfolder (example.com/uk/): consolidated authority, easiest to maintain — recommended for most businesses
Ahrefs data: subfolder sites average 48% more organic traffic than subdomain equivalents
Google Search Console country targeting can supplement subfolder geo signals
Once you choose a URL structure, changing it requires a full migration — choose carefully

hreflang: The Complete Implementation Guide

hreflang is an HTML attribute that tells Google which version of a page to show in which country and language. Without it, Google may show your Indian English page to users in the UK, or your Hindi page to users searching in English in the US. The hreflang tag uses ISO 639-1 language codes (en, hi, ar) and optional ISO 3166-1 alpha-2 country codes (IN, GB, US, AE). Common implementation examples: for a page targeting English speakers in India, use hreflang='en-IN'. For UK English, use hreflang='en-GB'. For Hindi speakers in India, use hreflang='hi-IN'. For Arabic in UAE, use hreflang='ar-AE'. The hreflang tag must be reciprocal: if page A points to page B via hreflang, page B must also point back to page A. This bidirectional requirement is the most common hreflang error — one-directional implementations are ignored by Google. Implement hreflang in one of three locations: in the <head> section of the HTML, in the XML sitemap (recommended for large sites), or in HTTP headers (for non-HTML files like PDFs). The XML sitemap implementation is most manageable for sites with hundreds of pages and multiple language versions.

1Use ISO 639-1 language code + optional ISO 3166-1 country code (e.g., en-IN, en-GB, hi-IN, ar-AE)
2Add hreflang tags to the <head> of every page, OR in the XML sitemap
3Every page must link to all variants including itself (self-referential hreflang required)
4All implementations must be reciprocal: if A points to B, B must point to A
5Add x-default hreflang for the fallback page shown when no country match is found
6Validate implementation using Google Search Console's International Targeting report
7Use Ahrefs Site Audit or Semrush's Site Audit to detect hreflang errors automatically

x-default hreflang: What It Is and When to Use It

The x-default hreflang attribute is the fallback instruction — it tells Google which page to show when no language or country-specific version matches the searcher's context. For example, if you have English versions for India, UK, and US, but a user in South Africa searches for your product, Google needs to know which version to show. Without x-default, Google makes its own decision, which may not align with your business goals. Implement x-default on the page you want to serve as your global fallback — usually your primary English domain root or a language-selection page. The tag syntax is: link rel='alternate' hreflang='x-default' href='https://example.com/'. A common mistake is applying x-default to the US English version when the business is India-focused — this causes Google to surface the US page for all unmatched countries, potentially confusing visitors from those markets. For Indian businesses expanding to the UAE and UK, the recommended setup is: en-IN for the Indian version, en-GB for the UK version, en-AE or ar-AE for the UAE version, and x-default pointing to the Indian version (your primary market) as the fallback.

x-default hreflang is the fallback for users in countries not specifically targeted
Point x-default to your primary market's version — for Indian businesses, this is typically the en-IN page
Without x-default, Google decides which page to show unmatched users — often incorrectly
x-default can also point to a language-selection landing page if you want users to self-select
Include x-default in every page's hreflang set even if you only target 2 countries

CDN Configuration for International SEO

A Content Delivery Network (CDN) serves your website from geographically distributed servers, reducing page load time for international visitors. For international SEO, CDN configuration affects two things: user experience (page speed, which is a Google ranking factor) and Googlebot crawling (Google uses servers in multiple countries to check geo-targeted content). Cloudflare is the most widely used CDN for international SEO, used by over 20% of all websites. For a subfolder-based international site (example.com/uk/, example.com/ae/), configure your CDN to cache each subfolder independently and set cache rules that respect the Accept-Language and geo-location headers. A critical CDN-related SEO issue: some CDN configurations automatically redirect users based on detected location (IP geolocation redirect) — redirecting a UK user from example.com to example.co.uk without preserving the original URL. This breaks Googlebot's ability to crawl all versions and prevents link equity from accumulating on the correct URLs. If your CDN offers geo-redirect functionality, implement it as a JavaScript-based suggestion ('We noticed you are in the UK — view our UK site?') rather than an automatic server-side redirect, which Googlebot will follow and potentially disrupt international targeting.

CDN reduces page load time for international visitors — improves user experience and rankings in each market
Cloudflare: most widely used CDN — configure subfolder caching independently for each country version
Avoid automatic IP-based geo-redirects — they prevent Googlebot from crawling all language versions
Use JavaScript-based geo-suggestions instead of server-side redirects for user experience
Verify Googlebot can access all international versions using URL Inspection in Google Search Console
Set appropriate Cache-Control headers per country version to prevent serving stale localised content

Content Localisation vs Translation: What Google Rewards

A technically perfect hreflang and subfolder setup does not help if your 'localised' content is simply machine-translated copy with the country name swapped. Google's quality guidelines are clear: content that is translated without meaningful localisation provides minimal additional value and will not rank significantly better than the original language version. True localisation means: using local currency and pricing norms (AED for UAE, GBP for UK, not USD globally), referencing local regulations, tax structures, and compliance requirements relevant to that market, using local spellings and idioms (labour not labor for UK, colour not color), including local case studies and testimonials from businesses in that country, and addressing the local market's specific pain points and context. For an Indian digital marketing agency targeting the UAE market, a localised page should reference VAT compliance in UAE, specific UAE business licensing requirements, Arabic-language market reach, and Gulf-specific competitive dynamics — not just replace 'India' with 'UAE' in the copy. The additional ranking signal from genuine localisation is significant: Semrush's international SEO study found that genuinely localised pages rank an average of 6-9 positions higher than translated-only pages for competitive queries in their target market.

Machine translation alone is insufficient — Google rewards genuine localisation, not word substitution
Localise: currency, pricing norms, local regulations, local case studies, local spelling conventions
Genuinely localised pages rank 6-9 positions higher than translated-only pages (Semrush)
Include local testimonials and customer logos from businesses in the target country
Reference country-specific compliance, legal, or regulatory context to signal genuine local relevance

Diagnosing and Fixing Common International SEO Errors

Even correctly designed international SEO architectures frequently develop errors over time as the site grows. The five most common international SEO errors: (1) Missing return tags — hreflang is implemented on Page A pointing to Page B, but Page B does not point back. Fix: audit all hreflang tags with Ahrefs Site Audit's hreflang report. (2) Inconsistent URLs — hreflang tags point to URLs with trailing slashes in some places and without in others, creating different page versions. Fix: standardise all URLs in hreflang tags to a single format and ensure canonical tags match. (3) Canonicals conflicting with hreflang — a page has a canonical pointing to a different URL while also having hreflang tags. Google will prioritise the canonical and may ignore hreflang. Fix: ensure canonical and hreflang tags on each page are consistent. (4) Indexing blocked on some language versions — robots.txt or noindex meta tags blocking a language subfolder while other versions are indexed. Fix: crawl all subfolders with Screaming Frog and verify indexability. (5) Google Search Console country targeting set incorrectly — subfolder international sites require country targeting set separately for each subfolder property in GSC. Fix: create separate GSC properties for each international subfolder and set country targeting in each.

1Run Ahrefs or Semrush Site Audit — navigate to hreflang section, fix all flagged errors
2Check for canonical/hreflang conflicts: canonical must point to the same URL as the hreflang self-reference
3Verify all international subfolders are indexable: no noindex tags, no robots.txt blocks
4Create separate GSC properties for each subfolder (example.com/uk/) and set country targeting
5Validate hreflang tags with Google's Rich Results Test or Merkle's hreflang tags testing tool

International SEO technical setup is one of the highest-leverage investments for Indian businesses expanding to Gulf markets, the UK Indian diaspora, or US markets. The technical foundation — URL structure, hreflang implementation, CDN configuration, and genuine localisation — takes 4-8 weeks to implement correctly but determines whether 12 months of subsequent international content investment produces rankings or nothing. Get the architecture right first, then scale localised content on top of it.

Frequently Asked Questions

Should Indian businesses use subfolders or subdomains for international SEO?

Subfolders (example.com/ae/, example.com/uk/) are recommended for most Indian businesses expanding internationally. They consolidate domain authority under one domain, are easier to maintain, and Ahrefs data shows subfolder-based international sites average 48% more organic traffic than subdomain equivalents due to consolidated link equity.

What is hreflang and why is it necessary?

hreflang is an HTML attribute that tells Google which version of a page to show in which country and language. Without it, Google may serve your Indian page to UK searchers, or your Hindi page to English speakers. It is essential for any website with content in multiple languages or targeting multiple countries.

What are the most common hreflang implementation mistakes?

The three most common errors: (1) Missing return tags — hreflang must be bidirectional, every page must reference all variants including itself; (2) Canonical conflicts — canonical tags pointing to a different URL than the hreflang self-reference confuse Google; (3) Inconsistent URL formats — mixing trailing slash and non-trailing-slash URLs in hreflang tags creates duplicate entries.

How does CDN affect international SEO?

CDN improves page load speed for international visitors, which is a Google ranking factor. Properly configured CDNs serve content from servers geographically close to the user. The key CDN risk for international SEO is automatic IP-based geo-redirects, which can prevent Googlebot from crawling all language versions — use JavaScript-based suggestions instead of server-side redirects.

Does translated content rank for international markets?

Machine translation alone ranks poorly — Google's quality systems identify thin translated content. Genuine localisation that addresses local pricing, regulations, case studies, testimonials, and market context ranks significantly better. Semrush found genuinely localised pages rank 6-9 positions higher than translated-only pages for competitive international queries.

How do I set up Google Search Console for an international site?

Create a separate GSC property for each international subfolder — example.com/uk/ requires its own property separate from example.com. Within each property, use the International Targeting report to set the country target. This supplements your hreflang implementation and gives Google an additional geographic signal for subfolder-based international sites.

How long does it take to rank internationally after implementing these technical changes?

Technical implementation alone does not produce rankings — it enables the localised content to rank. After correct technical setup, well-localised pages targeting low-to-medium competition queries in new markets typically show first page rankings within 3-6 months. Competitive queries in established markets like the UK may take 9-18 months depending on domain authority and content quality.

← Back to all articles