eCommerce SEO that sells from your own store.

Both, with the queries split between them. The marketplaces carry the product-name and model-number searches and will keep carrying them, because a first-time buyer trusts the delivery promise more than a store they have not used. Your own site is where the category, comparison and brand terms are winnable, and where the customer record, the margin and the repeat order stay with you. The expensive mistake is not selling on both, it is funding organic work on terms a listing already holds.

Usually leave it, and take the level above it instead. Displacing your own listing on an exact product name means out-ranking a far older domain for a query that converts either way, and the order still arrives. The winnable move is the category page, the comparison and the buying guide, where a marketplace has no equivalent page to rank. We check this term by term rather than assuming it, because on an own-brand or niche product the store often can win.

It has to match what the page shows the shopper, and in the UAE that displayed price is VAT-inclusive. Google compares the price in your Offer markup with the price rendered on the page, and a mismatch removes the rich result and can suspend the Merchant Center feed. Set the offer price to the VAT-inclusive figure and the currency to AED, then confirm the same number reaches the feed. The usual cause of a mismatch is a plugin writing the pre-VAT value straight from the database.

No. Google reads the price from your Offer markup, not from the instalment widget beside it. The widget still changes the page in two ways that matter: it is a third-party script loading right next to the price, which is a common reason a product page misses its mobile Core Web Vitals budget, and the instalment figure is often the largest number a shopper reads before clicking. Write the title and description around the full price rather than against it.

For consumer categories, yes, and it is a separate query set rather than a translation. An Arabic product term is frequently a different word, not the English one in Arabic script, so the research runs separately and the results land in product titles, attributes and category copy as well as the Merchant Center feed. For technical and trade lines the English catalogue often carries most of the demand. We scope the Arabic work alongside the English catalogue, or write down plainly that the engagement does not include it.

Catalogue size is the wrong test. The right one is whether category demand exists and whether a marketplace listing is already taking it. A Sharjah SAIF Zone consumer-electronics distributor carrying 4,000 lines whose trade half sells offline is a weaker case than an 80-product store in a category people actually type. Where that demand sits is a separate read, and for most UAE stores it starts with SEO in Dubai. Faceted-navigation crawl waste becomes the dominant problem above a few thousand URLs; below that the work is mostly category structure and markup.

Neither is better, and the crawl problem differs. Shopify keeps URLs tidy by default and limits some technical fixes; WooCommerce gives full control and lets facet parameters multiply unless they are governed from the start. The decision that matters more here is the checkout: whether Tabby, Tamara and your acquiring gateway are supported natively or through plugins that add script weight to every product page. If the store is still being built, that call belongs with the build team rather than with the SEO scope.