An SEO audit that tells you what to fix first
Free, runs in your browser, and it never gives you a score out of 100.
Every SEO extension I tried handed me a wall of numbers and left me to work out which ones mattered. Title length, word count, a health score, forty green ticks and three ambers. None of that tells you what to change on Tuesday morning.
So this one is a ranked list of actual problems, worst first, and every single item says the same four things: how bad it is, what is wrong, why it matters, and what to do about it. No score, because a number between 0 and 100 is a feeling, not an instruction.
The ranking is the whole product. A missing H1 and a slightly long title are not the same size of problem, and a tool that lists them next to each other in alphabetical order has made your job harder rather than easier.
How to use it
- Open the page you want to check.
- Click the icon. The audit runs on the page as it is right now, including anything JavaScript rendered.
- Read the list top down. It is already in the order I would fix it in.
- Open the side panel if you want the full report next to the page rather than in a popup.
- To do the whole site, paste your sitemap URL and let it crawl. That asks for permission to fetch your other pages, which is the point at which it needs it.
The whole-site audit is where it gets useful
A single page audit can only ever tell you about one page. Point this at your sitemap and it audits every page, then collapses the results into what is actually one job.
Forty pages missing a meta description is not forty problems, it is one template fix, and the report says so instead of making you scroll. That collapsing is the difference between a report you act on and a CSV you close.
It also catches two things a single page audit physically cannot see: duplicate titles and duplicate descriptions across your site. Those only exist in the comparison between pages, so no amount of checking one page will find them.
Handing the result to an AI
One click copies the whole audit as Markdown, laid out to paste straight into Claude or ChatGPT. I built that because it is what I was doing by hand, badly, with screenshots.
It works well for the writing tasks. Give it the list of pages missing descriptions and it will draft them. It is less good at deciding priority, which is the part the extension already did.
What it can access, and why
| Permission | Why it needs it |
|---|---|
| Reads the current tab | Only when you click the icon. This is how it sees your titles, headings, images and links. |
| Local storage | Saves your audit history so you can compare a page against last week. |
| Side panel | Shows the full report beside the page instead of in a popup that closes when you click away. |
| Other pages on your site (optional) | Requested only if you run a whole-site audit, because that has to fetch your sitemap and your other pages. |
Full detail in the privacy policy.
FAQ
Does it check Core Web Vitals?
Yes, measured on your own machine as the page loads. Worth knowing what that means: you are seeing the numbers for your connection and your hardware, not a lab score. A page that feels fine on your fibre line can still be slow for someone on mobile data, so treat a bad result as reliable and a good result as encouraging rather than conclusive.
Why no overall score?
Because I could not make one honest. Any single number has to weigh a missing H1 against a slow image against a thin description, and those weights are guesses dressed up as arithmetic. Worse, a score invites you to optimise the score. The ranked list is the same information without the false precision.
Can it audit a page behind a login?
Yes for the single page audit, since it reads whatever is on screen in your own browser, already logged in. The whole-site crawl is a different story, because those fetches do not carry your session, so pages behind a login will come back looking like the login page.
How big a site can the crawl handle?
It runs in a browser tab, so a few hundred pages is comfortable and a few thousand will be slow. If you have a genuinely large site this is the wrong shape of tool and a desktop crawler is the right one.
Does it change anything on my site?
No. It reads. There is no write path anywhere in it, and it has no way to authenticate to your CMS even if there were.