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">
<head>
<meta charset="utf-8" />
<meta name="viewport" content="width=device-width, initial-scale=1" />
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
[... 12 more head elements folded ...]
<meta name='robots' content='index, follow, max-image-preview:large, max-snippet:-1, max-video-preview:-1' />
[... 1 more head element folded ...]
<title>Mobile App Monetization | Verve</title>
<meta name="description" content="Grow your in-app revenue with premium demand and high-impact ad experiences from the highest brand and performance bidders." />
<link rel="canonical" href="https://verve.com/performance-marketplace-for-publishers/" />
[... 38 more head elements folded ...]
<meta name="generator" content="performance-lab 4.2.0; plugins: image-prioritizer, nocache-bfcache, speculation-rules, view-transitions">
<meta name="generator" content="view-transitions 1.2.1">
[... 5 more head elements folded ...]
<meta name="generator" content="speculation-rules 1.7.0">
<meta data-od-replaced-content="optimization-detective 1.0.0-beta7" name="generator" content="optimization-detective 1.0.0-beta7; url_metric_groups={0:complete, 480:populated, 600:populated, 782:complete}">
<meta name="generator" content="image-prioritizer 1.0.0-beta4">
[... 6 more head elements folded ...]
</head>
<body class="wp-singular page-template-default page page-id-16160 wp-embed-responsive wp-theme-verve">
<!-- Google Tag Manager (noscript) --><noscript>[... 158 characters folded ...]</noscript><!-- End Google Tag Manager (noscript) --><div
id="svg-sprites"
style="overflow: hidden; position: absolute; width: 0; height: 0; top: -9999px; left: -9999px; clip-path: polygon(0px 0px, 0px 0px, 0px 0px, 0px 0px);"
>
<svg xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink">[... 36,985 characters folded ...]</svg>
</div>
<div id="wrap">
<noscript>
<strong>Warning!</strong>
Your browser does not support JavaScript!
</noscript>
<div id="top-bar">
<header id="header" role="banner">
<nav role="navigation" class="navbar navbar-expand-lg">
<div class="align-self-stretch d-flex justify-content-start align-items-center gap-3">
<a href="#main" class="visually-hidden-focusable text-nowrap text-body-sm focus-ring m-0">
Skip navigation
</a>
<a
href="https://verve.com/"
class="navbar-brand flex-shrink-0"
rel="home"
title="Verve"
>
<?xml version="1.0" encoding="UTF-8"?>
<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 85 20" fill="#060723">[... 3,149 characters folded ...]</svg>
</a>
</div>
<button
class="navbar-toggler collapsed ms-auto"
type="button"
data-bs-toggle="collapse"
data-bs-target="#main-menu"
aria-controls="main-menu"
aria-expanded="false"
aria-label="Toggle menu"
>
<span class="visually-hidden">Menu</span>
<span class="navbar-toggler__line navbar-toggler__line--top"></span>
<span class="navbar-toggler__line navbar-toggler__line--bottom"></span>
</button>
<div class="navbar-collapse collapse align-self-stretch" id="main-menu">
<ul class="navbar-nav navbar-nav--main flex-lg-nowrap justify-content-start justify-content-lg-center mx-auto">
<li class="menu-item menu-item-type-custom menu-item-object-custom menu-item-has-children menu-item-12672 nav-item dropdown">
<a
href="#"
class="nav-link dropdown-toggle"
role="button"
data-bs-toggle="dropdown"
data-bs-display="static"
data-bs-auto-close="outside"
aria-expanded="false"
tabindex="0"
>
<span>For Advertisers</span>
<svg
viewBox="0 0 16 16"
><use xlink:href="#sprite-angle-down"></use></svg>
</a>
<ul class="dropdown-menu">
<li class="dropdown-eyebrow">
<div
class="eyebrow d-flex justify-content-center align-items-center text-uppercase dropdown-header text-uppercase"
>For Advertisers</div>
</li>
<li class="menu-item menu-item-type-post_type menu-item-object-page menu-item-12673 menu-item--link">
<a
href="https://verve.com/brand-and-agency-media/"
class="dropdown-item dropdown-item--link "
tabindex="0"
>
<span class="dropdown-item--link__icon">
<svg
viewBox="0 0 16 16"
class="d-block" ><use xlink:href="#sprite-brand-agency"></use></svg>
</span>
<div>
<span class="dropdown-item--link__title">Brand and Agency Media</span>
<span class="dropdown-item--link__desc text-body-sm">Illuminate new signals to drive outcomes.</span>
</div>
</a>
</li>
<li class="menu-item menu-item-type-post_type menu-item-object-page menu-item-14670 menu-item--link">
<a
href="https://verve.com/cpg-and-shopper-marketing/"
class="dropdown-item dropdown-item--link "
Shown with 122 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 248 KB.
Reading view the text a plain-fetch client can extract
title: Mobile App Monetization | Verve
Turn every tap into potential
Skip navigation Menu For Advertisers For Advertisers Brand and Agency Media Illuminate new signals to drive outcomes. CPG and Shopper Marketing Make every moment instantly shoppable. Performance Marketing Acquire app users in a privacy-first world. Retail Media Updates Evolution of intent: How LLM intent data helps advertisers get ahead For Publishers For Publishers Mobile App Monetization Maximize yield on mobile apps. Multi-channel Monetization Monetize cross-channel inventory. Audience Growth Reconnect with audiences across search, AI, and social. Integration Center Integrate flexibly across SDK and OpenRTB connection. Updates Publishers need partners, not pipes, to be premium For DSPs For DSPs Mobile App Growth Find high-value users on mobile. Omni-channel Growth Reach audiences across every screen. Deals Library Activate curated, audience-enriched deals. Integration Center Connect and scale with OpenRTB workflows. Updates Everyone sells premium media. Almost none can prove it. Company Company About Careers Investors Updates Verve Group launches Retail Media, delivering the first validated closed loop between mobile advertising and retail purchase Resources Resources Blog Case Studies Reports Events Press Updates New research: How marketers define and evaluate media value Login PubNative Smaato: SPX Contact Login PubNative Smaato: SPX Contact Performance+ Marketplace (formerly PubNative) Turn every tap into potential Grow your app
849 more words follow in the initial HTML.
| Check | Result | Detail |
|---|---|---|
| H1 in the initial HTML | Found one H1 | First H1: Turn every tap into potential |
| First 200 words in the initial HTML | Found 200 of 200 words | The initial HTML carries 1049 words of visible text; the first 200 are marked in the left pane. |
| llms.txt present and linked | Note present, not linked | 824 bytes, 7 links. Structure grade A (6 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 BreadcrumbList, EntryPoint, ImageObject, ListItem and 7 more | 11 schema.org types in JSON-LD blocks on the home page: BreadcrumbList, EntryPoint, ImageObject, ListItem, Organization, PropertyValueSpecification, QuantitativeValue, ReadAction, SearchAction, 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 pubnative.net.
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