One click. On-page SEO, AI-citation readiness and a keyword usage map for the current tab — including pages our web scanners physically cannot read, because this one runs after JavaScript has rendered.
extension/ folder out of the site source. It is five small files — a manifest, a popup, the audit script and three icons. Nothing to build or install.chrome://extensions — or edge://extensions / brave://extensions. They all work; it is the same engine.extension folder itself (the one containing manifest.json). Pin it to your toolbar and you're done.chrome:// and the Web Store are off limits to every extension, so open a normal site.They deliberately see different things. The disagreement is the useful part.
No JavaScript executed — on purpose, because GPTBot, ClaudeBot, PerplexityBot and CCBot don't execute it either. That makes them the right tool for "what can an AI crawler actually see on my page", and the wrong tool for auditing a React or Vue app, which they will report as nearly empty.
It runs in a real browser after rendering, so it audits what a human — and Googlebot, which does render — actually gets. It works on single-page apps, logged-in pages, staging behind basic auth, and localhost, none of which a server-side fetch can reach.
15 checks with a 0–100 score: title by pixel width, meta description, noindex, snippet directives, canonical, H1 count, heading skips, question-form headings, structured data validity, alt coverage, internal links, placeholder and empty links, viewport, lang and Open Graph. Each with the specific fix.
Every repeated term with its count, density and — the part that matters — whether it also appears in your title or a heading. A term used twelve times in the body and never in a heading is the cheapest fix on the page: you already wrote about it, you just never said so where it counts. Stuffing above 4% is flagged.
One button copies a plain-text report of every failing check and its fix — straight into a ticket, an email to a developer, or a client deliverable.
The manifest requests activeTab and scripting and no host permissions at all. That is not a promise in a policy document — it means the extension is incapable of making network requests or reading any tab you have not clicked it on. No analytics, no account, no server.
The extension is the quickest way to spot-check the page you are on. When it flags something, confirm the detail in the Page Audit and check AI readability with the AI Readiness Scanner. For a whole-site review, see our AEO and GEO consulting.