We Audited 20 Salla and Zid Stores: The SEO Defaults Saudi Merchants Inherit (2026)

We audited 20 Saudi stores and found platform defaults causing most problems. On 2 October 2026 we checked 10 Salla and 10 Zid stores: of 146 sitemap product URLs we sampled on Salla, 88 (60%) redirected or returned 410 instead of loading, against 0 of 143 on Zid. Zid’s robots.txt left out the sitemap line in 9 of 10 stores. Every Salla English product page we tested named the Arabic page as canonical.

How did we audit 20 Salla and Zid stores?

We picked 10 live Salla stores and 10 live Zid stores on their own domains, all selling in Saudi Arabia, and fetched each one on 2 October 2026. We checked robots.txt, the XML sitemap, one product page, its English version where one existed, and a sorted category page.

The stores came from search results for Saudi product categories: honey, dates, specialty coffee, nuts and sweets, oud and perfume, abayas and electronics. We confirmed the platform from each homepage’s source code, which loads Salla or Zid platform files. We kept both samples in similar categories so that any gap between them would come from the platform rather than the product.

Our fetcher behaved like a crawler’s first pass: a desktop Chrome user agent, Arabic as the preferred language, and raw HTML without running JavaScript. For sitemaps, we drew 15 random product URLs per store (8 for one small Zid store) and recorded the first HTTP response. Salla’s servers returned HTTP 429 (too many requests) when we went fast, so we reran every Salla check at 2 to 3 second intervals.

We do not name the stores, because this piece is about the defaults every merchant inherits. One Salla store was replaced before analysis because its homepage carried no product links and its sitemap pointed at another host.

What did the audit find?

Both platforms ship the basics: a canonical tag, a meta description, right-to-left Arabic markup and Product structured data with price and stock status. The differences sit in sitemaps, robots.txt, English pages and brand data. The table counts stores out of 10 per platform, measured on 2 October 2026.

Two rows explain most of the risk. Salla sitemaps send Google to URLs that no longer exist, and Salla English pages ask Google to index the Arabic version instead. Zid’s gaps are smaller and mostly sit in the robots.txt file.

Salla’s biggest default: sitemaps full of products that no longer load

On Salla, 88 of 146 sampled sitemap product URLs did not load directly: 48 redirected (302) to the homepage, 22 returned 410 Gone and 18 redirected (301) to a different product URL. Only 2 of 10 stores had a clean sample. On Zid, all 143 sampled URLs returned 200.

The pattern varied by store. Two stores returned 410 for most sampled products, which is a clear “removed” signal. Four stores sent most dead URLs to the homepage with a temporary redirect. Two had renamed many products, so their sitemaps still listed old slugs that now 301 to new ones.

Google’s sitemap guidance says to “include the URLs in your sitemap that you want to see in Google’s search results” (Google Search Central, Build and submit a sitemap). A product URL that bounces to the homepage is not one of those. Each one costs a crawl and tells Google the sitemap is unreliable.

From outside, we cannot see whether these products were hidden, out of stock or deleted inside the Salla dashboard. Merchants can see it in Search Console, where the Sitemaps and Page indexing reports list the URLs Google tried, and Salla’s SEO help article covers submitting the store sitemap to Google (Salla Help Center, SEO tools).

English pages that tell Google the Arabic page is the real one

Six Salla stores in our sample ran an English version. On all six, the English product page carried a canonical tag pointing at the Arabic product page, while its hreflang tags listed the English page as the English alternate. Zid stores with English pages (5 of 10) pointed each English canonical at itself.

Google is direct about this combination: “If you’re using hreflang elements, make sure to specify a canonical page in the same language” (Google Search Central, specify a canonical). A cross-language canonical asks Google to fold the English page into the Arabic one. For a Saudi store courting expatriate buyers, or a Gulf shopper who searches in English, that English page is the one that should rank.

The second problem is content, and it affects both platforms. On 4 of 6 Salla stores and 4 of 5 Zid stores, the English page’s title tag was still in Arabic script. Five of the 11 English pages also kept an Arabic-script slug. Zid’s own help page warns that enabling English is not automatic translation: every product, page and policy must be written again in English (Zid Help Center, store languages and currencies). On either platform, an English page with an Arabic title rarely wins an English query.

