# axray.online as an AI agent reads it Source: https://axray.online/ Fetched: 2026-09-04T02:36:44.537Z (one plain HTTP request, no browser, no JavaScript) AX score: 100/100 (A+) - https://axray.online/report/gBeTTFFFUZfMeQ Estimated context cost: ~3278 tokens, of which ~2949 are page content --- [Skip to main content](#main) [AXRAY](/) - [How it works](/how-it-works) - [The AX spec](/ax-spec) - [AX Index](/index) - [API](/docs) - [Pricing](/pricing) [Sign in](/login)[Create account](/signup) Menu - [How it works](/how-it-works) - [The AX spec](/ax-spec) - [AX Index](/index) - [API](/docs) - [Pricing](/pricing) - [Sign in](/login) - [Create account](/signup) AI readability check # People ask AI about you. See what it reads on your site. AXRAY reads your page exactly the way ChatGPT, Claude, Perplexity and Google's AI read it, then tells you in plain words how much of you reaches them, what never arrives, and which fixes win back the most. Paste your address and you will know in about two seconds. Website URL to scan Run the scan Prefer a terminal? `npx axray-cli example.com` - 1 free scan, no account - An answer in about two seconds - Nothing to install northline.coffee/ethiopia-guji Example 403 — CDN challenge served to GPTBot <**div** class="logo"> <**a** href="#"> × 4 Navigation is a dead end <**img** src="guji.webp"> No alt text

