Arabic SEO in Jordan is not English SEO translated. The language behaves differently inside a search index, users type differently, and the technical layer carries requirements that simply do not exist for left-to-right sites.

We audit a lot of bilingual Jordanian websites. The same three failures appear almost every time, and each is fixable in weeks rather than months. This guide covers all three, plus the local signals that decide rankings here.

Failure one: the Arabic pages are a translation, not a version

The most common pattern is an English site with Arabic produced by machine translation, published under a /ar/ path, then never touched again.

This fails because search intent differs between the two audiences. Someone searching in English for "ERP software Jordan" is often an IT manager comparing vendors. Someone searching the Arabic equivalent is more often a finance or operations lead looking for a local partner who will handle compliance. Same topic, different question, different page required.

Translate the meaning, then rewrite for the intent. Arabic SEO in Jordan rewards pages written for Arabic readers, not pages that merely contain Arabic words.

What to do instead

  • Research keywords separately in each language. Never translate your English list.
  • Let the two versions differ in structure wherever intent differs.
  • Have a native speaker edit. Machine output reads as machine output, and visitors leave.

Failure two: the technical layer is not bilingual

These are quick wins that a surprising number of sites miss entirely.

hreflang tags

Every page needs reciprocal hreflang tags pointing at its counterpart, plus an x-default. Without them Google frequently indexes only one language version and treats the other as duplicate content.

The dir attribute and layout

Set dir="rtl" and lang="ar" on the html element, not on a wrapper div. Then verify the layout actually mirrors. The common bug is a CSS rule using a physical property such as left: 50% where a logical property belongs, which pushes content off-screen in RTL only.

URL structure

Use a clear language prefix, /ar/ and /en/. Avoid Arabic characters in slugs; they percent-encode into unreadable URLs nobody will share.

Canonical tags

Each language version is canonical to itself, never to the other. Pointing the Arabic page's canonical at the English one removes it from the index entirely.

Failure three: keyword research ignores how people actually type

This is where most of the opportunity sits, and it is specific to Arabic.

Diacritics

Almost nobody types diacritics into a search box. Write naturally, but make sure the undiacritised form of your target term appears in headings and body text.

Hamza and alef variants

Users type أ, ا and إ interchangeably. Google normalises much of this, but not consistently across every query. Where a term matters commercially, include the common variants somewhere on the page.

Dialect against Modern Standard Arabic

Formal MSA is right for a legal page and often wrong for a commercial one. Jordanian users searching for a service frequently use colloquial or mixed phrasing, and pages written in stiff MSA miss those queries entirely.

English loanwords in Arabic script

A large share of technical searches in Jordan mixes scripts. People search "سيو" as often as "تحسين محركات البحث", and "اي كوميرس" alongside "التجارة الإلكترونية". If your page carries only the formal term, you are invisible to half the audience.

The highest-return exercise in Arabic SEO in Jordan is sitting with five real customers and writing down the exact words they use. It routinely beats any keyword tool.

Local signals that matter here

  • Google Business Profile in both languages, with the Arabic name matching how customers actually refer to you.
  • Consistent name, address and phone across every local directory, in both scripts.
  • Jordanian backlinks. A link from a local chamber of commerce, university or industry association carries far more weight for local queries than a generic international directory.
  • Schema markup with addressCountry: JO and Arabic inLanguage variants.

Measuring it properly

Segment Search Console by language from day one. Aggregate numbers hide the story. We have seen sites where English traffic grew steadily while Arabic traffic fell, and the combined chart looked flat and healthy.

Track impressions, average position and click-through rate separately per language. A low click-through rate at a good position almost always means the Arabic title or meta description reads awkwardly, which is a one-hour fix with a large payoff.

A realistic timeline

Technical fixes surface in four to eight weeks. Content rewrites take three to six months to mature. Authority building is a year-long effort. Anyone promising first-page Arabic rankings in thirty days is selling something else.