Zid’s biggest default: a 1,268-line robots.txt with no sitemap line

Eight of the 10 Zid stores served an identical default robots.txt of 1,268 lines. It blocks 627 named crawlers, mostly scrapers, and disallows cart, invoice and internal search URLs. Only 1 of 10 Zid files declared the sitemap, against 10 of 10 on Salla.

Every Zid store still had a working sitemap index at /sitemap.xml, so Google can find it once a merchant submits it in Search Console. The missing line matters for every other crawler, including Bing. Google’s own documentation shows the fix: one Sitemap: line anywhere in robots.txt (Google Search Central).

The default list also blocks PetalBot, the crawler behind Huawei’s Petal Search, along with hundreds of lesser-known bots. If your buyers do not use Huawei’s search app, you lose nothing by blocking it. None of the eight default files named GPTBot, ClaudeBot or Google-Extended, so AI crawlers are allowed by default on Zid. Salla also allows them by default, though 3 of 10 stores served a Content-Signal line declaring ai-train=no.

Zid merchants can edit the file. The robots.txt editor sits under Online Store, then SEO, and is limited to the Growth and Pro plans, which the help page calls Growth and Professional (Zid Help Center, customise robots.txt).

If you would rather have someone check your own store against these 20 checks, ask our SEO team for a Salla or Zid audit.

Arabic slugs: 57 characters on screen, 142 in the request

Six of 10 stores on each platform used an Arabic-script slug on the product URL we tested. Both platforms build the slug from the product name unless the merchant writes one. Zid’s product SEO page describes this field, and Salla’s developer docs list a custom URL field for products.

Arabic slugs read naturally in the address bar, but each Arabic letter is percent-encoded as six characters. Across our 12 Arabic-slug product URLs, the median length was 57 characters as displayed and 142 characters encoded. The eight Latin-slug URLs had a median of 41 characters.

Google supports this: its URL guidance recommends words in the audience’s language and uses a percent-encoded Arabic URL as its recommended example (Google Search Central, URL structure). The cost appears elsewhere. Links pasted into WhatsApp and email turn into long strings of percent codes, and some analytics and ad tools truncate them. Long titles turned into slugs make this worse, and our longest encoded URL ran to 227 characters.

If you write Arabic slugs, write them short and in the spelling customers actually type. Hamza and taa marbuta variants split search demand, as our study of Arabic spelling variants in Saudi search showed. Separate words with hyphens, as Google’s URL guidance recommends.

Which Product schema fields do Salla and Zid leave out?

Nineteen of 20 product pages shipped Product JSON-LD with a price in SAR and an availability value. All 10 Salla pages included SKU data, and 6 included review ratings. None of the 10 Salla pages included a brand property, while 9 of 10 Zid pages did.

Brand sits in Google’s own Product examples for merchant listings, next to SKU, GTIN and offers (Google Search Central, merchant listing structured data). Google reads it alongside your Merchant Center feed. For own-label honey, dates and oud, the brand is often the query itself.

The one Zid failure came from a theme. That store output a JSON-LD block typed as lowercase “product” with no offer, so validators do not read it as Product markup. Custom themes on either platform can break defaults that work on stock themes.

Salla’s API documentation shows brands carry their own SEO title, description and URL per language, and Salla’s help center covers MPN and GTIN fields on products. The merchant has to fill those fields in, and in our sample few had done so.

Salla fix checklist

Most Salla fixes happen in the dashboard and need no code. Start with the sitemap, because that is where 60% of our sampled URLs failed, then move on to titles and English pages. Salla’s developer docs confirm products carry a meta title, meta description and custom URL (Salla Docs, create product).

• Clean the sitemap at the source. Open Search Console, filter the Page indexing report to the sitemap, and list URLs that redirect or return 410. Decide per product: restore it, or delete it so it stops appearing.
• Stop sending removed products to the homepage. Where a product has a replacement, link to it from the old URL. Where it does not, a 410 tells Google it is gone.
• Fix the store name in titles. Every Salla title in our sample ended with the store name, and on 2 stores it appeared twice. If your SEO title field already includes the brand, test removing it there.
• Write English titles and descriptions for every product shown on the English site, not only the product name.
• Raise the English canonical with Salla support. We found no help article describing a setting that changes it. Test with Salla’s free SEO-GEO checker and Search Console’s URL Inspection.
• Add brand, GTIN and MPN to every product that has them.

