Skip to content
Localization 13 min read

Arabic product catalogue localization for UAE online stores: product data, filters, search, SEO and feeds

By Manager & CEO, SmartTech Studio

The Arabic version of most UAE online stores looks fine on the homepage. The trouble starts one click deeper. The product title is still in English, the filter reads «اللون: Black», the size chart sits on the wrong side, and a shopper who types «ساعه ذكيه» into the search box is told there are no results, on a store that sells forty smart watches. The problem lives in the catalogue, which is where the money is.

This guide is for e-commerce managers, merchandisers and store owners who sell in Arabic and English in the UAE, or plan to. It treats the catalogue as data, from how Arabic product information is stored to search, URLs, feeds and the workflow that keeps new products arriving in both languages. The wider question of what to localize and what to translate is in our piece on translation vs localization. This one is about the catalogue.

Where we stand: SmartTech Studio builds websites and platforms from Abu Dhabi, and our multilingual content team works alongside our sister company, Smart World Legal Translation. The marketplace we built for the Dakahlia Chamber of Commerce is Arabic-first, with search across member businesses and listings that members write themselves, and the Al-Azhar University platform we built runs in seven languages.

Treat the catalogue as data in two languages, not as translated pages

The usual way an Arabic store goes wrong is that someone exports the product pages, sends them for translation and pastes the Arabic back. It works once. Then the buying team adds 60 new products, changes the price on 200 and renames a colour, and the Arabic store starts to drift away from the English one. Six months later nobody knows which Arabic descriptions are still correct.

The fix is structural. Every product has fields that belong to no language (SKU, barcode, price, stock, weight as a number) and fields that exist once per language (title, description, URL slug, image alt text, SEO title). Attributes such as colour, size and material sit in between: store them as a code from a fixed list, and give each code a label in each language. Then “Black” is not a word typed by hand into 400 products. It is one value, labelled Black and أسود, and correcting the label corrects every product at once.

Which product fields are shared, and which exist once per language
FieldHow to store itWatch for
SKU, barcode, price, stockShared, one valueNever re-entered in the Arabic store; synced from one source
Title and descriptionOne field per languageA visible “Arabic missing” status, not a silent fallback to English
Colour, size, materialShared code with a label per languageLabels taken from a glossary, not typed freehand
Weight and dimensionsShared number, unit label per languageسم, مل and كغ written the same way everywhere
URL slug, SEO title, meta descriptionOne per languageWritten for Arabic searches, not translated from the English
ImagesShared, except images with words on themBanners and infographics need an Arabic version; alt text is per language

Decide the fallback rule before launch. When the Arabic title is missing, the store can show the English one, hide the product from the Arabic store, or block publishing until the Arabic is done. Showing the English quietly is the worst choice, because nobody notices the gap. We prefer a rule that a product cannot go live in Arabic without its Arabic title, description and attribute labels, plus a report of what is waiting.

Arabic product information is also a legal point in the UAE

This is not only about conversion. The UAE government portal’s page on consumer protection, which summarises Federal Law No. 15 of 2020 on Consumer Protection as amended by Federal Decree-Law No. 5 of 2023, says e-commerce businesses must give consumers and the authorities information in Arabic about the product or service, its specifications, the terms of the contract, payment, warranty and other relevant data. The same page says the invoice must be in Arabic, and that the supplier may add any other language.

The page adds that the law covers goods sold through e-commerce platforms registered in the UAE, not sales to UAE customers by businesses registered outside it. So for a store trading on a UAE licence, an English-only product page is more than a missed sale. We are not lawyers and the Executive Regulation adds detail, so confirm what applies to your licence with your legal adviser. In practice, specifications, warranty terms, delivery and return policies and the checkout terms should exist in proper Arabic, not only the marketing copy.

There is a knock-on effect. If the invoice must be in Arabic, the Arabic product name has to reach the system that prints it. When the online store and the shop till share one catalogue, as described in our guide to connecting an online store to the POS, make the Arabic title one of the fields that syncs, or the till will print a name somebody typed in a hurry.

