Short answer: bilingual SEO for a WordPress site in English and Arabic comes down to four things. Give each language its own URL (usually /en/ and /ar/ folders), link the matching pages together with hreflang tags, write Arabic content and keywords from research rather than direct translation, and build the Arabic version as a proper right-to-left layout. Do not automatically redirect visitors by location; let them choose, and let Google index both versions.
Businesses in the UAE, Saudi Arabia, Qatar and the wider Gulf often add Arabic as an afterthought: an English site with a translation plugin bolted on. The result is usually an Arabic version Google barely indexes and customers find awkward to use. Getting bilingual SEO right is not complicated, but the order matters.
On this page
- Bilingual SEO structure: folders, subdomains or separate domains?
- How do hreflang tags work?
- Why doesn't direct translation rank?
- What changes in a right-to-left design?
- Should you redirect visitors by location?
- What does a launch checklist look like?
- Keyword research for bilingual SEO in the Gulf
- Questions Gulf businesses ask us
Bilingual SEO structure: folders, subdomains or separate domains?
StructureExampleWhen it fits Foldersexample.com/en/ and example.com/ar/Most small and mid-sized businesses. Both languages share the domain's authority. Subdomainsen.example.com and ar.example.comWhen each language is run by a different team or on different systems. Separate domainsexample.ae and example.comWhen you have genuinely separate businesses or brands per country. For most businesses, folders are the right answer. They are the simplest to manage on WordPress and let links to either language help the whole site.
How do hreflang tags work?
Hreflang tells Google that two pages are the same content in different languages, so it shows the Arabic page to Arabic searchers and the English page to English searchers, instead of treating them as duplicates. Every page lists itself and its translation, and the tags must point both ways. Google explains the rules in its guide to localised versions of pages.
On WordPress, a multilingual plugin such as WPML or Polylang generates these tags for you when translations are linked properly. The most common bilingual SEO mistake we see is translated pages that were never linked as translations of each other, so the plugin has nothing to connect.
Why doesn't direct translation rank?
Because people do not search the way a translator writes. Arabic searchers in the Gulf mix Modern Standard Arabic, local dialect and English terms, often in the same query, and many search for services in English even when they browse in Arabic. Research Arabic keywords separately, using search suggestions and your Arabic-speaking customers' own words, then write the Arabic page around those terms. The English and Arabic pages will cover the same service but will not be word-for-word mirrors, and that is fine.
Each Arabic page needs its own title, meta description and URL. A useful rule: if a native speaker would not naturally say it, do not put it in a heading.
What changes in a right-to-left design?
-
Direction: the Arabic version needs
dir="rtl"and a layout that mirrors properly, not just right-aligned text. Menus, icons that imply direction and sliders all flip. - Fonts: choose an Arabic web font designed for screens, load only the weights you use, and check line height, because Arabic script needs more room.
- Forms and numbers: test phone and address fields in Arabic, and decide whether to show Western or Arabic-Indic numerals consistently.
- Speed: an extra font family adds weight. Treat the Arabic site's Core Web Vitals as their own project, using the same approach as our page builder speed guide.
Should you redirect visitors by location?
No. Automatically sending people to a language based on their IP address frustrates expatriates, travellers and the many Gulf residents who prefer English, and it can stop Google crawling one of your versions. Show a clear language switcher in the header and remember the visitor's choice.
What does a launch checklist look like?
The general technical basics behind this, such as indexing, sitemaps and canonicals, are in our technical SEO checklist.
- Both languages in their own folders, each page linked to its translation
-
Hreflang tags pointing both ways, plus an
x-defaultfor the language chooser or main version - Separate Arabic titles, descriptions and URLs
- An XML sitemap that includes both languages
- Right-to-left layout tested on real phones
- A Google Business Profile with details in both languages, if you serve customers locally
Keyword research for bilingual SEO in the Gulf
The biggest mistake we see is treating the Arabic site as a translation job. Searchers in Dubai, Riyadh or Doha do not type the Arabic equivalent of your English keywords. They use their own phrases, often a mix of Arabic and English, and sometimes Arabic words typed in Latin letters.
Research each language separately
Start from the Arabic side with a native speaker who knows the market. Look at what competitors rank for, what Google suggests as you type and which questions appear in the People Also Ask boxes. You will usually find the Arabic keyword list only partly overlaps the English one, and that some of your best Arabic terms have no neat English match.
Mind the dialect
Modern Standard Arabic suits formal pages, but everyday searches often lean towards Gulf usage. A service page for a Dubai clinic and one for a Cairo clinic should not read the same. Where you target more than one country, decide which market each page is really for rather than trying to please everyone with one version.
Plan for mixed searches
Brand names, product models and technical terms are often searched in English, even by Arabic speakers. Keep those terms in English on the Arabic pages where that is how people write them, and make sure the text around them is natural Arabic.
Give each language its own metadata
Every Arabic page needs its own title, meta description and URL slug written for Arabic searchers, not copied from the English page. Rank Math and Yoast both handle this per language when paired with WPML or Polylang.
Measure the two sites separately
In Google Search Console, filter by the /ar/ and /en/ folders so you can see how each language performs. Bilingual SEO often moves at different speeds: the English pages may rank quickly on brand terms while the Arabic pages take longer because the content is newer. Judge each on its own trend, and add Arabic content where the gaps show.
Google's guidance on managing multi-regional and multilingual sites is worth reading before you settle on a structure.
Questions Gulf businesses ask us
Which plugin is better, WPML or Polylang?
Both handle hreflang and translated URLs well. WPML suits larger sites and WooCommerce stores with many translated products. Polylang is lighter and fine for most service businesses. The plugin matters less than linking translations properly.
Do I need separate meta titles for the Arabic pages?
Yes. Write them in Arabic, around the terms Arabic searchers actually use. An English title on an Arabic page wastes the most visible line in the search result.
Why isn't my Arabic content being indexed?
The usual causes are missing or one-way hreflang tags, Arabic pages left out of the sitemap, a canonical tag pointing at the English version, or a location redirect that stops Google reaching the Arabic pages.
Should the Arabic site be a full copy of the English one?
Start with the pages that bring in enquiries: home, main services, contact, and your strongest case studies. A smaller, well-written Arabic site beats a full machine translation.
Planning a bilingual site?
We build multilingual WordPress sites and handle their bilingual SEO as part of our website development and SEO services. Tell us about your market through the contact page and we will suggest a sensible structure before anything gets built.
