
Use to summarize this article

- Built in: Webflow switches Arabic locales to right-to-left automatically on published sites. No custom code needed.
- What mirrors: Text, flexbox rows, grid columns, and inline elements flip on their own.
- What doesn't: Fixed left and right spacing, absolute positions, directional icons, and horizontal animations need Arabic overrides or logical CSS properties.
- Keep left-to-right: Numbers, prices, code, emails, URLs, and English brand names.
- SEO: Webflow adds hreflang for you. Pick ar, ar-SA, or ar-AE based on whether your content changes by country.
To build an Arabic and English website in Webflow, add an Arabic locale in Webflow Localize. Webflow flips the Arabic pages to right-to-left on its own. Your job is everything around that switch: the parts that don't mirror, Arabic fonts, SEO, and testing on the live site.
The direction switch takes one setting.
Getting an Arabic page to feel native takes a lot more than that.
Below, we go through it in the order we'd build it: setup, layout, type, content, and SEO. Each section tells you what changes in Arabic, how to handle it in Webflow, and what to test.
Still picking a partner for the GCC? See our lists of Webflow agencies in Saudi Arabia and Webflow agencies in Dubai.
How does Webflow handle Arabic by default?
Webflow applies right-to-left direction to Arabic locales by itself.
According to Webflow's Help Center, this works on published sites for Arabic (ar), Persian (fa), Hebrew (he), Urdu (ur), and Yiddish (yi). It covers regional versions too, like Arabic (Iraq), and it kicks in even before you translate anything.
Every locale in Webflow Localize also gets:
- Its own subdirectory, like yourbrand.com/ar/.
- Localized styles, available on every Localization plan.
- Localized SEO, with HTML lang tags, page-level hreflang, and hreflang in auto-generated sitemaps.
- Content inheritance, so the Arabic locale shows your English content until it's translated.
How different should your Arabic site be from your English one?
Answer this before anyone opens Figma. It decides how big the project is.
Most teams land on one of three levels:
| Level | What changes in Arabic | Webflow features you'll use | Best for |
|---|---|---|---|
| Mirror | Translated content, mirrored layout | Arabic locale, automatic RTL | A first Arabic launch |
| Adapt | Fonts, imagery, logos, proof, and regional details | Localized styles, images, and alt text | B2B teams actively selling in the GCC |
| Rebuild | Arabic-only sections or pages | Element visibility per locale | Markets that need a different story |
Webflow supports the middle option well, with localized styles, images, alt text, and element visibility per locale.
If Arabic starts needing its own product, team, or domain, read Should You Use One Webflow Site or Multiple Sites for Global Markets?
How do you set up the Arabic locale in Webflow?
Arabic becomes a secondary locale with its own URL path. Search engines treat it as another language version of the same site.
- Pick your primary locale. Every other locale inherits from it. For most global B2B sites, that's English.
- Add the Arabic locale. Choose Arabic alone, or Arabic plus a region, like Arabic (Saudi Arabia) or Arabic (United Arab Emirates).
- Set the subdirectory. For example, /ar/ or /ar-sa/.
- Check your plan. Localization Essential covers up to 3 locales. Advanced covers up to 10.
One Arabic version for every market? Use Arabic alone. Different content for Saudi Arabia and the UAE? Add a region.
What mirrors automatically, and what doesn't?
The dir="rtl" attribute changes direction. It doesn't rewrite your CSS.
So some things flip on their own, and some stay stuck to the wrong side:
| Element | Mirrors on its own? | What to do |
|---|---|---|
| Text alignment and reading order | Yes | Nothing |
| Flexbox rows | Yes, a flex row follows text direction | Nothing |
| Grid columns | Yes | Nothing |
| Margin and padding left or right | No | Switch to logical properties |
| Absolute positions set with left or right | No | Override on the Arabic locale |
| A hard text-align: left | No | Use text-align: start |
| Horizontal animations | No | Rebuild for the Arabic locale |
| Background images | No | Swap or flip per locale |
Webflow's own guidance is to use logical CSS properties instead of fixed left and right values:
- margin-inline-start instead of margin-left
- padding-inline-end instead of padding-right
- text-align: start instead of text-align: left
"Start" means left in English and right in Arabic. One style, both directions.
Add them as custom properties in the Style panel. Where you really can't avoid left or right, override it on the Arabic locale.
Then look for anything still hugging the wrong edge. Badges, close buttons, decorative shapes, and side panels are the usual suspects.
How do you handle navigation, icons, and logos?
In Arabic, the nav mirrors. The logo usually moves to the right, and menu items read right to left.
Arrows are the tricky part. An arrow pointing right means "next" in English and "back" in Arabic.
- Let flexbox handle the nav. A flex-based navbar mirrors without extra work.
- Flip directional icons. Add a horizontal flip to arrow and chevron classes, on the Arabic locale only.
- Never flip logos. Wordmarks stay exactly as designed.
- Never flip media. Photos, screenshots, and videos stay as they are.
- Add a language switcher. Webflow has a native locale switcher, so visitors can jump between the English and Arabic version of the same page.
Before launch, check breadcrumbs, pagination, carousels, and "Read more" arrows. Make sure the mobile menu opens from the right side.
Which fonts and type settings work for Arabic?
Most Latin fonts don't include Arabic characters. Arabic needs its own font.
Webflow recommends Unicode-friendly fonts with broad script support, set at the class level in the Arabic locale view. Google Fonts has solid options like Noto Sans Arabic and IBM Plex Sans Arabic. Pick one that matches the weight and feel of your Latin font, so the brand looks like itself in both languages.
The font is only half of it. These settings usually need to change too:
| Setting | English | Arabic | Why |
|---|---|---|---|
| Font family | Your brand font | An Arabic font, set on the Arabic locale only | Most Latin fonts have no Arabic characters |
| Letter-spacing | Whatever your design uses | Remove it | Arabic letters connect, and extra spacing breaks the script |
| Line height | Your default | Usually more | Arabic letterforms often need more vertical room |
| Font weights | Every weight you use | Check each one exists | Missing weights fall back to something else |
Webflow also supports localized variable collections. So font size and line-height tokens can be different for Arabic without touching English.
What should stay left-to-right on an Arabic page?
Not everything flips. Some content keeps its original direction, even inside an Arabic sentence.
| Content | Example | How to keep it left-to-right |
|---|---|---|
| Numbers, prices, phone numbers | +971 4 123 4567, AED 1,200 | Text direction set to LTR in the Style panel |
| Code and API examples | GET /v1/users | A custom attribute of dir="ltr" |
| Emails and URLs | [email protected] | dir="ltr" on the element |
| English brand and product names | Webflow, Flowtrix | Webflow's translation glossary |
| Text typed by visitors | A name in a form | dir="auto", so the browser decides |
Both the direction setting and the dir attributes are covered in Webflow's Help Center.
Then read a few sentences that mix Arabic with English names, numbers, and punctuation. Commas, brackets, and full stops are where mixed text usually goes wrong.
How do you handle forms, sliders, and interactions?
Interactive elements break most often in Arabic. They depend on position and movement, and those don't always mirror.
- Forms. Check label position and error messages in Arabic.
- Sliders. In one community thread, the native Webflow slider stopped working inside an RTL container. The fix was applying RTL to the text elements, not the slider's parent.
- Interactions. Horizontal movement doesn't reverse by itself. Rebuild slide-in effects for Arabic where you need them.
- Dropdowns and tabs. Make sure they open toward the right side.
Test all of it on the published site. The Designer preview won't catch everything.
Free website audit
Is your site ready for Arabic?
Get a scored breakdown of your positioning, proof, conversion paths and technical health before you add a new language. Results in about a minute.
85/100
Overall score
How do you translate CMS content into Arabic?
Every CMS item needs an Arabic version. Blog posts, case studies, and product pages all show English until someone translates them.
You can do it by hand, through a translation app, or with Webflow's Agentic Translation, which launched on September 29, 2026. It works in two modes:
- One-time translation does a whole language once, including page content and metadata. Your team reviews it before it goes live.
- Continuous translation keeps the locale in sync as your English content changes.
For an Arabic launch, we'd go with one-time translation and a review by a native Arabic speaker. Check that Arabic is available for AI translation in your locale settings before you plan around it.
Use exclusion rules to keep brand names, SKUs, and code out of translation. Translated words also count toward your plan's word limits, shared across locales.
One thing to test early: older community reports found that CMS Option fields couldn't be localized. Check this before you build filters or labels on Option fields.
More on the setup in What Is Webflow Agentic Translation and How Does It Work?
How do you set up SEO for Arabic pages?
Arabic pages need their own URLs, metadata, and keywords. Arabic search terms usually aren't word-for-word translations of English ones.
Webflow adds hreflang for every locale automatically. Your real decision is the locale code. Google's localized versions guide explains that hreflang uses a language code, with an optional region code, and a region code can't be used alone.
| Locale code | Who it targets | Use it when |
|---|---|---|
| ar | Arabic speakers anywhere | One Arabic version serves every market |
| ar-SA | Arabic speakers in Saudi Arabia | Saudi pricing, proof, or compliance differs |
| ar-AE | Arabic speakers in the UAE | UAE content differs from Saudi content |
A few more things to get right:
- Slugs. Use Arabic script or transliterated Latin letters. Pick one and stick with it. Collection slug translation needs an Advanced or Enterprise Localize plan.
- Metadata. Write an Arabic SEO title, meta description, and Open Graph settings for every page. Don't leave English metadata on Arabic pages.
- Visitor routing. On Advanced and Enterprise plans, Webflow can route visitors to their preferred language from browser settings. Keep a visible language switcher anyway.
- Keywords. Research Arabic keywords separately, based on how your buyers actually search.
Moving an existing Arabic site to Webflow? Our multilingual Webflow migration guide covers redirects and rankings for every locale.
What does a multi-locale Webflow build look like in practice?
The setup in this guide isn't theory. It's how we built Amazon Signage's website.
Amazon Signage sells the Signage Stick to schools, hospitals, restaurants, retailers, and corporate teams. The site needed to work across markets, with the language and content adapting to each visitor's region, while the core design stayed the same.
The site doesn't have an Arabic version. But it runs on exactly the locale setup an Arabic launch would use.
| What we set up | How it shows on signage.amazon.com | What it means for an Arabic launch |
|---|---|---|
| Locales with language and region | 8 versions, including en-US, en-GB, en-CA, fr-FR, fr-CA, de-DE, it-IT, and es-ES | The same choice you make between ar, ar-SA, and ar-AE |
| Subdirectory per locale | /de-de/, /fr-ca/, and so on, with US English at the root | Arabic would live at /ar/ or /ar-sa/ |
| Hreflang in the sitemap | Every page lists all its language versions, plus x-default | An Arabic locale gets added to every entry automatically |
| Localized SEO per page | The German homepage has its own German title and meta description | Arabic pages need Arabic metadata, not English |
| One design system | Same layout and components in every market | Arabic adds RTL on top of the same system |
.png)
The same language in two regions is worth noticing. French appears as fr-FR and fr-CA, and English as en-US, en-GB, and en-CA. That's the pattern you'd follow if Saudi Arabia and the UAE needed different Arabic pages.
.png)
We shipped 20+ pages in 5 weeks, on a CMS the Amazon team can update on its own.
How do Arabic pages show up in AI search?
When a buyer asks ChatGPT, Perplexity, or Google AI Overviews a question in Arabic, the engine looks for Arabic content to cite.
Without Arabic pages, you're relying on it to find your English pages and reinterpret them.
- Answer first. Open each Arabic section with a direct answer.
- Keep names consistent. Brand and product names should match across both languages.
- Add structured data on both locales. FAQ and organization schema help engines understand each page.
- Keep the Arabic locale current. Continuous translation helps once your rules are set.
The easiest test is to ask AI tools your key buyer questions in Arabic, and see which pages they cite.

