Technical SEO Consultant, UAE

Catalogs fed by an ERP and the URLs they multiply

Trading houses, distributors and retailers in the UAE often push product data from an ERP such as Odoo, Zoho Inventory, Dynamics or a legacy system into the website. That connection is efficient for staff and can be careless for crawlers. Every attribute the ERP holds, from size and color to brand, warehouse and unit of measure, can become a filter, and every filter combination can become a URL in two languages.

The typical symptoms are recognizable once you know where to look:

• Search Console reporting many more discovered pages than the catalog actually contains.
• Product pages duplicated because the sync creates a new record when a SKU code changes, leaving the old URL live with thin content.
• Discontinued items returning a normal status with an empty template, so they stay indexed for months.
• Arabic product names left blank in the ERP, so the Arabic page shows English text or nothing at all.

I map which facets carry real search demand, such as brand plus category, and which should be blocked, canonicalized or rendered without crawlable links. I also look at the integration itself: what triggers a new URL, how stock-outs are handled and where Arabic descriptions are meant to come from. Fixes sometimes belong in the ERP field mapping rather than the website, which is where my ERP integration background helps. The full audit method is described on the technical SEO audit page.

Right-to-left mirroring and the Arabic slug question

An Arabic version is more than translated text. The page needs a right-to-left direction attribute on the right element, a layout that mirrors through logical properties rather than a stack of manual overrides, and components that behave correctly in both directions. Sliders that scroll the wrong way, arrows that point backward, phone numbers that flip their digit order and tables whose columns read in the wrong sequence are all signs that mirroring was patched in late. Most of these are usability faults first, but they can also hide content or links from rendering and push layout shift up.

Then there is the URL. Arabic slugs are valid, yet browsers, analytics tools and server logs show them percent-encoded, which makes long strings of symbols that are hard to read, share or audit. Some letters also have several forms, so two spellings of the same word can create two addresses for one page. The alternatives are transliterated slugs or English slugs inside an Arabic folder. None is universally right. I set out the trade-offs for your CMS, choose a policy before pages are generated, and make sure redirects, canonicals and hreflang all use exactly the same encoded form. Structural choices about language folders and country versions are covered on the UAE international SEO page.

Speed on the phones your buyers actually carry

In the UAE most browsing happens on phones, often on fast networks, which tempts teams to assume performance is solved. Field data frequently disagrees, because the slow part is not the network but what the page asks the device to do. Core Web Vitals problems on Emirati sites tend to come from a few recurring sources:

• Arabic web fonts. Full font files with every weight and glyph, loaded for both scripts on every page, delay text and shift layout. Subsetting, fewer weights and a deliberate loading strategy help.
• Tag weight. Ad pixels for several networks, chat widgets, heatmaps and WhatsApp buttons all compete for the main thread, and slow taps show up as poor responsiveness.
• Consent banners. A banner injected after load can push content down. How consent is collected is a legal question for your advisor; how the banner renders is a technical one I can address.
• Hero media. Autoplay video and uncompressed lifestyle images on landing pages built for campaigns.

Hosting matters too. A site served from a distant data center without a CDN edge close to the Gulf adds delay before anything renders. Some organizations also prefer hosting data inside the country for compliance reasons; whether that applies to you is for your legal advisor, but I can assess the performance side of each option. The diagnostic method is on my Core Web Vitals consulting page.

Structured data for branches across the emirates

A business with a showroom in Dubai, a branch in Abu Dhabi and a warehouse in Sharjah needs search engines to understand that these are one organization with several locations, not several unrelated companies. Structured data is how you state that clearly. I plan it around your real page types rather than whatever a plugin outputs by default.

For UAE sites the model usually includes:

• One Organization entity with a stable identifier, defined once and referenced everywhere, with its Arabic and English names linked as the same entity.
• LocalBusiness markup on genuine branch pages, with addresses written the way the location is actually found, which in the UAE often means building, area and landmark rather than a street number.
• Product markup with offers in dirhams, availability that reads from the same stock field the page displays, and no ratings unless real reviews are shown on the page.
• Breadcrumb markup that matches the visible navigation in each language.

Common faults include three plugins each outputting their own organization block, prices in markup that lag behind the page because they read from a cache, and Arabic pages carrying English markup. Each value should come from one source, whether that is the CMS, the product feed or the location master. The schema markup consulting page explains the full approach.

Migrations, logs and working alongside your agency

Websites in the UAE are redesigned often: a rebrand, a new holding structure, a move from WordPress to a headless build, or a merger of brand sites into one group domain. Each of these can quietly erase years of search signals if old URLs are not mapped. I build the redirect map from crawls, Search Console, analytics landing pages and backlink data, test it on staging and again on production, and watch indexing closely after launch. The method is set out on the SEO migration consulting page.

Server logs are the most underused data source I ask for. They show which URLs Googlebot really requests, how often it visits the Arabic section compared with the English one, and whether it spends its time on filter combinations instead of new products. Many sites sit behind a CDN, so logs may need to be exported from the CDN rather than the origin server.

Many UAE companies rely on a development agency or an in-house team, and I work with either. I do not replace them; I give them precise specifications, answer their questions while they build, and check the result. Everything runs remotely, with calls arranged in Gulf hours and shared registers between them. For the wider picture of how the site connects to your systems, see the UAE digital transformation page or the UAE overview.