The Plain Fetch viewer
In short
The viewer requests a URL the way a plain-fetch agent does: no JavaScript, one request for HTML, one for markdown, one for llms.txt and one for a path that should not exist. It shows the initial HTML on the left, the readable text on the right, and seven flags underneath.
Pre-loaded with www.wikipedia.org, read 4 November 2026. Type any public URL to run your own.
The page answers a plain fetch: 4 of 6 checks found.
Initial HTML what a plain fetch receives
<!doctype html>
<html
lang="en-US"
dir="ltr"
><head>
<meta charset="UTF-8" />
<meta name="viewport" content="width=device-width, initial-scale=1" />
<meta http-equiv="X-UA-Compatible" content="ie=edge" />
<title>Live Chat Software with AI by Text | LiveChat.com</title>
<meta
name="description"
content="Text is live chat software for your website with an AI Agent that answers 24/7. Qualify leads and track sales from chats. Start your free 14-day trial."
/>
[... 2 more head elements folded ...]
<link rel="canonical" href="https://www.livechat.com/">
<link rel="alternate" hreflang="en-US" href="https://www.livechat.com/" />
<link rel="alternate" hreflang="es" href="https://www.livechat.com/es/" />
<link rel="alternate" hreflang="de" href="https://www.livechat.com/de/" />
<link rel="alternate" hreflang="fr" href="https://www.livechat.com/fr/" />
<link rel="alternate" hreflang="ja" href="https://www.livechat.com/jp/" />
<link rel="alternate" hreflang="pt" href="https://www.livechat.com/pt/" />
<link rel="alternate" hreflang="ru" href="https://www.livechat.com/ru/" />
<link rel="alternate" hreflang="zh" href="https://www.livechat.com/cn/" />
<link rel="alternate" hreflang="x-default" href="https://www.livechat.com/" />
[... 1 more head element folded ...]
<link
rel="sitemap"
type="application/xml"
title="Sitemap"
href="/sitemap.xml"
/>
[... 32 more head elements folded ...]
</head>
<body class="lang-en">
<noscript
>[... 195 characters folded ...]</noscript>
<div class="b--u-py-1 u-bg-accent c-announcement u-hidden" data-controller="announcement" data-namespace="website-livechat">
<div class="o-container u-relative">
<p class="b--u-text-2xs u-text-black u-maxw-6 u-flex u-items-center u-justify-center u-mx-auto u-mb-0 u-relative">
<svg class="u-basis-1 sm:u-basis-auto" width="21" height="21" fill="none" xmlns="http://www.w3.org/2000/svg">[... 348 characters folded ...]</svg>
<span class="b--u-ml-1 u-basis-11 sm:u-basis-auto" data-announcement-target="message"></span>
</p>
</div>
</div>
<div class="t-homepage-text-header">
<div
class="c-navbar u-border-b "
data-controller="attribute mobile-menu"
data-action="resize@window->mobile-menu#sync"
Shown with 233 long blocks (scripts, styles, long tags) folded into a marker that says how many characters they hide; the pane stops after the first 200 words; the page is 309 KB.
Reading view the text a plain-fetch client can extract
title: Live Chat Software with AI by Text | LiveChat.com
Live chat software that grows sales
mobile-menu#sync" > events#send" > Menu Close mobile-menu#trapFocus click->menu#toggleSubmenu keydown->menu#handleKeyDown focusout->menu#handleFocusOut pointerdown@document->menu#handleOutsidePointer resize@window->menu#repositionOpenSubmenu" data-attribute-target="element" data-attribute-toggle-class="v--active" hidden aria-label="Main navigation" > Back menu#enterSubmenu mouseleave->menu#leaveSubmenu" > Product Capabilities events#send" > AI Agent Answers that close sales events#send" > AI live chat AI replies, agents step in events#send" > Chat widget Turn visits into sales events#send" > Service automation Routine work on autopilot events#send" > Omnichannel inbox Sell on every channel Features events#send" > Security Keep customer data safe events#send" > Reports & analytics Track revenue per chat events#send" > Chat API Build custom chat flows events#send" > See all features menu#enterSubmenu mouseleave->menu#leaveSubmenu" > Solutions By business type events#send" > Education Enroll more students events#send" > SaaS & subscriptions Convert trials, cut churn events#send" > Small business Win more customers events#send" > Enterprise Grow revenue at scale By use case events#send" > Ecommerce Convert more shoppers events#send" > Sales Turn chats into sales events#send" > Lead generation Capture qualified leads events#send" > Customer service Turn support into revenue menu#enterSubmenu mouseleave->menu#leaveSubmenu" > attribute#addClass" >Integrations attribute#removeClass" >Marketplace Ecommerce platforms events#send" > Shopify events#send" > WooCommerce events#send" > WordPress events#send" > Webflow Popular integrations events#send" > WhatsApp events#send" > Messenger events#send" > Instagram events#send" > Klaviyo events#send" >
1417 more words follow in the initial HTML.
| Check | Result | Detail |
|---|---|---|
| H1 in the initial HTML | Found one H1 | First H1: Live chat software that grows sales |
| First 200 words in the initial HTML | Found 200 of 200 words | The initial HTML carries 1617 words of visible text; the first 200 are marked in the left pane. |
| llms.txt present and linked | Note present, not linked | 238040 bytes, 932 links. Structure grade C (4 of 6). Nothing on the home page points to it. Ora's lab found 86 percent of llms.txt fetches arrived through a link. |
| Markdown on request | Missing 200 text/html | Accept: text/markdown returned 200 with text/html; charset=UTF-8. The server ignores the header. |
| Status of a made-up path | Found 404 | /agent-ready-html-missing-path-check returned 404: a real status code for a missing page. |
| JSON-LD types | Found AggregateOffer, AggregateRating, Brand, ContactPoint and 11 more | 15 schema.org types in JSON-LD blocks on the home page: AggregateOffer, AggregateRating, Brand, ContactPoint, Corporation, EntryPoint, ImageObject, Offer, PostalAddress, QuantitativeValue, SearchAction, UnitPriceSpecification, WebApplication, WebPage, WebSite. |
| OpenAPI link | Note none on the home page | No OpenAPI link on the home page. It matters only for a site that ships an API. |
Run the full check
The viewer read one page with four requests. The full check we recommend next is Ora's scan. Its Access layer runs 42 checks worth 30 of its 100 points, among them content without JavaScript, bot detection, llms.txt, markdown on request, JSON-LD and the sitemap (Ora's check catalogue, contract 1.38.0, read 5 November 2026). Open Ora's report for livechatinc.com.
Limits: Ora reads public URLs only, says two runs of one scan land within a couple of points without publishing repeat-scan data, and keeps the product that fixes what it finds behind a waitlist. Cloudflare's scanner at isitagentready.com is a quick free alternative, and Mintlify's score covers documentation.
What the viewer does
It sends four plain GET requests with the user agent Mozilla/5.0 (compatible; agent-readiness-crawl/1.0): the URL itself, the same URL with Accept: text/markdown, /llms.txt on the same host, and a made-up path at the root. It runs no JavaScript. The left pane is the first bytes of the HTML as text, with long scripts and styles folded into a marker that says how many characters they hide. The H1 and the first 200 words of visible text are marked in both panes. The flags under the panes say what the four responses added up to.
Limits
- Ten seconds for all four requests together, 1.5 MB read from the home page, at most five redirects, each one checked again.
- http and https only, default ports only. Private, local and internal addresses and names are refused.
- Ten runs per address per minute. The counter lives in memory on the edge function, so it is per instance rather than global. Past ten you get a 429 with a Retry-After header.
- Results are cached for 24 hours by the response headers. Nothing is written to a database: the viewer keeps the first 200 words and the extracted fields for the length of the request and keeps no page body beyond that.
What it does not tell you
A plain fetch from this server is not a real agent. Bot protection weighs the source address more than the user agent, so a page that answers 200 here can still refuse an agent, and the reverse. Ora's lab found (2026-10-19) that returning 403 to agent user agents and hiding the answer in JavaScript were the only two of 19 configurations that stopped retrieval; the viewer can see the second, and can only hint at the first. The initial HTML reference covers both. The server logs and the published crawler address ranges settle the first.
The seven flags
- H1 in the initial HTML
- Whether the HTML the server sends already contains an H1. It is the cheapest sign that the page does not depend on scripts to say what it is.
- First 200 words in the initial HTML
- Whether at least 200 words of visible text arrive in the initial HTML. Under 40 words with an app root element is flagged as a JavaScript shell.
- llms.txt present and linked
- Whether /llms.txt answers with a plain-text file, whether the home page links it (an anchor, a link element or a Link header), and the structure grade the index uses.
- Markdown on request
- Whether a request with Accept: text/markdown comes back as text/markdown. Cloudflare Radar found 3.9 percent of scanned top sites passing this at its April 2026 launch.
- Status of a made-up path
- Whether a path that should not exist returns 404 or 410. A 200 is a soft 404 and reads as a live page.
- JSON-LD types
- The schema.org types found in JSON-LD blocks on the page. Ora's lab found JSON-LD made no difference when the answer was already in the HTML.
- OpenAPI link
- Whether the page links an OpenAPI file, by an anchor or a service-desc link relation. It matters only for a site that ships an API.
Sources
- Ora: AgentReady launch post (Ora's lab findings) https://ora.ai/blog/agentready-launch, read 4 November 2026
- Ora check catalogue, contract 1.38.0 (132 checks, 42 in the Access layer) https://ora.ai/api/checks, read 5 November 2026
- Ora home page (the fixing product is behind a waitlist) https://ora.ai/, read 5 November 2026
- Ora: Introducing Deep Scan (repeat scans) https://ora.ai/blog/introducing-deep-scan, read 5 November 2026
- Ora llms.txt (public URLs only) https://ora.ai/llms.txt, read 5 November 2026
- Vercel: Make your site readable by AI agents https://vercel.com/kb/guide/make-your-site-readable-by-ai-agents, read 4 November 2026
- llms.txt proposal (llmstxt.org) https://llmstxt.org/, read 4 November 2026
Last reviewed 5 November 2026