Zid fix checklist

Zid stores in our sample had cleaner sitemaps and correct English canonicals, so there is less to do, mostly in robots.txt, titles and English content. Zid’s product SEO page sets the targets: product titles within 70 characters and descriptions within 320 (Zid Help Center, product SEO).

• Add the sitemap line to robots.txt on Growth or Pro, then submit the sitemap in Search Console on any plan.
• Write an SEO title for each product. Six of our 10 Zid titles were the bare product name, one only 8 characters long. Add the type, size and your brand.
• Write meta descriptions by hand. When the SEO fields are empty, Zid fills them with the product name and the start of the product description.
• Translate before you enable English. An English page with an Arabic title gives Google one more URL and nothing for an English searcher to read.
• Use the redirect tool after renaming products. Zid’s redirects are 301s and only fire on URLs that return 404 (Zid Help Center, URL redirects).
• Check custom themes with Google’s Rich Results Test after any theme change.

Measurement is the last gap, because many of these stores also sell on Amazon.sa and noon, and GA4 files visits from those marketplaces as Referral, as our GA4 traffic study for Arab markets explains.

Our read

Choose between Salla and Zid on operations, payments and fees, not SEO. Both ship sound page-level basics. The expensive problems in our sample were defaults nobody revisited: Salla sitemaps listing dead products, Salla English pages canonicalised to Arabic, Zid robots.txt files without a sitemap line, and English pages that were never translated.

We would not migrate a store over any of these. A migration costs months of redirects and relearning, and every issue above has a fix or a support ticket on the current platform. What we would do is spend one afternoon per quarter on the sitemap and the English pages, because that is where 20 merchants left the most on the table.

There is also an AI-search angle, because AI assistants and Google’s AI features cite product pages they can crawl and understand. A sitemap full of redirects and an English page that defers to Arabic make that harder, a point we cover in our guide to GEO for Arabic content.

FAQ

Is Salla or Zid better for SEO in Saudi Arabia?

Neither wins outright. In our 2 October 2026 audit of 20 stores, Zid had cleaner sitemaps and correct English canonicals, while Salla declared its sitemap in robots.txt and appended the store name to titles. Both shipped Product schema with price and availability. Your setup and content matter more than the platform you choose.

Why does Google Search Console show so many redirected URLs from my Salla sitemap?

In our sample, 88 of 146 Salla sitemap product URLs did not load directly. Most redirected to the homepage or returned 410. That points to hidden, deleted or renamed products still listed in the sitemap. Check the Page indexing report, then restore, delete or redirect each product deliberately.

Should I use Arabic or English words in my product URLs?

Either works for Google, which crawls UTF-8 URLs. Arabic slugs read well but encode to about 2.5 times their visible length in our sample, 142 characters against 57. Keep slugs short, use the spelling customers type, and avoid turning long product titles into URLs.

My Zid store has an English version but it doesn’t rank in English. Why?

Check the title tag first. On 4 of 5 Zid stores with English enabled, the English product page title was still in Arabic script. Zid does not translate automatically, so each product, page and policy needs English text written separately. Then confirm the English page’s canonical points to itself.

Does the Zid robots.txt block Google or ChatGPT?

No. The default Zid file we read on 2 October 2026 blocks 627 named crawlers, mostly scrapers, plus cart, invoice and internal search URLs. It does not name Googlebot, GPTBot, ClaudeBot or Google-Extended. It does omit the sitemap line, which Growth and Pro merchants can add.

Is your Salla or Zid store losing search traffic to defaults?

Which platform ranks better matters less than which defaults you inherited and never checked. If your sitemap is clean and your English pages are translated and self-canonical, spend your effort on content and links. If not, fix those two first, because new content does little while your sitemap keeps sending Google to the homepage.

If you want the same 20 checks run on your own store, with the fixes ranked by effort, Send us your store link and we will tell you what we find.