01
Keep the store scope constant
Compare saved scans for the same Shopify store. StoreCheck's dashboard history is explicitly store-scoped so unrelated catalogs are not mixed into one trend.
Shopify catalog health
Measure Shopify catalog health monthly — and after every high-impact catalog change.
A useful catalog-health routine tracks more than one score. Save the overall trend, seven category scores, severity mix, issue movement, product count, and verification results so a cleanup has measurable before-and-after evidence.
StoreCheck does not currently schedule scans automatically. Run a checkpoint when it is operationally useful; monthly is a baseline cadence, not a requirement.
Monthly scorecard
Six measurements that keep one health score in context.
01
Overall health score
Use the 0–100 StoreCheck score as a compact catalog-level trend signal. Treat movement as descriptive, not a Shopify or Google rating and not proof that one action caused the next score.
02
Seven category scores
Compare Technical, Pricing, Inventory, Images, Content, SEO, Organization separately. A stable overall score can hide a new weakness in one category.
03
Critical + High findings
Track serious findings separately from the total issue count. StoreCheck gives Critical and High findings extra risk weight in the overall score.
04
Total active issues
Watch direction over time, but always interpret issue count alongside product count, severity, and category. A larger catalog can legitimately produce more findings.
05
Products scanned
Record catalog size so score and issue movement have context. Adding or removing products changes the denominator and can expose new rules.
06
Resolved, persistent, and new findings
When you run a verification scan from a saved report, compare finding identity and values instead of relying on score alone.
Cadence
Use monthly as a checkpoint, then scan again when the catalog materially changes.
Baseline monthly scan
For a catalog that changes continuously, one saved scan around the same point each month creates a simple operational checkpoint. Monthly is a practical baseline, not a StoreCheck requirement.
Scan after high-change events
Run an extra scan after bulk imports, migrations, major collection/merchandising projects, SKU restructures, pricing changes, or large catalog cleanup work. Event-driven verification is often more useful than waiting for the calendar.
Verify fixes against the source report
Use a verification scan when you want to know what resolved, persisted, changed value, or appeared after a cleanup. StoreCheck links that scan to its baseline rather than inferring improvement from a score alone.
Seven-category context
A catalog can improve in one area while regressing in another.
StoreCheck calculates a separate normalized score for every audit category. Review all seven before treating an aggregate score change as “healthy.”
TechnicalPricingInventoryImagesContentSEOOrganization
Monthly workflow
Keep trend interpretation reproducible.
02
Record score plus category movement
Start with overall health, then check all seven category scores. Prioritize a category decline even when the aggregate score barely moves.
03
Inspect severity before raw issue volume
Critical and High findings carry more risk weight than Medium and Low. A smaller number of serious issues can matter more than a large list of low-severity cleanup items.
04
Normalize your interpretation with product count
If the catalog grew from 200 to 400 products, raw issue totals are not directly comparable without considering the larger catalog and category scores.
05
Use verification scans for cleanup claims
After fixing issues, compare the new scan with its baseline. Look at resolved, persistent, changed-persistent, and newly introduced findings.
06
Add context outside the score
Note major imports, migrations, supplier changes, theme/content projects, or taxonomy work. StoreCheck shows descriptive scan movement; it does not infer why a score changed.
Free: short checkpoint history
Current Free entitlement: 5 catalog scans per month, 7-day scan history, one connected store, and verification comparisons while the saved baseline is available.
Pro: longitudinal trend window
Current Pro entitlement: unlimited scans, up to 5 connected stores, and 90-day store-health history with trend charts.
Compare current plansVerification beats a score-only success claim.
StoreCheck compares findings by stable rule/product/SKU/field identity and separates resolved, persistent, changed-persistent, and new findings. That lets you see whether an edit actually resolved the original rule instead of assuming a higher aggregate score means every intended fix worked.
Catalog health questions
Measure trends without over-interpreting them.
Does StoreCheck automatically run a monthly Shopify scan?
No. StoreCheck supports manual CSV scans and live read-only scans of connected stores, but it does not currently run an automatic monthly scheduler. Monthly is a recommended maintenance checkpoint you choose to run, with extra scans after major catalog changes.
What does the StoreCheck health score measure?
It is a deterministic prioritization score based on active catalog findings. StoreCheck calculates seven size-normalized category scores and then applies additional catalog-size-aware risk for Critical and High findings. It is not a Shopify rating, search ranking, revenue prediction, or conversion score.
Is a higher health score proof that my cleanup caused an improvement?
No. Score movement is descriptive. Catalog size, newly visible checks, ignored/reviewed findings, and other catalog changes can alter the result. StoreCheck's verification comparison is more useful for a specific cleanup because it tracks resolved, persistent, changed, and new findings against the saved baseline.
How much scan history does StoreCheck retain?
The current Free entitlement retains 7 days of scan history. Pro retains 90 days and exposes longitudinal store-health trend charts. Verification comparisons are available on both tiers while the relevant saved scans remain available.
Should I compare total issues month to month?
Yes, but not in isolation. Also compare products scanned, severity mix, and category scores. A growing catalog can have more total findings even when its normalized health is improving, while a few new Critical or High findings can matter more than many Low findings.
Create the first checkpoint