An ecommerce SEO audit is a review of the technical, content and commercial factors that affect a store's organic visibility and revenue.

A useful audit follows 14 stages:

  1. Define commercial goals and audit scope.
  2. Establish a performance baseline.
  3. Crawl the site and compare crawlable, indexable and ranking URLs.
  4. Check technical SEO, site architecture and faceted navigation.
  5. Review category, product and editorial templates.
  6. Validate product data, structured data and Merchant Center feeds.
  7. Test JavaScript rendering, mobile usability and Core Web Vitals.
  8. Rank issues by business impact.
  9. Retest the highest-value fixes and measure their effect on organic revenue.

Google's ecommerce guidance focuses on crawlable navigation, clear site structure, relevant structured data and product information that can be understood across Google Search and other shopping surfaces.

Ecommerce SEO Audit at a Glance

Audit area Main question Typical output
Business performance Which products, categories and queries matter most? Revenue and traffic priorities
Crawling and indexing Can search engines discover and index the right URLs? Technical issue list
Site architecture Are important categories and products easy to reach? Internal linking and navigation plan
Page templates Does each page type satisfy its search intent? Category and product page recommendations
Product data Do product details match across the website and feeds? Feed and structured data fixes
Performance Are key templates fast and usable on mobile? Template-level performance actions
Authority and trust Does the store demonstrate relevance and credibility? Link, brand and trust opportunities
Measurement Can improvements be connected to business results? Prioritised implementation roadmap

1. Define the Scope Before Crawling the Store

Start with the business context. Without it, an audit can become a long technical checklist that overlooks the pages generating the most value.

Record:

  • Main country, language and currency
  • Ecommerce platform, such as Shopify, WooCommerce, Magento or a custom build
  • Primary goals, such as revenue, qualified traffic, new customers or product visibility
  • Highest-revenue product categories
  • Best-selling and highest-margin products
  • Seasonal products and inventory constraints
  • Recent migrations, redesigns or domain changes
  • Organic traffic and revenue trends
  • Target competitors and search results for priority queries

Create a URL inventory by page type:

  • Homepage
  • Category pages
  • Subcategory pages
  • Product pages
  • Product variant pages
  • Faceted or filtered pages
  • Internal search results
  • Editorial content
  • Buying guides
  • Brand pages
  • Store locator pages
  • Out-of-stock and discontinued product pages

Review templates before reviewing individual URLs. A practical sample should include:

  • The homepage
  • The five to ten most valuable category pages
  • Several high-revenue product pages
  • A product with multiple variants
  • An out-of-stock product
  • A filtered category URL
  • An editorial page
  • A page with known traffic or indexing problems

2. Establish a Performance Baseline

Use Google Search Console to review search performance by query, page, country and device. Use Google Analytics 4 to understand what visitors do after they arrive. Google identifies Search Console as the source of truth for Google Search performance and Google Analytics as the source of truth for behaviour on the website.

Capture:

  • Organic clicks and impressions
  • Click-through rate by page and query
  • Average position for commercial queries
  • Organic landing pages
  • Organic add-to-cart rate
  • Organic checkout and purchase rate
  • Organic revenue by category and product
  • Indexed pages
  • Pages excluded from indexing
  • Merchant Center product disapprovals
  • Product feed coverage
  • Core Web Vitals by template
  • Organic traffic changes after major releases or migrations

Look for gaps between search visibility and commercial value. For example:

  • A category earns many impressions but has a low click-through rate.
  • A product ranks well but converts poorly.
  • A high-margin category receives little organic traffic.
  • Google indexes thousands of filtered URLs but few core category pages.
  • Merchant Center reports product errors for products that perform well on the website.

These gaps should shape the audit priorities.

3. Crawl the Website and Reconcile the URL Sets

Run a crawl using standard HTML parsing and JavaScript rendering when the store depends heavily on client-side functionality.

Compare four URL sets:

  1. URLs discovered by the crawler
  2. URLs included in XML sitemaps
  3. URLs Google has indexed
  4. URLs receiving organic traffic or revenue

