Technical SEO for Online Stores: Finding What Hides Your Products from Google

Technical SEO for an online store answers one question: can Google reach your product and category pages, index them, and understand what you sell and at what price? If not, neither blog posts nor backlinks will help. On hosted platforms such as Salla and Zid, the two main e-commerce platforms in Saudi Arabia, half the job is reading Search Console correctly and the other half is knowing what you can change yourself and what the platform controls.

Details about Google, Search Console and the platforms are current as of October 2026. If you came here for Salla or Zid specifically, the section on hosted platforms lists what each one documents.

What is technical SEO for a store, and why does it come before blogging?

Technical SEO is everything that makes a page crawlable, indexable and understandable: URLs, duplication, structured data, speed and the sitemap. Content SEO comes after it, because it improves a page that is supposed to be indexed already.

Starting with the blog is tempting because it is the visible part. My view is the opposite: a product page that isn't indexed won't sell through search however much you write around it, and a category page competing with five duplicate filter URLs loses before it starts. Fix the foundation, then write.

Search Console in 30 minutes: five reports, in order

Google Search Console is the free tool that shows how Google sees your site. This check is a tool you can run this week, in this order, because each step explains the next.

Minutes	Report	What to read	The question it answers
1–8	Page indexing (Pages)	Indexed vs not indexed, and the reasons for exclusion ranked by count	Does Google know my product pages, and why is it leaving some out?
9–12	Sitemaps	Last read date, URLs discovered	Can Google reach my full list of pages?
13–20	Performance	Pages and queries, with product and category URLs separated by a URL filter	Which pages show and get clicks, and which show without clicks?
21–26	Product reports (Merchant listings, Product snippets)	Valid items, errors, warnings	Does Google understand price and availability on my pages?
27–30	Core Web Vitals	Slow URL groups on mobile and desktop	Are product pages losing visitors before they finish loading?

Run the URL Inspection tool on three pages: a best seller, a new product and a category page. It shows whether each is indexed and which URL Google picked as canonical.

Then move every issue you find into this table, so you rank fixes by their effect on sales rather than by how many URLs they touch:

Issue	Report that shows it	Can you fix it yourself on a hosted platform?	Likely effect on sales
Product pages "Crawled - currently not indexed"	Page indexing	Partly: content, title, description, internal links	High: products missing from Search
"Duplicate" statuses, Google choosing a different canonical	Page indexing	Partly: internal links and category structure; canonical tags come from the platform	Medium: visibility goes to a weak URL
Large numbers of filter and sort URLs	Page indexing, Sitemaps	Usually platform or theme; ask support	Medium: crawl wasted on pages that don't sell
Empty or deleted categories showing "no products"	Page indexing (Soft 404)	Yes: remove or fill the category	Low to medium
Missing or wrong price and availability	Product reports	Usually the theme; the data itself from the dashboard	High: weaker product results
Duplicate or auto-generated titles and descriptions	Performance (impressions without clicks)	Yes on Zid, from product and category fields	Medium: lower click-through
Slow on mobile	Core Web Vitals	Partly: images, added apps, theme	Medium: visitors leave before buying

Why aren't product pages indexed? Causes and fixes

The page indexing report gives each excluded page a specific reason, and each reason needs a different fix. These are the statuses that matter most to stores, in Google's own definitions:

• Crawled - currently not indexed: Google crawled the page and didn't index it; it may or may not index it later. Possible causes in a store include descriptions copied from the supplier or identical to dozens of other pages. The fix is content that distinguishes the product and internal links from a strong category.
• Discovered - currently not indexed: Google knows the URL but hasn't crawled it. When this appears alongside thousands of filter URLs, crawling is being spent on pages you don't need.
• Duplicate without user-selected canonical and Duplicate, Google chose different canonical than user: Google treats the page as a copy of another. Inspect the URL to see which one it chose.
• Soft 404: a page that says "not found" or "no products" but returns a success code. Google asks for a real 404 for removed pages.
• Not found (404): normal for a product removed without a replacement. If it moved, use a permanent 301 redirect.
• Alternate page with proper canonical tag: nothing to do; the page correctly points to the indexed version.

After fixing, click "Validate fix" once. Google says validation typically takes up to about two weeks and can take much longer, and asks you not to click it again until it succeeds or fails.

Hypothetical example, rounded numbers: a store lists 1,800 products in its sitemap, and 950 product pages are indexed. The indexing report shows 6,000 URLs as "Crawled - currently not indexed", most of them color, size and sort parameters. Reading: Google is spending its time on filter URLs while 850 real products sit outside the index. The right order of work: stop filter URLs being crawled, then strengthen internal links to the unindexed products, then improve the weakest product content.

Duplicate pages in stores: filters, variants and categories

Duplication in stores comes from three sources, and Google has published guidance on each.

Filters and sort orders. URLs such as ?color=red&sort=price multiply into thousands of near-identical pages. Google's faceted navigation guide recommends disallowing filter URLs in robots.txt if you don't need them in Search, and says a canonical tag may reduce crawling of non-canonical versions over time but is generally less effective long-term than robots.txt. If you do want some filters indexed, use the standard & separator and return a 404 for filter combinations with no results.

