Ecommerce Website Audit Checklist

An ecommerce website audit tests product discovery, category filtering, product data, checkout, mobile interaction, performance and payment boundaries. Run each journey with representative products, stock states, customer types and devices.

Work through each section methodically. The checklist is organised by page type and function, reflecting how ecommerce sites are structured. Check every item against your actual site rather than your assumptions about how it works. Many ecommerce issues exist in the gap between what the CMS is supposed to do and what it actually outputs.

Product Pages

Product pages are the revenue-generating core of your site. Every element on these pages affects both search visibility and conversion rate.

• Unique title tags per product. Check that each product page has a distinct title tag that includes the product name and a relevant modifier (brand, key specification, or category). Templated titles like "[Product Name] | [Brand]" are fine as long as each title is genuinely unique. Duplicate product titles confuse search engines about which page to rank.
• Unique meta descriptions. Each product should have a unique meta description that summarises the product and includes a call-to-action element. Auto-generated descriptions that pull the first 160 characters of the product description are acceptable but less effective than deliberately crafted summaries.
• Unique product descriptions. Check whether product descriptions are original or copied from manufacturer data sheets. Manufacturer descriptions appear on every retailer's site, creating massive duplicate content. Identify your highest-traffic product pages and prioritise unique descriptions for those first.
• Image alt text. Every product image should have descriptive alt text that includes the product name and relevant visual details. Check that alt text is not keyword-stuffed or identical across all images of the same product. Gallery images should describe what each specific image shows (front view, side view, detail of stitching).
• Image file optimisation. Check that product images are served in WebP or AVIF format, appropriately sized for their display dimensions, and compressed without visible quality loss. Unoptimised product images are the single most common speed issue on ecommerce sites.
• Canonical tags. Verify that each product page has a self-referencing canonical tag and that product variants (colour, size) are canonicalised correctly. If variants have separate URLs, decide whether each should be independently indexable or canonicalised to a primary variant.
• Out-of-stock handling. Check what happens when a product goes out of stock. The page should remain accessible (not return a 404), display the out-of-stock status clearly, offer alternatives, and retain its SEO value. Products that are permanently discontinued should redirect to the most relevant category or replacement product.
• Customer reviews. Verify that reviews shown to users are authentic, moderated under a documented policy and available in the rendered page. If aggregate-rating markup is eligible, it must match the visible product reviews and Google's policies.
• Internal links to related products. Check that each product page links to related products, the parent category, and any relevant buying guides or comparison pages. These links should use meaningful anchor text, not just "View Product" or product codes.
• Breadcrumb navigation. Verify that breadcrumbs are present, reflect the correct category hierarchy, and are marked up with BreadcrumbList schema. Products that appear in multiple categories should have consistent primary breadcrumb paths.

Category Pages

Category pages often drive more organic traffic than individual product pages because they target broader, higher-volume keywords. They also control how search engines discover and understand your product catalogue.

• Unique category descriptions. Each category page should have a unique introductory paragraph that describes the category, includes relevant keywords, and helps users understand what products are available. Thin category pages with only product listings and no descriptive content struggle to rank.
• Faceted navigation handling. This is the most critical ecommerce-specific check. Examine how your site handles filter URLs. Each filter combination generates a URL. Check whether filtered URLs are canonicalised to the base category, whether they are blocked in robots.txt, whether they use noindex directives, or whether they are freely crawlable. Uncontrolled faceted navigation can generate millions of low-value URLs that waste crawl budget.
• Pagination implementation. Give component pages unique URLs and connect them with crawlable <a href> links. Google no longer uses rel="next" or rel="prev" as indexing signals.
• Sorting parameter handling. URLs generated by sorting options (sort by price, popularity, newest) create duplicate versions of category pages. Verify that sort parameters are handled with canonical tags pointing to the default sort order.
• Category hierarchy depth. Compare product depth with navigation and user tasks. Investigate important or in-stock products that are orphaned or unexpectedly difficult to reach; no universal three-click limit applies.
• Empty category pages. Check for categories with zero products, which commonly occur during seasonal stock changes or after product line discontinuation. Empty category pages provide no value to users or search engines and should be noindexed or redirected.
• Category page load time. Test category pages with full product grids loaded. Category pages with 40-60 product thumbnails, filter interfaces, and sorting options are often the heaviest pages on ecommerce sites. Measure Core Web Vitals specifically for these templates.

Checkout Flow

While not a traditional SEO concern, checkout issues directly affect the revenue that your organic traffic generates.

• Checkout pages are noindexed. Cart, checkout, payment, and order confirmation pages should all carry noindex directives. Verify this for every step of the checkout process.
• SSL across the entire checkout. Every page in the checkout flow must be served over HTTPS with no mixed content warnings. Test this on both desktop and mobile browsers.
• Account and guest checkout paths. Measure completion, errors and abandonment for the available paths. Test guest checkout as a product hypothesis where identity or regulatory needs do not require an account.
• Form field validation. Test form validation for address fields, payment details, and contact information. Validation should happen inline (as the user completes each field) rather than after form submission. Error messages should be specific and positioned next to the relevant field.
• Error state handling. Test what happens when a card is declined, a session expires, or an item goes out of stock during checkout. Each error should display a clear message and a path to resolution without losing the user's cart contents.
• Trust signals. Check for visible security badges, payment method logos, return policy links, and contact information during checkout. Trust signals that are visible during the purchase decision reduce abandonment.

