SSPS+

Use SSPS+ to read the deep audit’s findings about a rendered page.

SSPS+ overview

SSPS+ is a separate 0–100 score produced by deep checks. It is available after usable deep results are recorded, rather than after every standard audit.

A full-site crawl renders the reachable homepage without consuming the manual allowance. Plans with rendering beyond the homepage also render one representative per page type. You can request rendering and performance measurement of other HTML pages through Site audit or Page audit, using the monthly allowance.

What it measures

SSPS+ scores rendered-page readiness: rendering, extractability and access for agents. Editorial and page-fit checks may appear alongside it, but are not scored. It is a separate score, not a bonus added to SSPS. Page speed is not part of SSPS+: it is the separate PERF score. Site-level SSPS+ values recorded while speed was still included are not comparable with current ones.

How to read it

The interface colours SSPS+ green at 80–100, amber at 60–79 and red below 60. Read it alongside the specific deep findings and the last-deep-audit date. A dash means no available score, not measured zero. PDFs do not receive the HTML deep score.

A standard refetch can clear an old deep result if the extracted page content changed. A deep rerun measures the new version. On the domain card, check how many pages contribute: a homepage result does not establish that every page was deeply audited.

What to do when it’s low

1. Resolve failing standard blockers first. A deep request refreshes standard checks and skips deep analysis if an automatic blocker fails.
2. Open the render and content-analysis blocks in Page audit and read the findings.
3. Follow the relevant Technical recommendations and apply the fixes.
4. Use Measure performance to measure the page again. Manual deep requests use the monthly page allowance.

What it does not mean

It isn’t a better version of SSPS. The two scores share no checks. A page can score 95 here and 0 on SSPS — everything an assistant would enjoy reading, on a page it isn’t allowed to fetch.

A low SSPS+ doesn’t undo a good SSPS. They answer different questions: SSPS asks whether the page can be reached and understood from its source; SSPS+ asks how it holds up once rendered. A low SSPS+ on a well-scoring page means the page is reachable but its rendered content is hard to use or extract — worth fixing, not a contradiction.

A dash isn’t a zero. Pages where a deep audit doesn’t apply — a PDF, a binary document — show no score at all, on purpose. Reading that as a failure would send you fixing something that isn’t broken.

It isn’t a real-time measurement. SSPS+ describes the page at the time of its last deep audit. After a change, the result may remain visible until a standard audit detects a change in the extracted content and removes it. Run a new deep audit to obtain an updated score.

It doesn’t measure whether the page answers the question. Extractability is about whether an assistant can lift an answer out of the page, not whether the answer is there.