The differences can reveal problems such as:

  • Important products are not internally linked.
  • Sitemaps contain redirected, canonicalised or non-indexable URLs.
  • Google indexes filter combinations that the business does not want indexed.
  • Product pages return soft 404s after inventory changes.
  • Category pages are blocked by noindex.
  • The site links to tracking URLs or temporary session URLs.
  • Canonical tags point to the wrong product or category.

For every important URL, check:

  • HTTP status code
  • Indexability
  • Canonical URL
  • Robots directives
  • XML sitemap inclusion
  • Internal links
  • Rendered HTML
  • Title and meta description
  • H1 and visible page content
  • Structured data
  • Mobile version
  • Page speed

A sitemap should contain the preferred, indexable versions of important pages. Google treats sitemap inclusion as a weaker canonical signal than redirects and rel="canonical", so these signals should agree.

4. Audit Crawling, Indexing and Ecommerce URL Structure

Check Robots.txt and Noindex Directives

Robots.txt controls whether crawlers can access URLs. It is not a reliable way to remove a page from Google's index. Use noindex or authentication when a page should not appear in search, while allowing Google to crawl the page and see the directive.

Check whether the store accidentally blocks:

  • Product pages
  • Category pages
  • Images
  • CSS and JavaScript required for rendering
  • XML sitemaps
  • Important internal link destinations

Also review whether the store allows unnecessary URLs, including:

  • Internal search results
  • Session URLs
  • Tracking parameters
  • Sort orders
  • Empty filter combinations
  • Duplicate variant URLs
  • Cart and checkout pages

Inspect Canonicalisation

Ecommerce sites often create duplicate URLs through:

  • Colour and size variants
  • Filters
  • Sort orders
  • Pagination
  • Uppercase and lowercase URL variations
  • Trailing slash differences
  • HTTP and HTTPS versions
  • Tracking parameters
  • Multiple category paths to the same product

A canonical tag is a hint, not an absolute instruction. Google may select a different canonical when redirects, content quality or internal links conflict with the preferred URL. Check Google's selected canonical in URL Inspection instead of assuming the canonical tag worked.

Review Faceted Navigation

Do not index every possible filter combination. First identify filters that represent meaningful search demand and deserve dedicated landing pages.

A fashion store might create indexable pages for:

  • Black maxi dresses
  • Waterproof hiking jackets
  • Women's wide-fit running shoes

It would usually avoid indexable pages for every combination of colour, size, sort order and stock status.

For each facet, decide whether it should be:

  • A permanent indexable landing page
  • Crawlable but canonicalised
  • Marked noindex
  • Excluded from crawling where appropriate
  • Replaced by a curated category page

Base the decision on search demand, unique content, inventory stability, conversion potential and whether the page offers value beyond a filtered product list.

5. Audit Site Architecture and Internal Linking

Google uses the relationships between linked pages to understand site structure and relative importance. A basic ecommerce structure should let crawlers and shoppers move from the main navigation to categories, subcategories and products through standard links.

Check that:

  • Important categories are linked from the main navigation.
  • Subcategories are linked from relevant parent categories.
  • Product pages are reachable through category or collection pages.
  • Breadcrumbs link to valid category pages.
  • Related products create useful contextual links.
  • Best-selling products are not buried several clicks deep.
  • Links use standard HTML <a href> elements.
  • Internal links do not depend entirely on JavaScript events.
  • Anchor text describes the destination accurately.
  • Orphaned products and categories are identified.

Internal links should help shoppers find related products, alternatives, accessories and buying guides. Authority distribution is only one part of the job.

6. Audit Category Pages Against Search Intent

Category pages usually target broader commercial searches than product pages. Each important category should have a clear purpose and a distinct search target.

Check whether the page provides:

  • A descriptive, unique title
  • A clear H1
  • An informative introduction where useful
  • Relevant products in crawlable HTML
  • Useful filters without uncontrolled indexation
  • Descriptive product links
  • Breadcrumbs
  • Internal links to related categories and guides
  • Content that explains the category's differentiators
  • Proper pagination or incremental loading
  • A useful experience when products are unavailable

Avoid adding large blocks of generic text to increase word count. Category content should help shoppers compare products, understand attributes and move through the catalogue.

