usdigitalmarketingindex.com SEO
How can right-to-left language interfaces affect crawlable website navigation?
Updated November 15, 2026
Through the way the right-to-left version is built, not through the direction of the script. A crawler follows links in the HTML and is indifferent to which side of the screen they appear on. Problems arise when an Arabic, Hebrew, Persian, or Urdu version is produced by adapting a left-to-right template: a menu rebuilt with scripts for the mirrored layout, links hidden or reordered by styles written for the other direction, an off-canvas panel that slides in from the wrong edge and is never opened, or navigation items left untranslated or missing from the right-to-left template. The direction attribute tells browsers how to lay out text. It does not show that the navigation exists, works, or matches the other language versions. That has to be tested in the page’s source and in a browser.
RTL layout and link labels
In a right-to-left interface the layout mirrors: the logo and the start of the menu sit on the right, reading order runs right to left, and “next” points left.
| Element | Left-to-right | Right-to-left |
|---|---|---|
| Menu order on screen | First item at left | First item at right |
| Breadcrumb | Home at left, arrows pointing right | Home at right, arrows pointing left |
| Pagination | "Next" at right | "Next" at left |
| Icons with direction | Arrow right for forward | Arrow left for forward |
| Off-canvas menu | Slides from left | Slides from right |
The mirroring should come from the direction setting, with the HTML in the same logical order in both versions: first item first in the source. Risks appear when the visual order is forced by other means.
| Practice | Risk |
|---|---|
| Reordering the DOM by hand for RTL | Source order no longer matches reading order; screen readers and keyboard navigation follow the source |
| Reversing order with CSS flex or float rules | Visual and logical order diverge |
| Arrow characters typed into link text | They point the wrong way when mirrored |
| Text embedded in images | Not translated, not mirrored, not readable by a crawler |
| Mixed-direction labels, such as an English brand name inside Arabic text | Punctuation and numbers can display out of place without isolation |
Link labels need translation and sense in the target language. An untranslated “Home” or “Products” in an otherwise Arabic menu tells readers the localization is unfinished, and Google’s guidance asks for “a single language for content and navigation on each page”.
Mirroring the layout is one part of adapting a page for a market. The examples inside the text need adapting too, and checking them is covered in the guide to how translated pages can be checked for geographic examples that do not fit the target country.
Direction attributes
Correct HTML direction markup for a right-to-left page:
<!DOCTYPE html>
<html lang="ar" dir="rtl">
<head>
<meta charset="utf-8">
<title>...</title>
</head>
<body>
<nav aria-label="القائمة الرئيسية">
<ul>
<li><a href="/ar/">الرئيسية</a></li>
<li><a href="/ar/products/">المنتجات</a></li>
<li><a href="/ar/contact/">اتصل بنا</a></li>
</ul>
</nav>
<p>رقم الطلب: <bdi>ORD-2291-A</bdi></p>
<p>العلامة التجارية: <span dir="ltr">Northgate T200</span></p>
</body>
</html>
What each part does:
| Markup | Purpose |
|---|---|
| <!–INLINECODE0–> on the html element | Sets the base direction for the whole document |
| <!–INLINECODE1–> | Declares the language for browsers and assistive technology |
| <!–INLINECODE2–> element | Isolates text whose direction is unknown, such as codes and user names |
| <!–INLINECODE3–> on a span | Marks an embedded left-to-right phrase |
| <!–INLINECODE4–> on inputs and user content | Lets the browser choose direction from the content |
In the stylesheet, logical properties such as margin-inline-start and padding-inline-end follow the direction automatically, where margin-left and padding-right do not.
Two limits. On the lang attribute, Google’s documentation says it determines a page’s language from the visible content: “We don’t use any code-level language information such as lang attributes, or the URL” (Google’s guidance on multi-regional and multilingual sites). The attribute matters for browsers and accessibility. And dir governs presentation. A page can carry dir="rtl" and still have a menu that no crawler can follow.
Menu visibility
The navigation of the right-to-left version should contain the same links as the others, as anchor elements in the served HTML.
Failures specific to adapted templates:
| Failure | How it happens |
|---|---|
| Menu positioned off-screen | A style written for LTR moves the panel to a negative left offset; in RTL it stays hidden or overlaps content |
| Menu rendered only by script | The RTL menu was built as a separate script-driven component |
| Dropdowns opening off the edge | Submenus extend past the viewport and cannot be reached |
| Fewer links | The RTL template was built once and not updated when the site's navigation changed |
| Links to the wrong language | Menu items point to the default-language URLs |
| Language switcher missing | No route from the RTL version to others, or back |
| Footer omitted | The RTL template dropped secondary navigation |
A crawler does not see off-screen positioning as such. It reads the links in the HTML. So a visually hidden menu may still be crawlable, and a menu inserted by a failing script may be visible to no one. Check both views.
Crawler-accessible navigation testing
A navigation QA checklist:
| Check | Method | Pass condition |
|---|---|---|
| Direction set | View source | <!–INLINECODE12–> on the html element |
| Links in served HTML | Fetch the page without JavaScript; list anchors in navigation | All menu links present with <!–INLINECODE13–> values |
| Link parity | Compare the list with the LTR version's navigation | Same destinations, in the RTL version's own URLs |
| Link targets | Request each | 200, in the right language |
| Logical order | Read the source order | First item first; not reversed in the DOM |
| Visual order | Load in a browser | Mirrors correctly; first item at the right |
| Keyboard order | Tab through the menu | Follows reading order |
| Mobile menu | Open on a narrow screen | Opens from the correct edge; all items reachable |
| Dropdowns | Open each | Fully visible within the viewport |
| Breadcrumbs and pagination | Inspect | Correct direction; links work |
| Mixed-direction text | Check brand names, numbers, codes | Display in the intended order |
| Language switcher | Use it both ways | Reaches the equivalent page |
| Rendered HTML | URL Inspection in Search Console on an RTL page | Navigation links present in what Google rendered |
| Crawl | Crawl the RTL section from its home page | Every page found; depth comparable with other versions |
| hreflang | Inspect an RTL page | Lists itself and the other versions, and they list it |
Test visual order and logical order as two separate things. A page can pass one and fail the other.
Use real content when testing, with long and short labels and embedded Latin text. Placeholder text hides bidirectional problems.
Have a native reader use the site. Mirroring errors and awkward labels are obvious to them and easy for an outsider to miss.
Keep the versions in step. When navigation changes in the primary template, the change belongs in the right-to-left one in the same release. A shared template with direction-aware styles removes the risk of a separate template falling behind.
What the links in that navigation say, and how to render them in each language, is a translation question taken up in the guide to how internal link anchor text should be translated across language versions.
The test: the right-to-left version’s navigation should be the same links, in the same logical order, present in the served HTML, and usable in a browser from right to left.
Add your comment to this answer