BILINGUAL WEBSITES

Arabic and English website SEO: URLs, hreflang and launch checks

Give each language a complete, crawlable edition with its own URL and canonical. Connect equivalent pages with language annotations and a useful switcher, then test the delivered HTML, internal links and mobile experience before launch.

What makes a bilingual website more than a translation?

A bilingual company website gives each audience a complete way to understand the business and take the next step. It includes appropriate wording, working navigation, readable typography, relevant examples and contact options. Replacing English strings with Arabic inside the same visual layout is only part of the work.

Start with the commercial questions each page answers. A service may have the same scope in both languages, while the familiar terminology and order of explanation differ. An Arabic business reader should not need to mentally translate awkward English phrasing to understand what will be delivered.

For companies serving Jordan, Saudi Arabia and the UAE, this matters in service descriptions, proposals and campaign landing pages. Keep actual business facts consistent without inventing offices, local credentials or country-specific availability merely to place a location keyword in the page.

Choose a stable URL structure

Language folders such as /en/ and /ar/ provide a straightforward structure for a single brand domain. English paths can use descriptive English words, while Arabic paths can use meaningful Arabic words. Both approaches should lead to stable, readable addresses rather than generated page IDs and unnecessary parameters.

There is no universal ranking rule that every URL must contain fewer than a particular number of characters. Keep paths concise and useful. Avoid repeating the company name, city and service category several times, and do not rename an established URL simply to add another keyword variation.

Google’s URL structure guidance supports clear, crawlable addresses. Arabic addresses appear percent-encoded in some technical contexts; that is normal. Test the exact generated links in the browser and sitemap instead of treating encoded characters as a broken URL.

Keep each language’s canonical on its own page

A canonical identifies the preferred version of a page when alternative addresses can show equivalent content. For complete Arabic and English editions, each normally points to its own preferred URL. Automatically pointing every Arabic canonical to English can send the wrong consolidation signal.

Keep protocol, hostname and trailing-slash decisions consistent. The canonical, internal links and sitemap should agree on the preferred address. Tracking parameters should not create a new canonical destination for each campaign visit.

Google’s canonicalisation documentation explains how these signals work. A canonical is not a substitute for a redirect when the business has intentionally moved a public URL. Plan old-to-new address mapping before a domain or platform cutover.

Connect genuine equivalents with hreflang

Use language annotations to connect the actual counterparts. The English service page should refer to the matching Arabic service page and itself; the Arabic page should reciprocate. Check the final absolute URLs and avoid pointing every page’s Arabic alternate to the Arabic homepage.

Generic language codes can be appropriate when the same edition serves several countries. Do not create country variants solely to make the markup look more comprehensive. A regional page needs meaningful differences in scope, information or audience experience to justify its existence.

Read Google’s localised-version guidance for the supported implementations. Choose a maintainable approach and validate the relationships as new pages are added. A correct homepage pair does not establish that all service and article pairs are correct.

Make the language switch preserve context

A visitor reading an implementation guide should reach the corresponding guide after changing language. If a counterpart is genuinely unavailable, show an honest alternative rather than pretending the same content exists. The language control should remain visible and understandable on a phone.

Use actual links so people can open the destination in another tab and search engines can discover it. Do not depend entirely on a browser-language redirect. A bilingual user may prefer an Arabic explanation on an English-configured device, and a saved campaign link should retain its intended destination.

Include a clear Home or الرئيسية route in navigation as well as the logo link. A recognisable wordmark is useful, but explicit navigation reduces guesswork for visitors who do not know the convention that clicking a logo returns to the homepage.

Design Arabic reading direction deliberately

Set the Arabic document’s language and right-to-left direction, then use logical spacing and alignment in the layout. Keep Arabic shaping intact. Avoid letter spacing that separates connected letters or fixed-height text areas that crop marks and descenders.

Some content should retain its own direction: email addresses, phone numbers, technical identifiers and parts of mixed-language tables. Use appropriate isolation rather than reversing strings. A project screenshot or supplied logo should not be mirrored merely because the surrounding page is right-to-left.

The W3C directionality guidance provides an implementation reference. Review actual paragraphs, buttons and forms in context. A page can have the correct dir attribute and still feel awkward if the composition was never checked with real Arabic copy.

