GEO Audit: Test Any Page's AI Visibility FreeNew
Enter one URL and get a complete AI-visibility report in about ten seconds, free and with no signup. It checks whether AI crawlers can reach the page, whether the content exists without JavaScript, whether there is anything a model could actually cite, whether the fragments survive retrieval, and whether the identity is machine-readable. Findings are ordered worst-first, and each one links to the free tool that fixes it.
What is the GEO audit?
The GigAI GEO Audit takes one URL and reports whether AI systems can find, read and cite that page. It checks 15 AI crawler tokens against robots.txt with real RFC 9309 matching, detects Cloudflare's default AI blocking, counts the words visible without JavaScript, scores citability using the KDD 2024 GEO study's factors, and slices the page into retrieval chunks. Every finding links to the free tool that fixes it.
The GigAI GEO Audit answers the question the 200-dashboard AI-visibility industry charges $99+/month to monitor: is there anything technically stopping AI systems from finding, reading and citing this page? It makes three stateless fetches (your page, your robots.txt, your llms.txt), then runs every analysis in your browser. Crawler access is computed with real RFC 9309 robots.txt matching for 14 AI crawler tokens. GPTBot, OAI-SearchBot, ChatGPT-User, ClaudeBot, Claude-SearchBot, Claude-User, PerplexityBot, Perplexity-User, Googlebot, Google-Extended, Bingbot, Applebot-Extended, meta-externalagent, Bytespider and CCBot, and quotes the exact rule line behind each verdict, plus a Cloudflare check, because Cloudflare now blocks AI crawlers at the firewall by default on new zones regardless of robots.txt. Rendering analysis counts the words a JavaScript-free crawler actually receives and spots client-rendering framework markers. Citability is scored with the factors the published GEO study (Aggarwal et al., KDD 2024) measured as increasing AI citation, with every formula shown. The chunk section slices the page the way a RAG pipeline does and reports how many fragments fail standalone. The result is not a score to subscribe to: it's a repair list, and every line of it links to a free GigAI tool that does the repair.
- Difficulty:
- Easy
- Typical time:
- ~15s
- Processing:
- Secure cloud processing
Last updated
How to use the GEO audit
- 1
Enter any page URL
Your homepage, a key article, a product page: the audit works per-page, because that's how retrieval works. Audit the pages you want cited.
- 2
Watch the three fetches
The page, robots.txt and llms.txt are fetched statelessly through our proxy (fetched, analyzed, discarded). Everything else runs in your browser.
- 3
Read the report worst-first
Six sections, each scored 0–100 and sorted by severity: crawler access, rendering, citability, chunks, answer snippets, machine-readable identity.
- 4
Open the linked tool for each failing finding
Each finding names its fix and links the component tool: generate a correct AI robots policy, see the exact failing chunks, get per-section rewrite targets.
- 5
Re-run after you ship
The audit is stateless and unlimited. Fix, redeploy, re-run: the score moves when the evidence moves.
What GigAI GEO Audit includes
14 AI crawler verdicts with the deciding line quoted
Real RFC 9309 robots.txt matching (group specificity, wildcards, longest-match, Allow beating Disallow on ties) for every OpenAI, Anthropic, Perplexity, Google, Microsoft, Apple, Meta, ByteDance and Common Crawl token.
Catches the Cloudflare block robots.txt can't show
Cloudflare now blocks AI crawlers by default on new zones and can inject managed robots.txt rules above yours. The audit reads the response headers and the file itself for both signals and tells you the exact dashboard setting to check.
What a no-JavaScript crawler actually sees
Counts the words in the raw HTML, detects client-rendering framework markers (Next.js flight data, empty SPA shells, Nuxt payloads) and estimates how much content is trapped in serialized JS.
Citability scored with published methodology
Fact density, source citations and quotability (the factors the KDD 2024 GEO study measured) plus answer-first openings, question headings and self-containment. Every sub-score shows its formula.
Retrieval chunk survival
The page is sliced the way a RAG system slices it (heading sections, then ~300-token windows). You get the count of fragments that would be incomprehensible retrieved alone.
Every finding links to its fix
This is a repair list, not a subscription hook. Each failing check links to the free GigAI tool that digs deeper or generates the fix: robots policy, schema, snippets, chunks.
Why use our GEO audit
Answer the question before buying the dashboard
AI-visibility monitoring platforms track how often you're cited over months. None of that matters if GPTBot is blocked or your content only exists after hydration. The audit settles the technical layer for free, first.
Evidence, not a verdict
Every verdict quotes its source: the robots.txt line, the framework marker, the counted statistics, the failing chunk. You can check our work. Which is exactly what makes the report trustworthy enough to act on.
Severity-ordered, so you fix the right thing first
Sections are ordered worst-first. A perfect citability score is irrelevant while crawlers are firewalled out. The report never lets polish hide a foundation problem.
Shareable deep link
Every report has a URL that reproduces it live: send it to a client, a developer or a skeptical boss, and they see the same evidence, not a screenshot.
Built for the way you work
From quick one-off fixes to daily workflows, see how people put this tool to use.
- SEO / marketing lead
The pre-dashboard sanity check
Before committing to a paid AI-visibility platform, confirm the technical layer is clean. A $99/month dashboard can't fix a robots.txt block. A free audit finds it in ten seconds.
- Content team
Audit the money pages
Run the guide or landing page you most want cited by ChatGPT and Perplexity. The citability and snippet sections give per-section rewrite targets, not vague advice.
- Developer
Verify a framework migration
Moved to a new framework or rendering strategy? The rendering section shows exactly how many words survive without JavaScript, with the framework markers it found as evidence.
- Agency
A client-ready report with receipts
The share link reproduces the full report live. Every claim in it is backed by a quoted rule, a counted number or a listed fragment: the kind of audit a client can't dismiss.
What this tool does not do
Boundaries stated plainly, with the right tool for each neighbouring job.
- It does not monitor how often AI assistants mention your brand over time: that's outcome tracking, which needs continuous paid API querying. This audit checks the technical layer that makes mentions possible.
- It audits one page per run, not a whole site crawl. Run it on each page you want cited.
Supported formats
Accepts URL, and produces Report and Share link, all processed locally in your browser.
- URL
- Report
- Share link
Frequently asked questions
Use this in a workflow
See how the GEO audit fits into a step-by-step journey with related tools.
Recommended tools
AI Crawler Access Checker
Check whether GPTBot, ClaudeBot, PerplexityBot, OAI-SearchBot, Bingbot and every other AI crawler can read your site. Real RFC 9309 robots.txt matching with the deciding rule quoted, plus Cloudflare default-blocking detection. Free, instant, no signup.
JS Rendering Checker
See your page the way AI crawlers see it: without JavaScript. Fetch the raw HTML, count the words that survive, detect client-rendering framework markers, and diff against the rendered DOM to list exactly which content is invisible to GPTBot, ClaudeBot and PerplexityBot.
Content Citability Scorer
Score any page or draft on the factors a published study (KDD 2024) measured as increasing AI citation: fact density, source citations, quotability, answer-first openings, question headings and self-containment. Every sub-score shows its formula and what it counted.
Retrieval Chunk Preview
See your page the way a RAG system does: split into retrieval chunks and read one at a time, with no surrounding context. Flags every fragment that collapses alone: pronoun openers, 'as mentioned above', sections that never name their subject.
AI Crawler Log Analyzer
Drop a server access log and see which AI crawlers actually visit: per-bot hit counts, first and last seen, most-fetched pages, status-code health, daily trend, and the pages no AI crawler has ever touched. Parsed in your browser: logs contain visitor IPs and never leave your device.
AI Robots.txt Generator
Generate a correct robots.txt policy for every AI crawler (GPTBot, ClaudeBot, OAI-SearchBot, PerplexityBot and 11 more) with per-bot allow/block toggles and a plain-language line on what each choice costs. Free, in your browser.
Common problems, solved
Hit a snag? Here are quick fixes for the issues people run into most.
The audit says it couldn't fetch my page.
Some sites block all automated requests at the firewall (which, note, may also be blocking AI crawlers: that's a finding in itself). Use the component tools in paste mode: paste your robots.txt into the AI Crawler Access Checker and your page HTML into the citability and chunk tools.
My crawler-access section is perfect but AI tools still can't read my site.
robots.txt is a request, not a gate. Check the Cloudflare finding in the report: the 'AI bots' firewall setting blocks crawlers before they ever read robots.txt, and it defaults ON for new Cloudflare zones. The audit flags Cloudflare from response headers, but only the dashboard shows the toggle's state.
Why does my score differ from my AI-visibility platform's score?
Different question. Monitoring platforms measure how often you appear in AI answers (outcome). This audit measures whether anything technically prevents you from appearing (mechanism), with the arithmetic shown. Fix the mechanisms. The outcome metrics follow.
The rendering section flags my site but it looks fine in Google.
Googlebot renders JavaScript. Most AI crawlers don't. A page can rank in Google while being nearly empty to GPTBot, ClaudeBot and PerplexityBot. That gap is precisely what this section measures.
Get the most out of it
Audit individual pages, not just the homepage. Retrieval is per-page, and your most-citable page is usually a specific guide, not the front door.
Fix sections in the order the report shows them: access before rendering, rendering before content. Polishing citability on a page crawlers can't read is wasted work.
Re-run the audit from the share link after deploying fixes. The diff between two runs is your changelog of real progress.
A blocked training bot (GPTBot, ClaudeBot) can be a deliberate policy: the audit marks those as informational, not failures. Make sure it's your policy and not a CDN default.
Pair the audit with your server logs in the AI Crawler Log Analyzer: the audit says whether bots CAN read you. The logs say whether they DO.
What's new
Recent updates and improvements to the GEO audit.
Initial release: six-section audit (crawler access with RFC 9309 matching + Cloudflare detection, JS rendering, GEO-study citability, retrieval chunks, answer snippets, schema/identity), severity ordering, per-finding tool links, shareable deep-link reports.
Keep exploring
Related tools
Problems we solve
From the blog
Explore categories
Common tasks
Next steps
Your privacy is built in
The page, robots.txt and llms.txt are fetched through our stateless proxy: it fetches, returns the content for analysis, and stores nothing, no URLs logged, no results kept. All scoring runs in your browser. The share link encodes only the audited URL itself.
- Ephemeral processing
- Deleted instantly
- Never logged
Ready to try the GEO audit?
Free and instant, GigAI GEO Audit processes your file securely and removes it right after.