WooCommerce Technical SEO Audit Checklist
A WooCommerce technical SEO audit should find the issues affecting useful product and category pages, then turn them into fixes you can verify. Start with access and discovery before polishing metadata.
Read the guide
Search Field Notes
A useful next read.
36 field notes
No matching guide yet. Try “checkout”, “shipping” or “catalog”.
All Field NotesChoose the page types that matter
List the categories, products and buying guides the business needs people to find. Sample simple and variable products, large and small categories, unavailable items and any filters intended as landing pages. A full crawl can be useful, but the audit still needs to explain which findings affect these destinations.
Use Search Console evidence where available, including page indexing and the queries important pages already receive. Record country, date range and search type when interpreting performance. Without that access, an auditor can inspect technical behaviour but should not claim to know the store’s actual search traffic or demand.
Check responses, crawl access and indexing rules
Confirm that intended public pages return the correct content and successful response. Review redirects, server failures, robots.txt, rendered robots tags and response headers. A public product accidentally marked noindex needs a different fix from a crawl blocked by the host or firewall.
Compare affected examples with a working page from the same template. Use URL Inspection to distinguish Google’s indexed information from a live accessibility test. Keep private account and checkout information protected. Removing every restriction across the site is not an audit remedy; change only the unintended rule on pages meant for discovery.
Follow the catalog through ordinary links
Walk the menu, categories, pagination and product links. Important products should be reachable without relying only on a search form or a JavaScript event that exposes no ordinary link. Check that navigation points to the intended URLs and that important categories are not stranded.
Review the sitemap against those same destinations. Include preferred public URLs and investigate stale or contradictory entries. A submitted sitemap helps discovery; it is not proof of indexing. If a template makes an entire category hard to reach, fixing that shared route is more useful than adding isolated links to a few products.
Review canonicals, filters and URL duplicates
Check the declared and Google-selected canonical on representative pages. Tracking URLs, sorting, filters and variations can expose alternative paths. Decide which combinations serve a distinct useful search intent, then make their indexing and canonical treatment consistent.
Align internal links, redirects and sitemap entries with the preferred URLs. Avoid blanket rules copied from a different catalog. Pagination must still support discovery, and an equivalent duplicate differs from a useful filtered landing page. Record the policy so a new import or navigation extension does not undo it.
Turn an SEO finding into a fix
Tie each issue to a URL or template and a clear way to check the change.
| Check | What to check | Next step |
|---|---|---|
| Access + discovery | Record the response, indexing rules and route from category to product. | Correct the observed block. |
| Template output | Check shared titles, canonicals and product markup against the visible page. | Fix the responsible component. |
| Catalog URL policy | Distinguish useful filters, duplicate paths and removed products. | Apply one consistent policy. |
Inspect the product and category templates
Review titles, headings, descriptions and the information a buyer needs to choose. Find patterns across templates rather than rewriting individual tags while the shared output remains wrong. Product identity, specifications, variant information and availability should be clear and accurate.
Test product structured data against what the page displays, including price, currency and availability. Identify which plugin or template emits it before adding a second implementation. Do not invent reviews or ratings to pass a validator. Valid markup supports eligibility for certain displays, while Google decides whether those displays appear.
Decide how unavailable and removed pages behave
A temporarily out-of-stock item can still answer a useful product question. A permanently removed item needs a separate decision about its content, replacement and URL. Check empty categories and removed ranges with the business before redirecting them.
Where a genuine equivalent replacement exists, assess the redirect to that destination. Sending every removed product to the homepage can leave visitors and search systems with an unrelated result. Keep useful information accessible where appropriate, and use the correct response when a page is actually gone. Include the URL policy in future catalog operations.
Deliver a backlog with evidence and acceptance
Each finding should identify representative URLs, the observed issue, affected templates, priority and the component owner. Add the proposed change and the check that will confirm it. Group repeated issues so the owner can commission a coherent fix, rather than receive hundreds of rows with no decision attached.
After implementation, repeat the technical checks and monitor the relevant search evidence. Keep delivery success separate from ranking or traffic changes, which need their own observation and context. A good audit leaves the store with a short, ordered backlog and a way to tell whether each task was actually completed.
Common questions
Is a crawler export a WooCommerce SEO audit?
It is one input. The audit should interpret it against catalog rules, important templates and available search evidence, then identify priorities and verifiable fixes.
Should all product-filter URLs be indexed?
No blanket rule fits every catalog. Decide which are distinct, useful landing pages and review their links, content and technical signals before implementing the policy.
Does product schema guarantee rich results?
No. It needs to describe the visible product accurately and meet applicable requirements. Display remains Google’s decision.
What should the audit handover include?
Evidence, affected scope, priority reasoning, component owners, proposed fixes, acceptance checks and access limitations. Implementation should be clearly included or separately scoped.