Ecommerce SEO Audit Checklist: A Step-by-Step Guide for Australian Stores

Introduction

An ecommerce website can look perfectly healthy while quietly creating thousands of unnecessary URLs, hiding profitable products from crawlers, publishing conflicting stock data and making customers wait for scripts they never asked for. The homepage smiles. The catalogue is chaos.

An ecommerce SEO audit finds those problems and turns them into prioritised decisions. It examines how search engines discover, render, understand and index the store, then connects those findings with the pages, products and categories that matter commercially.

This guide provides a step-by-step ecommerce SEO audit checklist for Australian online stores. It covers crawling and indexation, architecture, category and product pages, variants, faceted navigation, content, structured data, Google Merchant Center, site performance, internal links, authority and measurement. It also explains how to document findings so developers, merchandisers, content teams and business owners know what to do next.

The purpose is not to produce the longest possible list of warnings. Crawling software can already do that before breakfast. The purpose is to identify what is genuinely wrong, understand its business impact and recommend a fix that can be implemented and verified safely.

Ecommerce SEO audit at a glance

A useful audit follows five principles:

1. Start with commercial context. Identify priority categories, products, markets and organic revenue paths before opening a crawler.
2. Separate crawling, rendering, indexing and ranking. A page can pass one stage and fail another.
3. Audit systems and templates, not only individual URLs. One faulty product template can affect an entire catalogue.
4. Prioritise findings by impact, reach, confidence, effort and risk.
5. Validate every significant fix. A recommendation is not complete until somebody confirms the intended result.

The core audit sequence is:

• Establish the baseline and scope
• Build a trustworthy URL inventory
• Audit crawling, rendering and indexation
• Review architecture and internal linking
• Inspect category and product templates
• Test variants, stock and discontinued-product handling
• Review keywords, content and cannibalisation
• Validate structured data and product feeds
• Assess mobile performance and Core Web Vitals
• Examine authority, analytics and conversion evidence
• Prioritise, assign and validate fixes

What is an ecommerce SEO audit?

An ecommerce SEO audit is a structured assessment of an online store’s ability to earn relevant organic visibility. It identifies technical, structural, content and authority issues that may prevent search engines from finding important pages, understanding their purpose or selecting them for suitable searches.

An audit should answer questions such as:

• Can search engines discover the products and categories the business wants indexed?
• Are low-value filters, searches and parameter combinations consuming unnecessary crawl attention?
• Does Google index the intended canonical URLs?
• Can users and crawlers navigate from broad categories to specific products?
• Do category and product pages satisfy the search intent assigned to them?
• Are price, availability, shipping and return details consistent across visible content, structured data and product feeds?
• Do internal links emphasise commercially important pages?
• Does organic traffic contribute to enquiries, purchases and revenue?
• Which problems deserve attention first?

An ecommerce website audit can cover SEO, conversion, accessibility, analytics, security, merchandising, paid media and operations. This article focuses on SEO, but it uses conversion and revenue evidence to decide whether an SEO finding matters. A page that attracts visits but fails to help customers is not a complete success story.

Why ecommerce audits differ from standard SEO audits

Ecommerce stores have features that create unusual scale and complexity:

• Categories, subcategories, products and variants
• Filters, sorting controls and query parameters
• Internal search-result pages
• Pagination or infinite loading
• Constant stock and price changes
• Products appearing in several categories
• Manufacturer-supplied descriptions used by multiple retailers
• Reviews, specifications, images and videos
• Product structured data and Merchant Center feeds
• Multiple currencies, regions or languages
• JavaScript-heavy themes and third-party applications

A five-page professional-services website may have a relatively stable URL inventory. An online store with 5,000 products can generate many times that number of crawlable combinations through filters, variants and tracking parameters. An apparently small template error can therefore spread widely.

The commercial model also changes prioritisation. A technically imperfect category that generates substantial organic revenue may deserve more attention than hundreds of low-value metadata warnings. Conversely, one accidental noindex directive on a best-selling category can become urgent even if the audit tool reports it as a single URL.

Define the audit scope and business baseline

Do not begin by crawling everything and hoping the exports reveal a strategy. First document what the store is trying to sell, where it sells and which parts of the catalogue matter.

Record the commercial context

Gather:

• Primary product categories and subcategories
• High-revenue and high-margin products
• Seasonal ranges and launch dates
• Products that are frequently unavailable
• Priority Australian states, cities or delivery areas
• International markets, currencies and languages
• Major ecommerce platform, theme and important applications
• Recent migrations, redesigns or catalogue changes
• Known organic traffic or revenue declines
• Internal search terms and customer questions
• Competitors serving the same customer and product market

Ask stakeholders where the business expects organic search to contribute. A store may need category discovery, individual product demand, informational content, local showroom visits or a combination.

Establish a measurement baseline

Record available evidence before changes are made:

• Organic clicks, impressions and queries in Google Search Console
• Indexed and non-indexed URL patterns
• Organic sessions, landing pages, transactions and revenue in analytics
• Conversion rate and average order value by organic landing-page type
• Brand versus non-brand query performance
• Performance of priority categories and products
• Product-feed warnings and disapprovals
• Core Web Vitals field status by template group
• Rankings for mapped category, product and informational queries
• Backlinks and internal links to priority pages

Check analytics implementation before trusting it. Duplicate purchase events, missing consent configuration, self-referrals, excluded payment gateways or broken channel rules can make revenue data misleading. An SEO priority model built on faulty analytics is just confident guesswork in a spreadsheet.

Define exclusions

State what the audit does not cover. For example, a technical and on-page ecommerce SEO audit may exclude a full accessibility assessment, penetration testing, legal review, paid shopping campaign audit or complete conversion-research programme. Record adjacent issues when discovered, but route them to the right specialist rather than pretending one document covers everything.

Collect the tools and evidence

No single tool provides a complete ecommerce audit. Combine sources that show what the site publishes, what crawlers can access, what Google reports and what customers do.

