Ecommerce Technical SEO Audit Checklist

A technical SEO audit for an ecommerce site is not just a scan for broken links and missing tags. It is a structured review of how search engines crawl your store, understand its category and product architecture, process its product data, and decide which URLs deserve indexing. Google’s ecommerce guidance centres on crawlable structure, product discoverability, structured data, pagination, and controlled handling of faceted navigation.

That matters more on ecommerce sites because catalogues generate more technical risk than most other site types. Products go in and out of stock, filters create URL combinations, pagination buries inventory, variants create near-duplicates, and platform templates can multiply errors at scale. Google explicitly warns that category pages that do not link to all products can limit discovery, and its faceted-navigation guidance says uncontrolled parameter combinations can create near-infinite crawl paths.

At Cartiful, the most useful way to audit ecommerce SEO is to separate the work into layers: crawlability, indexation, architecture, page templates, product data, and ongoing monitoring. That turns the audit from a long issue list into a practical roadmap.

Quick answer

A strong ecommerce technical SEO audit should answer these questions:

• Can Google crawl the pages that matter?
• Are the right URLs getting indexed?
• Is the site structure helping product discovery?
• Are canonicals, pagination, and filters under control?
• Are product pages technically complete for search and shopping features?
• Are sitemaps, internal links, and structured data aligned with the real site? Google’s Search Central documentation covers each of these areas across crawling, ecommerce best practices, pagination, sitemaps, and product structured data. 

How to use this checklist

Run this audit in order. Start with the sitewide issues that affect crawling and indexing, then move into ecommerce-specific systems such as categories, products, filters, schema, and feeds. Screaming Frog and Ahrefs both recommend starting with a crawl because it gives you the base dataset for almost every technical check that follows. 

A practical tool stack usually includes:

• Google Search Console
• Merchant Center, if the store uses Google shopping surfaces
• a crawler such as Screaming Frog or Ahrefs Site Audit
• analytics
• optional server log data for larger stores. Google’s docs, Screaming Frog’s audit content, and Ahrefs’ audit guidance all support crawl-led auditing and Search Console-based validation. 

1. Check crawlability first

If Google cannot crawl the pages that matter, everything else becomes secondary. Google says it generally discovers and crawls pages through crawlable links, and its link best-practices document says normal HTML anchor links with href attributes are the safest pattern for discoverability. 

Start by checking:

• important category pages
• important subcategory pages
• top product pages
• store or location pages if relevant
• editorial and buying-guide pages
• pagination URLs
• approved filter landing pages

Look for:

• blocked URLs in robots.txt
• pages blocked by meta robots or X-Robots-Tag
• JavaScript-only navigation that hides links from crawlers
• internal links that trigger events instead of exposing real URLs. Google’s crawlability and robots documentation supports all of these as core technical checks. 

What good looks like

• Core pages are reachable through crawlable links.
• Important templates are not blocked by robots rules accidentally.
• Product discovery does not depend only on filters, on-site search, or JavaScript clicks. Google’s ecommerce structure docs say Googlebot may not find all products if category pages do not link sufficiently to them. 

2. Check indexation, not just crawlability

A page being crawlable does not mean it is indexable, and a page being indexable does not mean it should be indexed. Google’s crawling and indexing docs separate these concepts clearly. 

Review:

• Search Console Page Indexing report
• number of indexed pages vs expected indexable pages
• excluded URLs by reason
• soft 404s
• duplicate without user-selected canonical
• crawled, currently not indexed
• discovered, currently not indexed

For ecommerce sites, the biggest indexation issues often come from:

• duplicate product URLs
• parameter URLs
• thin or expired pages
• weakly differentiated variants
• empty category or search pages
• redirect leftovers. Google’s crawling-error and indexing guidance, plus its faceted-navigation guidance, support these as common issue classes. 

What good looks like

• Core categories and products are indexed.
• Low-value filter and sort URLs are not taking up index space.
• Soft 404 patterns are controlled.
• Important new products are being indexed at a healthy pace.

3. Audit site architecture and click depth

Ecommerce SEO performance often depends on how easily Google can move from your homepage to categories, subcategories, and products. Google’s ecommerce best-practices documentation says navigation links should connect home to categories, categories to subcategories, and subcategories to products. 

Check:

• homepage links to main categories
• category links to subcategories where relevant
• category and subcategory links to products
• breadcrumb paths
• whether important pages sit too deep in the structure
• whether key commercial pages are supported by internal links from relevant content

For large stores, also look at:

• orphan products
• near-orphan products
• categories that exist but are barely linked
• subcategories hidden only behind filters. Screaming Frog’s sitemap and crawl audit guidance is especially useful here because it helps compare crawl paths and find orphan or poorly connected URLs.

What good looks like

