Agent Experience report · spec v1.2.0 · 12h ago
axray.online
https://axray.online/
Unchanged at 100 since the measurement 1d ago.
axray.online scores 100/100 (A+) for Agent Experience. This page is built for agents. It is in the top fraction of a percent of the web on Agent Experience.
This report is not listed anywhere. It is reachable only by this link, and axray.online does not appear in the public AX Index. Listing it is something the domain's owner has to ask for.
In plain English
An AI assistant can find axray.online, read it, and act on what it finds.
Can an AI assistant open this page at all?
Yes. When an assistant goes to look, the page answers it.
This is the thing most sites get wrong first, and this one does not.
Will it describe this business correctly?
Yes. The page states plainly what it is, in words the assistant can read.
What an assistant says about this page comes from the page itself.
Can it quote the facts — prices, contact details, opening hours?
Yes. The key facts are published in a form it can lift word for word.
Asked what this costs or how to get in touch, an assistant answers with the real number.
Can it take the next step — follow a link, use a form, get in touch?
Yes. Links lead somewhere, forms are labelled, and there is a clear way to make contact.
An assistant can carry somebody from an answer all the way to you.
Have the AI companies been told your rules?
Yes. The site states which AI systems may use it and on what terms.
The terms are yours, in writing, where the crawlers look for them.
What to do with a page that already passes
Every question above is already answered yes. The work now is keeping it that way:
run npx axray-cli axray.online --min 95
in your deploy pipeline, and a change that breaks it fails the build instead of being
discovered months later.
What an assistant could tell somebody
The questions people ask about you, and whether this page answers them.
2 of the 7 questions below have no answer on this page at all. An assistant asked one of them either says it does not know, or fills the gap from somewhere you do not control.
| The question | Answer | What is actually there |
|---|---|---|
| What is this company, and what does it do? | Stated | Organization data names you and describes you: "AXRAY measures Agent Experience: whether AI agents can reach, understand and act on a web…" |
| What do they sell? | Stated | 1 declared: AXRAY. |
| What does it cost? | Stated | 4 declared Offers, starting at 0.00 USD. |
| How do I get in touch with them? | Stated | A ContactPoint is declared in structured data. |
| Where are they? | Missing | No PostalAddress, no areaServed and no link to a locations page. |
| Is it in stock? | Missing | An Offer is declared with no availability property, and the text says nothing about stock. |
| What happens if I want to send it back? | Implied | No MerchantReturnPolicy on the page, though llms.txt may point an assistant at the terms. |
Where are they? Every "near me" question, every "is this a local company", every assistant deciding whether you serve a customer's country is answered from this. With nothing declared, you are answered as though you were nowhere.
Is it in stock? A shopping agent that cannot read availability treats the item as unknown and moves to a listing it can read. This is the fact that decides whether you are in the comparison at all.
What happens if I want to send it back? Return terms are one of the last things a buyer checks and one of the first an assistant is asked about. Unanswerable, it says so, and the hesitation is yours to absorb.
Stated means the fact is in a form a machine lifts out and repeats exactly. Implied means it is on the page in prose, or one fetch away behind a link — findable, paraphrasable, and often not worth the request. None of this changes the score above; it is a second reading of the same scan, published beside it rather than folded into it.
The context an agent gets
What the assistant actually came away with
No layout, no styling, no clicking: this is your page rebuilt from the bytes that arrived, in the shape a model reads. Everything an assistant can say about you, it says from this. Read it as your customer’s question would be answered from it — if a fact you sell on is missing here, it is missing from the answer.
Token counts are estimates, not a tokenizer’s output: AXRAY ships no vocabulary files, and the method is described in full. They are close enough to size a page against a context window and to compare the two halves of one page against each other.
[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
<h1> — missing <**div** class="p">$24.00</div> 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)Technical detail all 57 checks, the evidence behind each one, and copy-pasteable fixes
0 failing · 0 warnings · 52 passing
Fix list, highest value first
Each item shows the points it is currently costing on the same 0–100 scale as the score at the top. Items marked config only are content or configuration changes that do not need an engineer.
Nothing is failing. This page is genuinely agent-ready.
Passing checks
Kept here so the report is auditable rather than a list of complaints.
Pass Page responds to a plain HTTP request
HTTP 200 in 193 ms.
The baseline: an agent with no browser, no cookies and no JavaScript received your page.
Pass No bot wall in front of the content
The response body was the real page, not a challenge or block screen.
Bot protection that cannot tell a shopping assistant from a scraper silently removes you from AI answers, with no error anyone on your team will ever see.
Pass Content exists without running JavaScript
2032 words of readable text arrived in the HTML itself.
Most crawling agents never execute JavaScript. Whatever is not in the raw HTML does not exist for them.
Pass robots.txt is present and parseable
robots.txt served with 4 user-agent groups.
A valid robots.txt is how you talk to crawlers before they read a single page.
Pass Answer engines are allowed to crawl
All 5 crawlers in this group may fetch /.
These crawlers are the ones that put your link inside an AI answer. Blocking them removes the referral traffic, not just the training use.
Pass User-triggered fetchers are allowed
All 3 crawlers in this group may fetch /.
These fetches happen because a human just pasted your link into an assistant. A block here fails in front of a real person who wanted to read you.
Pass Classic search crawlers are allowed
All 2 crawlers in this group may fetch /.
AI Overviews and Copilot answers are grounded on the classic search index. Blocking Googlebot or Bingbot now also removes you from AI surfaces.
Pass No directive suppressing AI use of this page
Robots directives present and permissive: index, follow, max-snippet:-1, max-image-preview:large
noindex and nosnippet remove you from the surfaces that would otherwise quote and link you.
Pass Short redirect chain
The URL served content directly with no redirect.
Every hop costs latency and some agents cap redirects at two or three.
Pass Responds fast enough for an agent budget
Full response in 193 ms.
Agents fetch many pages per answer and drop the slow ones. Speed is a ranking input you control.
Pass HTML payload stays inside an agent context budget
11 KB of HTML, 11% of it inline script.
Agents truncate long documents. Anything past the cut simply is not read.
Pass Declares a correct content type
Content-Type: text/html; charset=utf-8
A declared charset avoids mojibake when an agent quotes your text back to a user.
Pass Has a descriptive <title>
"AXRAY - See what AI can actually read on your website." (54 characters).
This is the label assistants attach to you when they cite this page.
Pass Has a meta description
155 characters: "Paste a web address and find out how much of your page reaches ChatGPT, Claude, Perplexity and Google AI. Free, a score…"
This is the summary assistants reuse verbatim more often than any other field.
Pass The page describes itself consistently
<title>, og:title, twitter:title all describe the same page.
Agreement across the machine-readable labels is what lets an assistant state one name for this page and keep stating it.
Pass Exactly one <h1> naming the page
"People ask AI about you. See what it reads on your site."
The h1 is the strongest in-page signal of what the document is about.
Pass Headings form a sane outline
26 headings with no skipped levels.
A clean outline is what lets an agent quote the right section instead of the whole page.
Pass Enough substance to be worth citing
2032 words of readable text, 1915 of them in the main content.
Assistants prefer sources with enough material to answer a question outright rather than pages that just point elsewhere.
Pass Answers questions in a form that can be quoted
FAQ structured data with 5 question-and-answer pairs, and 9 question-shaped headings.
A question paired with its answer in structured data is the one format an assistant can lift whole, attribute to you, and quote without paraphrasing.
Pass Signal-to-markup ratio
27.3% of the payload is readable text.
A high ratio means an agent spends its limited context on your content instead of your tooling.
Pass Declares a document language
<html lang="en">, and the text is Latin as expected.
Language is how an assistant decides whether to answer a user in your words or translate them.
Pass Images carry alt text
1 of 1 images described; 0 intentionally marked decorative.
Alt text is the only way the content of an image reaches an agent.
Pass Main content is marked as such
<main> present with <article>; 4 of 4 landmark regions used.
The <main> element tells an extractor where your content stops and your chrome starts. It is the difference between quoting your argument and quoting your nav bar.
Pass Uses semantic elements, not div soup
37% of structural elements are semantic (53 semantic vs 92 div).
Semantic tags carry meaning an agent can use; a div carries none.
Pass URL describes the content
Site root.
Assistants show the URL next to the citation, and readable URLs get clicked more than opaque ids.
Pass Ships structured data
5 JSON-LD blocks on the page, 13 carrying real properties.
Structured data is the only part of your page an agent reads without having to interpret it.
Pass Structured data parses cleanly
All 5 blocks parse as valid JSON with a schema.org context.
A block with a syntax error is silently discarded by every consumer. You get the maintenance cost with none of the benefit.
Pass Structured data describes the right thing
Declared types: Organization, WebSite, WebPage, SoftwareApplication, Offer, FAQPage, Question.
The right @type is what lets an assistant answer "how much is it" or "when is it" without reading your prose at all.
Pass Open Graph card is complete
og:title, og:description, og:type, og:url and og:image all present.
Open Graph is the fallback summary almost every crawler reads when it cannot parse the page body.
Pass Declares a canonical URL
Canonical: https://axray.online/
Agents dedupe sources by canonical URL, and cross-origin canonicals hand your citation to somebody else.
Pass Publishes a sitemap
https://axray.online/sitemap.xml lists 31 URLs.
A sitemap is how a crawler discovers the pages your navigation hides behind JavaScript menus.
Pass Publishes a feed of its content
1 feed declared: https://axray.online/writing/feed.xml.
A feed hands an agent the whole content stream already parsed, with dates and titles attached, instead of making it crawl and guess. It is the cheapest way to be re-read as you publish rather than once.
Pass Prices are machine-readable
Prices in the copy ($24.00) are backed by Offer structured data.
A shopping or research agent comparing options reads Offer, not your pricing table CSS.
Pass Declares a link preview card
4 twitter:* tags present.
Several agents fall back to card metadata when they cannot extract the body reliably.
Pass Navigation uses real links
All 47 links resolve to a real URL.
Real hrefs are the only navigation primitive an agent has.
Pass Link text describes the destination
100% of links have descriptive text.
Link text is how an agent decides which link to follow when it is looking for something specific.
Pass Links onward into the site
43 internal links give an agent somewhere to go next.
Agents explore a site breadth-first from whatever page they landed on. Dense internal linking is how the rest of your content gets found.
Pass Form fields are labelled
All 2 fields have an associated label or aria-label.
An agent filling a form on a user's behalf reads labels to decide what goes in each box.
Pass Form fields have stable names
All 2 fields have readable name attributes.
Names are the keys an agent uses to build a submission. Generated hashes change on every deploy and break automation silently.
Pass Fields declare autocomplete tokens
2 of 2 fields declare an autocomplete token.
Autocomplete tokens are a standard vocabulary. They remove all ambiguity about which box is the email and which is the company.
Pass Controls are real buttons
4 native button controls, no div-as-button patterns found.
A <button> announces itself as an actionable control. A styled div announces nothing.
Pass Reachable by a human, discoverably
3 contact signals: 1 mailto link, contact page link, contactPoint in structured data.
Assistants routinely answer "how do I contact them". If they cannot find the answer they say so, and the user goes elsewhere.
Pass Site search is machine-usable
A GET form uses the same "url" parameter the declared SearchAction names.
A declared SearchAction lets an agent query your site directly instead of crawling it page by page.
Pass Programmatic surface is discoverable
/.well-known/mcp.json; docs link: /docs; OpenAPI document referenced
When an agent can call your API it stops scraping your HTML, which is cheaper for you and more reliable for the user.
Pass Publishes an llms.txt
https://axray.online/llms.txt served 6840 bytes, 908 words and 31 usable links.
llms.txt is the one file written for assistants rather than browsers: a curated map of what matters on your site, in the order you want it read.
Pass llms.txt is actually useful
9 sections, 31 curated links, 18 annotated, with a summary blockquote.
A well-formed llms.txt is read as a table of contents. A dumped sitemap is read as noise.
Pass States an explicit AI policy
robots.txt names specific AI crawlers rather than relying on the wildcard group.
Naming crawlers explicitly is how you separate "do not train on me" from "do not send me traffic". The wildcard group cannot express that distinction.
Pass Exposes an agent-callable manifest
https://axray.online/.well-known/mcp.json names "axray" and at least one endpoint.
A callable manifest turns you from something an agent scrapes into something an agent uses. Almost nobody has one yet, which is exactly why it is worth having.
Pass Identity is machine-verifiable
AXRAY declared with 1 sameAs link.
sameAs is how an assistant confirms that this site, that GitHub org and that company are the same entity. Without it you are three unrelated strings.
- https://www.instagram.com/axray.online/
Pass Says when the content changed
Last-Modified: Wed, 26 Aug 2026 00:00:00 GMT; ETag present; a usable date in structured data; <time datetime> elements.
Assistants prefer sources they can date, and they say so to users: "according to a page updated in March". Undated pages lose to dated ones.
Pass Declares content licensing
rel="license" pointing at https://axray.online/terms.
A machine-readable licence tells an agent how it may reuse your text. Ambiguity is usually resolved against you.
Pass Publishes security.txt
/.well-known/security.txt names mailto:hello@axray.online, valid until 2027-09-04T02:36:44.251Z.
It is the standard machine-readable place to say who to contact. Agents and researchers both look there first.
Not applicable
These questions were not asked of this page, and are excluded from the score entirely.
n/a Real agent user-agents are served normally
Live user-agent probing was not run for this scan.
Some sites answer 200 to a generic client and 403 to a named AI crawler. Only a live probe finds that.
n/a Provides a no-JavaScript fallback
Not needed: the page already server-renders its content.
n/a Declares its language alternates
No hreflang links, and nothing on the page suggests the content exists in another language.
hreflang is how a site with several language versions tells an assistant which one to quote to which reader. A site with one language has nothing to declare.
n/a Declares its place in the site
Top-level page; breadcrumbs are not expected.
n/a Inline microdata annotations
No microdata; JSON-LD is the preferred format anyway.
Crawler access
Who can actually reach this page
Resolved from robots.txt for this exact path, per crawler. Blocking a training crawler is a legitimate business decision. Blocking an answer engine removes you from the results that would have linked you.
Answer engine
Indexes you so an assistant can cite and link you. Blocking it removes you from AI answers.
User-triggered
Fetches your page because a human asked an assistant to open it right now. Blocking it breaks a live request.
Classic search
Traditional search indexing, increasingly the substrate AI answers are built on.
Training crawler
Collects content for model training. Blocking it is a legitimate business choice with no traffic cost.
Evidence
What we actually received
Every number in this report comes from this one plain HTTP response. No browser, no JavaScript, no retries.
| Observation | Value |
|---|---|
| Final URL | https://axray.online/ |
| HTTP status | 200 |
| Response time | 193 ms |
| HTML size | 42 KB |
| Inline script | 5 KB (11% of payload) |
| Readable words | 2032 |
| Text-to-markup | 27.3% |
| Title | AXRAY - See what AI can actually read on your website. |
| Language | en |
| Canonical | https://axray.online/ |
| Detected stack | (none detected) |
| robots.txt | served |
| sitemap.xml | 31 URLs |
| llms.txt | 9 sections, 31 links |
Share this report
Public report link, and a badge you can put in a README or a footer.
[](https://axray.online/report/gBeTTFFFUZfMeQ)