Useful sources include:

• Google Search Console for performance, indexing, sitemaps, crawl statistics, enhancements and URL inspection
• Google Analytics 4 or another analytics platform for landing-page behaviour and commercial outcomes
• A crawler such as Screaming Frog, Sitebulb or an enterprise crawling platform
• Server log files for actual crawler requests on large or complex stores
• PageSpeed Insights and the Search Console Core Web Vitals report
• Chrome DevTools for rendering, network and JavaScript investigation
• Google’s Rich Results Test and Schema Markup Validator
• Google Merchant Center diagnostics and product data
• A keyword and backlink platform such as Semrush or Ahrefs
• Ecommerce platform reports for products, categories, variants, stock and redirects
• A spreadsheet, database or issue tracker for evidence and prioritisation

Export data with dates and settings. A crawl without its configuration, user agent, scope and timestamp can be difficult to reproduce. Record whether the crawl rendered JavaScript, respected robots.txt, followed canonicals or included parameters.

Create representative samples

Even when running a full crawl, build a manual sample containing:

• Homepage
• Major category and subcategory pages
• Best-selling and low-traffic product pages
• Products with variants
• In-stock, temporarily unavailable and discontinued products
• Paginated category URLs
• Filter and sorting combinations
• Internal search URLs
• Blog or buying-guide pages
• Policy pages
• International or regional equivalents

This sample makes template comparison easier and exposes issues that averages can hide.

Step 1: Build a trustworthy URL inventory

An ecommerce audit begins by comparing what the business believes exists with what users, crawlers and Google can find.

Collect URLs from several sources:

• Crawler output
• XML sitemaps
• Ecommerce database or platform export
• Google Search Console pages reports
• Analytics landing pages
• Server logs
• Backlink exports
• Merchant Center feed destinations
• Internal search and navigation

Normalise the data carefully. Preserve the original URL and create separate fields for host, protocol, path, parameters, fragment and canonical target. Do not remove parameters before you understand what they do.

Compare sources to find:

• Products in the platform but absent from navigation and sitemaps
• URLs receiving organic traffic but missing from internal links
• Legacy URLs with backlinks but no valid destination
• Feed URLs that redirect or disagree with canonical tags
• Parameter patterns generating large numbers of duplicates
• Orphan pages discovered only through sitemaps or external links
• Staging, test or preview URLs that became crawlable

The aim is not to force every source to contain the same URLs. Account, cart and checkout pages have different purposes from product pages. The aim is to explain each important difference.

Step 2: Audit crawling, rendering and indexation

These stages are related but not interchangeable:

• Discovery means a crawler has found a URL.
• Crawling means it can request the URL.
• Rendering means it processes resources and JavaScript to construct content.
• Indexing means a search engine chooses to store and potentially serve the page.
• Ranking means the indexed page is selected and ordered for a query.

A blocked page is not the same as a noindex page. A submitted sitemap does not guarantee indexing. A self-referencing canonical does not force Google to select that URL. Keep those distinctions visible throughout the audit.

Check Google Search Console indexation

Use the Page indexing report to review patterns rather than trying to maximise the number of indexed pages. Google explicitly notes that a non-indexed URL is not automatically a problem.

Investigate categories such as:

• Server errors
• Redirect errors
• URLs blocked by robots.txt
• URLs excluded by noindex
• Duplicate URLs with or without a selected canonical
• Crawled or discovered URLs not currently indexed
• Soft 404s
• Valid indexed pages

Group examples by template and parameter pattern. If 20,000 filtered URLs are excluded as duplicates, that may be an intentional result or evidence of uncontrolled URL generation. If a high-value product page is crawled but not indexed, inspect content, duplication, canonical signals, internal links, rendering and demand before assuming the status itself explains the cause.

Use URL Inspection for representative pages to compare declared and Google-selected canonicals, last crawl, indexing status and rendered output. It is a sample investigation tool, not a substitute for catalogue-wide analysis.

Audit XML sitemaps

An XML sitemap tells search engines which canonical URLs the site considers important. Submission is a hint, not an indexing guarantee.

Check that sitemaps:

• Resolve successfully and use the preferred protocol and host
• Contain only intended canonical URLs
• Exclude redirected, blocked, noindex, duplicate and error URLs
• Update when products and categories are added or removed
• Use accurate modification dates where the platform supplies them
• Separate useful page types when that improves monitoring
• Stay within protocol limits and use sitemap index files when required
• Are submitted and processed in Search Console

Compare submitted and indexed groups by sitemap. Large differences deserve investigation, but do not impose a universal percentage target without considering the catalogue, stock model and indexation strategy.

Audit robots.txt correctly

The robots.txt file manages crawler access. It is not a reliable mechanism for removing a web page from Google’s search results. A blocked URL can still be known through links and may appear without a useful snippet.

Check for:

• Accidental blocking of product, category, image, CSS or JavaScript resources
• Old platform rules that no longer match current paths
• Wildcards that affect more URLs than intended
• Uncontrolled filters, searches or sort URLs that create large crawl spaces
• Sitemap references
• Different rules on subdomains
• Staging rules copied into production

If a page must not appear in search, use an appropriate index-control or access method. Importantly, Google must be able to crawl a page to see a noindex directive. Blocking the same URL in robots.txt can prevent that directive from being read.

Changes to robots.txt can affect large parts of a store quickly. Test patterns and obtain technical review before deployment.

Review status codes and soft 404s

Crawl internal and externally linked URLs and group response codes:

• 200 for successful content
• Permanent redirects for genuinely moved content
• Temporary redirects only where the move is temporary
• 404 or 410 for content that no longer exists and has no relevant replacement
• 5xx for server failures requiring investigation

Find redirect chains, loops, mixed protocols and internal links pointing through redirects. Update internal links to their final destinations where appropriate.

A product template can return 200 while displaying “product not found” or an empty page. Search engines may treat that as a soft 404. Ensure unavailable and removed products return content and status codes aligned with their real state.

