Ecommerce SEO Audit: Product, Category and Faceted URL Checks

Audit ecommerce product pages, category architecture, faceted URLs, product data and template performance with evidence instead of fixed SEO thresholds.

Updated

Published by AuditWeb

An ecommerce SEO audit checks whether search engines can reach the products and categories a store intends to index. It also tests duplicate URL controls, product data, inventory states, internal links and template performance so each finding has an affected URL set and a verifiable fix.

Organic visibility can affect product discovery and revenue, but a ranking movement is not equal to a sale. Connect search queries and landing pages to measured product views, transactions and margin where analytics permits. This guide covers product, category, facet, inventory and template checks.

Why Ecommerce Sites Need Special Audits

An ecommerce catalogue can expose many URL variants through categories, colours, sizes, filters and pagination. The audit should map these patterns and decide which combinations deserve crawlable, indexable destinations.

Crawl management can matter on large or rapidly changing catalogues. Facets may create a very large URL space and consume server or crawler resources. Use logs, Crawl Stats, internal links and indexation evidence to determine whether discovery or refresh is actually affected; page count alone does not prove a crawl-budget problem.

Products may be reachable through categories, variants and parameters that expose equivalent or similar content. Inventory the patterns, compare Google's selected canonical and consolidate signals where duplication is unintended. Shared manufacturer text may offer little differentiation, but it does not automatically trigger a site-wide quality filter.

Inventory changes add another layer. Products go out of stock, seasonal ranges rotate, and discontinued items leave behind 404 errors or redirect chains. Without a process for handling these lifecycle events, your site accumulates technical debt that degrades overall SEO performance. A proper ecommerce audit establishes not just what to fix now, but what processes to implement for ongoing inventory management.

Product Page SEO Checks

Product pages are the revenue-generating core of your ecommerce site, yet they are often the most neglected from an SEO perspective. Many stores rely entirely on manufacturer-supplied descriptions, resulting in thin, duplicated content that offers Google no reason to rank their page over any other retailer selling the same item.

Start your product page audit by checking these elements on a representative sample of at least 50 product pages across different categories:

  • Unique product information — check whether the page adds accurate details beyond a supplier feed. Include specifications, compatibility, use constraints and buying answers when they help the task; do not classify quality from a universal word threshold.
  • Title tag structure — product titles should follow a consistent template that includes the product name, key attribute (size, colour, model number), and brand. Avoid stuffing category keywords into product titles. A good pattern: "[Product Name] - [Key Feature] | [Brand] | [Store Name]".
  • Image optimisation — check that every product has multiple images with descriptive alt text. Audit image file sizes and ensure WebP or AVIF formats are served. Product images are frequently the heaviest assets on ecommerce pages and the primary cause of slow load times.
  • Canonical tags — verify that every product page has a self-referencing canonical pointing to the clean URL without parameters. If the same product is accessible via multiple URLs (different categories, tracking parameters), all variants must canonical to a single version.
  • Availability and retirement — keep a temporarily unavailable product useful when stock may return, with accurate availability and alternatives. For a permanently retired product, preserve the URL when it still serves users; redirect only to a genuine replacement that satisfies the same task, otherwise return an appropriate 404 or 410 and remove internal and feed references.

Compare product-page clicks and impressions with catalogue and inventory states. Segment by category and template before looking for patterns in descriptions, product data, availability and internal links.

Category Page Optimisation

Category pages are often the highest-value landing pages on an ecommerce site. They target broader, higher-volume keywords like "men's running shoes" or "wireless headphones under 100" and serve as the primary gateway for users entering from search. Despite this, many stores treat category pages as nothing more than a grid of product thumbnails with no unique content.

Your category page audit should assess the following:

  • Above-the-grid guidance — give shoppers the context needed to understand the category without obscuring products. Test the rendered desktop and mobile layout rather than enforcing a fixed word range.
  • Supporting category guidance — answer material buying questions and link to useful subcategories where that content belongs. Add only information that supports the category task.
  • Pagination implementation — check whether paginated category pages use proper next/prev linking or infinite scroll with progressive enhancement. Every paginated page should be crawlable. If using load-more buttons or infinite scroll, verify that all products are accessible to crawlers via the HTML source.
  • H1 and heading structure — each category page should have a single H1 that matches the target keyword. Subcategories and sorting options should not create competing headings.
  • Breadcrumb navigation — verify that breadcrumbs reflect the site's category hierarchy and include structured data markup. Breadcrumbs are critical for ecommerce because they establish the relationship between products, subcategories, and parent categories in a way that search engines can parse.