Arabic product titles and descriptions that people actually read

Arabic titles follow a pattern, as English ones do: the product type first, then what distinguishes it, then the size or capacity. A title such as «عباية كريب سوداء بأكمام واسعة، مقاس 56» tells the shopper and the search engine what the product is from its first word. A title that opens with the brand in Latin letters and leaves the Arabic product type to the end buries the word people search with.

Brand and model names usually stay in Latin letters, as on the packaging, because that is what shoppers see and often what they type. Where a brand is also widely written in Arabic script (آيفون, سامسونج), search must know both forms, as we cover below.

Descriptions are where machine output and pasted manufacturer text show most. Write them in plain Modern Standard Arabic with short sentences, and put the specifications in a table rather than a paragraph. Keep the words the Gulf shopper uses: a phone may be «هاتف محمول» in a user manual but «جوال» in a UAE search, and a sofa may be «أريكة» or «كنبة». Choose the term your customers use for the title and the category, and let the other one into the description and the search synonyms. Our guide to Arabic keyword research explains how to find out which term your customers use.

Arabic grammar leaks into the data too. A colour adjective agrees with its noun: «قميص أسود» but «عباية سوداء» and «حقيبة حمراء». A template that builds titles as product type plus colour label will produce «عباية أسود» unless every colour has a masculine and a feminine form and every product type knows its gender. Filters are easier: «اللون: أسود» is a label, not a phrase, so one form is enough.

Units and sizes need one house style: «سم» or «سنتيمتر», «مل», «كغ» or «كجم», written the same way across the catalogue and in the filters. Clothing and shoe sizes should say which system they follow (EU, UK or US), because shoppers in the UAE buy in all three. A size chart is product information too, so it needs Arabic headings.

Attributes and filters: one taxonomy, two sets of labels

Filters are where a half-localized store is most visible. A shopper on the Arabic store opens the filter panel and finds «المقاس: Small, Medium, Large», or a brand list with half the names in each script. The cause is usually attribute values typed by hand for each product, in whichever language the person entering them chose that day.

Build the taxonomy once. List every attribute your categories use, the allowed values for each, and the Arabic and English label for every value. Then decide the display order per attribute. Sizes and capacities sort by size, not alphabetically, and colours by a fixed order that makes sense, so the Arabic and English filter lists show the same values in matching order rather than in each language’s alphabet.

Category names deserve the same care as product titles, because category pages carry the commercial searches («عبايات نسائية», «عطور رجالية», «أجهزة منزلية»). Name Arabic categories after what shoppers search for, not after the English menu.

If vendors upload their own products, as on a marketplace, the taxonomy matters even more, because you cannot edit every listing by hand. Give vendors pick-lists rather than free text for attributes, and require both an Arabic and an English title at upload. We cover the rest of that model in our guide to multi-vendor marketplace development.

On-site search that understands how Arabic is typed

Search is the feature that fails Arabic shoppers most quietly. Shoppers rarely type the hamza, often type a final ه for ة and ى for ي, almost never type diacritics, and mix Arabic with English and with Arabizi (Arabic written in Latin letters and numbers, such as 3abaya). If the search engine compares the query with the product title letter by letter, it misses all of them.

The answer is normalisation: reduce both the product text and the query to the same simplified form before comparing them. Mature search engines ship this. Apache Lucene, the library underneath Elasticsearch, OpenSearch and Solr, has an Arabic normaliser that turns alef with a hamza into a bare alef, teh marbuta into heh and alef maqsura into yeh, and removes the harakat and the tatweel. The rule that matters is to apply it at both ends, when products are indexed and when the query is typed. Normalising only the query still misses products stored with the full spelling.

