# Technical SEO audit for online stores: a report on what blocks indexing, in fix order

Updated October 10, 2026

<https://mqudah.com/en/services/technical-seo-audit/>

I look for whatever stops Google from reading your whole store: pages left out of the index, Search Console errors, thin product data, slow mobile pages, and pages competing with each other. You get a fix list ranked by the organic sales each item brings back, and every line names the page, the change and who makes it.

## Is this what you need?

- Almost all our sales come from paid ads. Organic search barely exists for us.
- Search Console says thousands of pages aren't indexed, and nobody on the team knows where to start.
- I type my product's name into Google and get a filter or category page, not the product.
- We moved platforms or changed our URLs, and search traffic has been sliding ever since.
- The developer says the site is fine. The numbers say something else.

## Why it happens

Search Console holds two numbers that almost nobody at an online store looks at: pages indexed and pages not indexed. The second one grows with every new product and every filter the theme adds. Products added weeks ago stay out of search, while filter and sort pages nobody searches for take their place. And the store keeps paying for each visit with an ad, when part of that traffic could have come from search at no cost per click.

I judge a technical audit by the sales it brings back, not the warnings it clears. So I rank each fix by what the affected pages sell, and write it in terms a developer can act on the next morning. For stores in Saudi Arabia and Jordan on Salla or Zid, I always separate what the owner controls from what the platform controls, because half the time in this work usually goes on asking for changes that can't be made.

This audit is one part of the [marketing and revenue audit](https://mqudah.com/en/services/marketing-audit/). If your question is about paid traffic rather than organic, start with the [Google Ads audit](https://mqudah.com/en/services/google-ads-audit/).

## What I do, in order

- **I compare what you want indexed with what Google indexed**: I set the sitemap against the page indexing report in Search Console and sort the excluded pages by reason: blocked, duplicate without a declared canonical, or crawled and left out. Then I separate the products and categories that sell from the pages that never deserved indexing.
- **I rank errors by the sales they block**: A hundred warnings on pages that sell nothing matter less than one error on a main category. I tie each error to the pages it hits and to their sales, so the work starts with what brings money back, not with what clears the most warnings from the dashboard.
- **I trace Google's route to every product**: Categories, internal links and navigation: how many clicks separate a product from the home page, and whether any products have no internal link pointing to them. A product no link reaches may be a product Google never reaches.
- **I check the product page's structured data**: Can Google read price, availability and currency from the page itself, and do they match the Merchant Center feed? That data is what makes a product eligible to show with its details in search and in Shopping.
- **I name the cause of slow mobile pages**: What weighs down product and category pages on a phone: uncompressed images, scripts added by apps, or the theme itself. I name the cause and the page, because a speed score alone tells a developer nothing about what to fix.
- **I settle the pages that compete with each other**: Filters, color and size variants and sort orders spawn many URLs for the same content. I decide which get indexed, which point to the original, and which stay out of the crawl.

## What you receive

- A written report of fixes ranked by their effect on organic sales and the effort they take
- For each item: the affected pages, the exact change, and who makes it: you, your developer or the platform's support
- A list of pages to index, pages to point to an original, and pages to exclude
- A walkthrough for you and your developer that ends with an agreed order of work

## What I need from you

- Access to Search Console, and viewer access to GA4
- The store URL and the platform it runs on
- Sales by product or category for the last three months, so I can rank fixes by effect

## What this does not cover

- Code changes or theme edits; those sit with your developer or the platform's support
- Writing content or building external links
- Promises of rankings or page one; nobody can make them

## Questions

### Does the audit guarantee a first-page ranking?

No, and nobody can guarantee one. The audit removes what keeps Google from reading and indexing the store; ranking after that depends on content, competition and time.

### My store runs on Salla or Zid. What can I actually fix?

On Saudi hosted platforms like Salla and Zid, part of the technical structure belongs to the platform. The rest is yours: categories, product titles and descriptions, images and internal links. The report separates the two, so you never ask your developer for something the platform won't allow, and you know when to write to its support.

### When will the fixes show an effect?

Recrawling and indexing are in Google's hands, so I won't give you a date. What I can say is that this kind of work reads in months, not days; at Argan Package the rise came within four months.

### My products are also missing from Shopping results. Does the audit cover that?

It covers the structured data on product pages. Showing in Shopping runs through Merchant Center and the product feed, which is its own piece of work: [Google Merchant Center setup](https://mqudah.com/en/services/merchant-center-setup/).

### What does the audit cost, and how long does it take?

Scope sets both: the size of the store, the number of categories and the platform it runs on. You see the cost in writing before we start, and I set the timeline after I've seen the indexing report, not before.
