SRPS

Use SRPS to see how ready a page is for AI assistants to find, read and cite it.

SRPS overview

SRPS — the Suparanku Page Score — is a score from 0 to 100. Every page the audit reaches gets its own SRPS, and your domain gets an overall one that combines the pages with the checks that apply to the whole site.

You’ll see it as a ring on the Site page and at the top of each page audit. The ? next to the ring repeats the short definition.

SRPS comes from the standard audit, which runs on every audit and reads your page’s HTML directly. That means it’s always there — you don’t need to run a deep audit to get it.

What it measures

SRPS is about the things an AI assistant needs before it can use your page at all: whether the page responds, whether AI crawlers are allowed in, whether it can be indexed, whether it’s linked and discoverable, whether the page states clearly what it is, and whether the meta and social card are in place.

Each of those is a separate check, and the checks don’t all carry the same weight — a missing title matters more than a missing image dimension. A check that can’t be evaluated (“no data”) is left out rather than counted against you.

Good to know A few checks are gates rather than points. If the page returns an error, blocks AI crawlers, or is set to noindex, SRPS is 0 — not “a bit lower”. Nothing else can matter while the page can’t be seen at all, so a page with everything else green can still show 0. Those checks carry a Blocker badge in the audit. Fix them first and the rest of the score appears.

How to read it

The ring is colour-coded: green from 80 up, amber from 60 to 79, red below 60. The same colours apply to the page score and the domain score.

Treat those as a temperature reading, not a finish line. The target is 100 — every point below it is a check that didn’t pass, and each one is listed in the audit with what to do about it.

The domain score isn’t the average of your pages. It combines the page scores with the checks that only make sense for a whole site — robots.txt, the sitemap, whether the apex and www versions agree — so fixing one page moves it a little, and fixing a site-wide setting moves it more.

What to do when it’s low

Work in this order — the first item can invalidate everything below it.

1. Clear any Blocker first. Open the page audit and look for the badge. See Page audit.
2. Work the Technical queue. Every failing check that has a fix becomes a technical recommendation, with the steps and, where relevant, a ready-to-paste snippet. See Technical.
3. Re-run the audit on the page you fixed. You don’t have to re-audit the whole site — see Site audit.

Manual checks — the ones marked Manual check with a Mark done button — are yours to verify. Marking one done records that you’ve checked it; it doesn’t currently change SRPS.

What it does not mean

SRPS is a readiness score, and readiness is a narrow thing. It’s worth being precise about what it leaves out.

It doesn’t say whether AI mentions you. That’s a different measurement entirely — it comes from your scans, where the engines are asked your prompts and the answers are recorded. A page can score 100 and never be cited by anyone.

It doesn’t judge your content. The audit checks whether a page can be found, read and quoted. Whether what it says is any good, accurate, or persuasive is not something it looks at.

It isn’t a ranking. There’s no position in it, no comparison against anyone else. The audit only ever crawls your own domain, so SRPS can’t tell you that a competitor’s page scores better.

It isn’t a Google score. Some of the same signals matter to search engines, but SRPS is not a search ranking, and a change in it doesn’t predict one.

A perfect score is a starting line. It means nothing is in the way any more. What an assistant does next depends on whether the page is worth citing at all — which is what your prompts, competitors and content work are for.