Subdomain vs subfolder vs ccTLD for multilingual websites
Use a subfolder like /ar/ for most multilingual sites. When a subdomain or a country domain makes sense instead, what each costs, and what Google says.
By Sohail Hussain15 November 20266 min read
Use a subfolder, such as example.com/ar/, unless you have a specific reason not to. It keeps one domain, one hosting setup and one analytics account, and Google supports it fully through hreflang. A country domain such as example.ae or example.sa makes sense when each country is run as its own business with its own offer. A subdomain such as ar.example.com makes sense mainly when the second language runs on separate infrastructure. Query parameters such as ?lang=ar, and switching language with a cookie at the same URL, are not options for a public site.
That is the default we apply on every Arabic and multilingual website we build, and the reasoning is below. For the rest of the setup, start with the guide to building an Arabic website.
What are the options, and what does Google say about each?
Google's page on managing multi-regional and multilingual sites lists four structures with their pros and cons. In summary:
| Structure | Example | Setup and upkeep | Country signal | Google's main caveat |
|---|---|---|---|---|
| Subfolder on one domain | example.com/ar/ | Easiest: same host, same deployment | None by itself | Visitors may not tell from the URL which country it targets |
| Subdomain | ar.example.com | Moderate: separate site config, can be hosted elsewhere | None by itself | Visitors may not know if "ar" is a language or a country |
| Country domain (ccTLD) | example.ae | Hardest: one domain, one site and one set of links per country | Strong | Expensive, sometimes restricted, and targets only one country |
| URL parameter | example.com/?lang=ar | Looks easy | None | Google does not recommend it |
Google also recommends a different URL for each language version, rather than switching content with cookies or browser settings. Googlebot usually crawls from the United States without sending a language preference, so a site that changes language by cookie or browser setting may only ever be indexed in one language.
Are you targeting a language or a country?
This question decides the structure more than any other.
Language targeting means one Arabic version for every Arabic reader, wherever they are. That is the case for most company sites: the services, prices and contact details are the same for a reader in Dubai, Riyadh or Cairo. Use a language folder: /ar/.
Country targeting means the content differs by country: different prices, currencies, products, phone numbers or legal terms. Then the structure needs a country part, such as /ae/ and /sa/, or /ae/ar/ and /ae/en/ when each country also has two languages, or a separate country domain.
Do not create country versions with identical content. Google notes that targeting one country can improve rankings there at the expense of results in other places. Three Arabic copies of the same page labelled UAE, Saudi and Egypt add maintenance and split your signals for no gain. Hreflang explained shows how to label language and country versions correctly once you have them.
Why do subfolders suit most businesses?
Google does not say subfolders rank better than subdomains. The case for subfolders is practical, and it is strong:
- One domain. The site's history and the links it has earned belong to one address, and the Arabic section starts life inside it rather than as a new site.
- One deployment. One codebase, one CMS, one SSL certificate, one set of redirects.
- One Search Console property. You can still add a URL-prefix property for
https://example.com/ar/to see Arabic data on its own. - One analytics stream. Filter by path to compare languages, with no cross-domain tracking to configure.
The downsides Google lists for subfolders are minor for a language-based site. Visitors can tell /ar/ is Arabic once they see the page, and the single server location stops mattering once a CDN serves the site.
When does a country domain make sense?
A ccTLD is the strongest country signal a site can send. Google calls it a strong signal to both users and search engines that the site is intended for one country. It earns its cost when:
- each country is a separate legal entity, with its own team, offer and marketing;
- local presence matters to buyers, such as government or large corporate clients who expect a
.aeor.saaddress; or - you need to keep the sites separate for legal, data or branding reasons.
The costs are real. Each domain is registered and renewed separately; as of October 2026, a .ae costs around AED 100 to 250 a year, and .sa requires a Saudi presence such as a registered company or trademark. Each domain starts with no history, needs its own Search Console property, and earns its own links. A .ae site is also a poor fit for readers in Saudi Arabia, because it targets one country only. The registration rules for each extension are in .com vs .in vs .ae.
When does a subdomain make sense?
Rarely, for language versions. A subdomain is the right tool when the Arabic site really is a separate system: a different platform, a different hosting location required for data reasons, or a different vendor running it. If none of those apply, a subdomain gives you the separate-site overheads of a ccTLD without the country signal.
Should the URL slugs be translated too?
Both options work for search. Google's guidance says localised words in URLs are acceptable, as long as you use UTF-8 and escape the URLs properly.
English slugs under the Arabic folder, such as /ar/services, are easier to type, share and maintain, and hreflang pairs are simpler to generate because the paths match. Many Gulf business sites do this.
Arabic slugs, such as /ar/خدماتنا, read naturally to Arabic users and show in Arabic in the address bar of current browsers. Copied into an email or some chat apps, they turn into percent-encoding: those seven Arabic letters become %D8%AE%D8%AF%D9%85%D8%A7%D8%AA%D9%86%D8%A7, 42 characters long. Paste a URL into our URL encoder and decoder to see what yours will look like when shared.
If you translate slugs, the CMS has to store which slug matches which in every language, because the hreflang tags and the language switcher both depend on that mapping.
What should you avoid?
- Query parameters for language, such as
?lang=ar. Google does not recommend them, and they are easy to lose in links. - One URL that changes language by cookie, browser setting or a JavaScript toggle. Search engines see one version; visitors cannot share a link to the other.
- Automatic redirects by IP address or browser language. Google advises against them, because they can stop both users and crawlers reaching every version. Link the versions to each other and let people choose.
- Changing structure after launch without a plan. Moving from a subdomain to a subfolder, or from
/servicesto/en/services, is a migration: every old URL needs a 301 redirect to its new address and every hreflang tag must be regenerated. Migrating a website without losing SEO covers the process.
Choose the structure before the first Arabic page is published. It is the one decision in a multilingual project that is expensive to change later.
Was this guide useful?