• Key categories are easy to reach.
• Important products are not buried behind long pagination chains only.
• Breadcrumbs reinforce a real hierarchy.
• Editorial content supports commercial pages through relevant internal links. Google’s crawlable-links and ecommerce docs support this structure-first approach. 

4. Audit category pages as technical assets

Category pages are often the strongest SEO landing pages on ecommerce sites, so they deserve their own technical review. Google’s ecommerce docs emphasize category pages because they help Google find products and understand the store structure. 

Check category pages for:

• indexability
• canonical accuracy
• self-referencing canonical on the preferred URL
• pagination handling
• crawlable product links
• category intro or supporting content where helpful
• clean metadata and heading structure
• correct breadcrumb markup where implemented

Also check whether categories are being diluted by:

• duplicate category paths
• weak filtered alternates
• URL parameter sprawl
• case-sensitive duplicates
• trailing-slash inconsistencies. Google’s canonical and URL-structure docs support these checks. 

What good looks like

• One preferred category URL per intent.
• Category pages are crawlable, indexable, and internally supported.
• Product links are exposed directly and not only through JS or load-on-click interactions.

5. Audit product pages for technical completeness

Google’s product structured data documentation and merchant listing documentation make one thing clear: product pages need to be machine-readable, accurate, and technically stable if you want strong performance in search and shopping surfaces. 

Check product pages for:

• indexability
• canonical accuracy
• one preferred URL per product
• crawlable variant logic
• visible and matching price
• visible and matching availability
• high-quality images that are crawlable
• proper headings and page titles
• review and rating visibility where used
• correct product schema and offer data

Also check whether product pages are weakened by:

• thin templates
• duplicated descriptions across many products
• one URL serving many inconsistent variants
• no internal links beyond the main category path
• out-of-stock logic that removes too much content
• dead products returning 200 with “not found” messaging. Google’s product, merchant listing, and crawl-error docs support all of these as meaningful audit areas. 

What good looks like

• The page is indexable and self-canonical.
• Product facts on the page match structured data.
• Related-product or complementary-product links support deeper discovery.
• Out-of-stock and discontinued logic is handled cleanly.

6. Audit canonicals carefully

Canonical mistakes are one of the most common ecommerce SEO failures because platforms can generate many alternate URLs for the same product or category. Google’s canonical guidance says canonicals are hints about the preferred URL among duplicates or near-duplicates. 

Check:

• self-canonical on preferred product and category URLs
• no canonical chains
• no canonicals pointing to redirected URLs
• no canonical conflicts between HTML, headers, and sitemaps
• no product variants accidentally canonicalized in a way that hides valid pages
• no paginated pages canonicalized to page 1 when they should self-canonicalize. Google’s ecommerce pagination guidance is very explicit that paginated pages should have their own canonical URLs and should not canonicalize to page 1. 

What good looks like

• Every preferred indexable URL self-canonicalizes.
• Duplicate or alternate versions consistently point to the right preferred page.
• Canonical signals do not conflict across systems.

7. Audit faceted navigation and filter URLs

For ecommerce, this is one of the highest-impact technical audit areas. Google’s faceted-navigation guidance says uncontrolled facets can create a near-infinite number of URLs, which can lead to crawl waste and slower discovery of stronger pages. 

Check:

• which filter URLs are crawlable
• which filter URLs are indexable
• whether sort-order URLs are indexable
• whether size, color, or price combinations create thin pages
• whether empty filter states return useful status codes
• whether approved facet landing pages are separated from low-value filter noise

A practical audit split:

• worth indexing: a small set of approved faceted pages with real search demand
• crawlable but noindex: some utility pages if needed
• blocked or discouraged from crawl: low-value sort and filter patterns
• 404: empty or invalid combinations. Google’s December 2024 faceted-navigation guidance strongly supports this kind of controlled approach. 

What good looks like

• Filter systems help users without creating uncontrolled index sprawl.
• Search Console is not filling up with thin parameter pages.
• Approved landing pages are clearly distinct from utility states.

8. Audit pagination

Google’s ecommerce pagination documentation says each page in a paginated sequence should have its own URL and its own canonical URL, and Google no longer uses rel=”next” and rel=”prev” as an indexing signal. 

Check:

• crawlable anchor links between paginated pages
• self-referencing canonicals on each paginated page
• whether page URLs use real query/path URLs rather than fragments like #page=2
• whether products buried in deep pagination have other discovery paths
• whether sort-plus-pagination combinations are causing crawl clutter

For large stores, this is less about duplicate content and more about product discovery. Google says pagination can help users and site performance, but you may need to take steps to ensure Google can still find all the content. 

What good looks like

• Page 2, 3, and deeper pages are crawlable.
• Pagination exposes deeper inventory cleanly.
• Infinite scroll or load-more experiences have crawlable URL fallbacks if used.

9. Audit XML sitemaps

