Page audit

Open a page audit to see every check on one page, its scores, its links, and what to fix.

Page audit overview

You get here by clicking a page in the site schema on the Site page. Back to site schema returns you to where you were in the tree.

The top of the screen carries the page’s scores: SRPS always, then SRPS+ and PERF once the page has had a deep audit. Next to them is the verdict — how many issues were found, split into high and medium.

Below that the page is in sections: the standard checks, the deep checks, the Core Web Vitals card, the links on the page, the links pointing to it, and the technical recommendations.

How to read a check

Every check shows a state and a short note explaining the finding — not only “missing” but which value was found and what was expected.

The five states are OK, Needs work, Failing, No data and Manual check. No data means the check couldn’t be evaluated; it isn’t counted against your score.

A check marked Blocker is a gate rather than a point. While one is failing, the page can’t be seen by assistants at all, its SRPS is 0, and its deep audit is skipped.

The standard checks are grouped as Access & indexation, Meta & structure, Technical & language, Discoverability & linking, and Social card & media. The deep checks are grouped as Rendering & agents, Extractability, E-E-A-T & freshness, Schema & page fit and Core Web Vitals.

Good to know Standard and deep checks can disagree about the same page, and that’s not a bug — the standard checks read your raw HTML, the deep ones read the page after it renders. When the two differ, the gap itself is the finding: something arrives only after JavaScript runs.

How to complete a manual check

Some checks can’t be verified automatically — whether your page is indexed in Google or Bing, or whether your social image actually looks right.

These show as Manual check with a hint to verify it yourself. Check it, then click Mark done. If you change your mind, Mark as not done puts it back.

How to run or re-run the audit for this page

Two buttons sit at the top of the page audit: Run audit re-runs the standard checks, and Run deep audit runs the deep pass.

If the page has never had a deep audit, the deep sections say so. If it has one but the data is older than the last change, they show the date and offer to re-run.

Each deep run uses one unit of your monthly deep-audit quota. When the quota is used up, the app says so and points at your plan.

How to read the Core Web Vitals card

The Mobile (lab) card breaks performance into its parts: loading, interactivity and visual stability, each with the measured value, the threshold it’s judged against, and a status of Good, Needs work or Poor. Further metrics sit under Other lab metrics.

The summary of this card is the PERF score in the page header. See PERF.

How to check the links on a page

Links on this page lists every clickable link with its live HTTP status, grouped by where it sits in the page — in the body, navigation, contact, footer, or the language switcher. The summary line counts how many are OK, redirects, broken, or gave no response.

Filters narrow it to errors, no-response links, or external links only.

Where a link couldn’t be verified automatically, you can record the answer yourself: mark it as working or as genuinely broken.

Internal links to this page shows the inbound side — which of your own pages link here. A page with none is effectively invisible to a crawler that arrives by following links.

How to act on what you find

The Technical recommendations section at the bottom lists what to fix, with the steps and, where the fix is code, a snippet you can copy. Each one says whether it applies to this page, to a number of pages, or domain-wide.

Copy brief for any AI agent packages the finding, the fix and the acceptance criteria into one block you can hand to a developer or an assistant.

The same items appear in your Technical queue — see Technical.