Ecommerce SEO Checklist: A Step-by-Step Store Audit
An ecommerce SEO checklist covering crawling, indexing, categories, products, schema, speed and tracking: which tool to use and in what order to audit a store.
An ecommerce SEO checklist is an itemized work list for auditing, in order, how an online store is crawled, indexed and ranked on Google. The short answer: you start the audit with crawling and indexing, then check site architecture, category and product pages, structured data, speed and measurement. At the end, you rank the issues you found by their revenue impact.
I explained what store SEO is and how to set it up in my ecommerce SEO guide. This post is about auditing a store that is already live. Next to each item, I note which tool I use and when I consider the item “passed”.
Why is an ecommerce SEO audit done in a specific order?
An ecommerce SEO audit is done in order because each layer depends on the one before it. If Google cannot crawl a page, it cannot index it. Fixing the title, copy or schema of a page Google has not indexed will not pay off either. That is why I build the audit from the bottom up, from access to content.
On a corporate site this order is less critical, because there are few pages. A store, however, has thousands of products, hundreds of categories and countless URLs generated by filters. A single template error affects hundreds of pages at once. So I audit pages by template, not one by one: the category template, the product template, filter pages and internal search result pages.
What tools do you need for the audit?
Four tools are enough for a basic ecommerce SEO audit: Google Search Console, a site crawler, the Rich Results Test and PageSpeed Insights. Search Console shows how Google sees your site. A site crawler extracts the site’s own link structure, status codes and tags. I mostly use Screaming Frog for this; the site audit modules of Semrush and Ahrefs do the same job.
The real value of the audit appears when you compare these two sources. Pages that show up in the crawler but are not indexed in Search Console are a warning sign. Pages that show up in Search Console but that the crawler cannot find are another warning sign: these are often orphan pages with no internal links pointing to them.
1. How do you check crawling and indexing?
Checking crawling and indexing means verifying that Google can reach important pages and that it adds them to its index. At this step I look at four things: robots.txt, the XML sitemap, HTTP status codes and canonical tags.
robots.txt: I check that the file does not block category pages, product pages, CSS or JavaScript files. The same file should block the crawling of low-value pages such as the cart, account and internal search.
XML sitemap: The sitemap should only contain URLs that return 200, that you want indexed and that point to themselves as canonical. Google uses URLs listed in a sitemap as a signal of canonical preference, but this signal is weaker than the rel=canonical tag.[3] If redirected or noindexed pages stay in the sitemap, the signal gets muddled.
Status codes: In the crawler’s list, I filter out 404s, 5xx errors and redirect chains. The most common issue I find in ecommerce is that removed products are still linked from categories or blog posts.
Canonical: The canonical of every product and category page should point to its own clean URL. Google weighs the rel=canonical tag, redirects and the sitemap together when choosing a canonical.[3] Conflicting signals can lead Google to treat a URL you did not choose as canonical.
Then I move to the page indexing report in Search Console. I group the URLs in the “Crawled, currently not indexed” and “Duplicate, Google chose different canonical than user” states by template. If the group includes category or best-selling product pages, that becomes the audit’s first priority.
2. How do you audit site architecture and faceted navigation?
A site architecture audit verifies that every product can be reached in a few clicks through HTML links starting from the menu, and that filters do not generate uncontrolled URLs. Google recommends that ecommerce sites provide links with the <a href> tag. It also states that it can infer a page’s relative importance from the internal links pointing to it.[1]
I look at the crawl depth report in the crawler. If revenue-generating products sit at the fifth or sixth click, there is a problem in the category tree or the pagination. In pagination, each page should have its own URL, and users should be able to reach the following pages through normal links. A list that only works with a “load more” button can hide the products further down from Google.
Faceted navigation is where ecommerce sites burn the most crawl budget. Every combination of color, size, price and sort options can produce a new URL. Google recommends blocking the crawling of filter URLs with no search demand through robots.txt, or moving filters into the URL fragment (#).[2] During the audit, I compare the number of parameterized URLs the crawler found with the actual number of categories and products. If parameterized addresses outnumber the core pages many times over, this item is red.
3. What do you check on category and product pages?
A category and product page audit checks whether the templates produce a unique title, H1, description and internal links for every page. At this step, I filter the crawler’s list by template and look for duplicate values in the title and H1 columns.
On category pages, the title and H1 should contain the phrase people search for, there should be a short intro above the list, and the page should link to its subcategories. I covered this topic in detail in my category page SEO post. During the audit, I pay particular attention to empty categories: a category with no products left that returns 200 can be flagged as a soft 404 in Search Console.
On product pages, I check three things. First, whether the description is text copied from the manufacturer. Second, whether variants (color, size) are identified with separate URLs and whether their canonicals are consistent. Third, how out-of-stock products behave. A product page that is temporarily sold out should stay live, while a product removed for good should redirect to the closest category or return a 404/410.
Title and meta description length is also checked at this step. Because the title width shown in search results is limited in pixels, long titles get truncated at the end. With the tool below, you can type the title and description of a category or product template and see how it will look.
4. How do you validate product structured data?
Product structured data is audited by verifying that the Product and Offer markup on the product page is valid and that values such as price and availability match the information on the page. Google states that Product markup can be used to show information such as price, availability and ratings as rich results in search.[4]
I run this check with the Rich Results Test on a few sample URLs, then for the whole site with the “Product snippets” and “Merchant listings” reports in Search Console. The single-URL test shows the structure of the schema, while the Search Console report shows how many pages the errors affect.
The most common error I find is a schema price that differs from the price on the page. It usually appears during sale periods, in themes where the schema and the visible price are fed from different fields. If the store also sends products to Merchant Center, three values need to match: the price on the page, the price in the schema and the price in the feed. I covered the feed side in my Merchant Center free listings post.
5. How do you measure page speed and Core Web Vitals?
A page speed audit checks the real-user values of category and product templates using the Core Web Vitals report in Search Console and PageSpeed Insights. Core Web Vitals consists of three metrics that measure loading speed, responsiveness to interaction and visual stability. The thresholds Google publishes are below.[5]
- LCP: largest content loaded
- < 2.5 s
- INP: response to interaction
- < 200 ms
- CLS: visual shifts
- < 0.1
I measure per template, not on a single page. Search Console also reports URLs in groups of similar pages. In ecommerce, the source of an LCP problem is usually large, uncompressed product images. INP problems usually come from heavy third-party scripts, such as chat, review and tracking code. CLS comes from late-loading banners and images with no defined dimensions.
I read speed metrics with mobile device data. Because a significant share of store traffic often comes from mobile, a page with good desktop values can stay above the threshold on mobile. When I make a recommendation, I write a concrete target instead of “make it faster”, for example: “On the product template, serve the main image as WebP and keep it out of lazy-loading.”
6. How do you check measurement and internal links?
A measurement audit verifies that sales from organic traffic are recorded correctly in GA4 and that Search Console is linked to GA4. A store that cannot see its organic sales cannot calculate the revenue impact of its SEO work. That is why I check that the view_item, add_to_cart and purchase events arrive with product and value information.
At this step, I also check whether checkout moves to a different domain. If checkout is on an external domain and cross-domain measurement is not set up, sales can be attributed to the referral source instead of organic. This setup has to be handled together with ad measurement, and it is the common ground between SEO services and performance marketing for a store.
The internal link check covers whether blog and guide content links to the relevant categories. An informational guide should move the reader to the relevant category with a natural sentence. Conversely, the category page should link to the “how to choose” type of guide. I covered managing pages built for campaign periods separately in my Black Friday SEO post.
How do you prioritize audit findings?
Short answer
How do you prioritize ecommerce SEO audit findings?
Audit findings are prioritized by the revenue share of the affected pages and the cost of the fix. Easy-to-fix errors affecting category and best-selling product pages are solved first. Work that affects the whole site but needs long development goes onto a separate roadmap, and the same check is repeated after every fix.
- Group each issue by the template and number of pages it affects.
- Work out the share of organic revenue or traffic of the affected pages.
- Estimate the development time needed for the fix.
- Put high-impact, low-cost work into the first sprint.
- Write large infrastructure work into a separate roadmap.
- After the fix, repeat the same check and record the result.
The most common mistake in an audit report is listing hundreds of items as if they were equally important. A development team cannot tell what to do first from a list like that. I build the report with three columns: the issue, the page group it affects and the recommended fix. Then I give each row an impact and cost score.
When estimating impact, I look at the revenue those pages generate, not the page count. An error on a hundred low-value tag pages matters less than a single main category dropping out of the index. To make that distinction, I match organic revenue data in GA4 with the page list in Search Console.
Summary: a checklist is used regularly, not once
An ecommerce SEO checklist is the way to audit a store in order, from access to content. You start with crawling and indexing, check architecture and filters, then move to category and product templates, schema, speed and measurement. In the last step, you rank what you found by revenue impact.
As a next step, I suggest adapting this list to your own store’s templates and turning it into a spreadsheet. Repeat the full audit before theme changes and major campaigns, and the Search Console checks every week. You can find how I work on audits and technical SEO on the SEO services page, and my background on the about page.
Key terms
- SEO audit
- SEO audit is the systematic review of how a website is crawled, indexed and ranked by search engines, from a technical, content and measurement perspective. Its output is a prioritized list of issues and fixes.
- Crawl budget
- Crawl budget is the number of URLs Googlebot spends crawling on a site within a given period. When filter and sort parameters generate thousands of unnecessary URLs, that budget can be spent on worthless addresses instead of important category and product pages.
- Core Web Vitals
- Core Web Vitals is the set of three metrics Google uses to measure page experience through loading speed (LCP), responsiveness to interaction (INP) and visual stability (CLS). The values come from real user data and are reported in Search Console as groups of URLs.
Frequently asked questions
How often should an ecommerce SEO audit be done?
A full audit should be done once or twice a year, and right after a major platform change, theme update or site migration. The page indexing and Core Web Vitals reports in Search Console are monitored weekly. Smaller checks are repeated before busy campaign periods.
Where should an ecommerce SEO audit start?
An audit should start with crawling and indexing checks. If Google cannot crawl a page or does not index it, content and schema fixes on that page will not pay off. So robots.txt, the sitemap, status codes and canonical tags come first, then category and product pages.
What tools do you need for an ecommerce SEO checklist?
Google Search Console, a crawler (such as Screaming Frog), the Rich Results Test and PageSpeed Insights are enough for a basic audit. Search Console shows what Google sees, while the crawler shows the site's own structure. Comparing the two surfaces most problems.
Is an SEO audit different on a Shopify store?
Most of the checklist is the same, but some settings are managed by the platform. Shopify generates robots.txt and sitemap files automatically, products can also be reached through collection paths, and those addresses point to the main product URL with a canonical. The audit checks whether the theme has broken these automatic behaviors.
In what order should audit findings be fixed?
Issues that affect revenue-generating pages and are easy to fix come first. Category pages that dropped out of the index, wrong canonicals and broken schema are usually at the top. Site-wide work that needs long development time goes onto a separate roadmap.
Sources
- Google Search Central: Help Google understand your ecommerce website structure
- Google Search Central: Managing crawling of faceted navigation URLs
- Google Search Central: Consolidating duplicate URLs and canonicalization
- Google Search Central: Product structured data
- Google Search Central: Core Web Vitals and Google Search results
The full topic: E-commerce SEO guide ↗ · Technical SEO guide ↗