Arabic search: what the shopper types, what the catalogue says, and the rule that matches them
Shopper typesCatalogue saysRule that makes them match
ابريق شايإبريق شايFold أ, إ and آ to ا
ساعه ذكيهساعة ذكيةFold final ة to ه
شاى اخضرشاي أخضرFold ى to ي, and the hamza forms of alef to ا
عود كمبوديعُود كمبوديStrip the harakat
عطرعطـــر (in a decorative title)Strip the tatweel
مقاس ٤٢مقاس 42Map ٠١٢٣ and ۰۱۲۳ to 0123
عطورعطرSynonym or stem list: light stemmers miss broken plurals
3abayaعبايةSynonym taken from your search logs
ايفونiPhoneBrand alias in both scripts
جاكتجاكيتSpelling-variant synonyms for loanwords
جوالهاتف محمولDialect synonym

Normalisation handles spelling. It does not handle vocabulary. Broken plurals («عطور» for «عطر», «فساتين» for «فستان») are not caught by the light stemmers most engines use, dialect words and loanwords need a synonym list, and so does Arabizi. Build it from your own search logs: each week, export the Arabic queries that returned no results and add the ones that should have matched a product. A zero-results report split by language is the most useful search report an Arabic store can have.

Digits are easy to forget. Some phones and keyboards type Arabic-Indic digits (٠١٢٣) or the Eastern variant used for Persian and Urdu (۰۱۲۳), and a search for «مقاس ٤٢» must find size 42. Map both sets to the digits 0 to 9 at index time and at query time, and do the same for phone numbers and order numbers in forms.

If you rely on a hosted platform’s built-in search, test it first: type your twenty most common Arabic queries the way customers type them and see what comes back. If it fails, a search app or an external engine with Arabic analysis usually costs less than the lost sales.

The Arabic product page: right-to-left details that break

Our guide to bilingual right-to-left web design covers the layout itself. Product pages add a few problems of their own, mostly where Arabic text meets numbers, codes and Latin names.

Model numbers, SKUs and Latin brand names inside an Arabic sentence can jump to the wrong position when the browser lays out mixed-direction text. Put them in their own element with isolated direction: the HTML bdi element, or dir="auto" for content you do not control, such as customer reviews. Prices need one decision on how the currency appears (د.إ or AED) and on which side of the number, applied everywhere from the product card to the cart. Decide too whether the Arabic store uses Western digits or Arabic-Indic digits, and keep to it.

The image gallery should swipe in the reading direction, and the size chart should mirror its columns while keeping the numbers readable. The cart, checkout and error messages are interface copy rather than catalogue; our piece on Arabic UX writing covers that layer.

SEO for Arabic product and category pages

Google’s documentation is direct about the basics. It recommends a different URL for each language version rather than cookies or browser settings, and it advises against automatically redirecting users to a language version, which can stop users and search engines from seeing all the versions. So each product needs an Arabic URL that loads Arabic without a cookie, and the language switch should link to the counterpart page instead of reloading the same URL.

Google also says it works out a page’s language from the visible content, not from the lang attribute or the URL. A product page under /ar/ whose title, description and specifications are still English is an English page to Google. Google specifically warns against translating only the boilerplate (menus, buttons, footer) while the main content stays in one language. That is a common state for Arabic product pages: everything translated except the product.

Connect each pair with hreflang. Google’s rules are that each language version lists itself and every other version, that the tags are ignored if two pages do not point to each other, and that x-default covers users whose language matches none of your versions. Language-only codes (ar, en) are enough for a store that serves the UAE in both languages. Add a region only if you run separate versions per country.

Arabic URL slugs are a choice, not a rule. Arabic-script slugs read well but become long percent-encoded strings when copied into WhatsApp or email; transliterated or English slugs share cleanly. Either can rank if the content is Arabic. Pick one pattern and keep it, because changing slugs later means a redirect for every product.

Finally, the words. Arabic product and category pages rank for Arabic searches only if their title, meta description, H1 and category introduction are written for those searches. Machine-translating product copy at scale is where many stores cut corners; our guide to AI and machine translation for websites explains what Google says about it and where it is safe to use.

Feeds: Google Merchant Center and the Meta catalogue in Arabic

Shopping ads and free listings run on your product feed, not your pages, so the Arabic store needs Arabic feed data as well. Google’s Merchant Center help says product landing pages should be in the same language as the product data. In practice that means an Arabic data source whose titles and descriptions are Arabic and whose links point to the Arabic product URLs, with prices in AED, alongside the English source pointing to the English pages.

