Store health is four dimensions: technical health, conversion health, content/SEO health, and operational health. Miss one and you leak money — but most merchants only watch one of them, and usually the wrong one.
The most common misdiagnosis: treating an operations-layer problem as a theme-layer problem. Conversion drops, the first reaction is “the theme is bad,” so you swap themes, install apps, swap themes again — three months later the problem is still sitting there. In reality, a shipping rate was never configured for one region, abandoned checkout emails were never turned on, Markets is enabled but local payment methods aren’t connected. All of that lives in Settings, and none of it has anything to do with a single line of theme code.
The rules for this checklist are simple: everything runs through native Shopify admin paths, no third-party apps; sorted by check cost, not by importance; threshold references given, but no invented industry benchmark numbers. Admin paths are current as of 2026 — your own admin is the final word.
1. First, What Does “Store Health” Actually Cover?
Four dimensions, one table
| Dimension | What you check | Typical symptom | Check cost |
|---|---|---|---|
| Technical health | Speed, errors, indexing | Slow on mobile, LCP over threshold | 10 min |
| Conversion health | Checkout funnel, payments, shipping | Add-to-cart fine, checkout leaks | 30 min |
| Content/SEO health | Theme structure, structured data, multilingual | Low indexing, rich results missing | Requires theme code |
| Operational health | App bloat, inventory, order flow | 15 apps installed, no out-of-stock notice | Recurring |
Why sort by “check cost”
I always start with the 10-minute checks, because that’s usually where the problem is. Anything that requires touching theme code goes last — confirm the earlier layers are clean first, otherwise you’re editing for nothing.
One-line principle: rule out operations-layer problems before you suspect the theme layer.
Swapping a theme costs a few thousand dollars and two weeks. Fixing a shipping rate costs two minutes. Get the order wrong and you waste both.
2. Technical Health: 4 Checks You Can Finish in 10 Minutes
1. Theme performance report (Core Web Vitals)
Path: Analytics → Reports → search "Performance"
Watch three numbers: LCP, CLS, INP. Threshold references below — note these are Google’s general Core Web Vitals standards, not Shopify standards:
| Metric | Good | Needs improvement | Poor |
|---|---|---|---|
| LCP | < 2.5s | 2.5–4.0s | > 4.0s |
| CLS | < 0.1 | 0.1–0.25 | > 0.25 |
| INP | < 200ms | 200–500ms | > 500ms |
Focus on mobile, not desktop. You know your own traffic split. If desktop is a bit slow, deprioritize it.
2. App script injection audit
Path: Online Store → Themes → Edit code, search for script_tag and content_for_header
High-frequency failure point: multiple apps stacking JS through ScriptTag injection, dragging LCP down. Shopify’s own Web Performance documentation explicitly recommends auditing the performance impact of third-party app scripts.
How to do it: Settings → Apps and sales channels lists every app. Ask one question per app: “Am I still using this?” Installing “just to try it” and forgetting to uninstall is the norm.
3. Are images using CDN size parameters?
Check whether your theme’s image output uses Liquid’s image_url filter with width / height parameters.
Symptom: a custom theme outputs the original image directly, so mobile loads a 2000px file. This is a theme-layer problem, not an operations problem, and fixing it means touching code.
Shopify’s image_url filter supports width, height, and crop parameters. Used correctly, it cuts a large chunk of image weight.
4. Indexing and sitemap
Visit yourdomain.com/sitemap.xml and yourdomain.com/robots.txt directly.
Shopify generates both automatically, but a custom theme can break robots.txt. Cross-check with the Google Search Console verification status under Online Store → Preferences.
3. Conversion Health: 5 Checks You Can Finish in 30 Minutes
1. Checkout funnel: where the money leaks
Path: Analytics → Reports → Conversion rate, alongside the Abandoned checkout report.
Look at relative change, not absolute values. How much this week dropped versus last week is far more useful than “what’s the industry average.”
I deliberately won’t write numbers like “industry average conversion rate is 3.2%” — variance across categories is enormous, and quoting one only misleads.
2. Are payment methods complete?
Path: Settings → Payments
Check two things: any failed payment records; whether your primary payment methods cover your target markets. Running only one local wallet for the US market means voluntarily giving up orders.
3. Any “no shipping rates available” in shipping rules?
Path: Settings → Shipping and delivery
High-frequency failure point: some regions or weight brackets have no shipping rate configured, so checkout dead-ends — often without a readable error. Many people miss this because it doesn’t show on the checkout page; it only triggers under specific conditions.
4. Is abandoned checkout recovery turned on?
Path: Settings → Checkout → Abandoned checkout
Shopify has built-in abandoned checkout recovery, but it must be manually enabled and configured. Plenty of merchants assume it’s on by default. It isn’t. This is the highest ROI item on the list, and it takes two minutes.
5. Markets enabled but payments/currency not fully configured
Path: Settings → Markets
Symptom: users see local currency pricing, then can only pay with a USD card at checkout. Classic “fake internationalization” — conversion leaks immediately, and the user won’t tell you why. They just close the tab.
4. Content & SEO Health: 4 Checks That Require Theme Work
1. Theme structure: forked and never updated?
How to tell: Online Store → Themes, check whether the current theme was edited directly from an old version.
Consequence: once Shopify ships a new theme version, you can’t merge it, so security and performance fixes never reach you. A forked theme that stops updating is the root cause of many stores “getting slower over time.”
Recommendation: push changes through sections / app blocks rather than editing core files. The Online Store 2.0 JSON templates, sections, blocks, and app blocks system exists exactly for this.
2. Is structured data still there?
Path: Online Store → Themes → Edit code, check theme.liquid and product templates.
Check whether Product / Offer schema was stripped out by a custom theme. What’s at stake is Google rich results — whether price, rating, and availability can appear in search results.
3. Navigation and homepage SEO
Path: Online Store → Navigation (menu structure) + Online Store → Preferences (homepage title/meta)
Menu structure affects crawler paths and how users find products. Homepage title and meta description are blank zones in many stores — set once when the theme was installed and never touched again.
4. Multilingual translation completeness
Path: Settings → Languages
Check whether only the navigation was translated while product descriptions remain in the source language. Half-translated is worse for conversion than untranslated — a user clicks through native-language navigation and lands on all-English content. Trust drops instantly.
5. Operational Health: 4 Recurring Checks
1. App bloat inventory
Path: Settings → Apps and sales channels
Method: three questions per app — still in use? Are the permissions reasonable? What scripts does it inject?
Suggested frequency: quarterly. Apps are subscriptions; uninstalling saves money and speeds things up.
2. Inventory and out-of-stock
Path: Analytics → Reports → Inventory
Check turnover, and SKUs that have been out of stock long-term while still running ads. Advertising something nobody can buy is the most direct form of waste.
3. Order flow: unfulfilled / overdue orders
Path: Orders → filter unfulfilled / overdue
Overdue unshipped orders are a hotbed of bad reviews and refunds. No need to wait for the quarter — scan weekly.
4. Product SEO field completeness
Path: Products → individual product → Search engine listing
Check whether handle, title tag, and meta description are missing in bulk. With a large catalog this is manual labor, but you can sort by sales and fix the best sellers first.
6. If You Only Have 1 Hour, Run These 7 First
Execute in order; the first 4 finish within 10 minutes:
| Order | Check | Path | Time |
|---|---|---|---|
| 1 | Mobile LCP | Analytics → Reports → Performance | 3 min |
| 2 | Installed app list | Settings → Apps and sales channels | 3 min |
| 3 | Abandoned checkout email on? | Settings → Checkout | 2 min |
| 4 | Payment method completeness | Settings → Payments | 2 min |
| 5 | Checkout funnel relative change | Analytics → Reports → Conversion rate | 15 min |
| 6 | Shipping rule dead zones | Settings → Shipping and delivery | 15 min |
| 7 | Markets payment/currency match | Settings → Markets | 20 min |
The first four total 10 minutes but eliminate most “money can’t get in” problems. The last three require reading data and making judgment calls, so slower is normal.
7. Pseudo-Metrics: Looks Like a Problem, Actually Ignore It
| Pseudo-metric | Why not to panic |
|---|---|
| High bounce rate | Single-page landing pages are naturally high; not a signal |
| Slow desktop speed | Check mobile first; desktop is lower priority |
| Many apps installed | What matters is script injection and whether they’re still used |
| Conversion below some “industry value” | Category variance is huge; compare only to your own history |
| Low sitemap indexed count | Normal for new stores; watch the trend, not the absolute |
The real harm of pseudo-metrics isn’t wasted time — it’s making decisions in the wrong direction. Redesigning your homepage because “bounce rate is high,” then finding bounce rate didn’t move, because the landing page was always a single page.
8. FAQ
Q1: How do I check Shopify store health? Is there a one-click tool?
There’s no official “one-click health score.” Every check in this article can be done natively in Shopify admin, with no third-party app. Third-party audit apps can supplement, but don’t treat one as your only source — it tests what it can test, not what you need.
Q2: Which Shopify admin settings should I check?
The four highest-priority groups: Settings → Checkout, Settings → Payments, Settings → Shipping and delivery, Settings → Markets. These four directly determine whether money can come in. Everything else can wait.
Q3: How do I diagnose low Shopify conversion rate?
Start with the checkout funnel (Analytics → Reports → Conversion rate) and determine whether the leak is “add-to-cart to checkout” or “checkout to payment.” The former is usually shipping or payment; the latter is usually trust or payment method coverage. Don’t jump straight to swapping themes.
Q4: How do I check Shopify theme performance?
Analytics → Reports → search "Performance", look at mobile LCP / CLS / INP. If LCP is over threshold, check app script injection first, then whether images use CDN size parameters. Those two account for most of it.
Q5: Shopify Markets is enabled but nothing changed. What’s wrong?
Most likely “fake internationalization”: currency switched but local payments not configured, local domains not set, only navigation translated. Go through Settings → Markets item by item — don’t just check whether the toggle is green.
Q6: How often should I run this?
- Technical health + conversion health: monthly
- Content/SEO health: quarterly
- Operational health (apps, inventory): quarterly
- Before major sales events (BFCM, etc.): run the full set two weeks ahead
Closing
Health isn’t a one-time physical; it’s a recurring checkup. Suggested cadence:
| Frequency | What to check |
|---|---|
| Monthly | Technical health (performance, app scripts), conversion health (funnel, payments, shipping) |
| Quarterly | Content/SEO health (theme structure, structured data, translations), operational health (app inventory, stock) |
| 2 weeks before major sales | Run all four dimensions end to end |
Remember one thing about order: check the operations layer first, touch the theme layer second. Run the “1 hour, 7 items” today, write down the results, and compare next month. Comparison is what creates judgment — a single data point tells you nothing.