Our SEO and AEO team works on multilingual Webflow SEO, including AI search visibility.
Arabic Launch Checklist
- Arabic locale and code chosen: ar, ar-SA, or ar-AE
- Fixed left and right values replaced with logical properties or Arabic overrides
- Directional icons flipped, with logos and media left as designed
- Arabic font set on the Arabic locale, with letter-spacing removed
- Numbers, code, and emails kept left-to-right
- Sliders, forms, and interactions tested on the published site
- Arabic metadata and Open Graph localized on every page
- Native Arabic review done before launch
Where should you start if you're adding Arabic to an existing site?
Start with an audit, not a translation.
- Find every fixed left and right value on the English site. Each one becomes an Arabic bug. Replace it with a logical property or plan an override.
- Choose your level: mirror, adapt, or rebuild. This decides how much design and content work Arabic needs.
- Set up the Arabic locale and fonts first. Then translate, starting with your highest-value pages.
- Test on the published site. Sliders, forms, interactions, and mobile menus, all in Arabic, before you announce anything.
Building for the GCC? See our guides to Webflow agencies in the Middle East and headless CMS agencies in the Middle East.
Planning an Arabic and English Webflow site? Talk to Flowtrix. Our Webflow Enterprise team plans both directions before design starts.
FAQ's
The most common questions teams ask before building an Arabic and English website in Webflow.













