Direct answer: start by defining the URLs that should be indexed, then crawl the paths customers and bots can follow. Control filters and parameters, and reconcile redirects, canonicals, internal links, and sitemaps. Next, inspect category and product templates, Product and variant data, and stock states. Finally, compare the cleaned inventory with Search Console. Fix discovery and canonical conflicts before rewriting page copy or chasing rich-result warnings.
This checklist diagnoses a store-wide URL and template system. It does not teach product or category copy in depth, replace a migration plan, or repeat every crawler setting. Use the technical SEO audit workflow when you need the full crawl and Search Console evidence process.
Jump to verification checklist →
Use this audit map
Area Evidence to collect Pass condition
Indexable inventory Template list, URL samples, XML sitemap Every intended category and product has one preferred URL Discovery Navigation crawl, orphan report, pagination paths Important pages are reachable through crawlable links Filters and parameters Parameter patterns, combinations, crawl volume Useful landing pages are distinct; unwanted combinations do not expand the crawl Canonical signals Status, redirect, canonical, internal links, sitemap membership Signals consistently point to the same preferred URL Templates HTML, rendered output, mobile output, structured data Primary content and signals survive every representative template Measurement Search Console pages, queries, indexing groups Issues are prioritized by affected templates and search evidence
1. Define the indexable store inventory
List the page types the store intentionally wants in search before opening a crawler. Typical candidates include the homepage, departments, categories, useful subcategories, product detail pages, editorial guides, store locations, and selected campaign pages. Account, cart, checkout, internal search, sorting, session, and tracking URLs normally serve users or operations without needing a separate search result.
Do not decide by URL shape alone. A filtered collection can deserve indexing when it serves a stable demand with unique inventory and useful context. The same filter can be wasteful when it creates a thin duplicate or an empty combination. Record the business owner, intended canonical, indexability, sitemap state, and one real example for every template.
Template Example URL Index? Canonical target Sitemap? Owner
Category /ceramics/Yes Self Yes Merchandising Product /ceramics/blue-vase/Yes Self Yes Catalog Filter /ceramics/?color=blueNo Policy decision No SEO Search /search?q=blueNo None No Product
2. Crawl the paths shoppers and Google can follow
Run a normal crawl from the preferred origin with robots rules respected. Then compare it with XML sitemap URLs, Search Console landing pages, analytics landing pages if available, product feeds, and the commerce platform export. The differences matter more than a single crawl total.
Google says it uses page relationships to understand ecommerce structure and recommends linking categories, subcategories, and products with crawlable <a href> links. Googlebot generally does not submit a site search form, so search-only products may remain undiscovered. A sitemap or Merchant Center feed can supplement discovery, but neither repairs a weak internal path. See Google's guidance on helping Google understand an ecommerce site structure .
Protect the store while crawling. Exclude checkout, accounts, carts, wish lists, internal search, and unbounded parameter spaces. Use a considerate crawl rate and test against a small sample before expanding.
Investigate four gaps:
important URLs in the catalog but not in the crawl;
crawlable URLs missing from the intended inventory;
sitemap URLs that redirect or canonicalize elsewhere;
Google landing pages that no current navigation path reaches.
3. Decide what happens to faceted and parameter URLs
Group parameters by function: filtering, sorting, pagination, tracking, session state, display mode, and campaign attribution. Sample real combinations and count how quickly each family expands. A five-filter interface can create far more URLs than products.
Google's current faceted navigation guidance warns that generated combinations can consume large amounts of crawling. When faceted URLs are not needed in search, prevent the unwanted crawl through an enforceable URL and robots policy. When a subset should be indexable, keep parameter order stable and return a real 404 for empty or nonsensical combinations. Give each selected landing page consistent internal links, content, canonical signals, and sitemap treatment.
Pattern Default audit decision Reason to make an exception
Sort order Do not index Rarely creates a distinct search job Tracking and session Do not index No separate content value Single useful attribute Evaluate Stable demand, enough inventory, useful landing-page context Multiple arbitrary filters Usually do not crawl or index Only when intentionally curated as a durable collection Empty combination 404 None when no matching inventory exists
Do not use one blanket canonical to the unfiltered category as a substitute for controlling an infinite crawl. Canonical is a consolidation signal, not a crawl-budget switch. For the implementation sequence behind filter combinations, pagination, empty states, and crawlable internal discovery, continue with faceted navigation and pagination for ecommerce SEO .
4. Test pagination and category discovery
Open a deep category with JavaScript disabled and inspect the source links. Each paginated URL should have a unique, crawlable address, and products beyond the first viewport should still be discoverable. Infinite scroll and load-more interfaces need an underlying sequence of URLs and links that a crawler can follow without clicking or scrolling.
Google's pagination guidance for ecommerce explains that crawlers may not trigger user interactions. Test first, middle, and final pages for self-canonicals, status codes, duplicate metadata, empty states, and products that disappear when inventory changes.
Do not canonicalize every paginated page to page one when later pages contain distinct products. Also verify that removing or adding a product does not leave an endless chain of empty pages.
5. Align redirects, canonicals, links, and sitemaps
For every representative URL, compare the requested URL, final status, redirect target, HTML canonical, internal-link destination, sitemap URL, and any locale or variant signals. The preferred version should be the version the site actually links to and submits.
Google treats redirects and rel="canonical" as strong canonicalization signals, while sitemap inclusion is weaker. Signals can reinforce each other when they agree. Review Google's duplicate URL consolidation guidance , then use the sitemap and non-canonical URL fix for implementation detail.
Protocol and host: HTTP, HTTPS, www, and non-www should resolve consistently.Path variants: casing, trailing slashes, duplicate category paths, and legacy handles need one policy.Parameters: internal navigation should not add tracking or display parameters to canonical product links.Sitemaps: include absolute, preferred, indexable URLs that return a successful response.
6. Inspect product templates, variants, and stock states
Sample products by revenue, category, inventory state, number of variants, age, and traffic. Include a simple product, a multi-variant product, an out-of-stock item, a discontinued item, a product with reviews, and a newly created item. Inspect initial HTML, rendered DOM, mobile output, status, canonical, links, title, primary heading, price, availability, media, and purchase state.
Choose variant URLs deliberately. In a single-page model, each variant should be directly preselectable through a distinct stable URL state while the overall ProductGroup keeps one canonical product URL. Separate variant pages can work when users search for the variation and each page remains stable, internally linked, and accurately represented. Avoid a hybrid where feeds, internal links, canonicals, and structured data disagree about whether variants are separate products.
Stock state Audit question Typical safe route
Temporarily unavailable Will the same product return? Keep the useful page, show accurate availability, preserve alternatives Permanently discontinued with replacement Is there a close successor? Redirect only when the replacement satisfies the same user job Permanently discontinued without replacement Does the page still help users? Keep useful reference content or return 404/410 when it has no remaining value Deleted by mistake Should the catalog item still exist? Restore the original URL and repair feed or inventory synchronization
Do not redirect every removed product to its category. A misleading redirect hides the missing item without giving the user an equivalent result.
7. Check structured data against the visible offer
Validate Product markup on representative product pages, not category templates. Compare every property with the visible page and current offer: name, image, price, currency, availability, condition, seller, ratings, and reviews. Google notes that Product markup can support product snippets or merchant listing experiences, and variants can be represented with ProductGroup and Product. Read the official Product structured data documentation and product variant documentation .
A valid Rich Results Test is not the end of the audit. Confirm that the server or rendered page exposes the same current price and stock state users see. Google cautions that rapidly changing price and availability produced only through JavaScript can be less reliable for crawling. Also reconcile website markup with merchant feeds so the same offer does not publish conflicting values.
Markup describes the specific product page, not a category of many unrelated products.
Variant and group identifiers are stable and consistent with canonical decisions.
Ratings and reviews are visible, attributable, and about the marked-up product.
Currency, price, and availability match the purchasable offer.
Validation warnings are prioritized by eligibility and data accuracy, not by count alone.
8. Prioritize with Search Console and template reach
Join the cleaned inventory with Search Console performance and indexing evidence. Use normalized URL keys, but preserve raw URLs so canonical aggregation and parameter behavior remain inspectable. Segment by template, category, indexability decision, status, canonical target, sitemap state, and issue type.
Real FloxoLab Search Console Page indexing snapshot. The counts and validation states are property-specific; use the issue groups to choose what to inspect, not as universal targets.
Prioritize a defect when it affects an intended template at scale, blocks discovery or consolidation, contradicts the store's inventory policy, or is tied to meaningful impressions, clicks, revenue, or strategic products. A warning on one obsolete URL is not automatically more urgent than a navigation defect hiding thousands of products.
Once the technical inventory is stable, use the product and category page SEO guide to implement useful store templates, variants, availability, media, links, and Product data. Use the on-page SEO audit checklist for the wider page-level review.
What not to do
Do not crawl every filter combination by default. Scope and sample the parameter space first.Do not submit every platform-generated URL. Sitemaps should reinforce the preferred inventory.Do not canonicalize conflicts without fixing internal links. Users and crawlers should receive the preferred URL directly.Do not treat every excluded URL as an error. Carts, searches, duplicates, and controlled facets may be intentionally excluded.Do not remove out-of-stock pages automatically. Decide from permanence, replacement fit, links, demand, and remaining user value.Do not add Product markup to a category just to increase schema coverage. Mark up the actual eligible product offer.Do not rewrite thousands of descriptions before fixing discovery and canonical conflicts. Repair the system that determines which pages can compete.
Verification checklist
Every store template has an explicit indexability and canonical policy.
Important categories and products are reachable through crawlable links.
Search forms, filters, sorting, tracking, and sessions do not create an uncontrolled crawl space.
Pagination exposes stable URLs and links to products beyond the first page.
Redirects, canonicals, internal links, feeds, and sitemaps agree on preferred URLs.
Representative product and category templates return complete mobile and desktop output.
Variant URLs and ProductGroup relationships match the store's actual selection model.
Price, currency, availability, ratings, and reviews match the visible offer.
Temporary and permanent stock states have separate, documented handling.
Search Console evidence is segmented by template and compared with the intended inventory.
Fixes are ranked by template reach, search evidence, user harm, and commercial importance.
An ecommerce audit is complete when the store can explain which URLs should exist, how crawlers reach them, which version cons