Do not redirect every discontinued product to the homepage or a vaguely related category. Irrelevant redirects confuse users and may be treated like soft 404s. Use the stock decision framework later in this guide.

Review canonicalisation

Canonicalisation helps search engines choose a representative URL among duplicate or very similar pages. A rel=”canonical” element is a strong signal, not an absolute command.

Check that:

• Indexable category and product pages use intended canonicals
• Canonical targets return 200 and are themselves indexable
• Internal links and sitemaps reinforce preferred URLs
• HTTP, HTTPS, host and trailing-slash versions are consistent
• Product variants follow a documented strategy
• Filter, tracking and sorting URLs do not send conflicting signals
• Paginated pages do not all point to page one without a sound reason
• International pages do not canonicalise incorrectly across languages or regions
• Canonicals remain stable when JavaScript renders

Compare the declared canonical with the canonical selected by Google on representative URLs. If they differ, examine content similarity, redirect signals, sitemaps and internal linking rather than repeatedly rewriting the tag.

Audit faceted navigation and URL parameters

Faceted navigation helps shoppers filter by attributes such as colour, size, brand, material and price. It can also generate a near-infinite combination of URLs.

Inventory every parameter and answer:

• What user function does it perform?
• Does the resulting page have unique search demand and sufficient products?
• Should the page be internally linked and indexable?
• Does the combination change content materially or only reorder it?
• Can crawlers create endless combinations or repeat parameters?
• What canonical, robots, index and link behaviour applies?

Create an indexation matrix rather than applying one rule to every filter. For example, a retailer may create a curated, indexable landing page for a valuable single-attribute demand such as black office chairs, while keeping arbitrary price, sort and multi-filter combinations out of the index.

Do not block faceted URLs in robots.txt before considering whether search engines need to recrawl them to see a noindex directive or changed canonical. Sequence matters. Large stores should involve an experienced technical SEO specialist and developer because one pattern rule can affect millions of URLs.

Audit pagination and incremental loading

Category products may be presented through numbered pages, “load more” controls or infinite scroll. Users can interact with buttons; crawlers need discoverable URLs and crawlable links.

Check that:

• Products beyond the initial view can be reached through crawlable links
• Paginated URLs have stable, unique addresses where required
• Each page returns the expected products without relying on user interaction
• Canonical signals match the indexation strategy
• Sorting and filters do not create uncontrolled duplicate sequences
• Internal links do not repeatedly reset customers to the wrong page
• Analytics and event tracking do not break during incremental loading

Use rendered HTML and crawl tests, not visual inspection alone. A product visible after a browser click may still be undiscoverable to a crawler if the implementation lacks crawlable links.

Test JavaScript rendering

Modern ecommerce platforms often use JavaScript for product grids, navigation, reviews, prices, variants and recommendations. Google can render JavaScript, but rendering adds dependencies and potential failure points.

Compare initial HTML with rendered HTML for representative templates. Confirm that important content and links are available, including:

• Product names, descriptions and specifications
• Category copy and product links
• Canonical and robots directives
• Structured data
• Price and availability
• Review content
• Pagination links
• Internal navigation

Check for blocked resources, hydration errors, delayed content, client-side redirects and differences between mobile and desktop experiences. Use Search Console’s rendered view and browser testing where relevant.

Step 3: Audit architecture and internal linking

Site architecture determines how customers and crawlers move from broad topics to specific products. Google says it uses links and navigation relationships to understand ecommerce structure and relative importance.

Map the hierarchy:

Home > Category > Subcategory > Product

Then review whether the hierarchy reflects customer language, product relationships and commercial priorities.

Navigation checks

• Priority categories are accessible through normal crawlable links.
• Category names match language customers recognise.
• Menus do not contain links to internal searches or unintended filtered URLs.
• Mobile navigation exposes equivalent important destinations.
• Breadcrumbs reflect the logical hierarchy and link to useful parents.
• Products are not discoverable only through a search box.
• Seasonal navigation has a removal and redirect plan.

Avoid relying on a universal three-click rule. Click depth is a diagnostic clue, not a law. Examine whether high-value pages are unnecessarily buried and whether link prominence reflects business importance.

Internal-link checks

Measure internal inlinks, unique source pages, anchor text and link position. Look for:

• Orphan categories and products
• High-value pages with weak internal support
• Excessive links to low-value or discontinued pages
• Links pointing through redirects or to errors
• Generic anchors that hide destination context
• Blog content that never connects to relevant categories
• Related-product widgets that create random or repetitive links
• Pagination and filter links overwhelming useful navigation

Link buying guides, comparisons and educational articles to relevant commercial pages where the connection genuinely helps the reader. Link categories to supporting guides as well. Internal linking should support journeys in both directions.

For deeper strategy, use CFM’s guide to advanced ecommerce SEO architecture.

Step 4: Audit category and collection pages

Category pages often target broader commercial searches and help customers compare products. On Shopify, these are usually called collection pages. Audit both the template and individual priority categories.

Search intent and keyword mapping

Confirm that each priority category owns a distinct query cluster. Review:

• Primary commercial topic
• Important attributes such as use, material, size, style or audience
• Search-result competitors
• Whether Google favours category pages, product pages, guides or a mixture
• Overlap with other categories and filtered landing pages
• Regional language and Australian terminology

If two categories target the same intent with similar products, decide whether they should be consolidated, differentiated or repositioned.

Category content

A useful category page should help customers understand what is available and choose the right path. Check for:

• Clear H1 and introductory context
• Logical product assortment
• Useful subcategory and filter options
• Unique copy based on actual customer questions
• Buying guidance, specifications or comparison information where valuable
• Trust, shipping and return information placed without overwhelming shopping tasks
• Relevant FAQs supported by visible content
• Original or useful imagery
• Links to related categories and guides

Do not add a giant block of generic SEO text beneath the product grid merely to increase word count. Content should reduce uncertainty, explain distinctions and support decisions.

