Free · MIT · Chrome extension

AI-SEO Page Auditor

A Chrome extension that audits the page you are currently browsing for AI-search visibility. 43 checks across crawlability, structured data, content, and technical health. Grade in the toolbar badge. Fix recipes in the popup. No URL to copy and paste.

What it does

The AI-SEO Page Auditor extension reads the current tab URL and runs it through the same 43-check audit engine that powers the AI SEO Checker web tool. The extension calls a server-side proxy at automatelab.tech to fetch the page HTML, robots.txt, XML sitemap, and llms.txt, then scores six categories on the client side.

Results appear in the popup within a few seconds: an overall letter grade (A through F), per-category scores, and a check-by-check breakdown with a plain-English fix for each failing or warn-level check. The toolbar badge shows the current page's grade so you can see AI-SEO visibility without opening the popup. Results are cached per URL in chrome.storage.local so revisiting a page shows the last audit instantly, and the full report links out to the web tool.

Audit categories

crawlability
Whether the six major AI crawlers (GPTBot, OAI-SearchBot, ChatGPT-User, ClaudeBot, PerplexityBot, Google-Extended) are allowed in robots.txt. Also checks whether robots.txt is reachable, the self-canonical URL is consistent, the XML sitemap is present, and no noindex or nofollow directives block the page.
structured-data
JSON-LD blocks present and correctly typed. Required schema.org properties populated for the detected type (Article, FAQPage, HowTo, Product, Organization). OpenGraph title, description, image, and url tags present. Twitter card present. Article author includes a sameAs link to a public profile. Organization JSON-LD includes a logo.
on-page-content
Title length between 50 and 60 characters. Meta description present and 140 to 160 characters. Exactly one H1, question-shaped where appropriate. H2 and H3 headings use question phrasing. Title entity overlaps with H1. Heading hierarchy has no skipped levels. Word count above 300, answer in the opening paragraph. Internal and outbound links present. Image alt-text coverage above 80%. Anchor text is descriptive.
ai-readability
llms.txt present and parseable. First paragraph answers the implied query in under 60 words. Lists or tables present. Named entities visible. Author and publication date visible in the page body. Content is server-rendered, not JS-only. dateModified is present and recent. Outbound citations point at authoritative domains.
agentic-browsing
llms.txt entry point present for agent crawlers. WebMCP integration declared via script, link, or meta tag. Accessibility tree intact: html lang, main and nav landmarks, image alt coverage, labeled form controls. Images, iframes, and videos declare explicit width and height to prevent layout shift. Mirrors the four Lighthouse Agentic Browsing signals added in May 2026.
technical-health
HTTPS with a valid certificate. Mobile viewport meta present. HTML payload under 1 MB. Hero image has explicit width and height. HSTS header set. Security headers (X-Content-Type-Options, Referrer-Policy) present. No mixed content.

Install from the Chrome Web Store

  1. Open the Chrome Web Store listing and click Add to Chrome Google prompts you to confirm three permissions: activeTab, storage, and access to automatelab.tech. Approve them.
  2. Navigate to any live https:// page Localhost and http:// pages are not supported because the audit proxy fetches from the internet.
  3. Click the AI-SEO Page Auditor icon in the Chrome toolbar The popup opens, triggers an audit, and sets the badge to your page's grade within a few seconds. Expand any category to see per-check findings and fix recipes.

Prefer installing unpacked? The full source is on GitHub. Load the chrome-extensions/ai-seo-page-auditor/ folder via chrome://extensions in developer mode.

Permissions

Permission Why
activeTab Read the URL of the tab you clicked the extension icon on. The extension cannot read any other tab.
storage Cache audit results in chrome.storage.local so revisiting a page shows the last audit instantly without a new network request.
https://automatelab.tech/* Call the SSRF-hardened audit proxy (/api/audit-fetch) that fetches page HTML and supporting files on the server side. The only outbound host the extension contacts.

Example workflow

You publish a new blog post and want to know how it scores before the first crawl round picks it up.

Open the post in Chrome. Click the AI-SEO Page Auditor icon. Badge shows C. Popup: structured data and AI readability are amber, crawlability is green. Expand structured data: author sameAs is missing and the FAQPage block has no mainEntity array. Add both, redeploy. Click the extension icon again, hit Audit. Badge flips to B. Crawlability stays green. AI readability is now the only amber category.

The web tool at automatelab.tech/tools/ai-seo-checker/ generates a shareable URL for the same result, useful for passing an audit to a colleague or tracking changes over time.

FAQ

How is this different from the web tool?
The check engine is identical. The difference is where you use it: the extension runs from the browser toolbar on whatever page you are browsing, shows the grade in the badge, and caches results per URL. The web tool is accessible without Chrome, generates a shareable result URL, and is easier to batch-audit multiple URLs. Use the extension for fast per-page checks during development and the web tool when you need a link to the result.
Does the extension send my URL to any third party?
No. The only outbound request is to https://automatelab.tech/api/audit-fetch. That endpoint fetches the page HTML, robots.txt, sitemap, and llms.txt server-side through an SSRF-hardened proxy. No URL is stored or forwarded to any third party. No analytics in the extension itself.
Can I run the same checks from Claude or Cursor instead?
Yes. The ai-seo-mcp package ships the same audit as the audit_page tool, plus rewrite suggestions, batch sitemap audit, and schema-level checks. Useful for CI pipelines or when you want to pipe audit results into another agent step.
Does it work on localhost or http pages?
No. The audit proxy fetches your page from the public internet, so the page must have a publicly reachable HTTPS URL. Localhost and http:// pages return a proxy error.
What does it cost?
The extension is free and MIT-licensed. The source is on GitHub.

Links

Need AI-SEO coverage across your whole site?

We audit the top 50 pages by traffic, identify the structural patterns dragging your score, and ship the fixes inside two weeks. Schema, llms.txt, content rewrites. Fixed-scope.

Get in touch