Bilingual SEO for Arabic and English Pages

Bilingual SEO for Arabic and English pages works when each language is researched, written and measured as its own market, not when the Arabic side is a copy of the English one. The pages that rank and convert start from separate keyword research, use transcreation for anything that sells, and give Arabic visitors a conversion path built for them. This guide covers that content and conversion side; the technical markup is covered elsewhere.

What bilingual SEO actually involves

Most UAE businesses already know they need hreflang tags and a right to left layout. Those are necessary, and our guide to planning a bilingual site before design starts explains where they fit. But markup only tells Google that two pages are equivalents. It does not make either page good, and it does not make the Arabic page match what Arabic searchers type.

Bilingual SEO is the work that sits on top of the markup:

• Finding what each audience searches for, in its own words.
• Deciding which pages need translation and which need transcreation.
• Writing titles, headings and descriptions natively in each language.
• Making forms, calls to action and trust signals work in Arabic as well as they do in English.
• Reporting on each language separately so problems are visible.

How Google reads a two language site

Google's documentation on managing multilingual and multi regional sites sets three points worth keeping in mind. It recommends a different URL for each language version. It determines the language of a page from the visible content, not from the lang attribute or the URL. And it advises against translating only the boilerplate, such as menus and footers, while the main content stays in one language. In practice, an Arabic page with an Arabic menu and English body copy is treated as an English page.

Separate keyword research for each language

Translating an English keyword list into Arabic is the most common mistake in Arabic SEO. A literal translation is often not what people search for. Some terms are searched in English even by Arabic speakers, some have two or three common Arabic forms, and some concepts are phrased differently altogether.

Start from the market, not the English list

Run Arabic research from Arabic seed terms. Useful sources include:

• Search Console. Filter queries by the Arabic directory or subdomain to see what already brings impressions.
• Autocomplete and related searches in Google with the interface set to Arabic.
• Sales and support conversations. The words Arabic speaking customers use on calls and WhatsApp are often better seeds than any tool.

Expect mixed language and spelling variants

Arabic searches in the UAE are not uniform. Brand names, software products and technical terms are often typed in Latin script inside an otherwise Arabic query. The same word can be spelled with or without certain letters or diacritics. Some users write Arabic in Latin characters. Group these variants by checking whether they return the same results, the method explained in our guide to keyword clustering, rather than creating a page for each spelling.

Map keywords per language, then align the pages

Build two keyword maps and only then compare them. Most pages will pair up: an English service page and an Arabic service page targeting the same need. Some will not. An Arabic audience may care about a question the English audience never asks, which can justify an Arabic only article. The reverse also happens. The structure does not have to be a perfect mirror, as long as each page that does have an equivalent is linked with hreflang.

Translation versus transcreation

Not every page needs the same treatment. Translation keeps the meaning and structure of the source. Transcreation rewrites the message for the target audience, keeping the intent but changing examples, emphasis, headlines and sometimes the order of sections.

When translation is enough

• Policies, terms and legal pages, where accuracy matters more than persuasion. Have these reviewed by counsel.
• Product specifications and technical documentation.
• Help centre articles that describe steps in an interface.

When transcreation pays off

• Home page, service pages and landing pages, where the job is to persuade.
• Headlines, title tags and meta descriptions, which must contain the Arabic keyword and still read naturally.
• Calls to action and form labels, where a literal phrase can sound stiff or unclear.
• Case studies and examples, which may need local references to land.

Machine translation can be a useful first draft, but publishing it at scale without review is risky. Google's spam policies list automated transformations such as translating among the techniques that count as scaled content abuse when they add little value for users. A native editor who knows the subject should review every page that is meant to rank.

Hypothetical example: a Dubai logistics company translates its English home page headline literally into Arabic. The result is grammatically correct but reads like a manual, and it does not include the phrase Arabic buyers actually search. A transcreated headline names the service the way customers describe it on the phone, places the main keyword naturally, and keeps the same promise. Nothing else on the page changes, yet the Arabic page now has a target it can rank for.

Arabic content optimisation on the page

Arabic content optimisation follows the same principles as English on page work, with a few details that are easy to miss.

Titles, headings and descriptions

Write the Arabic title tag and meta description from the Arabic keyword map, not by translating the English ones. Arabic text can take more or less space than English, so check how titles display in results. Headings should describe what follows in plain Arabic; a heading that only makes sense in English will not help the page.

Images, alt text and structured data

Alt text, captions and any text inside images need Arabic versions. Structured data on Arabic pages, such as the name and description in an Organization or Service block, should be in Arabic to match the visible content.

Internal links

Link Arabic pages to other Arabic pages with Arabic anchor text. A common fault is an Arabic article whose related links all point to English URLs because the CMS pulls them from a shared list.

RTL conversion UX: where Arabic visitors drop off

Ranking an Arabic page is only half the work. If the enquiry path breaks in Arabic, the traffic is wasted. RTL conversion UX is about the moments where a visitor decides to act.

Forms

• Labels, placeholders and error messages should all be in Arabic, including validation messages produced by plugins.
• Phone and email fields usually need to stay left to right inside an Arabic form, or numbers and addresses display in a confusing order.
• Test whether the form accepts Arabic characters in name and message fields, and whether the notification email shows them correctly.

Calls to action and contact options

Button text should be short and natural in Arabic. If WhatsApp is the preferred contact method, make sure the prefilled message is in Arabic on Arabic pages. Phone numbers should be clickable and displayed in a readable direction.

Trust signals

Reviews, certifications the business genuinely holds, and project examples should appear on Arabic pages too.

Measuring each language separately

A bilingual site should be reported as two sites that share a domain. Set up the following:

1. Search Console filters or properties for each language folder, so impressions, clicks and queries can be compared.
2. Analytics segments by language for sessions, engagement and conversions.
3. CRM fields that record which language version a lead came from, so sales can see lead quality by language.
4. Separate conversion events or thank you pages per language, so you can see whether Arabic pages convert at all.

Review the Arabic queries that bring impressions but few clicks. They usually point to a title that does not match the search, or to a page that answers a slightly different question. Our article on SEO data that guides decisions covers how to turn reports like this into actions.

A practical workflow for bilingual pages

1. Build the English and Arabic keyword maps separately.
2. Compare the maps and decide which pages pair, which are language specific, and which need transcreation.
3. Write a short brief per page in each language: keyword, intent, key points and call to action.
4. Draft, then have a native Arabic editor with subject knowledge review every page meant to rank.
5. Check forms, buttons, WhatsApp links and thank you pages in Arabic on a phone.
6. Publish with hreflang links between true equivalents only.
7. Report on each language monthly and revise the weakest pages first.

For larger sites going through a redesign, these decisions belong in the rebuild plan rather than after launch. Our guide to planning an enterprise rebuild that keeps SEO, UX and governance explains how to include them. If the business also relies on maps visibility, see local SEO for Dubai service businesses.

Get your Arabic pages working as hard as your English ones

Codeeo plans and builds bilingual websites and runs digital marketing and SEO for UAE businesses, including Arabic keyword research, content structure and the right to left conversion path. The team of 80+ works from Dubai, Riyadh and Karachi, and UAE clients can meet the team at the Dubai office. Explore digital marketing and SEO, website development and UI/UX design, start with a technical SEO review, or contact Codeeo to talk through your Arabic and English pages.