Category metadata and snippets

Review titles and meta descriptions at scale. Templates should avoid duplicates while allowing important categories to be written individually. Titles should be descriptive and concise. Meta descriptions are suggestions for snippets, not guaranteed display copy.

Compare SERP presentation for priority categories. Look for rewritten title links, missing brand context, stale promotional language and snippets that do not match the current range.

Merchandising and indexability

Confirm that important products are reachable in the category’s HTML and not hidden behind unsupported interactions. Review empty or low-stock categories, default sorting, pagination, temporary campaigns and cross-category duplication.

An empty category should not remain indexable indefinitely with a cheerful message and no useful path. Decide whether it will be restocked, redirected, replaced, consolidated or removed.

Step 5: Audit product pages

Product pages must explain a specific item accurately enough for customers and search systems to understand it.

Unique product information

Check whether the page provides original, useful information rather than copying a manufacturer description used across many stores. Depending on the product, useful fields may include:

• Product name and model
• Clear benefits and intended use
• Specifications and dimensions
• Materials, ingredients or compatibility
• Size, fit or installation guidance
• Care and maintenance
• Safety or warranty information
• Shipping, collection and return details
• Price and current availability
• Original images and video
• Genuine customer reviews
• Questions specific to the product

The purpose is not to write an essay for every low-value SKU. Create content standards by product type and commercial importance, then prioritise products with demand, margin, stock stability and strategic value.

Product keyword targeting

Review brand, model, product type, attributes and problem-led queries. Confirm that the page targets the specific product intent while categories target broader selection intent.

Avoid forcing every variation into the title. A readable title and well-structured product data are more useful than a keyword train containing every colour, size and synonym.

On-page structure

Check:

• One clear main heading describing the product
• Descriptive title element
• Useful meta description where appropriate
• Logical headings for details, specifications, delivery and FAQs
• Crawlable links to categories, related products and guides
• Accurate image alt text where an image conveys content
• Visible information matching structured data
• Reviews that are genuine and attached to the correct product
• No important content hidden from mobile users or crawlers

Conversion evidence

Organic visibility and customer usefulness overlap. Review product-page conversion rate, add-to-cart behaviour, returns, internal search refinements and customer enquiries. A page may attract the correct query but fail because sizing, delivery, stock or compatibility information is unclear.

Do not interpret every conversion problem as an SEO problem. Record the evidence and assign the appropriate owner.

Step 6: Audit variants, stock changes and discontinued products

Variants and inventory changes require policy decisions, not one universal redirect rule.

Product variants

Document how the platform represents colours, sizes, materials and configurations. Some variants share one URL; others have separate URLs or parameters.

Check:

• Whether each important variant has a stable URL if it needs to be linked or indexed
• Canonical behaviour across variants
• Unique images, prices, availability and identifiers
• Product and ProductGroup structured data where applicable
• Internal links and sitemaps
• Consistency with Merchant Center destinations
• Whether changing a selector updates the URL and content reliably

The correct strategy depends on search demand, product distinction and platform capability. Do not canonicalise genuinely distinct, valuable variants to a generic parent without assessing the consequences.

Temporarily unavailable products

If a product will return, keeping the page live can preserve customer information and search signals. Clearly state availability, offer restock notifications where suitable and link to relevant alternatives. Ensure visible content, structured data and Merchant Center agree.

Avoid changing the page to 404 every time stock reaches zero. Equally, do not show an in-stock offer in structured data while the page says sold out.

Discontinued products

Use a decision framework:

Review the effect on customer experience, feeds, internal search, analytics and paid campaigns before changing large product groups.

Step 7: Audit keywords, content and cannibalisation

Technical cleanliness does not create demand alignment by itself. Map queries to the pages best suited to satisfy them.

Build a page-type keyword map

Typical ownership might be:

• Categories for broad commercial product classes
• Subcategories or curated facets for valuable attribute combinations
• Product pages for specific items, models and high-intent attributes
• Buying guides for comparison and selection questions
• How-to content for usage and problem-solving questions
• Policy pages for delivery, returns, warranties and service information

Review Google Search Console queries and landing pages alongside keyword research. The page already receiving impressions may reveal Google’s current interpretation, but it is not automatically the best long-term owner.

Detect cannibalisation

Look for:

• Multiple categories appearing for the same query cluster
• Product and category pages swapping positions for broad searches
• Filtered URLs competing with curated categories
• Blog articles outranking commercial pages for buying intent
• Regional or international pages appearing in the wrong market
• Old campaign pages competing with evergreen categories

Confirm whether the pages truly satisfy the same intent. Similar keywords do not always mean harmful cannibalisation. When overlap is real, choose an owner URL and use content differentiation, internal links, redirects, canonicals or consolidation as appropriate.

Audit editorial content

Evaluate buying guides, comparisons, FAQs and tutorials for:

• Original expertise and accurate product knowledge
• Clear search intent
• Helpful links to categories and products
• Evidence of organic visibility and assisted conversion
• Outdated product claims or broken links
• Duplicate articles addressing the same question
• Opportunities to update, consolidate or remove weak material

Do not publish informational articles merely to surround a category with words. Each article should answer a real customer question better than the commercial page can.

Step 8: Audit titles, headings, snippets and images

Title elements

Export titles and group missing, duplicate, overly templated and misleading examples. Review priority pages manually. Google recommends descriptive, concise and page-specific titles, but it may generate a different title link when other signals appear more useful.

Check whether templates:

• Put the distinguishing product or category information first
• Add brand names consistently
• Avoid repeating filters and attributes
• Remove stale sale messages automatically
• Handle unavailable products sensibly
• Produce readable titles for long product names

Meta descriptions

Descriptions can influence the snippet Google chooses, although Google may use page content instead. Check for duplicates, missing product distinctions, expired promotions and claims inconsistent with the page.

