Subfolder vs Subdomain for Arabic: Which to Use
A subfolder like /ar/ shares your domain's authority; a subdomain runs independently. Here is how to choose for an Arabic section of your site.
For most sites, a subfolder such as example.com/ar/ is the better choice for Arabic content, because it shares the main domain's authority and needs only one property to manage. A subdomain or country domain earns its keep only when a different team, CMS or hosting setup genuinely requires the separation.
This is one of the technical decisions covered in the full Arabic SEO guide; get it right once, because changing it later means redirecting every URL in your Arabic section.
On this page
What actually differs between a subfolder, a subdomain and a country domain?
Technically, not much from a crawling standpoint — Google can discover, crawl and index content on any of the three [1]. What differs is authority sharing, operational independence and how much work each one takes to set up and maintain well.
A subfolder, example.com/ar/, is treated by search engines as part of the same site as the rest of example.com. It inherits the domain's existing trust, backlink profile and crawl budget from day one. A subdomain, ar.example.com, is closer to its own entity: it can be hosted separately, run a different CMS, and in some analytics and reporting tools it behaves like a distinct property, even though search engines still associate it with the parent brand. A country domain, example.sa, is legally and technically its own website with no inherited authority at all.
| Structure | Example | Inherits domain authority | Setup effort | Best for |
|---|---|---|---|---|
| Subfolder | example.com/ar/ | Fully | Lowest — same stack, same CMS | Most businesses adding an Arabic section |
| Subdomain | ar.example.com | Shared but weaker in practice | Medium — can reuse or separate infrastructure | A different team or CMS running Arabic content |
| Country domain | example.sa or example.ae | None — starts from zero | Highest — a second domain to run and defend | A standalone regional entity or legal requirement |
Why does a subfolder win for most businesses?
Because it is the path of least resistance for both search engines and your own team. New Arabic pages under /ar/ benefit immediately from whatever trust the rest of the domain has already earned, rather than starting from nothing. One domain also means one sitemap strategy, one set of analytics properties to reconcile, and one place for a developer to look when something breaks.
There is a quieter operational reason too: a subfolder is harder to neglect. Because it lives inside the same repository and deploy pipeline as the main site, it tends to get updated when the main site does. A subdomain, especially one run by a different team or vendor, is easier to treat as a side project — and an Arabic section that goes stale loses more than an English one would, because Arabic readers notice outdated prices and offers just as quickly as anyone else.
Confirm your CMS can handle two languages cleanly
Check that it supports right-to-left rendering, a separate URL prefix and independent metadata per language before committing to a subfolder.
Pick one URL pattern and apply it everywhere
Decide between example.com/ar/ and example.com/ar-sa/ once, based on whether you need country-level targeting, and never mix patterns across the section.
Set self-referencing hreflang on every page
Each language version should list itself and every sibling version, plus an x-default for everyone else.
Route the Arabic homepage and every parent page
A visitor landing on /ar/ should reach every major section without falling back into an English-only page.
When does a subdomain make more sense?
When the constraint is real and structural, not just a preference. The clearest case is a different team, agency or CMS running the Arabic side of the business — a subdomain lets that team deploy independently without touching the main site's codebase. Another is a technical stack that genuinely cannot serve two languages from one application without a costly rebuild.
A subdomain is not a downgrade in Google's eyes; the company has said publicly that a subdomain can rank just as well as a subfolder when the content and authority-building are equally strong [1]. The real cost is discipline: someone has to make sure the subdomain gets the same investment in content, links and maintenance as the main site, because nothing about the structure enforces that automatically.
When is a separate country domain worth it?
When local presence has to be unmistakable, usually for legal, regulatory or trust reasons rather than pure SEO ones. A country-code domain such as .sa or .ae tells a user, at a glance, that the business is locally registered, which matters more in some regulated categories than a ranking edge ever would.
The cost is real and ongoing. A country domain starts with zero backlinks, zero history and zero accumulated trust, and building all three again from scratch takes the same work as launching a second website, because that is functionally what it is. Most companies expanding into an Arabic-speaking market do not need this; a subfolder with strong hreflang and genuinely local content does the job for a fraction of the ongoing cost.
How does the choice affect hreflang, URLs and links?
All three structures still need correct hreflang connecting every language version to every other one — the structure changes where the pages live, not whether they need to be linked to each other [2]. Get the URL pattern settled at the same time, because Arabic slugs, transliterated slugs and English slugs on the Arabic version each behave differently once real traffic hits them; we cover that separately in Arabic URLs vs transliteration.
Link building is where the structure matters most in practice. Every Arabic backlink you earn — see our list of Arabic link building sources for where those actually come from — strengthens the whole domain when it points at a subfolder page, because that authority is shared automatically. The same link pointing at a subdomain or a country domain builds up a separate pool of authority that does not flow back to the main site as directly.
| Structure | Where the earned authority lands |
|---|---|
| Subfolder | Shared with the whole domain immediately |
| Subdomain | Mostly stays with the subdomain; some signal passes to the root domain |
| Country domain | Stays entirely on that domain |
What about page speed, schema and other technical work?
Largely unaffected by which of the three you choose. Structured data still needs to describe the Arabic page correctly, with Arabic values and the right inLanguage tag, regardless of whether it lives on a subfolder or a subdomain — we walk through working examples in schema markup in Arabic. Page speed depends on your hosting and build, which a subdomain can sometimes improve by running on lighter infrastructure, but this is a secondary consideration next to authority sharing for most businesses.
Sitemaps are worth planning early either way. A subfolder can usually extend the existing sitemap or add one indexed from it; a subdomain typically needs its own sitemap submitted as its own property in Search Console [3]. Neither is hard, but forgetting it delays indexing of the whole Arabic section by weeks.
What does each structure cost to maintain, month after month?
The setup decision gets most of the attention, but the ongoing cost is where the three structures diverge more than people expect. A subfolder rides on infrastructure you are already paying for and a team that already owns it, so its marginal maintenance cost is close to the cost of producing the Arabic content itself.
A subdomain adds a second surface to keep current: its own analytics configuration in some tools, sometimes its own hosting bill, and a real risk that whoever owns it treats it as separate from the main roadmap. That risk is not technical, it is organisational — the subdomain does not fall behind because of anything about DNS, it falls behind because nobody's job explicitly includes it.
A country domain is the most expensive to maintain honestly, because it is, in every practical sense, a second website: a second SSL certificate to renew, a second set of analytics and Search Console properties to check, a second set of technical SEO basics to audit, and a second reputation to build and protect. None of that is a reason to avoid it when the business case is real, but it should be priced in before the decision is made, not discovered afterward.
What does switching structures actually involve?
More work than most teams expect going in, which is exactly why the decision is worth getting right the first time. Moving from a subdomain to a subfolder, or the reverse, is not a settings change; it is a full site migration limited to one section of the domain, and it carries the same risks any migration does if a step is skipped [3].
Map every old URL to its new equivalent
A one-to-one map, not a pattern guess, is what makes the redirect step reliable.
301 redirect every old URL individually
A blanket redirect to the new homepage loses the specific page authority each URL had built up.
Rebuild hreflang across every language version
Every Arabic page and every sibling English page needs its hreflang block reissued to point at the new addresses.
Resubmit a fresh sitemap for the new structure
Submit it in Search Console under the correct property so re-crawling starts as soon as possible.
Watch indexing and rankings for six to eight weeks
A temporary dip while search engines re-crawl and re-evaluate the new URLs is normal; a permanent one usually means a redirect or hreflang step was missed.
Budget real time for this, not just engineering hours. The pages themselves do not change, but every signal search engines have already built up around the old addresses has to transfer cleanly, and that transfer is where most of these migrations go wrong.
How do you decide, in practice?
Start from the constraint, not the preference. If nothing structurally forces a separate subdomain or domain, use a subfolder and put the authority-sharing to work. If a real team, CMS or legal boundary exists, a subdomain is a legitimate choice as long as someone owns its ongoing investment the same way they would the main site's.
Whatever you choose, commit to it. The cost of switching later is not the decision itself but the migration: every URL changes, every redirect has to be mapped one to one, hreflang has to be rebuilt, and rankings typically dip for weeks while search engines re-crawl the new structure. Decide once, with the real constraints in front of you, and build for the long term.
Write the decision down, with the reason behind it, somewhere the next person to touch the site will actually read it. The most common way teams end up debating this twice is that nobody recorded why the first choice was made, so a new hire re-opens a settled question with none of the original context.
Questions people also ask
Does Google rank one structure higher than the other?
No. Google supports subfolders, subdomains and separate country domains equally as ways to serve different language versions, and treats none of the three as a ranking advantage on its own.
Can I switch from a subdomain to a subfolder later?
Yes, but it is a migration: every URL changes, so you need redirects, an updated sitemap, refreshed hreflang and a period of watching indexing before you can call it finished.
Does a subfolder inherit my whole domain's authority automatically?
It shares the domain's overall trust and crawl budget, but each page still has to earn its own rankings through content and links; a subfolder is a head start, not a guarantee.
Is a subdomain bad for SEO?
No, and Google has said publicly it can rank a subdomain just as well as a subfolder. The practical downside is operational: it is easier for a subdomain's Arabic content to be neglected because it feels like a separate project.
What about a separate country domain like .sa or .ae?
It sends the strongest signal of local relevance to users, but it starts with zero authority and zero links, and you are effectively running two websites to maintain instead of one.
Sources
- Managing multi-regional and multilingual sites — Google Search Central (checked 23 September 2026)
- Tell Google about localized versions of your page — Google Search Central (checked 23 September 2026)
- URL structure best practices for Google — Google Search Central (checked 23 September 2026)
- SEO Starter Guide — Google Search Central (checked 23 September 2026)
Get a second opinion on your Arabic site structure
Book a free 30-minute consultation with Ibrahem and Jeremy. We look at your site while we talk, and you leave with a prioritised plan.
Who wrote this
Ibrahem HelalCo-founder
Leads strategy and delivery.
Works on: SEO, GEO
Reviewed before publishing by Jeremy Zava, Co-founder.
- Arabic SEO: the complete guide for 2026Arabic SEO is ranking pages written for Arabic searchers: research in Arabic, write natively, build a clean /ar/ section and earn Arabic links.
- How Long Should Arabic Content Be?Arabic content length should match what already ranks for the query, not a fixed word count — here is how to size a page correctly.
- 12 Arabic Link Building Sources That WorkArabic backlinks come from news sites, directories, universities, associations and original data, not bought link packages. Here is where to start.
- Schema Markup in Arabic: A Working GuideStructured data is language-neutral: property names stay in English, values go in Arabic. Here is how to write JSON-LD correctly for Arabic pages.