Prioritise category changes using impressions, clicks, commercial relevance and evidence of a correctable gap. Record the implementation date and remeasure the same query and page groups without promising a ranking timescale.

Faceted Navigation Issues

Faceted navigation — the filtering system that lets shoppers narrow results by price, colour, size, brand, rating, and other attributes — is the single most common source of SEO problems on ecommerce sites. Every filter combination can potentially generate a unique URL, and on a site with hundreds of products and dozens of filter options, this creates millions of possible URL combinations.

The core problem is index bloat. If Google discovers and indexes thousands of filtered URLs like /shoes?colour=red&size=10&brand=nike&sort=price-low, your crawl budget gets consumed by low-value pages while your important category and product pages receive less frequent crawling.

Audit your faceted navigation by checking these specific issues:

  • Parameter inventory — identify parameters created by sorting, filtering, tracking and display controls. Search Console no longer provides the old URL Parameters tool, so verify crawl controls in site configuration, internal links and Google's current faceted-navigation guidance.
  • Crawl and index controls — choose controls from the intended role of each filtered URL. Google documents options for preventing crawling and separate practices for facets that need to be crawled or indexed; canonical, noindex, robots and internal-link choices are not interchangeable.
  • Internal links to filtered URLs — check whether your site's navigation, footer, or sitemap links to filtered URLs. These links signal to Google that filtered pages are important, contradicting any noindex or canonical directives.
  • Valuable filter combinations — some filtered URLs may satisfy distinct search tasks. Choose indexable combinations from demand, inventory and unique page value; handle other facets according to Google's faceted-navigation guidance and the site's crawl evidence rather than applying blanket noindex.

Run a crawl of your site and count the total number of unique URLs discovered. If your crawler finds significantly more URLs than the number of products plus categories, faceted navigation is likely creating URL bloat. Compare this against the number of pages Google has indexed in Search Console for a clear picture of the problem's severity.

Schema for Products

Product structured data can make an eligible product page understandable for product snippets or merchant listings. Markup does not control whether a rich result appears, and Google's general guidelines state that valid structured data is not a display guarantee.

Your schema audit should verify the following across a sample of product pages:

  • Product schema completeness — select product snippet or merchant listing markup for the page's role and check the current required properties. Google requires name plus at least one of review, aggregateRating or offers for product snippets.
  • Review and AggregateRating markup — if your products have reviews, the rating data must be marked up correctly. Google has strict policies against self-serving review markup, so verify that ratings reflect genuine customer reviews displayed on the page.
  • Offer accuracy — verify that price, currency and availability match the visible page and update with inventory changes. Misleading or non-representative markup can lose rich-result eligibility.
  • BreadcrumbList schema — confirm that breadcrumb structured data matches the visible breadcrumb navigation and accurately reflects the category hierarchy.
  • Product questions — answer recurring purchase questions visibly and keep the answers consistent with product, shipping and return data. Google limits regular FAQ rich results to well-known authoritative government and health sites, so do not promise ecommerce SERP expansion from FAQPage markup.

Use Google's Rich Results Test to validate schema on a sample of pages. Then check Search Console's enhancements report for any schema errors or warnings across the entire site. Common issues include missing required fields, invalid enum values for availability, and prices formatted without a currency code.

Site Speed for Stores

Ecommerce templates often carry heavy images and third-party scripts. Measure Core Web Vitals and conversion behaviour separately: performance can affect user experience, but a lab delay does not prove a specific revenue loss.