Google says sitemaps help search engines crawl sites more efficiently, especially large or complex ones, and that sitemap URLs should generally be the canonical URLs you want shown in search. It also says Google ignores priority and changefreq, while lastmod matters only when it is consistently accurate. 

Check:

• only canonical URLs included
• no redirected URLs
• no blocked or noindexed URLs
• separate sitemap files by useful segments where helpful
• accurate lastmod
• up-to-date sitemap index
• Search Console sitemap processing status

For large catalogs, segmented sitemaps by products, categories, content, or markets make debugging much easier. Google also says multiple sitemaps can help you track performance by section. 

What good looks like

• Sitemap equals a clean list of index-worthy URLs.
• Submitted and indexed counts make sense by section.
• lastmod is not being refreshed falsely on every generation.

10. Audit robots rules and index controls

Google’s robots meta tag documentation and crawling docs make clear that crawl control and index control are not the same thing. A robots.txt block controls crawling. A noindex controls indexability, but only if Google can crawl the page and see it. 

Check:

• robots.txt rules for accidental overblocking
• meta robots tags on templates
• X-Robots-Tag in headers where applicable
• staging or dev rules leaking into production
• filter, search, and internal utility pages using the right control method

What good looks like

• Important pages are crawlable and indexable.
• Low-value pages are controlled deliberately.
• There are no conflicting signals such as blocked pages that also rely on noindex.

11. Audit structured data

On ecommerce sites, structured data is not optional fluff. It supports machine understanding of products, offers, reviews, breadcrumbs, local stores where relevant, and more. Google’s product, merchant listing, breadcrumb, and local business docs each provide supported models and validation guidance. 

Review:

• Product markup on PDPs
• Offer data with matching price and availability
• review markup where valid and visible
• breadcrumb markup on categories and products
• local business markup on store pages, if relevant
• markup placed in initial HTML where possible for key commerce details

Also check that:

• structured data matches visible content
• no outdated or hidden review data is being marked up
• multi-currency pages use the right priceCurrency
• multi-region pages keep local data aligned with local content. Google’s product and structured-data policy docs support these checks directly. 

What good looks like

• Valid markup is present on the right templates.
• Product data is consistent between page, schema, and Merchant Center if used.
• Search Console rich result reporting is stable.

12. Audit URL structure and duplicate paths

Google’s ecommerce and URL-structure documentation recommends descriptive URLs, consistency, and avoiding unnecessary alternative URLs for the same content. 

Check for:

• uppercase/lowercase duplicates
• trailing slash inconsistencies
• both parameter and clean-path versions of the same page
• category-path duplicates for the same product
• session IDs or tracking parameters leaking into crawlable paths
• pagination and filter path duplication

What good looks like

• One preferred clean URL for each important page.
• Platform quirks are not multiplying alternate crawl paths.
• Internal links point to preferred versions consistently.

13. Audit redirects and status codes

Google’s technical SEO guidance says permanent moves should use server-side permanent redirects, and the crawl-error documentation supports using real 404 or 410 status codes for pages that are gone without a proper replacement. 

Check:

• 301 vs 302 usage
• redirect chains and loops
• discontinued product behavior
• soft 404s
• home-page or broad-category redirects for dead products
• internal links pointing into redirects

What good looks like

• Permanent moves use permanent redirects.
• Removed pages do not linger as weak 200 pages.
• Redirect rules help users and search engines reach the closest valid destination directly.

14. Audit internal linking quality

Google says links help it discover pages and understand relevance. On ecommerce sites, internal linking is how categories support subcategories, subcategories support products, and content supports commerce. 

Check:

• crawlable links in menus, breadcrumbs, categories, pagination, and modules
• descriptive anchor text
• related-product and complementary-product logic
• content pages linking to commercial pages
• orphan pages
• weakly linked priority products

What good looks like

• Important pages receive relevant internal support.
• Product discovery does not rely on only one path.
• Internal links reinforce the site’s real hierarchy.

15. Audit JavaScript and rendering risks

Many modern ecommerce stores depend heavily on JS for navigation, product rendering, filters, and inventory modules. Google can process JavaScript, but crawlable links and stable content exposure still matter, and broken or delayed rendering can weaken discoverability or create thin pages. Google’s crawling docs and ecommerce pagination guidance both imply this through their emphasis on crawlable URLs and links. 

Check:

• whether important content appears in the rendered HTML
• whether links are present as real anchors
• whether key product facts load too late
• whether store or pickup modules hide critical content from crawlers
• whether JS failure states return thin 200 pages

What good looks like

• Core product and category content renders reliably.
• Links stay crawlable.
• Important content is not dependent on user-triggered JS alone.

16. Audit Merchant Center and shopping-readiness, if used

For many ecommerce brands, SEO and shopping visibility overlap. Google’s ecommerce guidance and Merchant Center docs show that merchant listings and shopping surfaces depend on clean product data, matching landing pages, and accurate offer details. 

