Chrome extension
AEO/GEO Auditor is the toolkit’s scoring engine packaged as a Chrome MV3 extension. Open any page, click the toolbar icon, and it returns a 0 to 100 AI-readiness score with a letter grade, a filterable list of findings, and a PDF export.
- Install: Chrome Web Store
- Product page: advancelabs.dev/tools/aeo-auditor
- Source:
apps/chrome-extension - Publishing runbook:
CHROME_STORE.md
Why it says 44 checks (40 before 0.3.0)
These numbers all describe different things, so it is worth being precise about which one you quote.
The extension runs auditRules, which is defined in
packages/scoring/src/audit.ts as:
export const auditRules = [...technicalSeoRules, ...aeoRules];From extension 0.3.0 (scoring 0.3.x) that is 31 technical-SEO rules + 13 AEO rules = 44, across 9 categories; auditRules.length is 44 in the built bundle. The Chrome Web Store build before this (0.2.0, scoring 0.2.x) ran 29 + 11 = 40. The store serves 0.3.2 as of 2026-11-17, so the store build runs 44. Rules that do not apply to a page are dropped, so one audit can show fewer than 44 results.
The 14 E-E-A-T signals in
packages/scoring/src/eeat-rules.ts are a separate
scorer with a different shape. They are not findings; they are weighted boolean signals grouped
into four pillars, and auditRules does not include them. 44 + 14 = 58 is the engine total. The hosted technical audit runs the 44 checks and the E-E-A-T scan is a
separate tool with its own 14 signals, so 58 is never what a single audit runs.
Verify rather than trust this page:
grep -c "id: '" packages/scoring/src/technical-seo-rules.ts packages/scoring/src/aeo-rules.tsgrep -rhoE "category: '[a-z-]+'" packages/scoring/src/{technical-seo,aeo}-rules.ts | sort -u | wc -lThe 9 categories
| Category | Rules | What it looks at |
|---|---|---|
| Crawlability | 8 | robots.txt, and specifically whether GPTBot, PerplexityBot and ClaudeBot are permitted. Sitemap presence, lastmod trustworthiness, redirect chains, broken pages. |
| Answer engine optimization | 13 | Question-shaped headings, answerable depth, FAQ, article-author, Organization and breadcrumb schema, identity consistency, AI crawlers unblocked, llms.txt, server-rendered content, extractability as paragraphs plus lists and tables, dated content (dateModified). |
| Metadata | 8 | Title and description presence and length, exactly one H1, heading hierarchy, declared language, declared charset. |
| Indexing | 5 | Indexability, declared canonical, canonicals that resolve, titles unique across pages, valid hreflang. |
| Content | 4 | Alt-text coverage, internal linking, thin content, headings used structurally. |
| Social | 2 | OpenGraph, Twitter Card. |
| Mobile | 1 | Mobile viewport. |
| Security | 1 | HTTPS. |
| Structured data | 2 | JSON-LD presence and validity, read recursively into @graph. |
What it sends
Nothing about the page you audit.
Analysis runs against the live DOM in the tab you are already looking at. There is no account,
no server, no analytics, and no telemetry, and no audit is persisted because none is
transmitted. The only network requests the extension makes are to the audited origin’s own
robots.txt, sitemap.xml, and llms.txt, which is what the <all_urls> host permission is
for and the thing to be ready to justify at store review.
The full statement is at advancelabs.dev/privacy/aeo-auditor, which is the URL the Chrome Web Store review reads.
Three fixes worth knowing about
Version 0.2.0 corrected three cases where the engine failed markup that was correct. They are listed here because if you audited a site with v0.1.0, these are the findings to re-check.
alt="" is not missing alt text. Under WCAG an empty alt is the prescribed markup for a
decorative image, so scoring it as absent told authors to introduce an accessibility regression.
Three states are now distinguished rather than two, and decorative images are excluded from both
sides of the coverage ratio.
Typed nodes nested in an @graph are now visible. The validator previously read only
top-level node types, so an author: Person inside an Article, which is the pattern Google
documents, was invisible. Types are collected recursively at any depth.
Checks that do not apply are dropped, not failed. A homepage is the root of a breadcrumb
trail and is not an article, so aeo.breadcrumbs and aeo.article-author-schema no longer fire
on one. Passing them would have been equally wrong: that would claim a check ran when it did not.
Building it
pnpm --filter @advance-labs/chrome-extension packageThat generates the icons, runs vite build, and zips dist/ into
apps/chrome-extension/aeo-extension.zip with manifest.json at the archive root, which is
where Chrome requires it. To run an unpacked build, load dist/ via chrome://extensions with
Developer mode on.
Icons are committed PNGs in public/icons/ (not generated). They carry the AEO Toolkit mark, the
faceted sphere. See brand/README.md under “Mark”.
AEO Toolkit is an open-source instrument by Advance Labs.