How do you conduct an ecommerce SEO audit?

An ecommerce SEO audit is a structured review of the factors that affect a shop’s crawling, indexation, rankings, user experience and organic revenue. Conduct it by establishing the site’s goals and page inventory, checking technical accessibility, analysing indexation and site architecture, reviewing category and product pages, validating internal links and structured data, assessing mobile performance, and comparing organic performance with commercial priorities. Finish by turning the findings into a prioritised action plan and measuring the effect of each change.

Start with the audit scope and objectives

Define what the audit needs to achieve before reviewing individual URLs. The scope may cover the whole domain, a particular ecommerce platform, a product range, a country subfolder or a migration. Record the key commercial objectives, such as increasing visibility for category terms, recovering traffic to affected products, improving non-brand discovery or increasing organic revenue.

Collect the information needed to interpret the findings accurately:

• Access to Google Search Console and analytics data, including organic landing pages, conversions and revenue where available.
• A complete or representative URL list from the XML sitemap, ecommerce platform and website crawl.
• Product, category, brand, filter and editorial content inventories.
• Details of recent platform changes, migrations, redesigns, stock issues or seasonal campaigns.
• Information about priority products, high-margin categories and pages that support business objectives.

This prevents the audit from treating every URL as equally important. A technical issue on a key category page normally deserves more attention than the same issue on a discontinued product URL.

Build a reliable URL inventory

Combine crawl data with XML sitemaps, analytics, Search Console and the ecommerce platform’s product catalogue. The combined inventory should show each URL’s status, page type, indexability, canonical target, organic visits, impressions, clicks, rankings, conversions and commercial value where those data are available.

Classify URLs by purpose, for example:

• Home page, category and subcategory pages.
• Product and product-variant pages.
• Brand, collection and editorial pages.
• Search results, filters, sorting and pagination URLs.
• Basket, checkout, account, login and other utility pages.
• Out-of-stock, discontinued, duplicate and redirected URLs.

Compare the URLs that exist in the site’s navigation and sitemap with the URLs receiving organic traffic and the URLs being indexed. Gaps often reveal orphaned pages, unwanted parameter URLs, missing products or important pages that are difficult for crawlers and users to reach.

Check crawlability and technical accessibility

Search engines need to be able to discover and request important pages. Review the robots.txt file for rules that block valuable categories, products, images, JavaScript or CSS. Blocking a URL in robots.txt does not reliably remove it from search results, so use the appropriate indexing controls for pages that should not appear in search.

Check for:

• Server errors, repeated redirects, redirect chains and redirect loops.
• Pages returning a successful status but containing little or no useful content.
• Important content that depends entirely on interactions or scripts that search engines may not process consistently.
• Slow or unreliable server responses.
• Inconsistent HTTP and HTTPS, www and non-www, or trailing-slash versions.
• Incorrect handling of URL parameters, session identifiers and tracking parameters.

Crawl the site as both a search engine and a user would experience it. A technically accessible URL can still be difficult to discover if it is not linked from relevant navigation, category content or other indexable pages.

Review indexation and canonicalisation

Indexation should reflect the pages that deserve to rank, not every URL the platform can generate. Compare indexed pages with the URL inventory and investigate unexpected patterns, including:

• Important category or product pages excluded from indexing.
• Duplicate product pages created by variants, filters or tracking parameters.
• Thin internal search results, basket pages or account pages appearing in search.
• Out-of-stock or discontinued pages that remain indexed without useful alternatives.
• Canonical tags pointing to the wrong category, product or language version.
• Pages marked noindex while also being included in XML sitemaps or prominent internal links.

Use self-referencing canonicals on pages intended to be indexed unless there is a clear reason to consolidate them. Canonical tags are signals rather than guaranteed instructions, so they must agree with redirects, internal links, sitemap entries and the page’s visible content.

Check whether the XML sitemap contains only canonical, indexable URLs that return a successful response. Separate sitemaps by page type where this makes monitoring easier, and remove obsolete URLs promptly after changes to the catalogue.

Evaluate site architecture and internal linking

A strong ecommerce architecture makes important pages easy to discover and establishes clear relationships between products, categories and supporting content. Review the number of clicks required to reach priority pages, the consistency of navigation and the descriptive quality of anchor text.

Pay particular attention to:

• Categories that are not linked from the main navigation, relevant parent categories or other useful pages.
• Products that can only be reached through internal search or filters.
• Orphaned URLs that appear in a sitemap but have no internal links.
• Overlapping categories that target the same search intent.
• Links that lead to redirected, unavailable or non-canonical URLs.
• Faceted navigation that creates a very large number of low-value crawlable combinations.

Use breadcrumbs to clarify hierarchy and link back to relevant category levels. Add contextual links between closely related categories, buying guides and products where they help users make a decision. Avoid forcing links into copy solely to distribute internal authority; relevance and usability should guide the structure.

Audit category and collection pages

Category pages often target broader commercial searches and should provide more than a product grid. Check whether each important category has a clear, unique purpose and accurately reflects the products displayed. The page title, main heading, introductory copy, product listings, navigation and metadata should support the same topic.

Review whether category pages have:

• A descriptive title and clear main heading.
• Useful introductory or supporting content that helps visitors understand the range.
• Logical subcategory links and filters that do not obscure the main range.
• Unique copy rather than text copied from another category or supplier.
• Products that are available, relevant and arranged in a useful order.
• Content and links that remain accessible without requiring excessive interaction.

Do not add large blocks of generic copy simply to increase word count. Explain product differences, specifications, use cases, compatibility, materials, sizing or buying considerations where those details genuinely help the customer.

Audit product pages

Product pages should make the product understandable, comparable and easy to purchase. Check that each important product has a unique, indexable URL with accurate information that matches the catalogue and the structured data.

Assess:

• Product names, titles and headings for clarity and consistency.
• Descriptions for originality, useful specifications and coverage of customer questions.
• Images for quality, descriptive alternative text and appropriate file handling.
• Availability, price, delivery, returns, sizing, compatibility and other material purchase information.
• Variant handling, including whether variants need separate URLs or should be consolidated.
• Reviews, questions and other genuine customer-generated information where relevant.
• Related products, accessories and alternatives that create useful internal links.

Handle unavailable products according to their circumstances. A temporarily unavailable item can usually remain available with clear stock information and suitable alternatives. A permanently discontinued product may need a relevant redirect, removal from navigation or a useful replacement page. Avoid redirecting every discontinued product to the home page, as that rarely satisfies the original intent.

Assess on-page targeting and content quality

Map target search intent to the appropriate page type. Broad commercial searches generally belong on category or collection pages, while specific product searches usually belong on product pages. Informational searches may be better served by buying guides, comparison content or help pages that link naturally to relevant products.

Check for keyword cannibalisation, where several pages offer substantially the same answer and compete for the same searches. Resolve it by clarifying each page’s purpose, improving differentiation, consolidating genuinely overlapping pages or changing internal linking. Do not create separate pages for minor wording variations unless they serve a distinct audience, product set or intent.

Review titles and meta descriptions for accuracy and distinctiveness. They should describe the actual page and set an appropriate expectation, rather than repeat generic template text. Check headings, image alternative text and copy for clarity, but avoid awkward keyword repetition.

Check structured data

Validate structured data on products, breadcrumbs, organisation information, reviews and other relevant page types. Confirm that the markup reflects information visible to users, including product name, price, availability, brand and review details where applicable.

Look for invalid properties, stale prices, incorrect availability, duplicate markup and structured data placed on pages that do not contain the referenced content. Structured data can help search engines interpret a page, but it does not guarantee enhanced search results and cannot compensate for weak or inaccessible content.

Review mobile experience and performance

Evaluate the mobile version as the primary experience. Check navigation, filters, menus, product images, variant selection, add-to-basket controls, forms and checkout transitions on common screen sizes. Important content and links should not be absent or substantially reduced on mobile compared with desktop.

Investigate performance issues affecting real users, such as oversized images, unnecessary scripts, layout shifts, slow server responses and delayed interaction. Review field data where available rather than relying only on laboratory tests. Prioritise changes that improve the experience on key templates, especially category, product and checkout journeys.

Performance improvements should preserve functionality. Lazy-loading images below the initial view can be useful, but essential product images, content or controls should not be delayed in a way that harms usability or discoverability.

Analyse organic performance and competitors in the search results

Use Search Console and analytics data to compare impressions, clicks, organic landing pages, conversions and revenue over relevant periods. Segment the data by page type, device, country, brand and non-brand queries where possible. Look for pages with high impressions but weak click-through rates, pages ranking near the first results with room for improvement, and pages that have lost visibility after a technical or content change.

Compare performance with seasonality and catalogue changes before drawing conclusions. A fall in traffic may reflect reduced demand, stock availability or a change in product range rather than an SEO fault.

Review the search results for priority topics to understand what users are being offered. Note the dominant page type, content depth, product information, value propositions, review presentation, filters and questions addressed. Use this analysis to identify genuine gaps, not to copy another site’s wording or design.

Prioritise the findings

Turn the audit into an action backlog rather than a list of observations. Prioritise each issue according to:

• Impact: how many important URLs, users or commercial journeys are affected.
• Confidence: how clearly the issue is connected to crawlability, indexation, rankings or conversions.
• Effort: the development, content or operational work required.
• Urgency: whether the issue risks ongoing loss, affects a launch or blocks other improvements.

Address issues that prevent valuable pages from being crawled, indexed or understood first. Next, fix widespread template problems, incorrect redirects, broken internal links and poor mobile experiences. Then work on page-level content, internal linking, structured data and conversion improvements. Record the affected URLs, recommended change, owner, priority, dependencies and validation method.

Validate changes and measure outcomes

Test changes in a staging environment where possible, while preventing staging pages from being indexed. After release, confirm status codes, canonicals, robots directives, sitemap entries, internal links, structured data and rendered content on representative templates.

Monitor crawling, indexation, impressions, clicks, rankings, organic landing pages and commercial conversions after implementation. The appropriate measurement period depends on the size of the change, crawl frequency and demand patterns. Annotate releases so that performance changes can be compared with known technical and content updates.

Re-crawl the site after major fixes and use URL-level checks for priority pages. An audit is most useful as a repeatable process: establish a baseline, resolve the highest-value issues, validate the implementation, measure outcomes and then review newly generated URLs or catalogue changes. This keeps technical health, content quality and commercial priorities aligned as the ecommerce site develops.