Variants. A product in several colors or sizes. Google's ecommerce URL guide asks that each variant be identifiable by its own URL, by path or parameter, and that variant pages defined by optional parameters point their canonical to the main product URL.

Categories. The same product in five categories can carry five URLs. Use one URL for the product in every internal link, the sitemap and the canonical tag; Google asks for one consistent URL form everywhere. Empty categories get noindex; deleted ones return 404.

For Saudi sales seasons: give the White Friday or Ramadan page a permanent URL you refresh each year, rather than a new page every season that starts from zero.

Product structured data: what Google requires and how to check it

Structured data is code on the page that tells Google what the page contains in a machine-readable form. For products there are two kinds: product snippets, and merchant listings for pages that sell directly. Merchant listings are stricter, and Google asks for:

• Required: product name, image, and an offer with the actual price and currency, such as SAR.
• Recommended: availability, shipping details, return policy, GTIN, and aggregate rating.

On Salla and Zid the theme usually writes this markup, not you. Your job is to check it. Search Console shows a Merchant listings report and a Product snippets report when Google finds that markup on your site, and Google recommends the Rich Results Test for checking an individual page. If neither report appears at all, ask the platform whether your theme outputs product markup.

The rule that matters most: the price in structured data matches the page price and the Merchant Center feed price. Google compares them, and a mismatch gets products disapproved in Shopping, as I explain in Merchant Center disapprovals and suspensions.

Internal links: how do you tell Google which store pages matter?

Internal links are the links between your own pages, and they are how Google learns what you consider important. Google's ecommerce guide has a whole page on helping it understand store structure through navigation and internal linking, because a store where a product sits four clicks from the homepage is telling Google that product is secondary.

Four rules I apply in any store:

1. The main menu carries the categories that sell, not every category. A category that brings in sales earns a place in the menu and on the homepage.
2. Category pages link to each product with one stable URL, not a URL carrying category or sort parameters.
3. Product pages link back to their category and to complementary products, so they are never a dead end.
4. Unindexed products get links from strong pages: the most-visited category, or an active season page.

If the store runs in Arabic and English, the menu should carry the same links in both versions, so neither looks like a different store.

Store speed on mobile and Core Web Vitals

Core Web Vitals are three page-experience measures Google publishes: Largest Contentful Paint within 2.5 seconds, Interaction to Next Paint under 200 milliseconds, and Cumulative Layout Shift below 0.1, per Google's Core Web Vitals documentation. Google doesn't call them a direct ranking factor, but strongly recommends good scores for success in Search.

On a hosted store you don't control the server, but you control three things: the size of the images you upload, the number of apps and add-ons that inject scripts into every page, and the choice of theme. Check the mobile report first, and start with the product pages that bring in the most sales.

What you can and cannot change on Salla and Zid

Salla and Zid are hosted platforms: the platform runs the server and the base theme, and you manage content and the settings it exposes. This is what each platform documents in its help centre as of October 2026. Anything I couldn't find documented goes in the "ask the platform" column rather than being assumed.

Setting	Zid (help centre)	Salla (help centre)	Ask the platform
Product page title, description and URL	Yes, on the product page: title within 70 characters, description within 320, URL from the product name	Unconfirmed
Category title, description and URL	Yes, under Products, then Categories	Unconfirmed
Homepage title and description	Yes, under Online Store, then SEO	Unconfirmed
Product GTIN and MPN	Unconfirmed	An article covers adding them to improve product visibility
Sitemap	Describes the sitemap and submitting it through Search Console	Unconfirmed
Search Console connection	A 2024 article explains URL-prefix verification	Unconfirmed
robots.txt, canonical tags, filter URLs, structured data			Yes

Two notes. First, Zid says it fills the title and description from the product name and description when the fields are empty, which produces near-identical titles; write them yourself for your key products. Second, the character limits a platform gives are not Google's; Google truncates titles by available width, so put the important words first. If the store runs in Arabic and English, confirm with the platform that each version points to the other with hreflang tags.

Measure organic sales, not visits

Organic sales are the revenue from orders that came through unpaid search results. That is the number that judges SEO, not traffic. In GA4, open the Traffic acquisition report, select the Organic Search channel, read revenue and orders, and compare with the same period before the fix, and with the same period last year if a season such as Ramadan falls inside it.

In Search Console, compare clicks to product and category pages only, not to the whole site. Blog traffic can rise while sales stay flat, and that is not success.

From my work: At Argan Package in Saudi Arabia, where I was Digital Marketing Manager, organic sales rose 15% within four months after Search Console and technical SEO issues were fixed. It is one store in one period, and it doesn't mean every store will see the same figure. The details are in the Merchant Center and SEO case study.

What to do next

Set aside 30 minutes this week for the Search Console check in the order above, move every issue into the sales-effect table, and start with whatever keeps product pages out of the index. Then read how to make your store a source AI answers cite in showing up in ChatGPT and Google's AI answers, and where SEO sits in the store growth map. If you want someone to read Search Console and your store with you and rank the fixes by effect, that is the work of my technical SEO audit.

Want your team trained on this? Training programs are built on your own store and accounts.