Site Speed

• Core Web Vitals by page type. Test LCP, INP, and CLS separately for homepage, category pages, product pages, and checkout pages. Each template has different performance characteristics and may require different optimisation approaches.
• Image lazy loading. Verify that below-the-fold product images use lazy loading. Above-the-fold hero images and the first row of category product grids should NOT be lazy loaded, as this delays Largest Contentful Paint.
• Third-party script audit. List every third-party script loaded on your site: analytics, heatmaps, chat widgets, retargeting pixels, review platforms, and personalisation tools. Measure the individual performance cost of each. Remove or defer scripts that provide insufficient value relative to their performance impact.
• Caching configuration. Verify that page caching is active for anonymous users, that browser caching headers are set correctly for static assets, and that CDN caching is functioning for all resource types. Test TTFB from multiple geographic locations if you serve international customers.
• Search functionality performance. Measure response, rendering, result relevance, errors and abandonment by device and query type. Set a latency budget from observed user needs rather than a universal 300-millisecond rule.
• Mobile performance specifically. Use field data where available and repeatable throttled lab tests on key product, category, basket and checkout states. Diagnose the measured bottleneck rather than assuming a desktop result applies.

Schema Markup

• Product markup on eligible pages. Follow the current Google Product feature documentation for the page type. Required and recommended properties differ by merchant-listing or product-snippet use; offers and reviews must match visible, current facts.
• BreadcrumbList schema. Verify BreadcrumbList schema on category and product pages. The schema should match the visible breadcrumb navigation exactly. Mismatches between visible and structured breadcrumbs can trigger manual review.
• Organisation entity is accurate. Where Organization markup is used, keep its name, URL, logo and relevant identifiers consistent with visible business information. Do not repeat conflicting entity blocks on every template.
• FAQ markup eligibility. Google normally restricts FAQ rich results to authoritative government and health sites. Do not add FAQPage solely for an ecommerce search enhancement; any markup must still match visible content.
• Structured-data support is current. Compare markup with the current Google feature documentation and Schema.org vocabulary. A warning can describe a useful recommended property; it does not mean the markup should be removed.
• Structured-data results are interpreted. Use the Rich Results Test for Google features and Schema.org's validator for vocabulary. Record errors, warnings, affected templates and eligibility; validation does not guarantee a rich result.

Mobile Commerce

• Mobile product image gallery. Test the product image gallery on mobile devices. Images should be swipeable, zoomable, and load quickly. Gallery controls should not obscure product content or conflict with browser back gestures.
• Add to cart on mobile. Verify that users can find and operate the control without obscuring product information or other actions. Test a sticky control with owned funnel data or a controlled experiment before claiming conversion impact.
• Filter interface on mobile. Test category filters on mobile. Overlay filter panels are generally more usable than inline filters on small screens. Applied filters should be clearly visible and easily removable.
• Touch target sizing. Test WCAG 2.2 AA's 24 by 24 CSS pixel rule with its spacing and inline exceptions. Use larger controls where product filters or checkout tasks need them.
• Mobile search experience. Test on-site search on mobile. The search input should be easily accessible, results should be well-formatted for small screens, and search suggestions should be tappable without precision targeting.
• Payment method integration. Evaluate suitable wallet and payment methods from customer demand, region, device, fees, accessibility and fraud controls. Measure completion and conversion after a controlled rollout rather than promising a universal lift.

Security

• SSL certificate validity. Check that your SSL certificate is current, covers all subdomains in use, and is from a trusted certificate authority. Set a calendar reminder for renewal if your certificate does not auto-renew.
• PCI DSS scope is confirmed. Ask the acquiring bank or payment provider which current PCI DSS validation applies to the merchant and integrations. A hosted payment flow can reduce scope but does not automatically remove every merchant responsibility.
• Secure headers. Check for security headers: HSTS (Strict-Transport-Security), Content-Security-Policy, X-Content-Type-Options, X-Frame-Options, and Referrer-Policy. These headers protect against common attack vectors that are particularly damaging for ecommerce sites handling personal and payment data.
• Admin access security. Verify that CMS admin panels are protected with strong passwords, two-factor authentication, and IP restriction where feasible. Compromised admin access on an ecommerce site can lead to skimming attacks that steal customer payment information.
• Data handling and privacy. Inventory cookies, pixels and recipients and compare them with the privacy notice and the consent rules for the user's jurisdiction. Record the evidence; refer legal compliance to qualified counsel.
• Backup and recovery. Verify that automated backups run daily and include both the database and file system. Test your recovery process at least once to confirm that backups are actually usable. An ecommerce site that cannot recover from a security incident or technical failure faces existential risk.

Google's ecommerce structured-data guidance explains supported product and merchant data. Confirm payment scope against the current PCI DSS and use the security checklist for authorised testing.