AI Search Visibility Tool

Check AI search visibility on any page: AI crawler access, JS-hidden text, schema, llms.txt — GPTBot, PerplexityBot, Googlebot.

AI search visibility is the new front page. People ask ChatGPT, Perplexity or Google AI Overviews instead of scrolling ten blue links, and the answer they read is assembled from pages a machine could fetch. This extension records what an agent really receives from the page you are on, then scores it against what your browser rendered. 🔍 What the score actually measures Open the side panel on any URL. The page is recorded twice: once as your browser rendered it, once as a plain request carrying no JavaScript, no cookies, no session. That second document is what a crawler gets, so the AI search visibility score comes out of the gap between the two, split across five channels. 🔓 Access — can an AI crawler reach this page at all, 25 points 👁 Visibility — does body text survive without JavaScript, 25 points 🧱 Structure — does the page break into answerable chunks, 20 points 🧾 Context — does it declare its facts in schema markup, 20 points 🏅 Trust — is the page attributable, dated, sourced, 10 points ⚙️ Every check that runs Eleven page types are detected automatically, from homepage to pricing to documentation, with weights rebalanced for each before the score is normalized. A pricing table and a long guide never fail for the same reasons. 1. robots.txt matched per crawler against this exact path 2. llms.txt discovery, sitemap declarations, canonical tags 3. noindex, noai plus X-Robots-Tag directives at page level 4. Raw versus rendered coverage, measured word for word 5. Headings, shadow DOM, iframe content lost to JavaScript 6. JSON-LD validity, required fields, sameAs entity links 7. Author, publication date, outbound citations 8. Time to first byte, graded apart as a hard gate 🤖 It starts with access Twenty five registered agents are matched against the page, split by what they do: fetch to answer a live question, index for later answers, or gather training data. Blocking a training crawler is a different decision from blocking a live fetcher, so this crawlability check keeps them apart. 📊 AI search visibility across a whole site One URL tells you about one URL. A run over many tells you which findings are template findings, which is the difference between a task list and a work order. Three ways to build the queue: 1️⃣ Sitemap — taken from robots.txt, following a sitemap index down 2️⃣ Links — same origin links from the page you are standing on 3️⃣ List — pasted URLs, competitor domains included, for comparison Large sitemaps are sampled by path shape instead of crawled end to end, so /blog/:id or /products/:id each contribute, newest first. The report ranks findings by points recoverable, marking each as one site wide change, one template fix, or local work. 📄 A report you can hand over - PDF, a paged document with a checklist beside every fix - Markdown, for pasting into a ticket or a pull request - JSON, the complete raw record, ready for tooling of your own - CSV, one row per URL once a bulk run finishes 🔒 Local by design No account, no API key, no backend. Requests reach the site under audit, nowhere else; records stay in your browser; one button in settings erases them. That keeps the work possible on staging, on client sites under NDA, on internal tools. 👥 Who works with it Already tracking brand mentions inside AI answers? This is the layer beneath that. A tracker reports that nobody cites you; this reports why, one page at a time. 🧑‍💻 Developers shipping React, Next.js, Vue or any client rendered stack 📈 Consultants who need JavaScript SEO evidence for a single URL 🏢 Agencies delivering generative engine optimization to clients ✍️ Writers confirming that published text truly reaches an agent The scope stays narrow on purpose: one page, measured honestly, with no quota to spend. Use it before publishing, as a checklist during a redesign, or as proof of structured data when a client asks what changed. Every finding arrives with evidence, a plain reason it costs you readers, plus markup ready to paste. Install it, press Alt+Shift+A, read the score for whatever page is open.