Programmatic descriptions can be appropriate for very large catalogues if templates produce accurate, useful summaries. Handwrite priority pages where the opportunity justifies it.

Headings

Review the rendered document structure. Ensure headings describe sections and do not exist only for visual styling. Product names, category names, specifications and supporting content should form a logical hierarchy.

Images

Ecommerce images influence search discovery and conversion. Audit:

• Descriptive filenames where practical
• Accurate alt text for meaningful images
• Image dimensions and responsive delivery
• Compression and modern formats
• Lazy loading below the initial viewport
• High-quality product imagery available to users and search systems
• Image sitemap needs for complex catalogues
• Broken or placeholder images
• Licensing and ownership
• Consistency between page images, structured data and feeds

Alt text should describe the image’s purpose, not repeat a list of keywords. Decorative images can use empty alt attributes where appropriate.

Step 9: Audit structured data

Structured data gives search systems explicit, machine-readable information about page content. Correct markup can make a page eligible for supported search features, but it does not guarantee rich results.

Relevant ecommerce types can include:

• Product and Offer
• ProductGroup for variants where applicable
• AggregateRating and Review when policy requirements are met
• BreadcrumbList
• Organization
• Shipping and return-policy information supported by Google

Audit at three levels:

Template validity

Test representative product, variant, category and policy templates with Google’s Rich Results Test and a schema validator. Fix syntax errors and unsupported nesting.

Data accuracy

Compare markup with visible content. Product name, image, SKU, brand, price, currency, availability, ratings and review counts must be accurate. Do not mark up content users cannot see or attach reviews from one product to another.

Catalogue consistency

Use crawler extraction or platform data to identify missing and inconsistent fields at scale. A few valid samples do not prove every SKU is correct.

Monitor Search Console enhancement reports after deployment. Treat warnings according to their meaning and business value, not as a command to populate fields with invented data.

Step 10: Audit Merchant Center and product-feed consistency

Google can use both on-page structured data and Merchant Center product data. Feed participation is required for some surfaces, and conflicting information can create warnings, disapprovals or poor customer experiences.

Compare feed records with landing pages for:

• Product identifiers such as GTIN, MPN, brand and SKU
• Title and description
• Destination URL and canonical URL
• Main image and additional images
• Price, sale price and currency
• Availability
• Shipping cost and delivery settings
• Return-policy information
• Variant grouping and attributes
• Condition and product category
• Australian target country and language settings

Check Merchant Center diagnostics for item-level and account-level issues. Segment by product importance and error type. A disapproved top seller deserves different priority from a warning on a product that will be retired.

Automated item updates may help reconcile some price and availability differences, but they are not a substitute for reliable source data. Find why the website, structured data and feed disagree.

Product-feed optimisation also supports unpaid product visibility and paid Shopping activity, so involve SEO, ecommerce and paid-media owners when changes affect shared data.

Step 11: Audit mobile experience, speed and Core Web Vitals

Google primarily indexes the mobile version of content. Audit mobile rendering, navigation and purchase information, not only a desktop screenshot.

Test representative templates

Review the homepage, priority categories, products, filtered views, cart and important editorial pages. Test different product states and devices where practical.

Look for:

• Content or links missing on mobile
• Intrusive overlays blocking the page
• Unstable layouts as images, reviews or recommendations load
• Delayed product information
• Slow variant selection
• Oversized images and video
• Heavy third-party applications
• Duplicate tag-manager scripts
• Unused JavaScript and CSS
• Font and consent-manager delays
• Interaction problems during add-to-cart or filtering

Distinguish field and lab data

The Search Console Core Web Vitals report groups URLs using real-world field data where sufficient data exists. PageSpeed Insights may also provide lab diagnostics that help identify causes. A lab score is not the same as field performance or business impact.

Review the current Core Web Vitals:

• Largest Contentful Paint for loading experience
• Interaction to Next Paint for responsiveness
• Cumulative Layout Shift for visual stability

Segment results by template. A product-page application may cause a widespread problem even when the homepage passes. Validate changes in both testing and field data over time.

Do not chase a perfect score while breaking functionality or measurement. Prioritise improvements that help customers and affect important templates.

Step 12: Audit international and multi-region ecommerce

Australian stores selling into other countries may use separate domains, subdomains or subdirectories. Audit whether users and search engines receive the intended language, currency, availability and policies.

Check:

• Unique, stable URLs for each regional or language version
• Correct hreflang values and reciprocal references
• Self-referencing or otherwise appropriate canonicals
• Consistent language and region signals
• Country-specific prices, currency, tax, stock, shipping and returns
• Region-specific Merchant Center feeds
• Internal links that preserve the selected market
• Sitemaps containing the correct alternates
• No forced redirects that prevent crawlers or travellers from accessing another version

Do not use hreflang to solve duplicate content or substitute for canonicals. It helps Google understand alternate language or regional versions; it does not fix fundamentally incorrect URL architecture.

For an Australian-only store, still audit currency, delivery regions and claims. A page showing US dollars while the feed submits Australian dollars creates a very practical kind of SEO problem: the result may attract a customer the checkout immediately annoys.

Step 13: Audit backlinks and external authority

Backlinks can help search engines discover pages and understand reputation, but an audit should focus on relevance and recoverable value rather than an arbitrary domain-authority score.

Review:

• Referring domains and linked pages
• Links to redirected, broken or discontinued products
• Priority categories with little external support
• Brand mentions without links
• Retail partners, manufacturers, stockists and industry associations
• Digital PR and editorial assets that earned relevant coverage
• Suspicious patterns that may warrant expert investigation
• Competitor content and category pages earning useful links

Reclaim strong links pointing to broken URLs by restoring content or redirecting to the closest genuine replacement. Do not redirect every old link to the homepage.

Google’s spam systems handle many low-quality links automatically. Avoid routine mass disavowal based solely on a third-party toxicity score. The disavow tool is an advanced measure for particular circumstances and can cause harm when used carelessly.

