Agent Web Index › rttnews.com

Can AI assistants read rttnews.com?

Measured on 2026-09-19 by asking the site 7 times — once as a browser, once as each of the 6 crawlers that feed ChatGPT, Claude, Perplexity, Gemini, Meta AI, Apple Intelligence and Doubao — and comparing what came back. The AI-training opt-out tokens that never crawl are read from robots.txt instead.

D52 / 100
0 of 6 crawlers can read this page.
More readable than 7% of the 47,315 sites measured so far. Structured data: NewsMediaOrganization, WebSite, SiteNavigationElement.

What each crawler got back

CrawlerHTTPResultrobots.txt
ClaudeBot (Claude)403 challenged blocked
GPTBot (ChatGPT)403 challenged blocked
OAI-SearchBot (ChatGPT Search)403 challenged allowed-by-star
PerplexityBot (Perplexity)403 challenged blocked
Google-Extended (Gemini, AI Overviews)
a robots.txt token, not a crawler: it controls how already-crawled pages may be used, and never makes a request of its own
opted out in robots.txt blocked
Meta-ExternalAgent (Meta AI)403 challenged allowed-by-star
Amazonbot (Alexa, Rufus)403 challenged blocked

What to change, in order

  1. Let in the 2 crawlers your own robots.txt already allows+2 crawlers
    OAI-SearchBot, Meta-ExternalAgent are turned away before reading the page (served a bot challenge instead of the page), while robots.txt permits them — so this block is not written in your site. No CDN signature was found in the response headers, so the refusal comes from the origin server itself or from a WAF this index does not recognise. Fixing it takes this domain from 0 to 2 of 6 crawlers.
  2. Publish llms.txt
    llms.txt is missing, so an assistant has to discover the site by following links. llms.txt is the emerging convention for telling an assistant which pages actually matter.
  3. Mark the content with <main>
    The content-reachability check scores 30/100: with no <main> or <article> landmark, or with most of the page outside it, an assistant reads the navigation and the footer at the same cost as the text it came for.
  4. 4 crawlers are named and refused in robots.txt — a deliberate choice
    ClaudeBot, GPTBot, PerplexityBot, Amazonbot are blocked by a rule that names them. Nothing to fix here: this page records what is true, not what should be. It is listed so the deliberate part of the block is not confused with the accidental part above.

The checks

Re-run this audit live → Full AI-visibility report for rttnews.com →

Sites with a similar score

kjephotography.myshopify.comD 56audit-it.ruD 53ydns.ioD 53rtcg.meD 52saltwire.comD 52raisin.comD 52servsafe.comD 52paulovivanco.shopD 52timberwings.comD 52henryschein.comD 52desiporn.oneD 51google.bsD 47

Browse the whole index →

Embed this score

Put the badge on rttnews.com — it links back here, and re-measures every time this index re-crawls.

rttnews.com AI readability: D 52/100
<a href="https://shop.lumnika.com/ai-readiness/rttnews.com"><img src="https://shop.lumnika.com/ai-readiness/rttnews.com/badge.svg" alt="AI readability"></a>
Method. 7 live HTTP requests (one per crawler, one as a browser) plus robots.txt, llms.txt, sitemap.xml and security.txt, 12-second timeout each, from a single vantage point. Blocking AI crawlers is a legitimate choice, not a failure: this page records what is true, not what should be. Domain comes from a shop-platform seed (Shopify/WooCommerce/Magento/BigCommerce/Shopline fingerprint or JSON-LD price), not the Tranco traffic ranking. One page per domain — the homepage — is audited.

Part of the Agent Web Index, 47,315 domains measured, updated continuously.