— missing <**div** class="p">$24.00 Price is not an Offer <**div** onclick="buy()"> Not a link — an agent cannot follow it llms.txt — not found schema.org — 0 blocks What an agent receives, beside what you see Drag the beam ↔ What this is, in one sentence ## AXRAY tells you whether AI can find your site, describe it correctly, and send you the customer. An assistant does not browse your site the way a person does. It takes one pass at the page, with no browser and no clicking, and writes its answer from whatever came back. Everything on this page is about that gap. If you do one thing here, paste your address in the box above. 01 ### Can it get in at all? A great many sites turn AI crawlers away at the front door without ever meaning to. Nothing breaks, no error is logged, no alert fires — you simply stop appearing in answers, and there is no way to notice from the inside. 02 ### Does it get you right? What you sell, what it costs, where you are, how to buy. If those are not stated in a form a machine can lift out, the assistant fills the gaps by guessing — and the guess is what your customer reads, in a conversation you never see. 03 ### What should you fix first? You get one ordered list, not a wall of warnings. Each item carries the points it wins back and says whether it is a setting you can change this afternoon or a rebuild that needs a developer, so you can start at the top and stop wherever you like. 57checks run against every URL, across five weighted pillars 16named AI crawlers resolved against your robots.txt individually 294well-known public sites measured to build the baseline 68is what the median one of them scores out of 100 Resolved individually against your robots.txt OAI-SearchBot ChatGPT-User GPTBot ClaudeBot Claude-User Claude-SearchBot PerplexityBot Perplexity-User Google-Extended Googlebot Bingbot Applebot-Extended meta-externalagent Amazonbot CCBot DuckAssistBot The gap nobody is measuring ## Lighthouse scores the human experience. Nothing scores the other half of your traffic. You already measure how fast a page paints and how it ranks. Neither of those tells you whether an assistant can quote your pricing correctly, whether a shopping agent can find your stock status, or whether the crawler that would have cited you was turned away at your CDN this morning. Those are different questions with different answers, and they are the ones deciding how you are described in an answer you never get to see. weight 25 Reachability ### Can it get the bytes? Can an agent fetch your content at all, without a browser and without being blocked? A Cloudflare challenge that a browser solves silently returns a wall to ChatGPT. Your page simply does not exist in that answer. weight 25 Comprehension ### Can it tell what this is? Once fetched, can the agent work out what this page is and what it says? No h1, no description, 40 words of text: the assistant writes its own summary of you, and it will be wrong in a way you never see. weight 18 Structure ### Can it read the facts? Is the important data machine-readable instead of implied by visual layout? Your price is styled text in a div. A competitor publishes an Offer. The shopping agent quotes their number and calls yours "not stated". weight 17 Actionability ### Can it do the next thing? Can the agent take the next step - navigate, search, submit, buy - without guessing? Navigation built from click handlers on empty anchors works for a mouse and is a dead end for an agent. Everything behind it is unreachable. weight 15 Agent Contract ### Did you tell it the rules? Have you told agents the rules: what they may use, where the docs are, who to contact? No llms.txt, no per-crawler policy, no manifest. Every operator applies its own default to you and you find out afterwards. What actually happens · AX spec v1.2.0 ## One request, 57 checks, a list in priority order. ### We fetch it as an agent would One plain HTTP request, no browser and no JavaScript engine, announcing itself honestly. Whatever comes back is the whole of what an agent has to work with — including the redirect chain, the status code and the wall, if there is one. ### We grade what arrived 57 checks across five weighted pillars, plus your robots.txt resolved against 16 named AI crawlers one at a time. Severity gates cap the score when something fundamental is broken, so a blocked page cannot pass on presentation points. ### You get an ordered fix list Every finding carries the points it is costing you on the same 0–100 scale, so the list sorts itself. Configuration fixes are flagged apart from architectural ones, because the first kind ships this afternoon and the second needs a sprint. What you get back ## A number you can act on, not a wall of warnings. axray.online/report/8vi5_VXkgntVzw live 100 / 100 A+ Our own report axray.online axray.online scores 100/100 (A+) for Agent Experience. Reachability 100 Comprehension 100 Structure 100 Actionability 100 Agent Contract 100 Scanned 12h ago · 57 checks [Open the full report →](/report/8vi5_VXkgntVzw) ### The report - Overall AX score and letter grade, with five pillar sub-scores - Per-check verdict, the evidence we found, and why an agent cares - A copy-pasteable snippet for every fix that has one - Your potential score if you applied only the configuration fixes - A shareable public URL and an embeddable badge ### The crawler check We resolve robots.txt against 16 named AI crawlers individually, and separate the ones that send you traffic from the ones that only train on you. Most sites that "blocked the AI bots" blocked both without meaning to. - `OAI-SearchBot` — OpenAI - `ChatGPT-User` — OpenAI - `Claude-User` — Anthropic - `Claude-SearchBot` — Anthropic - `PerplexityBot` — Perplexity - `Perplexity-User` — Perplexity The AX Index ## What the web actually scores [See the distribution](/index) 68median AX score across 294 well-known public sites 31%score below 58, the point where an agent starts getting you wrong Measured by us across SaaS, retail, news, documentation, government and reference sites. Counted, not named — they did not ask to be graded in public. In your terminal and your pipeline ## The same engine, everywhere you work. The CLI and the API run the same scoring code as this page, from the same package, so the number in CI is the number on the report. The CLI is free and needs no account; the API is included on the Team plan and above. your terminal ``` $ npx axray-cli example.com $ npx axray-cli example.com/pricing --verbose $ npx axray-cli example.com --crawl 50 --json > ax.json # the site you have not deployed yet $ npx axray-cli localhost:3000 --allow-private ``` your pipeline ``` # fails the build if the score drops below 70 $ npx axray-cli "$DEPLOY_URL" --min 70 ``` the JSON API ``` $ curl -s https://axray.online/api/v1/scan \ -H "authorization: Bearer $AXRAY_API_KEY" \ -H "content-type: application/json" \ -d '{"url":"example.com"}' | jq '.score' ``` What it costs ## Free to find out. A few dollars to keep watching. One scan costs nothing and needs no account, because a number you cannot get is not worth publishing. You pay when you want the whole site crawled rather than one page, or the scanner running in your pipeline instead of your browser. Free Free forever Find out where you stand. - 1 scan a day with no account at all - 2 a day once you sign up - Full 57-check report and fix list - Reports reachable by their own private link [Scan a URL](#url) Pro 2.99 per month For one site you actually care about. - 100 scans a day - Whole-site crawl up to 50 pages - 3 pages watched on a schedule, with alerts - Systemic issue analysis across templates [Start Pro](/pricing) Team 8.99 per month For a team wiring AX into a pipeline. - 1,000 scans a day - Crawls up to 500 pages - 25 monitored pages, alerting to a signed webhook - An API key, for calling the JSON API from a server [Start Team](/pricing) Higher volume than Team is [Scale, 19.99 per month](/pricing) — the same product, more of it. Prices are shown in your own currency at checkout, tax included. [See the full comparison](/pricing). Before you paste an address ## The questions people ask first. Do I need an account to try it? No. 1 scan a day with no account, no card and nothing to install — paste an address and the report is on screen in about two seconds. An account is free as well: it raises the daily allowance to 2, keeps your reports to yourself and remembers what you have scanned. My site is a React or Next.js app. Will it just score zero? It scores whatever arrives without a browser, and if your content is assembled in the visitor’s browser then very little arrives. That is not us failing to read your site — it is the same empty shell the crawler gets, and the reason your pages can be missing from answers while looking perfect to you. The fix is to render on the server: Next.js server components or `getStaticProps`, Nuxt or SvelteKit in SSR mode, or a prerender step for the routes that matter. Frameworks already doing that score normally here. How is this different from Lighthouse or an SEO audit? Lighthouse runs a browser and measures how fast the page paints for a person. An SEO tool asks how you rank. AXRAY runs no browser at all, which is the point: it reproduces the budget a crawling agent actually gives you and reports what survived. Around a third of the 57 checks have no equivalent in either tool — whether a named AI crawler is allowed through, whether your prices are machine-readable, whether an agent can operate your forms. Can I run this automatically, on every deploy? Yes. `npx axray-cli your-site.com --min 70` exits non-zero below the threshold, so a change that would have broken what agents can read fails the build instead of shipping. The command-line tool is free, needs no account and runs the same scoring code as this page; the JSON API, for calling it from your own server, comes with the Team plan. Does scanning my site publish anything about it? No. The report is reachable only through its own unguessable link, and your domain does not enter the public [AX Index](/index) unless you prove you control it and ask to be listed. Scanning a staging URL publishes nothing. More about the method, and the objections to it, on [how it works](/how-it-works#faq) and in the [published specification](/ax-spec). ![The AXRAY agent holding a scorecard reading 100 out of 100, grade A plus] ## Find out what AI sees on your site. It takes about two seconds and you do not need an account. Most people are surprised, and the majority of what turns up is fixable the same day. [Scan a URL](#url) Scan any page Run the scan AXRAY See what AI can actually read on your website. Agent Experience specification v1.2.0. Open rubric, open CLI. ## Product - [How it works](/how-it-works) - [Pricing and plans](/pricing) - [The AX Index](/index) - [Compare two sites](/compare) - [Get an AX badge](/badge) ## Developers - [CLI and API documentation](/docs) - [The AX specification](/ax-spec) - [llms.txt](/llms.txt) - [OpenAPI schema](/openapi.json) ## Company - [Writing](/writing) - [AI crawler reference](/ai-crawlers) - [Türkçe yazılar](/yazilar) - [About AXRAY](/about) - [Changelog](/changelog) - [Contact us](/contact) - [Terms of service](/terms) - [Privacy policy](/privacy) - [Security](/security) - [security.txt](/.well-known/security.txt) © 2026 AXRAY. Built to be read by machines. Last updated 2026-08-26. [hello@axray.online](mailto:hello@axray.online)