INFORMATION ARCHITECTURE

Arabic and English Navigation That Works for Both Audiences, Not Just One

Ignited Nepal structures the page hierarchy, navigation, and content organisation of Qatari websites with Arabic and English as genuine parallel content streams. RTL and LTR are not the only difference between the two versions. We design the navigation logic, page hierarchy, and content structure for each language independently, then connect them into a single coherent site architecture.

Request your IA Diagnostic View the evidence

We are proudly featured on

  • Search Engine Journal
  • Shopify
  • SEO Fomo

Trusted by businesses we have shipped growth for

  • Global IME
  • IME Remit
  • Chandragiri Hills
  • Sublime Trails
  • VEVS
  • Kangaroo
  • Ishan

/ This is for you if

Who This Is For

Your primary audience is Arabic-speaking and your secondary audience is English-speaking international clients, partners, or investors. Your current site was built primarily in Arabic and the English version was added as a mirror, with translated labels and reversed layout. English-speaking visitors experience the site as a translation rather than as a native experience. You want both versions to feel authoritative for their respective audiences.

You have an existing English-language website and you are adding Arabic for the Qatari and Gulf market. You know that adding Arabic is not simply a matter of translating your content and flipping the layout direction. The navigation logic, the content hierarchy, the page structure, and the information density expectations of Arabic-speaking audiences in Qatar differ from those of your existing English-speaking audience. You need an IA that reflects both sets of expectations rather than forcing one into the other's structure.

Your site was built with both language versions at launch and they were structurally aligned at that point. Over time, updates to one version have not been replicated in the other. Service pages in Arabic cover topics that the English version does not address. The English version has sections that have no Arabic equivalent. You are planning a rebuild and you want to reconcile the two versions into a documented structure before development begins.

/ What's broken

What's Broken

RTL Is Treated as a Layout Property, Not an Architecture One

The most common error in Arabic/English bilingual websites is treating RTL as a CSS property to flip on and off. RTL affects more than text direction. It affects the visual weight of navigation items, the reading entry point of each page, the priority order of content sections, and the way a visitor scans a page to orient themselves. An Arabic page designed by mirroring an English page gives Arabic-speaking visitors a navigation experience that feels off without them being able to identify why.

Navigation Labels Are Translated, Not Rewritten

Arabic navigation labels derived by translating English labels inherit the logic and vocabulary of English-language information architecture. Terms that work in English navigation, whether they are service category names, industry labels, or action-oriented menu items, do not always have natural Arabic equivalents that carry the same navigational meaning. When labels are translated rather than rewritten, the Arabic navigation feels foreign to native Arabic speakers even before any structural problem is encountered.

The Two Versions Are Structurally Inconsistent in Ways That Affect Search

Bilingual sites in Qatar and across the Gulf frequently have hreflang implementation errors, URL structures that do not clearly signal language, and content that exists in one language but not the other without any canonical or alternate tag signal to search engines. The result is that each language version competes with itself for search visibility rather than reinforcing the other.

Content Depth Expectations Differ and Are Not Accounted For

Arabic-speaking audiences in Qatar and the Gulf region frequently expect more contextual and supporting information on service and product pages than Western English-language conventions suggest. A page structure designed for English reading patterns that also serves the Arabic version will consistently underserve Arabic-speaking visitors by omitting the level of supporting detail they expect before making an enquiry or a purchase decision.

/ What we engineer

What We Do

Each workstream is built by the team that audits it, and wired into the rest of your growth system.

Discovery Workshop

We run a structured workshop with your key stakeholders in Arabic and English. We establish the primary audiences for each language version, the tasks those audiences come to complete, and the business objectives each version needs to serve. We treat the Arabic and English versions as parallel structural briefs from the first session rather than original and translation.

Content Audit

We catalogue every page in both language versions. We document the URL, the Arabic title, the English title, the page purpose, the structural relationship between corresponding pages, and any hreflang or canonical tag issues. We flag pages that exist in Arabic but not in English, pages where the content depth of one version significantly differs from the other, and pages competing with each other within a single language version.

User Journey Map