Check which languages your Merchant Center account accepts for the UAE before you build the Arabic feed. Arabic feed titles are often shown with no description beside them, so put the product type and the key attribute first, exactly as on the page.

Meta’s catalogue works differently. Its localized catalogs let one catalogue carry translated names and descriptions, local prices and currency, and a language-specific product URL, so the same product can appear in Arabic in ads and shops with a link to its Arabic page. The language data is added as a separate feed tied to the same product IDs as the main catalogue, which is one more reason to keep IDs and SKUs shared across languages, as in the first section. Feed errors are catalogue errors, so fix them in the product data, never in a spreadsheet that only feeds the ads.

Workflow: where the Arabic lives, who writes it, and how it is checked

Where it lives depends on size. Most platforms used in the UAE can hold a second language per product: Shopify through its markets and translation tools, WooCommerce through multilingual plugins, and Arabic-first platforms such as Salla and Zid natively. A product information management system (PIM) earns its cost when you have thousands of SKUs, several sales channels and several editors, because it adds completeness checks per language, approvals and one export to every channel.

Who writes it matters more than where it lives. A native Arabic writer who knows the product category should own the glossary (product types, attribute values, colours, materials, units) and a short style guide: register, how brands are written, which digits to use, how sizes are shown. With that in place, the long tail of specification-heavy products can be drafted by machine translation and reviewed by a native editor, while best-sellers, category pages and anything that persuades are written natively. Our multilingual content team works this way.

Then check it as a shopper would. Review a sample from every batch on a phone, in the Arabic store, not in a spreadsheet. Search for each new product the way a customer would type it. Read the Merchant Center diagnostics after each feed update. And build the rule into the process: new products from the buying team join a queue for Arabic, and nothing goes live in Arabic until its fields are complete.

What it costs, and where we fit

Catalogue localization is priced by the word, and catalogues hold more words than people expect. 500 products with descriptions of around 120 words each come to about 60,000 words, before titles, attributes and policies. This is where the glossary pays for itself: an attribute value or a colour is localized once, not 500 times. Our human localization starts from AED 0.35 per word, and full bilingual website copy from AED 1,500, both excluding VAT.

If you are building or rebuilding the store itself, a bilingual e-commerce store with payments and inventory starts from AED 8,000, excluding VAT, and our guide to e-commerce website costs in the UAE explains what moves that figure. Arabic search tuning, a PIM and feed work are quoted on top, once we have seen the catalogue.

The best first step costs little. Send us a product export and the twenty searches your customers use most. Get in touch and we will tell you where your Arabic catalogue is losing shoppers, and whether you need us to fix it.

Sources

FAQ

Does every product need its own Arabic URL?

If you want the Arabic pages to appear in search, it should. Google recommends a different URL for each language version rather than cookies or browser settings, and it decides a page’s language from the visible content. Give each product an Arabic URL with Arabic content, connect it to the English page with reciprocal hreflang tags, and make the language switch link to the counterpart page.

Can we machine-translate product descriptions for a large catalogue?

For the long tail of specification-heavy products, a machine draft reviewed by a native Arabic editor against a glossary is a reasonable approach. Best-sellers, category pages, titles and anything that persuades should be written natively. Nothing should be published unreviewed, because attribute errors and wrong terms end up in search, filters and feeds.

Does a UAE online store have to provide product information in Arabic?

The UAE government portal’s consumer protection page says e-commerce businesses must provide information in Arabic about the product or service, its specifications, contract terms, payment and warranty, and that invoices must be in Arabic. The law covers platforms registered in the UAE. Confirm the detail for your licence with a legal adviser.

How much does it cost to localize a product catalogue into Arabic?

It is priced by the word. With us, human localization starts from AED 0.35 per word, excluding VAT. A catalogue of 500 products with descriptions of around 120 words each is about 60,000 words before titles and attributes, and a shared glossary means each attribute value and colour is localized only once.

العربية