SERP Audit

Give it a URL and it fetches the page server-side, so it can check the redirect chain, response headers, robots.txt and time to first byte alongside 32 checks on the HTML itself. Ends with a ranked fix list, a pixel-accurate snippet preview, and an alignment map showing whether your title, description, H1 and slug agree.

How to use it

  1. Paste a URL. The page is fetched server-side, which is what makes the delivery checks possible, a browser cannot see another origin’s redirect chain, response headers or time to first byte.
  2. Or paste raw HTML instead, if the page is behind auth or not deployed yet. You lose the delivery group and the audit says so rather than quietly scoring you on 32 checks instead of 38.
  3. Read the ranked fix list. It is ordered by what each failure costs you, not by how easy it is to detect, so a missing title outranks a missing Open Graph tag.
  4. Check the alignment map before you leave. It shows whether your title, description, H1 and URL slug are all describing the same page, disagreement between them is the most common quiet cause of a low click-through rate.

What the numbers mean

38 checks in 6 groups
Meta information, title quality, page structure, structured data, answer readiness and delivery. The delivery group only runs when the page was fetched by URL, because those six checks are impossible from pasted HTML.
Priority by cost of failure
Most auditors sort by severity label. This one weights each failure by what it actually costs: a page that is not indexable scores worse than one missing a canonical, because one of those makes everything else irrelevant.
Blind spots
The audit names what it cannot know (rendered content, ranking position, competitor context) rather than scoring you as though it does. The list shrinks when you fetch by URL rather than pasting HTML.
Answer readiness
Whether the page states its answer in an extractable form near the top. This matters for AI answer surfaces and for featured snippets, and it is the check most on-page tools do not have.

Questions

Why does this one fetch the page server-side when your other tools do not?

Because redirect chains, response headers, robots.txt and time to first byte are invisible to browser JavaScript on a different origin. It is the one place where a server is genuinely required rather than convenient. Nothing about your page is stored. The fetch is made, parsed and discarded.

Can I audit a page that is not live yet?

Yes, paste the HTML instead of a URL. You get 32 of the 38 checks, and the audit tells you which six it skipped rather than scoring you as though they passed.

How is this different from Lighthouse?

Lighthouse measures performance, accessibility and technical best practice. This measures whether the page will earn a click from a search result: what the snippet will look like, whether the fields agree with each other, whether the answer is extractable, and what the structured data actually says.

Why measure the snippet in pixels rather than characters?

Because truncation is a pixel decision. "Illinois" and "lllllllll" are the same character count and nowhere near the same width. Character counting is why tools disagree with what you see in the results page.

Does it check my whole site?

No, one page at a time by design. Site-wide crawlers encourage fixing hundreds of low-cost issues; this is built to tell you the highest-cost issue on the page that actually matters to you.

Guides that use this tool

Other free tools