Why auditing a store is different from auditing a regular website
A corporate site has a few dozen pages, and each can be reviewed by hand. An online store has thousands or tens of thousands, and most are generated automatically: categories, filters, sorting, product variants and pagination. A single template error repeats across every page at once. That is why a store audit starts not with individual URLs but with the templates and rules the platform uses to generate pages.
The second factor is the platform. Shopify, WooCommerce and other systems have their own constraints. Some settings depend on the theme and third-party apps, and not everything can be changed without rebuilding the store. A good audit separates what can be fixed in a day from what needs a business decision by the owner.
The third is product data. Price, availability, reviews and attributes must be correct on the page, in the structured data and in your feeds at the same time. Mismatches hurt organic search, sales and visibility in Google's AI features alike.
What we check
- Crawler accessibility. We look at the site as a crawler sees it, not a browser: status codes, redirects between domain versions, robots.txt, bot protection rules and CDN settings.
- Indexing and crawl budget. Which pages Google indexes and which it ignores, whether valuable categories are blocked, and whether thousands of filter and parameter combinations are left open.
- Duplicates. Product variants, one product listed in several categories, pagination, sorting and canonical URLs.
- Structured data. Validity and completeness of Product, Offer, Review, AggregateRating and BreadcrumbList across all templates.
- Meta tags and headings. Title and description templates, pixel length, H1-H3 structure and duplicates.
- Speed. Field and lab Core Web Vitals, and the impact of the theme, apps, images and scripts.
- Content and keywords. Category copy, cannibalization between categories and filters, and weak pages.
- Analytics and feeds. Accuracy of GA4 ecommerce tracking, conversions and availability data in product feeds.
- GEO. How your products and brand appear in AI Overviews and other AI answers, and whether the site is accessible to AI crawlers.
What we have found in real stores
In a Shopify store that was growing but not getting the expected results from search, we discovered that a Cloudflare bot challenge was returning a 403 error to search crawlers on the www version. Regular visitors saw nothing wrong, so the owner had no idea. Alongside that, we removed duplicate headings, cutting them from 54 to 35, and shortened the meta title from 663px to 410px. The page structure score in Seobility rose from 25% to 58%. To be transparent about the limits: mobile PageSpeed stayed at 22 because of the theme and apps, and it can only be improved meaningfully by replacing the theme or dropping some of the apps.
For an online brand in a health-related niche, the structured data audit showed that only 93 pages had valid markup, while 684 contained errors. After the fixes, 914 pages had valid markup, one page still had an error, and pages outside the index fell from 1,906 to 1,307. Impressions in Google's AI features grew by 546.7% over two months.
In an online pharmacy with tens of thousands of product pages, the main problems were filters and URL parameters that diluted the crawl budget, plus identical template meta tags. After controlled indexing was implemented, clicks from Google grew 10.7x over a year.
And while preparing a marketplace feed in another project, we found a bug that showed 97 out of 422 products as in stock with no actual inventory.
What you receive
Not a PDF full of tool screenshots, but a task table: the issue, the template or section where it repeats, how to fix it, who should do it (developer, content manager or marketer) and the expected impact. We flag separately anything that runs into platform limits and suggest the best available option.
Timelines
An audit usually takes 5-10 business days, depending on catalog size and the number of languages and markets. The impact of implementation depends on what we find: unblocking crawlers or fixing markup works quickly, while growth from a new category structure usually takes several months. After delivering the audit, we can support implementation or verify the results.
How we set priorities
In a large store, an audit always uncovers more issues than a team can fix in a month. So we score each task on two factors: impact on traffic and revenue, and the effort needed to implement it. Blockers that hide part of the store from Google come first: crawler access errors, an accidental noindex, blocked categories. Next come template errors repeated across thousands of pages: schema, canonical URLs and meta tags. After that we tackle category content, internal linking and speed. We separately mark quick wins that can be done in a day and tasks that require changing a theme, plugin or platform, with an honest view of whether the result justifies the cost.
When to order an audit
- before migrating to another platform or redesigning the store;
- when organic traffic or search revenue starts falling for no obvious reason;
- when the store is growing but SEO is not delivering the expected results;
- before launching in new markets or on marketplaces;
- if your store has never had a technical review.