Authority building should connect with assets customers and publishers have a reason to reference: original research, useful tools, detailed guides, proprietary data, expert commentary and genuinely distinctive products.

Step 14: Audit analytics, attribution and conversion evidence

An ecommerce SEO audit should connect visibility with business outcomes without pretending attribution is perfect.

Validate tracking

Check:

• Ecommerce events and parameters
• Purchase value, tax, shipping and currency
• Product and category naming consistency
• Cross-domain and payment-provider configuration
• Consent behaviour
• Referral exclusions and channel classification
• Duplicate or missing transactions
• Internal-search tracking
• Campaign parameters on owned links

Compare analytics transactions with ecommerce-platform records for a sample period. Differences may be expected because of consent and attribution, but unexplained gaps reduce confidence.

Review organic landing-page groups

Segment homepage, category, product and editorial landing pages. Compare:

• Organic sessions or users
• Engaged visits
• Product views
• Add-to-cart and checkout progression
• Transactions and revenue
• Conversion rate
• Average order value
• New versus returning customers where reliable

Use these metrics to prioritise, not to assign simple causation. A product page with low conversion may suffer from price, stock, trust, delivery or audience mismatch. SEO can bring the right person to the door; the rest of the store still has to answer it.

Account for assisted journeys

Buying guides and category pages may assist later direct, paid or email conversions. Review path and CRM evidence where available. Avoid deleting useful informational content solely because it has few last-click sales.

Step 15: Audit AI search readiness

AI-supported search experiences can surface product facts, comparisons, guides and merchant information. There is no special shortcut that replaces ordinary search fundamentals.

Audit whether important information is:

• Accessible to permitted crawlers
• Present in rendered content
• Accurate and consistent across the page, structured data and feed
• Organised with clear headings, specifications and direct answers
• Supported by original images, expertise or evidence
• Connected through descriptive internal links
• Attributable to the business with clear brand and contact information
• Updated when products, policies and stock change

Review how priority product and category questions appear across Google search features and relevant answer engines, but do not promise inclusion or citation. Record which sources are referenced and whether CFM’s client pages lack essential facts or useful comparative content.

Avoid creating schema types that Google does not support or publishing hundreds of generic AI-written FAQs. Clarity, accuracy and usefulness matter more than decorating a thin page with machine-readable optimism.

Step 16: Use automation and AI with human review

Automation helps ecommerce teams audit large catalogues. Crawlers can extract canonicals, directives, titles, headings, schema fields, prices and availability. Scripts can compare product feeds with landing pages. AI can cluster issues, summarise patterns and help draft ticket descriptions.

The operating principle is:

Real Intelligence = Human + AI

Automated findings still need human verification. A tool may label every non-indexed filter URL an error when exclusion is intentional. An AI summary may recommend canonicalising variants without understanding that customers search for them separately. A severity score may prioritise missing descriptions above a broken checkout script.

For every automated recommendation, check:

• Is the evidence reproducible?
• Is the behaviour intentional?
• Which templates and commercial pages are affected?
• Does the recommendation follow current platform and Google guidance?
• Could the change remove valuable pages or create conflicting signals?
• Who owns implementation and validation?

Use AI to reduce repetitive analysis, not to outsource accountability.

Step 17: Prioritise findings and assign owners

A good audit may uncover hundreds of issues. The deliverable should make the next decision easier.

Score findings using:

Then classify the recommendation:

• Critical: blocks access, indexation, transactions or essential data across valuable pages
• High: widespread or commercially important issue with strong evidence
• Medium: meaningful improvement with limited reach, confidence or urgency
• Low: minor enhancement, isolated hygiene issue or unproven hypothesis
• Monitor: insufficient evidence for a change, but worth observing

Tool severity should inform this decision, not dictate it. A crawler cannot see margin, stock strategy or development risk unless the team supplies that context.

Assign each issue to an owner such as development, SEO, content, merchandising, analytics, paid media or legal. Include dependencies and an acceptance test. “Fix canonicals” is not an implementable ticket. “Update the colour-filter template to emit the approved parent canonical, then verify rendered HTML and Google-selected canonical on the sample URLs” is closer.

Ecommerce SEO audit output template

Record each finding in a consistent format:

Keep raw exports separate from the decision log. Stakeholders need access to evidence, but a folder containing 27 spreadsheets is not an audit conclusion.

Condensed ecommerce SEO audit checklist

Use this summary after reading the detailed guidance.

Scope and data

• Priority categories, products, markets and seasonal ranges documented
• Organic traffic, revenue and conversion baseline recorded
• Analytics implementation checked for material errors
• Recent migrations and catalogue changes documented
• Audit scope and exclusions agreed

URL inventory and crawling

• Platform, crawl, sitemap, Search Console, analytics, feed and backlink URLs compared
• Orphan and legacy URLs identified
• Important pages accessible through crawlable links
• robots.txt rules tested for unintended blocks
• JavaScript resources required for content and links accessible
• Server and crawl-log patterns reviewed where scale justifies it

Indexation and URL controls

• Search Console Page indexing patterns reviewed by template
• XML sitemaps contain only intended canonical URLs
• noindex directives match the indexation plan
• Canonical targets are valid, indexable and consistently reinforced
• Redirect chains, loops, errors and soft 404s addressed
• Facet, sort, search and tracking parameters mapped
• Pagination and incremental loading expose crawlable product paths

Architecture and internal links

• Category hierarchy reflects customer language and business priorities
• Priority pages are not unnecessarily buried
• Mobile and desktop navigation support important destinations
• Breadcrumbs are logical and crawlable
• Orphan products and categories resolved
• Internal links point directly to current canonical URLs
• Editorial content links naturally to useful commercial pages

Category pages

• Each priority category owns a distinct search-intent cluster
• H1, title and description accurately describe the range
• Category copy supports product selection rather than word count
• Products are accessible without unsupported interactions
• Empty, seasonal and low-stock categories follow an agreed policy
• Category templates avoid duplicate or stale metadata

