How to Audit Your WooCommerce Store for AI Shopping, Speed, and Health (2026 Checklist)

Most WooCommerce store owners find out something is wrong the slow way: sales drift down for a few months, a competitor starts showing up in places they don’t, and nobody can say exactly why. The truth is usually a stack of small, invisible problems — a blocked AI crawler, product pages missing the structured data that shopping tools rely on, a three-second server response that quietly taxes every visit. None of them announce themselves, and none of them show up in your order screen. They show up as sales you never got.

An audit is how you make those problems visible before they cost you more. This post is the checklist we use ourselves — roughly twenty checks across four areas that decide whether your store gets found, gets recommended by AI assistants, and loads fast enough to convert. We built the whole thing into a free tool, the WooCommerce Checkup, so you can get the same graded report in about a minute. But the checklist matters more than the tool, so let’s walk through what to look at and why each item earns its place.

Why audit a store that’s already running?

Because the ground moved. For a decade, “getting found” meant one thing: rank in Google. That still matters, but a second discovery layer now sits on top of it. Shoppers ask ChatGPT, Perplexity, and Google’s AI Mode to recommend stores directly, and those assistants build their answers from a different set of signals than the classic ten blue links. A store can rank respectably in Google and still be completely invisible inside an AI answer, because the assistant couldn’t read its pages, couldn’t parse its product data, or found nothing structured enough to quote.

So a modern audit has to look in two directions at once: the traditional SEO and performance issues that have always mattered, and the newer answer engine optimization (AEO) signals that decide whether AI tools will name you. The good news for a small shop is that most competitors have done nothing about the second category yet, so the bar to stand out is still low. Here is how the two disciplines differ:

	Traditional SEO	Answer Engine Optimization (AEO)
Goal	Rank in the list of search results	Get named inside an AI-generated answer
Optimizes for	Google’s ranking algorithm	AI assistants — ChatGPT, Perplexity, Gemini, Google AI Mode
Key signals	Content quality, backlinks, on-page SEO	Crawler access, structured product data, third-party trust
You win by	Ranking on page one	Being readable and quotable — even from page two

The checklist below is grouped into four sections that cover both. Start at the top, because that’s where the leverage is.

1. AI shopping readiness (AEO)

This is the area most stores fail, and the one with the most upside. AI assistants can only recommend a store they can read and trust. That breaks down into three questions: can their crawlers reach your pages, is your product data structured enough to quote with confidence, and are there signals that vouch for you? These are the specific checks worth running.

• AI crawler access in robots.txt. The most damaging single mistake. Blocking a citation bot — GPTBot (ChatGPT), PerplexityBot, ClaudeBot, or Amazonbot — removes you from the answer entirely. Blocking a training-only bot such as CCBot is a legitimate choice and only worth noting. Know the difference before you edit that file, because a blanket block throws away the good crawlers with the ones you meant to stop.
• Renders without JavaScript. Most AI crawlers don’t execute JavaScript. If your product name, price, and description only appear after a script runs, the assistant sees an empty page. Your core content has to be in the raw HTML.
• Product structured data (Product + Offer). Schema.org Product markup with an Offer block carrying price and availability is the minimum threshold for an assistant to consider your product with confidence. WooCommerce’s default output is thin, so this is worth checking on a real product page, not assuming.
• Schema completeness (brand, GTIN, MPN). Even when the base Product schema is present, missing identifier fields lower confidence. A page with brand and a GTIN is easier to match and cite than one without.
• Review schema (aggregateRating). Star ratings in structured form are a trust signal both search engines and assistants read directly.
• Breadcrumb schema. Helps machines understand where a product sits in your catalog.
• FAQPage schema. Self-contained question-and-answer blocks are among the easiest content for an assistant to lift verbatim into an answer.
• Organization schema on the homepage. Tells assistants who you are as an entity — the foundation for being recognized by name.
• llms.txt file. An emerging convention that gives AI engines a curated map of your most important pages. Cheap to add, and still rare enough to be a differentiator.
• Product sitemap coverage and a merchant feed signal. Assistants lean heavily on structured product feeds; ChatGPT’s shopping picks in particular track closely with Google Shopping’s organic results, so a complete feed and sitemap are foundational.

Two of these deserve their own reading if you want to go deeper: which AI bots actually crawl your WordPress site (from eight weeks of our own server logs) and how to add schema in JSON-LD without a premium plugin.

2. On-page SEO fundamentals

The classics still decide whether Google — and by extension the AI layers built on top of it — can index and understand a page. These are quick to check and quick to fix, which makes them easy wins in an audit.

• Meta description present and the right length. Aim for roughly 50–160 characters. Too short wastes the slot; too long gets truncated in results.
• Canonical tag correct. It should be present, point to the page itself, and not sit alongside a conflicting noindex. WooCommerce’s variations, filters, and pagination make duplicate URLs easy to create by accident, so canonicals matter more here than on a brochure site.
• Exactly one H1. A single, clear top heading tells search engines what the page is about. Themes and page builders sometimes emit zero or several — worth confirming on your key templates.