A category for "women's waterproof hiking jackets" might explain waterproof rating, insulation, fit and intended conditions. It should not use copy that could apply to every clothing category.

7. Audit Product Pages and Product Variants

A product page should make the product, offer and buying conditions clear.

Check each product template for:

  • Unique product name
  • Brand
  • Model or product identifier
  • Clear description
  • Current price and currency
  • Availability
  • Product condition
  • Variant selection
  • Size, colour, material or other relevant attributes
  • Useful images
  • Image alt text
  • Reviews and ratings where legitimate
  • Shipping information
  • Returns information
  • Delivery estimates
  • Stock messaging
  • Related products
  • Clear purchase controls

Product variants need a clear URL strategy. Decide whether variants use:

  • One URL with selectable options
  • Separate URLs for individual variants
  • A parent product page with linked variant pages

When separate variant URLs exist, each URL should identify the variant and explain its relationship to the parent product. Google supports product variant structured data using ProductGroup, hasVariant, variesBy and productGroupID.

Review what happens when products are:

  • Temporarily out of stock
  • Permanently discontinued
  • Replaced by a newer model
  • Removed from the catalogue
  • Available in only one variant
  • Available in another country or currency

Do not redirect every discontinued product to the homepage. Redirect to a relevant replacement when one exists. Otherwise, preserve useful product information where appropriate or return the correct status code when the product and its alternatives are no longer available.

8. Validate Structured Data and Merchant Center Data

Review page-level structured data alongside product feed data.

Google says product structured data can make pages eligible for richer search experiences, while Merchant Center data supports product visibility across Google surfaces. Google recommends using both where possible because the sources can help Google understand and verify product information.

Validate:

  • Product and Offer markup
  • Product name
  • Image
  • Brand
  • SKU
  • GTIN or MPN where available
  • Price
  • Currency
  • Availability
  • Product condition
  • Review and rating data
  • Shipping information
  • Return policy
  • Variant relationships
  • Product URL

Compare structured data, visible page content and Merchant Center values. They should agree on:

  • Product title
  • Price
  • Currency
  • Availability
  • Variant
  • Colour
  • Size
  • Shipping
  • Returns

Google Merchant Center recommends matching product data to the landing page, including the exact product variant and colour naming. Google also advises providing strong product identifiers, such as GTIN or MPN with brand information, when available.

Use the Rich Results Test and URL Inspection on representative product pages. Fix errors that affect product eligibility or data accuracy first, then review lower-impact warnings.

9. Test JavaScript Rendering and Page Delivery

JavaScript can affect product content, navigation, links, canonical tags and structured data. Google processes JavaScript through crawling, rendering and indexing, but blocked resources or content that appears only after unreliable interactions can cause problems.

Compare the raw HTML with the rendered DOM for:

  • Product name and description
  • Price and stock status
  • Category text
  • Internal links
  • Breadcrumbs
  • Canonical URL
  • Robots directives
  • Structured data
  • Image URLs

Important product information should not depend on a shopper clicking a control before it becomes available to crawlers. Google recommends putting merchant product markup in the initial HTML where possible, especially for frequently changing information such as price and availability.

Test:

  • Client-side category loading
  • Infinite scroll and pagination
  • Variant switching
  • Add-to-cart functionality
  • Filter links
  • Mobile navigation
  • Cookie and consent scripts
  • Third-party review widgets
  • Personalisation scripts
  • Lazy-loaded product descriptions and images

10. Measure Mobile Performance and Core Web Vitals

Test the templates receiving the most organic traffic, not only the homepage. Review field data alongside lab diagnostics.

The current Core Web Vitals targets are:

Metric What it measures Good target
LCP Loading performance 2.5 seconds or less
INP Responsiveness to interactions 200 milliseconds or less
CLS Visual stability 0.1 or less

Google recommends assessing these thresholds at the 75th percentile, segmented by mobile and desktop where appropriate.

Common ecommerce causes include:

  • Oversized hero and product images
  • Slow theme code
  • Excessive third-party scripts
  • Review and chat applications
  • Delayed font loading
  • Unstable image dimensions
  • Sticky banners that move page content
  • Slow search and filtering interfaces
  • JavaScript blocking the main thread
  • Slow server response times

