Sign in Start free

← Docs  /  SEO Health & AI Visibility

SEO Health

Updated 2026-09-11

The crawler-based on-page SEO score: what it checks, how to read the four bands, scheduling, and the white-label PDF.

Browse documentation

What it does

SEO Health crawls a site the way a search engine does — following its own sitemap and internal links, up to a page cap per run — and scores what it finds. Each page is checked for the on-page fundamentals: titles and meta descriptions (present, unique, the right length), a single H1 with a sane heading order, image alt text, canonical tags, robots directives, broken internal links, and structured data. Findings roll up into one 0–100 score for the site.

The score, explained

The score starts at 100 and loses points for each open finding, weighted by how much it matters — a missing title costs more than a missing alt tag. The score lands in one of four bands:

BandScore
Excellent90–100
Good70–89
Needs attention40–69
Critical0–39

A run that can't complete a crawl (the site is unreachable, or transport fails outright) reports the affected checks as skipped rather than passing them by default — a broken crawl never quietly produces a flattering score.

How to run and schedule it

  1. Open a site's SEO Health tab to see its current score, the checklist by category, and every open finding with what to fix.
  2. Click Rescan for an on-demand run at any time.
  3. Scans also run on a schedule: weekly on Free, daily from Studio up. Search Console sync (from Studio up) adds real query and impression data alongside the crawl findings.
  4. Generate a branded, white-label PDF of the report from the SEO Health tab — your logo and colors, no WPClientHub mention required, for sending straight to a client.

Limits & defaults

SettingDefault
Scan frequencyWeekly on Free · daily from Studio up (plus on-demand rescan anytime)
Search Console syncStudio and up
White-label PDFStudio and up
Pages crawled per runCapped per run, following the site's own sitemap and internal links

Troubleshooting

The score dropped after a run and nothing changed on the site
Check the checklist for newly skipped checks — a crawl that timed out or was partially blocked reports the affected checks as skipped, not passing, which can move the score even when the site itself is unchanged. Rescan once the site is reachable.
Search Console data isn't showing
Search Console sync requires Studio or above and a connected Google account (Settings → Integrations). It runs on its own daily schedule, separate from the crawl.