Product pages

• Product information is accurate, useful and sufficiently distinctive
• Specifications, compatibility, sizing and policies are easy to find
• Product titles and headings match the item and search intent
• Images are useful, optimised and legally available
• Reviews are genuine and assigned to the correct product
• Important product content appears in rendered mobile output
• Conversion and customer-question evidence reviewed

Variants and inventory

• Variant URL and canonical strategy documented
• ProductGroup and Product data evaluated where relevant
• Price and availability update correctly when variants change
• Temporarily unavailable products remain useful and accurate
• Discontinued products follow a demand, link and replacement decision tree
• Internal links, sitemaps and feeds update with lifecycle changes

Content and keywords

• Queries mapped to category, product and editorial page types
• Genuine cannibalisation separated from harmless query overlap
• Duplicate and manufacturer-default content assessed
• Buying guides answer real questions and link usefully
• Outdated and overlapping content consolidated or improved

Structured data and Merchant Center

• Product, Offer, ProductGroup and Breadcrumb data tested where applicable
• Markup matches visible product information
• Required and valuable properties checked across the catalogue
• Feed destinations match canonical landing pages
• Price, currency, availability, identifiers, shipping and returns agree
• Merchant Center diagnostics prioritised by business impact

Mobile and performance

• Key templates tested on mobile devices and connections
• Core Web Vitals field groups reviewed
• Lab diagnostics used to investigate causes
• Images, applications, scripts and fonts assessed
• Layout stability and interaction responsiveness tested
• Performance changes checked against functionality and tracking

International, authority and measurement

• Regional URLs, canonicals and hreflang checked where relevant
• Currency, stock, shipping and policy data match each market
• Valuable backlinks to retired URLs reclaimed appropriately
• Priority pages and link gaps reviewed
• Organic landing pages connected with commercial outcomes
• Assisted journeys considered before removing content

Delivery and validation

• Findings include evidence, examples, impact and recommendation
• Issues scored by impact, reach, confidence, effort and risk
• Owners and dependencies assigned
• Acceptance tests written
• High-risk technical changes reviewed before release
• Implemented fixes validated in the site, crawl, Search Console or feed as appropriate

Common ecommerce SEO audit mistakes

Treating every warning as an error

Tools report patterns, not strategy. An intentionally noindex account page is not a problem. A missing canonical on a revenue-critical product template might be.

Confusing robots.txt with deindexing

Robots.txt manages crawling. If Google cannot crawl a page, it cannot see a page-level noindex directive. Choose controls based on the actual objective.

Checking only the homepage

Ecommerce problems are often template-specific. Sample categories, products, variants, filters, paginated pages and stock states.

Redirecting discontinued products indiscriminately

Redirect only to a genuinely relevant replacement or destination. Otherwise preserve a useful archived page or return an appropriate not-found status.

Canonicalising valuable facets without research

Some filtered combinations reflect distinct demand. Map search intent before consolidating or excluding them.

Chasing crawl budget on a small store

Crawl efficiency matters, but crawl-budget management is most relevant to large or frequently changing sites. Do not invent a scale problem while important content remains weak.

Reporting lab scores as customer reality

Lab tests help diagnose performance. Field data represents real-user groups where available. Use both correctly.

Ignoring Merchant Center

Price, availability, identifiers and destinations can disagree across the page, markup and feed. SEO, ecommerce and paid-media teams need a shared product-data truth.

Delivering findings without owners

An issue nobody owns becomes a permanent feature of the audit deck. Assign responsibilities, dependencies and validation tests.

Auditing without commercial context

A technically neat site can still target the wrong demand. Prioritise around products, categories and customer journeys that matter to the business.

When to self-audit and when to involve specialists

A smaller store with a stable catalogue can perform many checks using Search Console, analytics, platform reports and a crawler. A knowledgeable internal team may be best placed to understand product data, stock policies and customer behaviour.

Specialist support becomes more valuable when the store has:

• Large or rapidly changing catalogues
• Complex faceted navigation
• Headless or JavaScript-heavy rendering
• Multiple regions, languages or currencies
• A planned replatform or migration
• Unexplained indexation or traffic loss
• Conflicting canonicals and variant URLs
• Product-feed or structured-data problems at scale
• Limited development capacity
• High revenue risk from technical changes

CFM provides Ecommerce SEO services for strategy and implementation, SEO Website Audit services for broader diagnosis and Technical SEO services for high-risk crawl, rendering and indexation work.

Whether the audit is internal or external, ask for evidence, prioritisation, ownership and validation. A branded PDF containing exported warnings is not expertise merely because the cover looks expensive.

Conclusion

An ecommerce SEO audit should reveal how the store’s technical systems, catalogue structure, content and product data work together. It should also show where they do not.

Begin with business context and a reliable baseline. Compare URL sources, then separate crawl, render, index and canonical issues. Review categories, products, variants and inventory states as systems rather than isolated pages. Check that visible information, structured data and Merchant Center feeds agree. Connect findings with organic demand, customer behaviour and commercial importance.

Most importantly, turn observations into decisions. Prioritise by impact, reach, confidence, effort and risk. Assign an owner, document the evidence and define how the fix will be validated. That is what transforms an ecommerce audit checklist from a large collection of red cells into useful work.

The perfect audit is not the one with the most pages. It is the one the team can trust, implement and verify without accidentally sending the best-selling category into the digital basement.

Frequently Asked Questions (FAQs)

1. What is included in an ecommerce SEO audit?

An ecommerce SEO audit reviews how search engines discover, crawl, render, understand and index an online store. Its scope commonly covers URL inventory, XML sitemaps, robots.txt, index controls, canonicals, status codes, faceted navigation, pagination, JavaScript, site architecture and internal links. It should also assess category and product pages, variants, stock handling, keyword targeting, content duplication, structured data, Merchant Center feeds, mobile performance, Core Web Vitals and backlinks. A strong audit connects findings with organic traffic, conversions and revenue priorities. It should finish with evidence, affected URLs, recommended fixes, owners and validation methods. Accessibility, security, paid campaigns and full conversion research may require separate specialist audits.