Prioritise templates with high traffic, high revenue or high mobile usage. A small improvement across thousands of product pages may be worth more than a large improvement on a low-traffic editorial page.

11. Review Content Quality, Trust and Authority

An ecommerce store should give shoppers enough evidence to make a purchase decision.

Check for:

  • Original product descriptions
  • Accurate specifications
  • Demonstration images or videos
  • Clear sizing and compatibility information
  • Expert guidance for complex products
  • Genuine customer reviews
  • Transparent shipping and returns
  • Contact and business information
  • Secure checkout
  • Clear warranty information
  • Helpful buying guides
  • Evidence of experience with the products

Review external visibility as well:

  • Relevant backlinks to category and product pages
  • Brand mentions
  • Digital PR opportunities
  • Links to original research or useful tools
  • Unnatural or manipulative link patterns
  • Manual actions or security issues in Search Console

Seek links that make important commercial pages easier to discover and support the store's credibility. Avoid acquiring links without regard for relevance or business value.

12. Make Product Information Easy for Search Systems to Understand

There is no separate shortcut for AI-assisted search. The practical approach is to make the store's entities and relationships clear.

Ensure the website consistently identifies:

  • Brand
  • Product
  • Product type
  • Variant
  • SKU
  • GTIN or MPN
  • Price
  • Availability
  • Shipping
  • Returns
  • Reviews
  • Related products
  • Parent and child categories

Use the same product details in visible page content, structured data and Merchant Center feeds. Consistent information gives search systems clearer material to retrieve and summarise. Google says ecommerce product data can appear across Search, Images, Lens, Shopping and other Google surfaces, while Merchant Center supports product visibility on additional surfaces, including Gemini.

13. Prioritise Findings by Impact

An audit should not present every issue as equally important. Score each finding using:

Priority = business impact × affected URL value × confidence ÷ implementation effort

Classify issues as follows.

Critical

  • Important pages blocked from crawling
  • Accidental sitewide noindex
  • Incorrect canonical tags on revenue pages
  • Product pages missing from internal navigation
  • Incorrect prices or availability in feeds
  • Broken checkout or add-to-cart journeys
  • Major migration or redirect failures

High

  • Poor category architecture
  • Duplicate product and variant URLs
  • Indexable faceted navigation at scale
  • Thin or duplicated product templates
  • Missing product structured data
  • Slow product and category templates
  • Large organic landing pages with poor conversion rates

Medium

  • Missing or duplicated titles
  • Weak internal linking
  • Missing image alt text
  • Inconsistent breadcrumbs
  • Weak category introductions
  • Broken or outdated related-product links

Low

  • Minor metadata length issues
  • Non-critical crawler warnings
  • Small image optimisation opportunities
  • Cosmetic issues with limited search or revenue impact

Every recommendation in the final audit should include:

  • Affected URL pattern
  • Problem
  • Why it matters
  • Evidence
  • Recommended fix
  • Responsible team
  • Estimated effort
  • Success metric
  • Validation method

14. Re-crawl and Measure After Implementation

An audit is incomplete until the fixes have been checked.

After implementation:

  1. Re-crawl the affected URL patterns.
  2. Test representative pages in URL Inspection.
  3. Validate structured data again.
  4. Check Merchant Center diagnostics.
  5. Confirm sitemap and canonical consistency.
  6. Compare organic clicks, rankings and conversions.
  7. Monitor traffic by page template and category.
  8. Check whether Google selected the intended canonical.
  9. Record which changes produced measurable results.

When possible, release high-confidence fixes in controlled batches. This makes it easier to connect changes with performance effects.

What the Final Ecommerce SEO Audit Should Deliver

The final deliverable should be an action plan, not a software export. It should show:

  • The highest-value technical problems
  • The pages and templates affected
  • The commercial reason each issue matters
  • The exact implementation recommendation
  • The expected risk or limitation
  • The owner and effort required
  • The measurement plan
  • The order in which fixes should be released

Start with the pages and product groups that matter most to the business. Use crawlability, indexation, architecture, product data, search intent and performance evidence to explain what is holding them back.