Use typography and images that support the content

Select a readable Arabic font, such as the Tajawal family used on Markenity, and load the necessary weights without relying on synthetic bold. Give text enough line height and a sensible reading measure. Keep important body copy readable on mobile instead of shrinking everything to fit a desktop composition.

Images should have a job: demonstrating delivered work, explaining a process or supporting the service context. Give meaningful images concise, appropriate alternative text in the page’s language. Keep captions outside screenshots containing their own words so the two layers do not compete visually.

For campaign assets, see our brand-aware AI design guide. The same review principle applies: generate or prepare alternatives, then check language, brand rules, source accuracy and final composition before approval.

Use the selected language for navigation and related content. Link a guide to the relevant service and a cleared example of the work. Do not create an Arabic article that sends every useful next step to English while the matching Arabic destinations are available.

Make link text describe the destination. A natural phrase such as website lead routing is more informative than a row of identical “click here” links. Avoid turning every keyword occurrence into a link; choose the points where the reference helps the reader.

Use external references to support specific implementation claims. A familiar organisation’s homepage is not automatically the best reference. Prefer the actual documentation page, check that it remains accessible and explain why it is relevant to the decision being discussed.

Check the source that the server delivers

View the delivered HTML and verify language, title, description, canonical, language alternates, headings and appropriate structured data. Check social-card URLs and image dimensions as well. A settings screen can contain the right values while a template outputs them twice or substitutes the wrong page’s metadata.

Minified HTML can place much of the source on one line. That does not mean its semantic structure is missing. Search systems read the elements and their content, not indentation. Conversely, neatly formatted code can contain an invalid image URL or a canonical pointing to the wrong language.

Our AI search visibility guide explains how these foundations support discovery without guaranteeing a recommendation. An analytics container is not required to make a document structurally valid or indexable.

Prepare the migration and launch checklist

  1. Inventory existing public URLs and map important moves to relevant destinations.
  2. Test both language editions at narrow and wide viewport sizes.
  3. Verify navigation, language switching and real form behaviour.
  4. Compare canonical, hreflang and sitemap addresses for every built page.
  5. Keep review environments noindex and make the launch indexing change deliberately.
  6. Preserve email and verification DNS records during the website migration.
  7. Check redirects, HTTPS, 404s, robots and sharing assets on the final domain.
  8. Submit the real sitemap through verified search accounts and monitor processing.

Questions before commissioning a bilingual site

Ask who writes and approves each edition, which pages need counterparts, what systems receive enquiries and who maintains the content after launch. Include real Arabic samples in the design review. Our web design and development service can turn those decisions into a scoped build with clear handover and maintenance responsibilities.

Talk to Markenity

What are you working on?

Tell us what your company needs. We can talk through the requirements and a sensible next step.

MANUFACTURING & PACKAGING

Future Pack

A captured page from the Future Pack website, showing its packaging products.

Helping customers find the right packaging.

A company website and product catalogue for a Jordanian packaging business, with product information, custom printing options and enquiry forms.

DELIVERY ROLE

Website design & development

PROJECT SCOPE
  • Corporate presentation
  • Product discovery
  • Responsive website

Our team handled the design and development. These examples describe the work delivered.

Visit the website

REAL ESTATE · UAE

Deluxxis

A captured page from the Deluxxis property website.

A website for exploring property in Dubai.

A property website that brings listings, developments and brokerage services together, with ways to browse properties and contact the company.

DELIVERY ROLE

Website design & development

PROJECT SCOPE
  • Property presentation
  • Service structure
  • Responsive website

Our team handled the design and development. These examples describe the work delivered.

Visit the website

Discuss your project

Tell us about your project.

What does your company need help with? Share a few details below.

At least 10 characters. Please leave out confidential information.

Used to reply to your enquiry, without adding you to marketing lists. Privacy Policy

A USEFUL PLACE TO START

A few questions before we start.

You can use these to explain the project to your team or to ours.

  1. Who is this project for, and what needs to change?
  2. What would make the project a success?
  3. What content, data or systems can we work with?
  4. Who will review and approve the work?
  5. What budget and deadline should we plan around?

Answer what you can. We can work through the rest together.