Keywords, minus the boilerplate
Counts are scoped to the page's main content, so your nav and footer links stop outranking the words that matter. Single terms plus recurring two and three word phrases.
Free Chrome extension
Headings, indexability, meta, alt text, keywords and colour. The whole audit, without opening DevTools.
Counts are scoped to the page's main content, so your nav and footer links stop outranking the words that matter. Single terms plus recurring two and three word phrases.
Missing H1, duplicate H1s and every skipped level, tagged on the row that caused it.
skipped H2 to H4
Title and description measured against SERP truncation, 30 to 60 and 70 to 160 characters, with a pass or fail at a glance.
Colours resolved to hex and ranked by how often they are actually used, so the brand colour sits top instead of a stray border.
Total, unique, internal and external counts, then the full list with anchors, mailto and tel classified separately.
Thumbnails of every image with no alt attribute. Click one and the page scrolls to it. A deliberate empty alt on a decorative image is counted separately, not flagged as a fault.
Locates and fetches the XML sitemap, expands a sitemap index into its children, and checks robots.txt and llms.txt for the domain.
Most heading tools stop at the outline. Teardown opens with the answer to the question that actually matters: can this page rank at all? It reads the robots meta tag, the canonical, hreflang and the page language, then says plainly whether the page is indexable, blocked, or quietly canonicalised to somewhere else.
Open the popup on any page and hit the button. A content script reads the rendered DOM, so JavaScript-built pages and logged-in staging sites work the same as anything else.
Five tabs fill at once. Click any heading to scroll the live page to it, click a broken image to find it, copy a colour by tapping the swatch.
Markdown outline, plain list, a TXT report, or a CSV of the whole project history with indexability and health score per row.
Make a project per client or campaign and every scan lands in it, newest first, fifty deep. Rename and delete them from Settings. If you would rather scans did not stop at the popup, point the webhook at your own endpoint and each one gets posted there as JSON, straight into Make, n8n or your own API.
Webhook URL
https://hooks.yoursite.com/scan-received
Projects
Yes. No tiers, no trial, no upsell. It was built as a working tool for client audits and it stays free.
Nowhere. Scans live in Chrome's local storage on your machine. There is no account and no server behind this. The one exception is the webhook in Settings: if you enter a URL, scans get posted to that endpoint, and the field is empty unless you fill it in.
Yes. It reads the rendered page in your active tab, so if you are logged in and can see it, it can scan it. That includes JavaScript-rendered content, because it reads the DOM after render rather than the raw HTML.
A TXT report of the current scan, a CSV of a project's whole history, the outline as plain text or Markdown, the palette as a hex list, and the keyword lists. Scraped images download as a batch, foldered by hostname.
Chrome and any Chromium browser that takes Manifest V3 extensions, so Edge, Brave, Arc and Opera. Chrome's own internal pages and the Web Store are off limits to every extension, so scanning will not work there.
One click, five tabs, no account. Nothing leaves your machine.
Add to Chrome