Skip to content

Search PixyScan

Guide contents

User guide5 min

The site overview

The overview is the first screen you see when you open a site. It shows your health score out of 100, what changed since the last scan, and a card for each area of the site. Use it to see if the site got better or worse, and where to look next.

The health score#

A number out of 100. A site with no failing checks scores exactly 100.

PixyScan runs 202 checks on your pages. A check is one test, such as “every page has a title”. A finding is one place where a check failed.

Passing checks cost nothing. So if your score is below 100, every missing point comes from a failed check. There is no hidden deduction, and this screen shows every reason.

app.pixyscan.com/w/…/s/…

A site overview: the health score with its band and change, how many checks broke and cleared since the last scan, the trend across scans, four counts, and a card for each area.
The score, what broke and what cleared, the trend across scans, and a card for each area further down.
The figures across the top of the screen, from left to right.
FieldExampleWhat it does
Score83 / 100The health score from the scan you are looking at.
BandGoodA word for the score's range: Excellent (90 or more), Good (75 to 89), Needs work (50 to 74) or Critical (below 50).
Change−1Points gained or lost since the previous scan of the same branch. On a site's first scan it says “First scan on this branch” instead.
Broke and cleared4 broke · 2 clearedBroke: checks that passed last time and fail now. Cleared: checks that failed last time and pass now. If nothing changed, it says Nothing moved.
Trend83–84 across 4 scansA small chart of recent scores, with the lowest and highest beside it. On a first scan it shows the points lost at each severity instead.
CountsPages · Open issues · AI readiness · FindingsPages crawled, checks failing, the AI readiness score and the total findings. Each one links to its own screen.

How a failed check lowers the score#

Severity sets the base cost. The number of pages affected scales it up.

Severity means how much harm one instance of a problem does. 126 checks are scored, each with one of three severities. The other 24 are suggestions: advice that costs nothing.

The base cost of one failed check, before the number of pages is counted.
FieldWeightWhat it does
Critical10Can stop a page from being found, indexed (added to a search engine) or trusted.
Important5Weakens a page in search or AI answers, but the page still works.
Standard2A small problem. Fix it next time you edit the page.
Suggestion0Advice only. Suggestions show in the list but never cost points. You can ignore them all and still score 100.

A problem on every page costs far more than the same problem on one page. Each category also has its own multiplier, so a crawling or indexing failure costs more than one that only changes how a shared link looks.

A mistake in a shared template usually hits every page that uses it. That is why template fixes are often the quickest way to raise the score.

How it's scored

The score explainer dialog: the severity weights, the reach bands, and every problem with the points it is costing.
Press How it's scored below the score to see every failing check and what it costs you, worst first.

Want the exact formula?

Every weight and multiplier is published, so you can work the number out by hand. Read how the score is worked out

A card for each area#

Six cards: Trust, Content, Performance, Schema, Social and AI readiness. Click one to open its screen.

Each card shows a headline figure and the worst problems behind it. For example, Trust shows missing security headers and when your certificate expires. A card with nothing to report says so instead of showing a zero.

Why is the Performance card empty? Core Web Vitals (Google's page speed scores) need the Hobby tier or above, and a Google API key added in the workspace settings.

Connected to Search Console? A Search traffic card sits below the six cards, with the site's Google clicks, impressions, click-through rate and average position over the last 28 days. Under it, Your recent fixes and weekly charts of your health score and clicks appear once there is data for them. See Measure the impact of your fixes.

Lower on the same screen

The lower half of the site overview: where the work is by section, the split by kind of fix, and the checks grouped under config, template and per-page fixes.
Further down: where the work is, and what kind of fix each problem needs.
The three sections lower on the overview.
FieldSectionWhat it does
Where the work isBy folderThe three sections of your site, such as /blog, with the most findings per page.
The shape of the workA barHow your findings split between the three kinds of fix below.
Next actionsThree groupsFailing checks grouped by kind of fix. Config: one server or settings change fixes every page. Template: one change to a shared layout. Per-page: done page by page, such as titles or alt text.

Compare a site with itself, not with other sites

The score depends on each site's own pages. 83 on a 79-page marketing site and 83 on a 12,000-page shop do not mean the same thing. Compare one site over time instead, using the trend and Scan history.

Does something here not match what you see in the app? Tell us