Arabic image SEO for online stores
How to write Arabic alt text and file names that actually get found, and why translating an English image SEO checklist into Arabic rarely works.
Arabic image SEO means writing alt text and file names from the words an Arabic-speaking buyer actually searches, not translating an English checklist. It also means treating file weight as seriously as wording, since most Arabic-market ecommerce traffic is mobile, where a heavy image costs real, measurable load time.
This is the image half of the bilingual catalogue work covered in the Salla SEO guide, which sets out the rest of what a hosted Arabic-language store controls.
On this page
Why doesn't a translated alt text checklist work?
Because translation and search behaviour are different problems, and treating them as one is the single most common mistake on bilingual catalogues. An English alt text like "red ceramic coffee mug with handle, 350ml" translated word for word into Arabic produces grammatically correct text that describes the image accurately and still misses how an Arabic-speaking buyer would actually phrase the search that should find it.
Google's own guidance on image SEO is specific that alt text should describe the image's subject accurately, in the language a reader of that page would use, because the point of the text is to match what someone would type and to describe the image to anyone who cannot see it [1]. A translation optimises for accuracy to the English source; genuine Arabic alt text optimises for how the image would actually be described and searched for in Arabic, and those are not the same target.
| Literal translation | Written from Arabic research | |
|---|---|---|
| Grammar | Usually correct | Correct |
| Matches real search phrasing | Rarely | Yes |
| Accounts for regional word variation | No | Yes |
| Describes the image for accessibility | Adequately | Adequately |
| Cost to produce | Lower, automatable | Higher, needs a real speaker |
How do you actually write Arabic alt text well?
Start from the same keyword research that should already be informing your Arabic product titles, rather than treating alt text as an afterthought written last. If you have already done the work described in writing Arabic product titles, the vocabulary is largely the same: the words a buyer actually types, not the formal catalogue term.
Describe what is actually in the image
The product, its distinguishing attribute, and its context if relevant — not a keyword list stuffed into a sentence.
Use the phrasing a buyer would search, not a catalogue term
Colloquial and formal Arabic often diverge here more than English does between a product name and a search term.
Keep it specific to the actual image
A generic description repeated across fifty product photos tells a search engine nothing about any individual one.
Have a native Arabic speaker familiar with the market review it
Not just for grammar — for whether the phrasing is one a real shopper in that market would use.
The length that works is close to what works in English: a genuine, specific sentence, not a single word and not a paragraph. If the description would sound unnatural read aloud to a person, it is probably wrong for a search engine too, because both are ultimately judging whether the text is a real, useful description.
Regional variation is worth building into the research rather than treating as an edge case. The same product is often described differently by Arabic speakers in different parts of the market, and spelling conventions for the same word can vary in ways that change what a search engine matches. A short list of the most common variants for your main product categories, kept alongside your keyword research, is worth more here than any general rule, because it is specific to what you actually sell.
It is also worth deciding, once, how your store handles product variants in alt text — a mug that comes in five colours should not have five identical alt texts differing only by a colour word swapped in mechanically. A slightly fuller description that reads naturally in each variant, written by someone who checked what it actually says rather than generated by a find-and-replace pass across the catalogue, holds up better both for search and for anyone using a screen reader.
What about file names and URLs?
Keep them transliterated or in English, and put the real description in the alt text instead. This is a practical recommendation rather than a purist one: Arabic script inside file names and URLs is handled inconsistently across CDNs, hosting providers and even browsers, and a store that gets this wrong ends up with broken or double-encoded URLs that are worse for everyone than a plain, romanised file name.
A workable pattern is a simple, descriptive, transliterated or English file name — ceramic-mug-350ml.jpg rather than a camera's default IMG_4821.jpg — with the actual Arabic description living entirely in the alt attribute, where it displays and gets read correctly regardless of platform. This gives up nothing important: alt text is what search engines and screen readers actually read for meaning, and the file name mainly needs to be tidy and unique.
Does image weight matter more here than elsewhere?
Yes, in practical terms, because of where the traffic actually comes from. A store whose audience shops overwhelmingly on mobile networks pays a heavier real-world cost for an oversized image than a desktop-heavy audience does, and most Arabic-speaking ecommerce markets skew heavily mobile. Modern image formats reduce that cost meaningfully compared to an unoptimised original, and Google's own guidance on serving images in modern formats covers the mechanics of that trade-off [3].
web.dev's broader image learning material is worth a read even for a non-technical store owner, because most of what determines whether an image is "heavy" comes down to a handful of repeatable decisions — dimensions, format, compression — that apply the same way regardless of what language the alt text is in [2].
How does this connect to the rest of the store's structure?
Directly, through the same internal linking discipline that connects a buying guide to the products it discusses. An image with excellent alt text sitting on an orphaned product page still struggles to be found, because the image cannot be discovered any faster than the page carrying it can. Fixing images and fixing internal links are separate tasks that reinforce each other rather than substitutes for one another.
And if you are unsure how much of this is already right on your own store, an audit is the fastest way to find out rather than guessing page by page — see how to audit a Salla store for what that check should actually cover.
Is this worth doing before or after a redesign or migration?
Before, if you can manage it, because rewriting alt text and cleaning up file names is far cheaper to do once on a stable catalogue than twice — once now and again after a theme change moves or renames image assets. If a redesign or a platform move is already scheduled, it is reasonable to hold this work until just after it lands, so the naming conventions you set are the ones that survive rather than ones a migration immediately breaks.
Either way, write the convention down before starting: how file names are structured, what the alt text pattern looks like for a typical product, and who is responsible for applying it to new uploads going forward. A rule applied consistently by one person for an afternoon is worth more than a perfect one-off pass that nobody follows on the next product added a month later, and it is the difference between a habit that survives staff turnover and one that quietly stops the day whoever set it up moves on.
The bilingual stores that get this right treat Arabic as its own research project, not a translation step at the end. Alt text is one of the cheapest places that shows, because almost nobody checks it, and almost every catalogue has it wrong in the same way.
If bilingual catalogue work is a gap across more than just images, our ecommerce SEO service covers the Arabic research end to end, from product titles through to the photos.
Questions people also ask
Should Arabic alt text be a literal translation of the English version?
No. A literal translation carries over English phrasing and word order that an Arabic speaker would not actually search for. Write the Arabic version from scratch, describing what is in the image the way an Arabic-speaking buyer would say it.
Should image file names be in Arabic or English?
Transliterated or English file names are the safer default, since file systems and CDNs handle Arabic script in URLs inconsistently across platforms. Put the real Arabic description in the alt text, where it belongs and where it displays correctly everywhere.
Does image file size matter more for Arabic-market stores?
It matters for every store, but it matters more where mobile networks are the primary way people shop, which describes most Arabic-speaking ecommerce markets. A heavy, unoptimized image costs more there in real load time than the same image costs a desktop-heavy market.
Can a translation plugin generate Arabic alt text automatically?
It can generate something, but automated translation of alt text tends to produce grammatically correct Arabic that no one would actually type into a search box. Treat automated alt text as a rough draft that a human familiar with the market edits, not a finished product.
Does alt text help with AI shopping answers as well as search?
Yes. Assistants that read a page to answer a shopping question rely on the same descriptive text a search engine does when an image has no other extractable data attached to it, so accurate alt text is doing two jobs at once.
Sources
- Google Images SEO best practices — Google Search Central (checked 22 September 2026)
- Learn Images — web.dev, Google (checked 22 September 2026)
- Serve images in modern formats — web.dev, Google (checked 22 September 2026)
Check how your Arabic image SEO actually reads
Book a free 30-minute consultation with Ibrahem and Jeremy. We look at your site while we talk, and you leave with a prioritised plan.
Who wrote this
Jeremy ZavaCo-founder
Leads growth and client partnerships.
Works on: CRO, SEO
Reviewed before publishing by Ibrahem Helal, Co-founder.
- Salla SEO: the complete guideHow to rank a Salla store: what the platform controls, what you control, Arabic product pages, duplicate theme URLs, and the order to fix things in.
- Migrating Salla to Shopify without losing SEOHow to move a Salla store to Shopify without losing rankings: URL mapping, redirects, what to keep unchanged for a month, and when the move isn't worth it.
- Internal linking for online storesWhy most ecommerce stores only link top-down, category to product, and how to add the cross-links that turn a catalogue into a genuinely crawlable site.
- How to audit a Salla store's SEOA practical order for auditing a Salla store: what to check first, which tools to use, and how to turn the findings into a fixing sequence rather than a list.