Build a website, then check its SEO
Checks the website you built with your agent, its SEO and the rest, with the reason beside every finding. It never touches your code. It works on sites built with Astro, the way the show builds them.
- Runs on
- Website check
- Needs
- Any Astro project, and Claude Code if you want the slash commands. No install, no dependencies, no API key.
- Licence
- MIT
What it does
- Ten domains of checks, seven read your files and three load the running site
- Reports findings and never edits your project, so running it cannot break anything
- Every finding says what it found and why it matters, not just a rule number
- Marks a finding as a fix, a suggestion or a blocker, so you can tell what actually needs doing
- Runs as two slash commands in Claude Code, or as one script with node
- Has its own bug command for when it gets something wrong
- Zero dependencies, so there is nothing to install and nothing to keep updated
This site is audited by it. That is the honest test of a tool like this: I did not write a checker and then go looking for something to point it at, I kept getting the same things wrong and eventually wrote down how to catch them.
What it actually does
It reads your project the way a careful reviewer would. Ten areas, seven of which only need the files on your disk, and three that load the built site and measure it. Then it prints what it found, with the reason attached.
The reason is the part that matters. A checker that says font:bytes and a
number is telling you off. One that says you are shipping 532KB of webfonts in
two files against a 500KB budget has told you the thing and the size of it, and
you can decide whether you care.
What it will not do
It does not edit your project. Nothing is installed into the site being audited, there is no config file to add, and there is no contract between it and your code. It reads, it reports, you decide.
That is deliberate. A tool that fixes things for you has to be trusted with your repository; one that only reads can be run by anybody on anything without a conversation about what it might touch.
Where it came from
The same place everything here comes from. I kept shipping a site with a problem I already knew about, so I described the checks out loud until they existed.
What does it do?
Prompty