We map the primary user journeys for Arabic-speaking visitors and for English-speaking visitors separately. For Arabic-speaking visitors, the journey map reflects the content depth expectations and the reading entry points specific to RTL navigation. For English-speaking visitors, the journey map reflects standard LTR scanning patterns and Western content hierarchy conventions. Both journey maps feed into a single sitemap in which each page serves both audiences.

Bilingual Sitemap

We produce a sitemap with Arabic and English as parallel primary structures. Each page is listed with its Arabic title, its English title, its URL in both language versions, its position in the hierarchy, and its content type. The sitemap is reviewed and approved in both languages before any design or development work begins.

Navigation Labels

We write navigation labels for Arabic and English independently. Arabic labels are not translated from English originals. They are written by Arabic-language information architects who understand the navigational conventions of Gulf region web audiences. English labels are written separately. Both sets are tested against the tasks identified in the discovery workshop and the reading patterns of their respective audiences.

Page Template Outlines

We produce structural outlines for each content type in both language versions. Arabic page templates are designed for RTL reading patterns and the content depth expectations of Gulf audiences: primary information at the right-side entry point, supporting detail layered in, and related content positioned according to RTL visual flow. English page templates follow LTR conventions. Both templates serve the same page in the hierarchy with structurally equivalent but independently designed layouts.

URL Structure

We document the URL architecture for both language versions including the approach to language segmentation using subdirectories, slug format in Arabic-transliterated and English forms, hreflang tag mapping, and redirect plan for legacy URLs. We document the tradeoffs between Arabic transliterated slugs and English slugs for Arabic-language pages and make a recommendation based on your SEO objectives in the Arabic and English search markets.

Internal Linking Plan

We map the internal linking architecture for both language versions. Arabic-language internal links use Arabic anchor text. English-language internal links use English anchor text. Cross-language links, such as language switcher functionality, are documented with instructions for maintaining positional context when a visitor switches between languages.

Handover to Design

We deliver a bilingual design handover package. The design team receives independent structural briefs for the Arabic RTL version and the English LTR version, alongside the shared sitemap, navigation labels in both languages, and URL structure. The briefs are clear that the Arabic version is not the English version with the layout flipped.

Request your IA Diagnostic

/ What changes

What Changes

Before
After
BeforeThe most common error in Arabic/English bilingual websites is treating RTL as a CSS property to flip on and off. RTL affects more than text direction. It affects the visual weight of navigation items, the reading entry point of each page, the priority order of content sections, and the way a visitor scans a page to orient themselves. An Arabic page designed by mirroring an English page gives Arabic-speaking visitors a navigation experience that feels off without them being able to identify why.
AfterWhen the Arabic navigation is written independently, the page templates are designed for RTL entry points, and the content depth matches Gulf audience expectations, Arabic-speaking visitors experience the site as a native product rather than a translated one. This affects both initial trust and the likelihood of an enquiry or conversion.
BeforeArabic navigation labels derived by translating English labels inherit the logic and vocabulary of English-language information architecture. Terms that work in English navigation, whether they are service category names, industry labels, or action-oriented menu items, do not always have natural Arabic equivalents that carry the same navigational meaning. When labels are translated rather than rewritten, the Arabic navigation feels foreign to native Arabic speakers even before any structural problem is encountered.
AfterWhen the English version is a genuine parallel structure rather than a structural mirror of the Arabic version, English-speaking visitors find a site that meets their navigational expectations. The English version is not sparse because it is a secondary language stream. It is complete because it was designed for its own audience.
BeforeBilingual sites in Qatar and across the Gulf frequently have hreflang implementation errors, URL structures that do not clearly signal language, and content that exists in one language but not the other without any canonical or alternate tag signal to search engines. The result is that each language version competes with itself for search visibility rather than reinforcing the other.
AfterA bilingual IA with correct hreflang implementation, language-appropriate URL structure, and content depth calibrated to each audience's expectations gives both versions a foundation for search visibility in Arabic and English search results. This is the structural prerequisite for any multilingual SEO work.
BeforeArabic-speaking audiences in Qatar and the Gulf region frequently expect more contextual and supporting information on service and product pages than Western English-language conventions suggest. A page structure designed for English reading patterns that also serves the Arabic version will consistently underserve Arabic-speaking visitors by omitting the level of supporting detail they expect before making an enquiry or a purchase decision.
AfterWhen both language versions follow the same structural logic with independent content design decisions, maintaining them becomes a predictable process. New content is added into the correct position in both hierarchies. The content teams for each language version work from the same sitemap, with independent page templates.

