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.
A plain-fetch client does not get the heading: 3 of 6 checks found.
Initial HTML what a plain fetch receives
<!DOCTYPE html>
<html lang="en" dir="ltr" prefix="og: https://ogp.me/ns#">
<head>
<meta charset="utf-8" />
<meta name="description" content="New Relic is an AI-powered observability platform that correlates your telemetry across your entire stack, so you can isolate the root cause and reduce MTTR." />
[... 1 more head element folded ...]
<link rel="canonical" href="https://newrelic.com/?is_us=true" />
[... 11 more head elements folded ...]
<meta name="viewport" content="width=device-width, initial-scale=1" />
[... 1 more head element folded ...]
<meta name="Generator" content="Drupal 11 (https://www.drupal.org)" />
[... 3 more head elements folded ...]
<link hreflang="x-default" rel="alternate" href="https://newrelic.com" />
<link hreflang="en" rel="alternate" href="https://newrelic.com" />
<link hreflang="de" rel="alternate" href="https://newrelic.com/de" />
<link hreflang="fr" rel="alternate" href="https://newrelic.com/fr" />
<link hreflang="ko" rel="alternate" href="https://newrelic.com/kr" />
<link hreflang="ja" rel="alternate" href="https://newrelic.com/jp" />
<link hreflang="es" rel="alternate" href="https://newrelic.com/es" />
<link hreflang="pt-br" rel="alternate" href="https://newrelic.com/pt" />
<title>AI-powered Observability</title>
[... 46 more head elements folded ...]
</head>
<body class="mq-breakpoints--hide path-frontpage page-node-type-page bg-nr-sand selection:bg-nr-sand selection:text-nr-black nr-cookie-popup">
<script type="text/javascript">[... 78,619 characters folded ...]</script>
<a href="#main-content" class="visually-hidden focusable skip-link">
Skip to main content
</a>
<div class="page js-menu-screen-overlay bg-nr-white z-0">
<main class="page__content" id="main-content">
<div class=" section text-nr-black section--column-align">
<div class="row row--columns-1 nr-fluid-container grid gap-x-6 gap-y-8 items-center large:grid-cols-12" data-layout="12">
<div class="large:col-span-12 column--index-1 grid gap-8 grid-cols-1">
<div data-drupal-messages-fallback class="hidden"></div>
</div>
</div>
</div>
<article>
<div class="r01-layout pt-8 medium:pt-12 section text-left text-nr-black section--column-align section--column-align-end view--home_page_banner">
<div class="row row--columns-2 nr-fluid-container grid gap-x-6 gap-y-8 items-end medium:grid-cols-12" data-layout="7-5">
<div class="medium:col-span-7 column--index-1 grid gap-8 grid-cols-1">
<div class="p02-text min-w-0">
<h2 class="p02-text__headline text-hero-large" data-rotating-headline>
Observability that
<span class="p02-text__rotating-words-container" aria-live="polite">
<span class="nr-rotating-text p02-text__rotating-word-phantom" aria-hidden="true">
predicts
</span>
<span class="nr-rotating-text p02-text__rotating-word" data-word-index="0">
thinks
</span>
<span class="nr-rotating-text p02-text__rotating-word" data-word-index="1">
acts
</span>
<span class="nr-rotating-text p02-text__rotating-word" data-word-index="2">
knows
</span>
<span class="nr-rotating-text p02-text__rotating-word" data-word-index="3">
predicts
</span>
<span class="nr-rotating-text p02-text__rotating-word" data-word-index="4">
protects
</span>
</span>
</h2>
<div class="p02-text__description content text-body-large ">
<div><p><span class="text-sub-small">Intelligent Observability resolves issues at</span><br><span class="text-sub-small">scale—before they impact your bottom line. </span></p></div>
</div>
<div class="p02-text__cta-wrapper inline-flex flex-wrap flex-col medium:items-center small:flex-row gap-4 w-full medium:w-fit max-w-full">
<a href="/signup" aria-label="Get Started Free" class="btn-primary small:inline-flex w-full medium:w-fit group rounded-[36px] p-[32px] bg-nr-black p02-text__primary-cta max-w-full h-16 desktop:h-18 tracking-[-0.025em] large:tracking-[-0.5px]" >
<div class="h-6 overflow-hidden">
Shown with 273 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 656 KB.
Reading view the text a plain-fetch client can extract
title: AI-powered Observability
No H1 in the initial HTML
Skip to main content Observability that predicts thinks acts knows predicts protects Intelligent Observability resolves issues at scale—before they impact your bottom line. Get Started Free Get Demo SRE Agent Move beyond assistance to automated remediation. Session replay with AI Skip searching the video. Have AI identify friction points for you. Understand cloud costs Gain real-time visibility into multi-cloud and Kubernetes spend. AI and agentic monitoring Control behavior and token usage across your AI stack—automatically. OpenTelemetry Future-proof on a universal, open standard for every signal. Agentic Platform Deliver observability insights to AI agents where engineers work. Trusted by the world’s best Customers Retail/Commerce Media/Entertainment Finance SaaS/Technology Telecommunications Automotive COMPLETE OBSERVABILITY TOOLKIT Clarity for the modern tech stack View Platform Previous APM APM PROTECT REVENUE REDUCE MTTR DEVELOPER PRODUCTIVITY Business-aligned. Connect application performance to customer experience and revenue. Explore APM Digital Experience Monitoring USER SATISFACTION MAXIMIZE CONVERSIONS PINPOINT CUSTOMER FRICTION User-centric clarity. Use AI to pinpoint session friction and UX flaws before they impact margins. Explore Digital Experience AI and Agentic Monitoring MANAGE AI AGENTS SCALE AI SAFELY CONTROL AI COSTS Control for accuracy and cost. Monitor every model and agent interaction in real time. Explore AI Monitoring Infrastructure Monitoring PREVENT
3342 more words follow in the initial HTML.
| Check | Result | Detail |
|---|---|---|
| H1 in the initial HTML | Missing no H1 | A plain-fetch client finds no page heading in the bytes it receives. |
| First 200 words in the initial HTML | Found 200 of 200 words | The initial HTML carries 3542 words of visible text; the first 200 are marked in the left pane. |
| llms.txt present and linked | Note present, not linked | 43795 bytes, 200 links. Structure grade B (5 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 ContactPoint, EntryPoint, ImageObject, Organization and 2 more | 6 schema.org types in JSON-LD blocks on the home page: ContactPoint, EntryPoint, ImageObject, Organization, SearchAction, 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 newrelic.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