---
title: The Catalog Health Dashboard and Score
description: "The catalog health dashboard is the landing screen of [Catalog Health Scanner for WooCommerce Pro](https://wpfactory.com/item/catalog-health-scanner-for-woocommerce/): one score, a trend, a card per category, and two short lists that tell you what to do next. Open it at **WPFactory > Catalog…"
url: "https://wpfactory.com/docs/catalog-health-dashboard/"
updated: "2026-10-05"
category: How to
tags:
  - Catalog Audit
---

# The Catalog Health Dashboard and Score

The catalog health dashboard is the landing screen of [Catalog Health Scanner for WooCommerce Pro](https://wpfactory.com/item/catalog-health-scanner-for-woocommerce/): one score, a trend, a card per category, and two short lists that tell you what to do next. Open it at **WPFactory > Catalog Health**.

Everything on it describes the last completed scan. Before that scan exists, the dashboard shows a single empty state with a **Scan my catalog now** button and nothing else.

![Catalog Health Scanner showing 84% overall health score and detailed category analysis.](https://wpfactory.com/wp-content/uploads/Catalog-Health-Scanner-Dashboard.png)

## Scan controls

The top strip carries the **Scan profile** dropdown and the **Run Scan** button, plus shortcuts to **Schedule** and to the **PDF report** for the last scan. To the right it reads *Last scan: 2 hours ago, 934 products*, so the age of what you are looking at is never in doubt. While a scan is running, the dropdown is disabled and the buttons become Pause and Cancel. See [run your first scan](https://wpfactory.com/docs/run-your-first-scan/).

## The overall score and its band

The score panel shows a circular gauge with a percentage from 0 to 100, coloured by band, and next to it the number of open issues.

| Band | Score | Band ID | Reading |
| --- | --- | --- | --- |
| Healthy | 90 to 100 | `healthy` | The checks that apply to your store are passing on almost everything. |
| Minor issues | 75 to 89 | `minor` | Nothing urgent, but a visible tail of data problems. |
| Needs attention | 50 to 74 | `attention` | Whole classes of product data are wrong or missing. |
| Critical | Below 50 | `critical` | Most of the catalog is failing the checks that apply to it. |

One rule surprises people, so it is worth stating here: **a single open Critical issue caps the total at 89**, no matter how clean everything else is. A store with an unpurchasable product is not in a healthy state regardless of the arithmetic. The full method, including how excluded checks leave both sides of the fraction, is in [how the health score is calculated](https://wpfactory.com/docs/catalog-health-score/).

## The trend line

To the right of the gauge, a small line chart plots the score of the last 8 completed scans, oldest to newest, with the first and last values printed underneath. It appears only once you have more than one completed scan.

The trend is meant to be comparable over time, which is why changing your applicability settings recalculates the score of past scans from their stored counters rather than leaving a step in the line. Recalculated scans are marked in [scan history](https://wpfactory.com/docs/scan-history-compare/).

## Ignored issues are declared, not hidden

If any issue is ignored, the score panel says so directly under the open-issue count: *N ignored, not counted*, linking to the ignore list in Settings.

This line exists on purpose. An ignored issue is still a broken product; ignoring only removes it from the score. Without the declaration, a catalog where everything had been ignored would read as a flawless 100%, which is exactly the impression a client-facing report must never give. The same declaration appears on the PDF report cover. See [ignore false positives](https://wpfactory.com/docs/ignore-false-positives/).

## The skipped-products declaration

If the last scan did not cover the whole catalog, a warning strip appears above the category grid: *N products were not checked in this scan*, followed by the reason, and a **Change what gets scanned** link into **Settings > Scan scope**.

The reason is specific to your configuration: newer than the grace period, sitting in an excluded product category, or both. A score computed from part of a catalog is not a score for that catalog, and the products a scan skips tend to be the ones just imported, which are the most likely to be broken. Saying nothing would let "we ignored your import" read as "your import is healthy".

## The critical banner

When open Critical issues exist, a red banner sits above the category grid: *N critical issues are costing you sales right now*, with a chip per category showing how many are in each. Every chip deep-links to that category tab already filtered to Critical severity, and the main **Review & fix** button targets whichever category holds the most. Criticals are rarely confined to one category, which is why the banner shows the breakdown instead of always sending you to Purchasability.

## The category summary grid

Under the heading **Category scores**, a caption reads *7 of 10 categories apply to this store*, followed by one card per category. Each applicable card shows:

- the category name and its band chip;
- points earned out of points possible, for example *18.5 / 22*;
- a progress bar in the band colour;
- the number of open issues in that category.

Clicking a card opens that category tab. A category that the last scan's profile did not cover shows **Not scanned yet** instead of a score, while still counting its open issues.

### Greyed-out cards, with the reason

A category whose every check belongs to a non-applicable group is rendered as a flat grey card marked **Not applicable**, with no score, no bar, and no link. Underneath it prints the reason auto-detect or your own setting gave, for example "Your store uses flat rate, free shipping, or local pickup with no weight-based rules" or "No downloadable products found".

Those categories are not failing and are not passing. Their checks never ran and never entered the score on either side. Printing the reason on the card is what keeps a greyed card from reading as a defect. To change one, open **Settings > Applicability**, or read [applicability: why checks are skipped](https://wpfactory.com/docs/check-applicability/).

## Quick wins

The left panel lists up to 5 checks that have open issues *and* an automatic fixer: the changes that are unambiguous, such as clearing an expired sale price or syncing a stock status that contradicts its quantity. Each row names the check and how many products it affects, with a **Fix all** button for that one check.

The panel header carries a second **Fix all** that covers every auto-fixable group at once. It does not fire immediately. It opens a preview first: a summary line, the list of checks involved, and a table of the individual products with their exact current and resulting values. Only when you confirm are the changes written, as a single logged batch you can undo. The preview footer states the undo window, which is 30 days by default.

When there is nothing auto-fixable, the panel says *Nothing auto-fixable right now. Good.* That is a real result, not an empty screen: it means the remaining work needs a human decision. See [fix issues safely](https://wpfactory.com/docs/fix-catalog-issues/).

## Top issues

The right panel lists the 5 largest open issue groups, ranked by affected products multiplied by severity weight, so a handful of Critical findings can outrank a hundred Low ones. Each row shows the check label, its category, its severity badge, the product count, and a **View** link that opens the category tab with that group already expanded.

When there is nothing open at all, it reads *No open issues. Your catalog is clean.*

## Finding what changed since last time

The dashboard reports the current state, not the delta. To see only what is new, use either of these:

- **The New since last scan filter** in any category tab, which narrows every group to issues first seen in the most recent completed scan. See [triage issues in the category tabs](https://wpfactory.com/docs/triage-catalog-issues/).
- **The comparison view in History**, which sets any two scans side by side and splits the difference into fixed, regressed and new. See [scan history and comparison](https://wpfactory.com/docs/scan-history-compare/).

## Troubleshooting

- **The score is stuck at 89.** That is the critical cap. Clear the last open Critical issue and the next scan scores normally.
- **The score jumped without a scan.** Changing applicability recalculates historic scores so the trend stays comparable. Affected scans are marked in History.
- **A category card says Not scanned yet.** The last scan's profile did not include any of its checks. Run a Full Scan, or add those checks to your profile.
- **The category grid and the score disagree with your instinct.** Check the ignored-issues line and the skipped-products strip first. Both remove products or findings from the score by design.
- **No trend line.** It needs at least two completed scans.

## Where to go next

- [How the health score is calculated](https://wpfactory.com/docs/catalog-health-score/)
- [Triage issues in the category tabs](https://wpfactory.com/docs/triage-catalog-issues/)
- [Fix issues safely: preview, undo, log](https://wpfactory.com/docs/fix-catalog-issues/)
- [CSV export and PDF audit report](https://wpfactory.com/docs/catalog-health-reports/)

Need a hand? Our team answers every ticket on the [Catalog Health Scanner support forum](https://wpfactory.com/support/).

Related articles

- [What Catalog Health Scanner Does (and What It Does Not)](https://wpfactory.com/docs/catalog-health-scanner-overview/)
- [Install Catalog Health Scanner and Run the Setup Wizard](https://wpfactory.com/docs/install-catalog-health-scanner/)
- [Check Library: All 70 Catalog Health Checks](https://wpfactory.com/docs/catalog-health-checks-reference/)
- [Catalog Health Scanner Settings Reference](https://wpfactory.com/docs/catalog-health-settings/)
- [Catalog Health Scanner FAQ and Troubleshooting](https://wpfactory.com/docs/catalog-health-faq/)