Kuwaitis type three words, not sentences
Watch how people actually search here. A woman looking for an abaya types عبايات كويت or عبايات كويتية توصيل — three or four words, no verb, no question mark. She almost never types the full sentence version. Arabic product queries in Kuwait are a noun plus the country plus one qualifier: توصيل, رخيص, أصلي, or a brand name in Latin letters sitting inside an Arabic sentence. Add الكويت to any of those and you are competing with maybe eight real pages instead of eight hundred. That thin competition is the whole opportunity, and it exists only because most stores here never publish a single Arabic page.
Pull the real words out of your own data before you guess at them. Search Console filtered to Kuwait shows the Arabic queries you already get impressions for and never rank on. Better still, read your WhatsApp. The exact phrase a customer types when she asks عندكم عبايات صيفية is the exact phrase she types into Google, and the same goes for Instagram DMs. Write them down verbatim, spelling mistakes included. A lot of the volume sits on the misspelled or dialect version rather than the dictionary one, and a keyword tool working in formal Arabic will never show you that.
Ready to start your Shopify store?
Start a free trial and try the platform for yourself.
Your category pages rank; your product pages usually don't
The page that ranks for عبايات كويت is a collection page, not one product. Google wants a page that answers the whole query, and a category query deserves a category page. So build the Arabic collections first: ten to twenty of them, one per real buying phrase you found, each with a genuine 120 to 200 word Arabic intro above the product grid. Say what the range covers, how sizing or sourcing works, delivery time inside Kuwait, and that you take KNET and cash on delivery. Individual product pages then pick up long-tail traffic for exact brand and model names, which is a smaller and later prize.
Auto-translation is where most of this dies. Run your English descriptions through a plugin and you get Arabic that is grammatically fine and commercially dead — literal, stiff, and full of words no Kuwaiti buyer would ever type. Google is not fooled, and neither is the customer, who leaves in four seconds. Write the Arabic yourself, or have a Kuwaiti write it: the same product described the way a salesperson in Salmiya would describe it face to face. For a 400-product catalogue, hand-write the collection pages and your top 50 sellers, then let the tail be machine-drafted and edited by a human.
Then make the page legible to a crawler. The Arabic title tag and H1 carry the Arabic phrase itself, not a transliteration of the English one. URLs can stay in Latin letters — /ar/abayas is fine and safer than encoded Arabic slugs. Product images need Arabic alt text. Link your Arabic collections to each other from Arabic pages, never only through the English menu. And confirm the Arabic is a real page: if your theme renders English first and swaps in Arabic with JavaScript, Google may index the English version and the entire exercise is wasted.
Set hreflang once, then be patient — this is the slow channel
A bilingual store needs both versions to exist at their own address — yourstore.com/en/abayas and yourstore.com/ar/abayas — each carrying hreflang tags that point at the other, plus x-default. Do not auto-redirect visitors by browser language: it hides one version from crawlers and irritates the half of Kuwait that browses in English and buys in Arabic. Keep everything on one domain; a separate .com for Arabic splits your authority in two. If your current setup cannot give Arabic its own indexable URL, that is a platform limit, and moving to a store platform that handles bilingual URLs and hreflang natively costs less than fighting it for a year.
Now the honest part: this is slow. A new Arabic section on a domain that already exists usually shows movement in eight to twelve weeks and meaningful order volume in four to six months. Paid does in a day what this does in a quarter. If you need sales this month, put the money into Snapchat, Instagram and Google Search, and treat Arabic SEO as the thing you build in the background while those run. The point is that in a year, a third of your orders arrive without a media budget attached to them — not that you rank by Eid.
Budget it as a one-off. Writing 15 Arabic collection pages and 50 product descriptions properly runs somewhere between 300 and 900 KD, whether you pay an agency or a good Kuwaiti copywriter, and then it is done — no monthly retainer needed to keep it alive. Track it on its own: filter organic traffic to your Arabic pages in Analytics and watch orders, not sessions. If Arabic organic is producing traffic but no orders by month six, the problem is the writing, the price or the product, not Google.