Check:

• feed price vs page price
• feed availability vs page availability
• shipping and return policy alignment
• multi-country or multi-currency consistency
• landing page quality for merchant listings
• product identifier completeness where relevant

What good looks like

• Feed and site tell the same story.
• Product pages are technically ready for both search and shopping visibility.
• Market-specific product data stays aligned with local pages.

17. Prioritize fixes by business impact

A long issue list is not an audit strategy. Screaming Frog’s enterprise audit guidance and Ahrefs’ audit workflows both recommend prioritizing issues by impact rather than by raw volume alone.

A practical ecommerce prioritization model:

Priority 1

Issues blocking crawl, indexation, or major category/product visibility
Examples: robots mistakes, broken canonicals, massive duplicate sprawl, bad pagination, broken product templates

Priority 2

Issues reducing product discoverability or shopping eligibility
Examples: weak structured data, inventory/feed mismatch, thin out-of-stock handling, poor internal linking

Priority 3

Efficiency and scale improvements
Examples: sitemap cleanup, metadata cleanup on templates, URL normalization, supporting content links

This keeps the audit focused on revenue-related pages first.

A practical ecommerce technical SEO audit checklist

Crawlability

• Crawl the site with a crawler.
• Confirm key pages are reachable through crawlable links.
• Check robots.txt and robots meta tags.
• Check rendered HTML on JS-heavy templates. 

Indexation

• Review Page Indexing in Search Console.
• Check excluded URL reasons.
• Review soft 404s, duplicates, and not-indexed patterns.
• Compare expected vs actual indexed pages. 

Architecture

• Review click depth.
• Check category → subcategory → product paths.
• Look for orphan pages and weakly linked products.
• Review breadcrumbs and core navigation. 

Categories

• Check indexability and canonicals.
• Check product link exposure.
• Review duplicate category paths.
• Review filter overlap. 

Products

• Check canonicals and status codes.
• Check variant handling.
• Review title, headings, images, and content completeness.
• Review related-product modules. 

Facets and filters

• Audit indexable filter pages.
• Control sort-order URLs.
• Check empty states and invalid combinations.
• Reduce crawl clutter from parameter sprawl. 

Pagination

• Check crawlable links between pages.
• Self-canonicalize paginated pages.
• Avoid fragment-based page numbers.
• Make sure deeper products are still discoverable. 

Sitemaps

• Include only canonical URLs.
• Remove redirected and blocked URLs.
• Check lastmod accuracy.
• Segment when useful for reporting. 

Structured data

• Validate Product, Offer, Review, Breadcrumb, and LocalBusiness where relevant.
• Check schema against visible content.
• Review Search Console rich-result reports. 

Merchant and offer accuracy

• Compare feed data to landing pages.
• Review availability and pricing consistency.
• Audit local or international market targeting if used. 

1. What should an ecommerce technical SEO audit include?

It should cover crawlability, indexation, site structure, categories, product templates, canonicalization, faceted navigation, pagination, sitemaps, structured data, and feed-to-site alignment where shopping surfaces matter. Google’s ecommerce guidance spans each of these areas. 

2. How often should I run an ecommerce technical SEO audit?

Large stores benefit from ongoing monitoring plus regular formal audits. Ahrefs recommends recurring audits, and ecommerce sites change often enough that monthly or quarterly reviews are common, with tighter checks after migrations, template updates, or feed changes. 

3. What are the biggest technical SEO risks on ecommerce sites?

The biggest ones are usually duplicate URLs, uncontrolled filters, weak product discovery, broken canonicals, pagination errors, soft 404s, and mismatched product data. Google’s ecommerce and faceted navigation docs point directly at these risks. 

4. Are sitemaps enough to get products discovered?

No. Google says sitemaps help, especially on large sites, but product discovery still depends heavily on crawlable internal links and site structure. 

5. Should paginated pages canonicalize to page 1?

No. Google’s pagination guidance says each page in a paginated sequence should have its own canonical URL. 

6. What is the best way to handle faceted navigation in an audit?

Separate index-worthy facet pages from low-value utility URLs, then control crawling and indexing accordingly. Google’s faceted-navigation guidance strongly supports this selective approach. 

Final takeaway

A real ecommerce technical SEO audit is not a one-time health check. It is a way to make sure Google can crawl the right URLs, index the right pages, understand your store’s structure, and trust the product data it sees. Google’s documentation across crawling, ecommerce, pagination, faceted navigation, and structured data all point in the same direction: the stores that perform best technically are usually the ones that keep their architecture clean, their index focused, and their product systems aligned. 

For most ecommerce brands, the smartest way to use this checklist is not to chase every warning equally. Start with crawl and index control, then fix the systems that affect your main categories, top products, and product-discovery paths first. That is where technical cleanup turns into organic growth.