Bilingual SEO in Qatar often starts with a quick decision: “Let’s add Arabic.” The English pages get translated, a language switch appears in the header, and the project is declared finished.

Six months later, the Arabic pages get little traffic. Enquiries arrive, but nobody can say which language they came from. The two versions sometimes compete with each other in search results. None of this is a translation problem. It’s a planning problem, and it’s cheaper to fix before the site is built than after.

This article walks through the three decisions that shape bilingual SEO: site structure, content, and measurement.

Why translating your pages isn’t a bilingual SEO plan

Arabic and English audiences don’t always search the same way. A person looking for a service may type the query in Arabic, in English, or mix the two, depending on the topic and the device. Technical and product terms are a common example, where some people use the English term and others use an Arabic equivalent.

That means keyword research should be done per language, not copied across. A translated keyword list tells you what the English page targets in a different alphabet. It doesn’t tell you what Arabic-speaking customers actually type. Check search results in each language, look at the pages that already rank, and write for the intent you find.

Search intent also varies by audience. A procurement manager comparing suppliers and a consumer booking a service need different pages, even for the same service.

Choosing a site structure for Arabic and English

Google’s guidance on multi-regional and multilingual sites describes several URL approaches. The right one depends on your resources and how separate the two versions need to be.

Approach

Example pattern

When it suits

Watch out for

Language subdirectories

example.qa/ar/ and example.qa/en/

Most business sites. One domain, one set of analytics and one hosting setup.

Needs clean templates so each language has its own titles, headings and metadata.

Subdomains

ar.example.qa

Teams that run each language on a separate platform or with separate owners.

Extra setup for tracking, and each subdomain may need separate monitoring.

Separate domains

Different domain per language or country

Brands that serve distinct markets with different offers.

Higher maintenance cost, and authority isn’t shared automatically.

Parameters or cookies

example.qa/?lang=ar

Rarely recommended.

Search engines can struggle to find and separate the versions.

For most Qatar businesses serving both audiences from one site, language subdirectories give the simplest operating model. If you also plan to serve other Gulf markets, decide early whether Arabic content will be written for Qatar specifically or for a wider audience, because wording, offers and contact details may differ.

Tell search engines how the versions relate

When the same page exists in two languages, search engines need a signal that the pages are alternatives, not duplicates. Google documents this in its guide on localized versions of your page, using hreflang annotations.

The basics are straightforward. Each language version should point to the other, and to itself. The language and region codes need to be valid. If you add a fallback page for users whose language doesn’t match, mark it with the “x-default” value as the guide describes. Mistakes here are common after a redesign, so make hreflang part of your launch checklist.

Avoid redirecting visitors automatically based on their browser language or location. Google’s guidance cautions against this because it can stop both users and crawlers from reaching all versions. Offer a visible language switch on every page instead, and link each page to its matching page in the other language rather than to the homepage.

Build the Arabic experience properly

An Arabic page is more than translated text placed on an English template. Several technical points affect both usability and search performance:

  • Right-to-left layout should be handled in the template, including navigation, forms, tables and icons that imply direction.

  • Each page needs its own Arabic title, meta description and headings, not the English ones.

  • Fonts should render Arabic cleanly on phones as well as desktops.

  • Forms and checkout fields need to accept Arabic input and handle names, addresses and phone formats correctly.

  • URL slugs need a decision: Arabic script reads naturally to users but can be awkward when copied or shared, while transliterated slugs are easier to handle. Pick one pattern and apply it consistently.

Have a native Arabic writer review the pages. Machine translation without review can produce wording that reads oddly to the audience you want to convince.

Plan content by audience, not by page count

Start with the pages that drive enquiries: service pages, industry pages and contact paths. Write the Arabic and English versions with the same facts but allow the examples, phrasing and calls to action to differ where the audience differs.

If your business has a physical location in Doha or elsewhere in Qatar, make the address, opening hours and map details consistent across both languages and across your business listings. Inconsistent details confuse users and weaken local signals.

Then add supporting content, such as guides and comparison pages, in the language where your customers are asking the question. You don’t have to translate every article. Publish in the language where there’s demand, and add the other version when it earns its place.

Measure conversions by language

This is the step most bilingual sites skip, and it’s why many teams can’t tell whether Arabic content pays off.

Set up tracking so that each lead records the language of the page it came from. At minimum, track:

  • Contact and quote form submissions, with the page language attached.

  • Click-to-call and WhatsApp button clicks, if you use them.

  • The landing page and traffic source of each lead.

  • Lead status in your CRM, so you can see which language produces qualified enquiries and sales, not only form fills.

Passing the source and language into the CRM lets sales teams close the loop. A page that brings fewer enquiries but a higher share of qualified ones may be worth more than a busier page.

Check cookie, consent and data-handling requirements for your analytics setup with your legal advisers. Don’t assume a tool’s default configuration meets your obligations.

Common mistakes to avoid

Launching Arabic without a measurement plan

Without language-level tracking, you can only judge success by total traffic. Add it before launch so the first month of data is usable.

Duplicating the English title tags

If Arabic pages carry English metadata, they send mixed signals and look unfinished in search results. Audit titles and descriptions page by page.

Forgetting reciprocal links between versions

One-way language links are a frequent hreflang fault. Run a crawl after each release to catch broken pairs.

Treating Arabic as a one-off project

New English pages get published, and the Arabic version falls behind. Decide upfront who updates both, and how often.

A practical sequence

  1. Audit what exists: current pages, rankings, traffic by language and the lead sources you can already trace.

  2. Research keywords separately in Arabic and English, and note where users mix both.

  3. Choose the site structure and agree the URL pattern.

  4. Build RTL templates, then test forms, search and checkout in both languages on mobile.

  5. Write and review the priority pages with native speakers.

  6. Implement hreflang, language switchers and separate metadata, then crawl to check them.

  7. Set up conversion tracking with language and source captured in your CRM.

  8. Review results monthly and add content where the data shows demand.

How Carmatec Qatar can help

Carmatec Qatar’s SEO services page lists local and international SEO, on-page and off-page optimisation, website optimisation, content strategy and keyword strategy. When you speak to the team, ask how that scope applies to Arabic and English content, including structure, metadata and tracking, so the plan reflects your site and your CRM.

What to decide first

Settle the structure and the measurement plan before you commission content. Once you can see which language produces qualified leads, every later choice becomes easier to justify.

Speak with Carmatec Qatar’s team to review your current site and define a practical bilingual SEO plan.

EN
WhatsApp chat
DMCA.com Protection Status