Focus your speed audit on these ecommerce-specific areas:

  • Product image delivery — are images served in modern formats (WebP/AVIF) with responsive sizing via srcset? Many platforms still serve full-resolution PNGs or JPEGs regardless of viewport. Implement lazy loading for below-the-fold images but ensure the primary product image loads eagerly.
  • Third-party script impact — catalogue every third-party script on your product and category pages. Common offenders include live chat widgets, social proof popups, retargeting pixels, and A/B testing tools. Measure the Total Blocking Time contribution of each and defer or remove those that are not essential for the initial page load.
  • Server response — compare TTFB across product, category and account templates at representative times. Investigate caching, CDN or database work when server delay is a material part of the measured loading path.
  • Cumulative Layout Shift — product pages are particularly vulnerable to CLS from images without defined dimensions, dynamically injected price elements, and review widgets that load after the initial paint. Audit CLS on mobile across your top 20 landing pages.

Prioritise speed improvements on your highest-traffic templates. Fixing the product page template benefits every product. Fixing the category page template benefits every category. This template-level approach is far more efficient than page-by-page optimisation.

Internal Linking for Ecommerce

Internal linking on ecommerce sites serves a structural purpose beyond what content sites require. The link architecture must distribute authority from the homepage and high-authority pages down through categories, subcategories, and individual products in a way that reflects both the site hierarchy and the commercial value of each page.

Audit your internal linking with these checks:

  • Click depth analysis — compare priority products with the site's expected hierarchy. Add useful category and related-item routes when products are orphaned or unnecessarily difficult to reach.
  • Related product links — check that product pages link to genuinely related products, not just random items from the same category. "Customers also bought" and "frequently bought together" sections serve both UX and SEO purposes by creating contextual internal links between topically related products.
  • Orphan product pages — run a crawl and identify products that receive zero internal links. These pages are effectively invisible to search engines. Common causes include products removed from categories but still live, seasonal products not linked from current navigation, and products only accessible via site search.
  • Category cross-linking — related categories should link to each other contextually. If you sell running shoes and running socks, those category pages should reference each other. This creates topical clusters that reinforce your authority across related product groups.
  • Breadcrumb link equity — breadcrumbs pass link equity up the hierarchy from product pages to categories. Verify that every product page includes breadcrumb links and that the hierarchy is logical and consistent.

Visualise your internal link graph using tools like Screaming Frog or Sitebulb. Look for clusters of pages with minimal connections to the rest of the site — these isolated sections represent missed opportunities for both users and search engines.

Common Ecommerce SEO Mistakes

Check these recurring ecommerce failure modes against crawl, template and inventory evidence. Their presence and priority varies by platform and catalogue.

  • Supplier descriptions used without added value — review priority products for duplicated feed text. Add accurate retailer-specific information where it helps buyers and use business value to set the order rather than a fixed catalogue percentage.
  • Blocking CSS and JavaScript in robots.txt — some older ecommerce platforms block rendering resources by default. Google needs to render your pages to understand their content. Verify that no critical CSS or JS files are disallowed.
  • Session IDs in URLs — appending session identifiers to URLs creates infinite unique URLs for the same content. This should have been solved years ago, but legacy platforms still do it. Check your crawl data for URL parameters that look like session tokens.
  • No HTTPS on checkout pages — while most stores have migrated to full HTTPS, some still have mixed content issues where checkout or account pages load insecure resources. This triggers browser warnings that destroy trust and conversions.
  • Ignoring internal site search data — your site search logs tell you exactly what products customers are looking for and cannot find. Cross-reference top search queries against your product catalogue to identify gaps in inventory, navigation, or content.
  • Thin category pages with no content — a page that contains nothing but a product grid and a heading is thin content by definition. Add buying guides, comparison information, and answers to common questions on every category page.
  • Incorrect hreflang on international stores — multi-currency or multi-language stores frequently have hreflang implementation errors. Missing return tags, incorrect language codes, and conflicting canonical signals create confusion about which version of a page Google should show in each market.

Product catalogues and templates change, so monitor high-risk signals around releases and inventory updates. Schedule deeper reviews from catalogue churn, deployment rate and business consequence rather than a universal quarterly timetable.

Check Your Page HTML

Review titles, canonical links and other on-page signals from pasted HTML. Download your findings for follow-up.

Open HTML Checker

No signup required • Pasted HTML stays in your browser