Page audit

Every page you open, audited

140 rules run against the rendered DOM as the page loads. Production, staging, or localhost: if your browser can open it, the engine can score it.

From page loadto verdict

The audit runs in the tab you already have open, on the page as it renders, with nothing to set up first.

01

Browse

Open the page like you always do. The engine reads the render after JavaScript settles, not the raw HTML.

02

Scored on load

140 rules run in the tab: titles, canonicals, hreflang, schema, speed. The score is ready before you have scrolled.

03

Fix it, then check

A failure lands in the panel the moment it appears. Ask the AI panel why it failed, ship the fix, then ask it to check the page again.

Page history

What changed since your last visit

Every visit is kept on your machine, so the next one shows the difference: a rewritten title, a repointed canonical, a robots.txt that started blocking a folder.

Page text changes show word by word under their heading, and a phone visit is only ever compared with another phone visit. The History page lists every captured page that changed. Included on Pro and Team.

Kept on every visit

Title, meta, and headings

Canonical and indexability

Redirects and status codes

Structured data and robots.txt

The audit,up close

All of it reads the same render: the overview with its alerts, the rules on a local build, and the JavaScript, schema, and speed panels.

140 rules, one verdict. Titles, canonicals, hreflang, schema, OG tags, speed. The overview keeps the running verdict for the tab, and every failure sits underneath it.

Localhost included. Point it at staging or a local build. The same rules run before the deploy as after, in the same tab.

The rendered DOM. Checks run after JavaScript, on the page as it actually renders. The panel diffs what the server sent against what the browser built.

Schema, parsed. Every JSON-LD block validated against what the rich result needs, not the bare spec.

Speed from the session. Web Vitals from the tab you’re in, on your connection, not a lab average from somewhere else.

You opened the page.The audit already ran.