2. How often should an ecommerce website be audited for SEO?

There is no universal audit frequency. It depends on catalogue size, release pace, platform complexity and commercial risk. A stable store with a small range may need occasional comprehensive reviews plus routine Search Console and feed monitoring. A large retailer adding products daily may require automated checks and regular template-level reviews. Trigger an audit after a replatform, redesign, domain change, navigation rebuild, major application rollout, international expansion or unexplained organic decline. Monitor critical signals continuously where practical, including server errors, indexation patterns, structured-data failures and Merchant Center disapprovals. The sensible cadence is the one that detects material regressions before they spread while avoiding repetitive reports that nobody implements.

3. Which tools are needed for an ecommerce SEO audit?

Use several sources because no tool sees the whole system. Google Search Console provides performance, indexing, sitemap, enhancement and URL-level evidence. Analytics connects landing pages with customer and revenue behaviour. A crawler such as Screaming Frog or Sitebulb audits templates, links, directives, metadata and structured data at scale. PageSpeed Insights, Chrome DevTools and the Core Web Vitals report support performance diagnosis. Google’s Rich Results Test checks supported markup, while Merchant Center shows product-data issues. Keyword and backlink platforms add competitor, demand and authority context. Large stores may also need server logs and database exports. The most important tool remains human review, because automated warnings do not understand business intent.

4. How is an ecommerce SEO audit different from a normal website audit?

Ecommerce sites combine categories, products, variants, filters, sorting, internal search, pagination, stock changes, structured data and product feeds. These systems can generate many URLs and repeat template problems across an entire catalogue. A standard website audit may identify broken links and missing metadata, but an ecommerce audit must also evaluate which filtered pages deserve indexing, how variants are represented, what happens when stock changes and whether price and availability agree across pages, markup and Merchant Center. It should connect search demand with category and product ownership, then use revenue and inventory context to prioritise fixes. The principles are familiar, but ecommerce scale and product lifecycle make implementation much less forgiving.

5. Can I perform an ecommerce SEO audit for free?

You can complete a useful first-pass audit with free tools, especially for a smaller store. Google Search Console, Google Analytics, PageSpeed Insights, Chrome DevTools, Rich Results Test, Merchant Center diagnostics and manual site checks reveal many important issues. Some crawling tools offer limited free versions. The constraint is usually scale and interpretation rather than access. A free crawl may not cover the full catalogue, render JavaScript or compare feed records. More importantly, a warning does not explain whether a change is safe. Start by checking priority templates and commercial pages, document evidence and avoid bulk changes to canonicals, robots rules or redirects without technical review. Specialist help is worthwhile when mistakes could affect substantial revenue.

6. What are the most common ecommerce SEO problems?

Common problems include products that are unreachable through crawlable links, XML sitemaps containing redirected or non-indexable URLs, accidental noindex rules, conflicting canonicals and uncontrolled filter parameters. Stores also struggle with duplicate product descriptions, overlapping categories, thin collection pages, orphan products, broken links, unavailable products showing incorrect structured data and feeds that disagree with landing pages. Heavy themes and third-party applications can affect mobile performance and interaction. Other recurring issues include weak internal linking, vague titles, missing product identifiers, JavaScript-rendered content that fails and discontinued products redirected to irrelevant pages. The most important issue varies by store, so verify patterns and commercial impact before assigning priority.

7. Should every filtered ecommerce page be blocked from Google?

No. Some filters create low-value or near-duplicate combinations, while others represent useful landing pages with distinct customer demand. Begin by mapping every parameter and understanding what it changes. A curated page for a valuable attribute combination may deserve unique content, internal links and indexation. Arbitrary price ranges, sorting states and multi-filter combinations may need crawl or index controls. The solution can involve static category URLs, canonical signals, noindex, robots rules and link management, but sequencing matters. Blocking a URL in robots.txt can prevent Google from seeing a noindex directive. Large faceted systems should be reviewed by technical SEO and development specialists before bulk changes are released.

8. What should happen to discontinued product pages?

Choose the treatment according to customer usefulness, search demand, backlinks and replacement availability. If a direct replacement exists, a permanent redirect may be appropriate. If the old product still attracts meaningful demand or links, an informative archived page with accurate discontinued status and relevant alternatives may serve users better. Redirecting to a category can work when that category genuinely satisfies the former intent. If the product has no demand, links, traffic or useful replacement, return a proper 404 or 410, remove internal links and update the sitemap and feed. Products expected to return should usually remain live with accurate availability and a restock or alternative path. Avoid blanket redirect rules.

9. Does product structured data improve ecommerce rankings?

Product structured data helps Google understand product information and can make eligible pages suitable for supported rich search experiences. It is not a guaranteed ranking improvement or a promise that rich results will appear. Markup should match visible content and accurately describe fields such as the product, offer, price, currency, availability, identifiers, shipping, returns and reviews where applicable. Test representative templates, then audit consistency across the catalogue. Compare markup with Merchant Center data because conflicts can create warnings and poor customer experiences. Fix critical errors, assess warnings according to business value and never invent reviews or attributes simply to complete a field. Useful pages and sound SEO foundations still matter.

10. How should ecommerce SEO audit findings be prioritised?

Prioritise findings using impact, reach, confidence, effort and risk. First address issues that block access, indexing, transactions or accurate product information across commercially important pages. Widespread template errors usually matter more than isolated cosmetic warnings, but a single best-selling category accidentally set to noindex may still be critical. Connect each finding with affected products, organic demand, revenue and customer journeys. Then estimate implementation effort, dependencies and the possibility of unintended consequences. Assign an owner and write an acceptance test before work begins. Tool-generated severity can support the assessment, but it should not replace business context or technical judgement. Validate every completed fix using the relevant crawl, page, report or feed.