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: 5 of 6 checks found.
Initial HTML what a plain fetch receives
<!DOCTYPE html>
<html class="mdl-js" lang="en">
<head>
[... 2 more head elements folded ...]
<meta charset="utf-8">
[... 18 more head elements folded ...]
<meta name="viewport" content="width=device-width, initial-scale=1, shrink-to-fit=no">
[... 11 more head elements folded ...]
<title>Customer Engagement Platform for Email, Push… - OneSignal</title>
<meta name="generator" content="SEOmatic">
[... 1 more head element folded ...]
<meta name="description" content="The world's leader for mobile push notifications, web push, SMS, email and in-app messaging. Trusted by 2 million+ businesses to send 12 billion+ messages per…">
[... 1 more head element folded ...]
<meta name="robots" content="all">
[... 28 more head elements folded ...]
<link href="https://onesignal.com/" rel="canonical">
[... 1 more head element folded ...]
</head>
<body
class="home" >
<!-- Google Tag Manager (noscript) -->
<noscript>[... 151 characters folded ...]</noscript>
<!-- End Google Tag Manager (noscript) -->
<noscript class="hidden">
<div>Javascript must be enabled for the correct page display</div>
</noscript>
<a class="accessibility" href="#main">Skip to Content</a>
<div id="wrapper">
<header class="header" id="header"><svg class="only-print" width="172" height="40" xmlns="http://www.w3.org/2000/svg" fill="none" viewBox="0 0 172 40">[... 5,715 characters folded ...]</svg>
<nav class="navbar navbar-expand-lg navbar-dark text-white position-absolute w-100 head-header">
<div class="container">
<a class="navbar-brand" href="/" title="OneSignal Homepage">
<svg class="logo-white" width="172" height="40" xmlns="http://www.w3.org/2000/svg" fill="none" viewBox="0 0 172 40">[... 5,680 characters folded ...]</svg>
<svg class="logo-black" width="172" height="40" xmlns="http://www.w3.org/2000/svg" fill="none" viewBox="0 0 172 40">[... 5,715 characters folded ...]</svg>
</a>
<div class="header-menu d-flex flex-row-reverse flex-lg-row align-items-md-center justify-content-md-between">
<button class="navbar-toggler" type="button" data-toggle="collapse" data-target="#navbarSupportedContent" aria-controls="navbarSupportedContent" aria-expanded="false" aria-label="Toggle navigation">
<span class="navbar-toggler-icon"></span>
</button>
<div class="collapse navbar-collapse" id="navbarSupportedContent">
<ul
class="navbar-nav mr-auto ml-0">
<!-- Product Dropdown -->
<li class="nav-item dropdown">
<a class="nav-link dropdown-toggle" role="button" id="product" href="#">Product
<svg width="6" height="12" viewBox="0 0 6 12" fill="none" xmlns="http://www.w3.org/2000/svg">[... 1,028 characters folded ...]</svg>
</a>
<ul class="dropdown-menu sub-menu dropdown-menu-product dropdown-landscape" aria-labelledby="product">
<li
class="nav-dropdown-section">
<!-- Product > Messaging Channels -->
<span class="nav-dropdown-section-label">Messaging channels</span>
<ul class="nav-dropdown-section-list">
<li>
<a href="/mobile-push" class="dropdown-menu-channel">
<div>
<span class="nav-dropdown-item-link">Mobile push notifications</span>
<span class="dropdown-menu-item-caption">Direct, highly visible, mobile-first</span>
</div>
</a>
</li>
<li>
<a href="/web-push" class="dropdown-menu-channel">
<div>
<span class="nav-dropdown-item-link">Web push notifications</span>
<span class="dropdown-menu-item-caption">Direct, reach any browser visit</span>
</div>
</a>
</li>
<li>
<a href="/email" class="dropdown-menu-channel">
<div>
<span class="nav-dropdown-item-link">Email</span>
<span class="dropdown-menu-item-caption">Easy email built for real impact</span>
</div>
</a>
</li>
<li>
<a href="/in-app" class="dropdown-menu-channel">
<div>
<span class="nav-dropdown-item-link">In-app messaging</span>
<span class="dropdown-menu-item-caption">Visual, customizable, reach all app users</span>
</div>
</a>
</li>
<li>
<a href="/rcs" class="dropdown-menu-channel">
<div>
<span class="nav-dropdown-item-link nav-item-badge--new">RCS</span>
<span class="dropdown-menu-item-caption">Turn texts into branded experiences</span>
</div>
</a>
</li>
<li>
<a href="/sms" class="dropdown-menu-channel">
<div>
<span class="nav-dropdown-item-link">SMS</span>
<span class="dropdown-menu-item-caption">Effective, fast, mobile-first</span>
</div>
</a>
</li>
<li>
<a href="/live-activities" class="dropdown-menu-channel">
<div>
<span class="nav-dropdown-item-link">Live Activities</span>
<span class="dropdown-menu-item-caption">Highlight real-time app updates</span>
</div>
</a>
</li>
</ul>
</li>
<li
class="nav-dropdown-section-secondary section-right">
<!-- Products > Features -->
<div class="dropdown-secondary-flex">
<span class="nav-dropdown-section-label">Features</span>
<ul class="nav-dropdown-section-list">
<li>
<a href="/ai" class="dropdown-menu-channel-small nav-item-badge--new">
<span class="nav-dropdown-item-link">OneSignal AI</span>
</a>
</li>
<li>
<a href="/journeys" class="dropdown-menu-channel-small nav-item-badge">
<span class="nav-dropdown-item-link">Journeys</span>
</a>
</li>
<li>
<a href="/personalization" class="dropdown-menu-channel-small">
<span class="nav-dropdown-item-link">Personalization</span>
Shown with 138 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 795 KB.
Reading view the text a plain-fetch client can extract
title: Customer Engagement Platform for Email, Push… - OneSignal
Your users are churning. AI can bring them back.
Skip to Content Product Messaging channels Mobile push notifications Direct, highly visible, mobile-first Web push notifications Direct, reach any browser visit Email Easy email built for real impact In-app messaging Visual, customizable, reach all app users RCS Turn texts into branded experiences SMS Effective, fast, mobile-first Live Activities Highlight real-time app updates Features OneSignal AI Journeys Personalization Segmentation Analytics Events API SDKs Integrations directory View More Features Industries Gaming News/Media eCommerce Mobile apps Fintech/Financial See product tour Check out OneSignal in action with self-guided interactive demos Resources Resources Blog eBooks Customer case studies Webinars Podcasts Tools & templates Company events View all resources More to explore Use cases Demo videos Notification preview tool Why OneSignal? ROI of switching OneSignal Solution Partners Glossary See product tour Check out OneSignal in action with self-guided interactive demos Documentation Pricing Get a demo Log in Sign up Log in Talk to sales Get started now Your users are churning. AI can bring them back. Autonomous lifecycle marketing orchestrates the campaigns to onboard, engage, and retain users. Get started now Talk to sales One engine. Every stage of the lifecycle. Drive LTV and reduce churn without the manual effort. Define your brand guardrails and let
1016 more words follow in the initial HTML.
| Check | Result | Detail |
|---|---|---|
| H1 in the initial HTML | Found one H1 | First H1: Your users are churning. AI can bring them back. |
| First 200 words in the initial HTML | Found 200 of 200 words | The initial HTML carries 1216 words of visible text; the first 200 are marked in the left pane. |
| llms.txt present and linked | Note present, not linked | 3140 bytes, 1 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 | Found text/markdown | Accept: text/markdown returned 200 with text/markdown; charset=utf-8. Vary: Accept is set. |
| 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 BreadcrumbList, Corporation, CreativeWork, ImageObject and 1 more | 5 schema.org types in JSON-LD blocks on the home page: BreadcrumbList, Corporation, CreativeWork, ImageObject, ListItem. |
| 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 onesignal.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