The first time I log into a WooCommerce store I’ve never seen, I don’t fix anything. That surprises people who hired me to fix things. But a WooCommerce store audit done in a hurry tends to break the one thing that was quietly holding the store together, and then the first week of work is spent undoing my own change.
So the first ninety minutes are for looking. I’ve worked inside other people’s setups long enough, at Universal Wholesale and at Wild Bill’s Tobacco, to know that most stores have a reason for their odd choices. Sometimes the reason is bad. I still want to know it before I touch anything.
Minutes 0 to 15: access and a backup
Before I read anything, I confirm what access I have and take a backup. Admin login, hosting panel, and whoever controls DNS. If there’s no backup plugin and the host doesn’t offer one, I export the products, orders and customers as CSVs at minimum.
I also note the WordPress, WooCommerce and PHP versions. Outdated versions don’t mean I update on day one. They tell me how careful every later step needs to be.
Minutes 15 to 35: plugins and theme
I go through the plugin list slowly. For each one I want to know what it does and whether it’s doing anything the store relies on. Payment gateways, shipping rate plugins, pricing rules, anything that touches the cart. Those are the ones I won’t touch without a staging copy.
I’m also looking for overlap. Two SEO plugins. Two caching plugins. A page builder that’s installed but used on one page. Overlap is where conflicts live. I write it down. I don’t deactivate it.
For the theme, I check whether it’s a child theme and whether WooCommerce reports outdated template overrides under WooCommerce, Status. Outdated overrides are a common reason a cart or checkout looks fine and then misbehaves after an update.
What should a WooCommerce store audit checklist include?
People search for this a lot, and the lists I find online tend to be either a dozen items or a hundred. For a first visit, I care about the things that cost sales or put data at risk. Everything else can wait for the second pass.
- Can a customer find a product, add it to cart and pay?
- Is the catalog data consistent enough that filters and search work?
- Are orders arriving with the right totals, tax and shipping?
- Are there plugins or overrides that will break on the next update?
- Is there a backup and a way to roll back?
Speed, design and SEO matter. They’re just not first.
Minutes 35 to 55: a catalog sample
I export the products and open them in Excel. Not to fix them, to read them. I sort by SKU and look for blanks and duplicates. I filter for products with no price, no image, or no category. I check a few variable products to see if the variations have their own SKUs and stock or if everything rides on the parent.
Then I check attribute values. If a size attribute has “Large”, “large” and “LG” as three separate terms, the layered filters on the shop page are broken whether anyone has noticed or not.
This sample tells me more about the store’s history than anything in the admin. Clean data usually means someone cared. Messy data tells me how many hands have been in it.
Minutes 55 to 70: a real checkout
I place a test order as a guest in a private window. I pick a product with variations, change quantity, apply a coupon if the store uses them, and go all the way through. If the gateway has a test mode, I use it. If it doesn’t, I ask before spending real money.
Then I check the back end. Did the order show up with the right status? Did the confirmation email arrive? Did stock go down? A checkout that looks fine on the front end and drops the email on the back end is one of the most common problems I find, and the owner almost never knows about it.
Minutes 70 to 85: search, speed and Search Console
I search the store for a few product names and a few SKUs. If searching an exact SKU returns nothing, that’s a finding. I run the home page and one product page through a speed test, mostly to spot something extreme like huge uncompressed images.
If I have Search Console access, I look at the pages report for indexing problems and at whether old product URLs are throwing errors. That’s where missing redirects from an old migration show up.
Minutes 85 to 90: write it down
The last few minutes go into a short list sorted into three groups: breaking sales now, risky on the next update, and worth improving later. Each line says what I saw and where. No fixes yet.
That list is what I bring back to the owner. It turns a vague “the site needs work” into a short set of specific problems with an order to them. It also gives them a chance to say “that plugin is there because of our distributor” before I remove it.
If you’re about to take over a store, try this once. Give yourself ninety minutes, open nothing in edit mode, and end with a written list. Then fix the top item first.