SRPS+

Use SRPS+ to see how well a page holds up once an AI assistant actually renders and reads it.

SRPS+ overview

SRPS+ is a second score from 0 to 100, and it is not “SRPS but higher”. It’s a separate measurement with its own checks, and a page can score well on one and poorly on the other.

It only exists after a deep audit of that page. Deep audits run on demand and use your monthly quota, one page at a time — the standard audit that produces SRPS is unlimited.

Until a page has been deep-audited, its SRPS+ ring shows a dash rather than a number.

What it measures

Where SRPS reads the page’s HTML, SRPS+ looks at the page the way an assistant experiences it: whether the content is actually there once the page renders, how well it can be extracted and quoted, whether an agent can navigate it, and how fast it loads.

That last part is where PERF comes in — the performance measurement is folded into SRPS+ as one ingredient rather than being counted several times over. See PERF.

Good to know On some pages SRPS+ shows a dash even after a deep audit. That’s “doesn’t apply”, not “zero” — a PDF or another binary document has nothing to render, so scoring it would drag your site average down for no reason.

How to read it

The ring uses the same colours as SRPS: green from 80 up, amber from 60 to 79, red below 60. The target is 100.

Read it next to SRPS rather than on its own. A high SRPS with a low SRPS+ usually means the page is findable but hard to actually use — the content arrives late, or it’s there but not extractable. A low SRPS with a high SRPS+ means a page that reads beautifully and that nothing can reach.

Deep results carry a date. If the page has changed since, the audit says so and offers to re-run — the number stays as it was until you do.

What to do when it’s low

1. Fix the base audit’s blockers first. A deep audit is skipped entirely while a page has a failing blocker, so there’s nothing to improve until that’s cleared.
2. Open the page audit and read the Deep page audit section. Each failing check names what’s wrong. See Page audit.
3. Work the resulting items in the Technical queue, which is where the fixes and snippets live. See Technical.
4. Re-run the deep audit for that page. Each re-run uses one unit of your monthly deep-audit quota.

What it does not mean

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

A low SRPS+ doesn’t undo a good SRPS. They answer different questions: SRPS asks whether the page can be reached and understood from its source; SRPS+ asks how it holds up once rendered. A low SRPS+ on a well-scoring page means the page is reachable but heavy or hard to extract from — 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 current. SRPS+ is the result of the last deep audit of that page. If you’ve changed the page since, the number describes the old version until you run the deep audit again.

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.