/ How it works

Process

  1. IA Diagnostic

    We assess both language versions of your current site against five criteria: navigation logic in each language, RTL and LTR structural integrity, content depth parity between language versions, URL structure and hreflang implementation, and internal linking. We produce a findings document identifying the specific structural problems in each version. This takes five working days.

  2. Discovery Workshop

    We run a structured workshop in Arabic and English with stakeholders from both sides of the content operation. We establish the brief for both language versions in a single session, treating them as parallel from the outset.

  3. Content Audit and Journey Mapping

    We catalogue content in both language versions with parallel documentation. We map user journeys for Arabic-speaking and English-speaking visitors separately, noting where the journeys differ and where they cross.

  4. Bilingual Sitemap and Navigation

    We produce the parallel sitemap with independently written Arabic and English navigation labels. Both are presented for stakeholder review in a single session, with Arabic and English stakeholders reviewing their respective versions simultaneously.

  5. Page Templates and URL Structure

    We produce RTL and LTR template outlines for each content type and the URL architecture for both language versions including hreflang mapping.

  6. Internal Linking Plan

    We map internal links for both language versions with language-appropriate anchor text and document cross-language linking strategy including language switcher positional behaviour.

  7. Design Handover

    We deliver the bilingual design handover package with independent structural briefs for the Arabic RTL version and the English LTR version.

Request your IA Diagnostic

/ Common questions

FAQs

Straight answers on scope, timelines and cost. Anything else, ask us directly.

Ask us directly
Is the Arabic version of our site simply the English version with the layout reversed?

A mirrored layout with reversed direction is the most common and most damaging approach to Arabic website design. The Arabic version requires independently designed navigation labels, page templates structured for RTL reading entry points, and content sections ordered according to how Arabic-speaking visitors scan and prioritise information. The structural logic is different, not just the direction.

How do you handle navigation labels that do not have direct Arabic equivalents?

Arabic navigation labels are written by Arabic-language information architects with experience in Gulf web audiences, not derived by translation from English. Where English navigation conventions have no direct Arabic equivalent, the label is written to serve the same navigational purpose using vocabulary and structure natural to Arabic-speaking users in Qatar. The result is labels that work for their audience rather than labels that are technically accurate translations.

What URL structure do you recommend for Arabic and English content?

For most Qatari organisations, subdirectory-based language segmentation is the most practical approach: /ar/ for Arabic content and /en/ for English content on the same domain. We document the tradeoffs between using Arabic transliterated slugs, which can improve Arabic search relevance, and English slugs for Arabic-language pages, which simplify content management. The recommendation depends on your search objectives in each language market.

How do you handle the content depth difference between Arabic and English versions?

Content depth is treated as a template-level decision. Arabic page templates are structured to accommodate greater supporting detail in secondary sections, which reflects the content expectations of Gulf audiences. English page templates follow the scanning conventions of Western English-speaking visitors. Both templates serve the same page in the hierarchy with structurally equivalent sections, but the sections are sized and sequenced according to each audience's reading patterns.

What is hreflang and why does it matter for our bilingual site?

Hreflang is a technical signal in your site's HTML that tells search engines which version of a page corresponds to which language audience. Without correct hreflang implementation, search engines may serve the Arabic version to English-speaking users and vice versa, reducing the search visibility of both versions. Correct hreflang mapping is documented as part of the URL structure deliverable and handed to the development team as an implementation instruction.

/ Our team

The people behind the work.

Not a black box. Real specialists you can call, with their names on the work.

About us
Hawrry Bhattarai

Hawrry Bhattarai

Google Ads Expert

LinkedIn

Start here

Design Both Languages as First-Class Experiences

If your Arabic site is a mirrored version of your English site, if your navigation labels were translated rather than written for their audience, or if you are planning a bilingual build and want the structure right before development begins, the IA Diagnostic is the right starting point. Five working days, both language versions assessed independently, and a clear picture of what needs to change.

Request your IA Diagnostic View the evidence