3. WooCommerce health

These are the plumbing checks. They rarely make headlines, but a slow or bloated store leaks conversions on every single visit, and a security or version problem can take the whole shop down.

• WooCommerce version freshness. Running well behind current means missing security patches and, often, performance improvements. It’s the first thing to reconcile against your update process.
• Server response time (TTFB). Time to first byte is how long your server takes to start replying. Over about a second and everything downstream — rendering, Core Web Vitals, the shopper’s patience — starts from behind. This is usually a hosting and caching problem, not a theme problem.
• Mixed content / HTTPS. An HTTPS page loading an insecure asset throws browser warnings and undermines trust at exactly the wrong moment — the checkout.
• Plugin bloat. Every active plugin adds code to every request. A high count is a signal to look for overlap and dead weight — the most common cause of a store that got slower for no obvious reason.
• Cart-fragments loading site-wide. WooCommerce’s cart-fragments script updates the mini-cart via AJAX, but it’s often loaded on every page — including pages with no cart in sight — where it adds a request for nothing. A classic, easy speed reclaim.

4. Speed

Speed sits in its own category because it compounds everything else. A store that ranks, has perfect schema, and welcomes every crawler still loses the sale if the page takes five seconds to become usable. We measure it with Google PageSpeed Insights — the same performance data Google itself uses — rather than a stopwatch, so the number reflects real Core Web Vitals rather than a single lucky load.

If speed is your weak spot, that’s a deep enough topic to warrant its own plan; our WordPress speed optimization approach for small stores is a good starting point.

Running the whole checklist in a minute

Working through twenty checks by hand — reading robots.txt, validating schema on a live product page, timing your server, running PageSpeed — is a good afternoon’s work and assumes you know where to look. We got tired of doing it manually for every store we quoted, so we built an auditor that does it in one pass. Internally we call it Min; the public, free version is the WooCommerce Checkup. You enter your store URL, and it fetches your pages the way a crawler would, checks every item above, and returns a report.

A few things make the report worth reading rather than just another score:

• An A–F grade with your top three issues ranked by impact. Not a wall of 200 warnings — the three things actually holding you back, in order.
• It tells citation bots from training bots. Most checkers just flag “you block a bot.” The Checkup knows blocking GPTBot costs you a citation while blocking CCBot is a defensible choice, and grades accordingly.
• Facts, not guesses. Each check is based on a real fetch of your live site — the actual robots.txt, the actual schema on the page, the actual server timing — with the evidence behind every pass or fail.
• Re-scan to see progress. Run it again after you’ve made changes and it shows the before/after grade difference, so you can prove a fix worked rather than hoping it did.

It’s free, there’s no login, and the full report lands in your inbox so you can work through it at your own pace.

What to do with your grade

A grade is only useful if it changes what you do next. Here’s how we’d triage the result. If you scored well on health and speed but poorly on AEO, you’re in the most common — and most fixable — position: your store works fine, it’s just invisible to the new discovery layer. Start with crawler access and Product schema, because those are the two levers that move the grade most. If speed or TTFB is the problem, that’s usually a hosting and caching decision rather than a content one, and it’s worth solving properly because it drags on everything else. And if the report is red across the board, don’t try to fix it all in one weekend — work the top three, re-scan, and repeat.

If you’d rather hand the list to someone, that’s what we do. The same audit that powers the Checkup is the first step in how we scope a store optimization, so the report doubles as a plain-English brief you can act on yourself or send our way for a fixed-price quote.

Frequently Asked Questions

• How often should I audit my WooCommerce store? Run a full audit quarterly, and again after any big change — a theme update, a plugin overhaul, a hosting migration, or a WooCommerce major version. Those are the moments things silently break. A quick re-scan after each fix confirms it actually landed.
• What is AEO, and how is it different from SEO? SEO optimizes to rank in a list of search results. AEO — answer engine optimization — optimizes to be recommended inside an AI-generated answer from tools like ChatGPT, Perplexity, and Google’s AI Mode. They overlap, but a store can rank well in Google and still be invisible to AI assistants, so a modern audit checks both.
• Is the WooCommerce Checkup free? Yes. You enter your store URL, get an A–F grade with your top three issues on screen, and the full report is emailed to you. There’s no login and no charge.
• Will blocking AI crawlers protect my content? It’s a trade-off, not a free win. Blocking a training-only bot like CCBot limits use of your content for model training. But blocking a citation bot like GPTBot or PerplexityBot also removes you from the AI answers that send buyers to your store. Know which bot does which before you edit robots.txt.
• Why does server response time (TTFB) matter so much? TTFB is how long your server takes to begin replying, and it runs before anything a shopper sees. A slow TTFB — usually a hosting or caching issue — puts every downstream metric and every visitor’s patience on a delay. Getting it under a second is one of the highest-leverage speed fixes there is.