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: 4 of 6 checks found.
Initial HTML what a plain fetch receives
<!DOCTYPE html><!-- This site was created in Webflow. https://webflow.com --><!-- Last Published: Wed Nov 04 2026 15:46:43 GMT+0000 (Coordinated Universal Time) -->
<html data-wf-domain="webflow-prod.typeform.com" data-wf-page="66ffe2174aa8e8d5661c2710" data-wf-site="66ffe2174aa8e8d5661c2708" lang="en">
<head>
<meta charset="utf-8"/>
[... 1 more head element folded ...]
<title>Form Builder with AI Automation | Typeform
</title>
<link rel="alternate" hrefLang="x-default" href="https://www.typeform.com/"/>
<link rel="alternate" hrefLang="en" href="https://www.typeform.com/"/>
<link rel="alternate" hrefLang="es" href="https://www.typeform.com/es"/>
<link rel="alternate" hrefLang="fr" href="https://www.typeform.com/fr"/>
<meta content="Build AI-powered forms that get 3.5x more data — then trigger automated workflows to enrich leads, follow up, and grow revenue. No code. Start free." name="description"/>
[... 7 more head elements folded ...]
<meta content="width=device-width, initial-scale=1" name="viewport"/>
<meta content="Webflow" name="generator"/>
[... 9 more head elements folded ...]
<link href="https://www.typeform.com" rel="canonical"/>
[... 57 more head elements folded ...]
</head>
<body>
<div class="page-wrapper">
<div class="page-hero-5050_container container cc-skip"><a href="#content" class="screen-reader-link">Skip to main content</a>
</div>
<div class="ds2-code">
<div class="w-embed">
<style>[... 1,873 characters folded ...]
</style>
</div>
<div class="w-embed w-script">
<script src="https://cdn.jsdelivr.net/npm/gsap@3.14.2/dist/gsap.min.js">
</script>
<script src="https://cdn.jsdelivr.net/npm/gsap@3.14.2/dist/ScrollTrigger.min.js">
</script>
<script>[... 321 characters folded ...]
</script>
</div>
<div class="w-embed w-script"><!-- 5050 DOM Manipulation v2.0 -->
<script>[... 772 characters folded ...]
</script>
</div>
<div class="w-embed">
<style>[... 1,247 characters folded ...]
</style>
</div>
<div class="w-embed">
<style>[... 2,984 characters folded ...]
</style>
</div>
<div class="w-embed">
<style>[... 238 characters folded ...]
</style>
</div>
<div class="w-embed">
<style>[... 418 characters folded ...]
</style>
</div>
</div>
<div class="announcement-banner_wrapper">
<div class="w-dyn-list">
<div role="list" class="w-dyn-items">
<div role="listitem" class="w-dyn-item">
<div class="cc_announcement-banner-attributes code w-embed"><span cc-t-announcement-banner-promo="false"></span>
<span cc-t-announcement-banner-active="true"></span>
<span cc-t-announcement-banner-message="mcp-campaign-banner"></span>
<span cc-t-announcement-banner-value="mcp-campaign-banner"></span>
</div>
<div id="mcp-campaign-banner" data-banner-item="banner" data-banner-dismissable="true" style="color:white;background-color:#3e3040" class="announcement-banner_wrap">
<div class="announcement-banner_content-wrapper">
<p class="announcement-banner_text">Connect Claude, ChatGPT, or any MCP-ready assistant to your Typeform account.
</p>
<div class="announcement-banner_button-wrap"><a id="announcement-banner-primary-link" setting-size="announcement" href="/mcp" class="text-button is-banner w-inline-block">
<div class="text-button_label">
<div>Try it now
</div>
<div class="text-button_overline-component">
<div style="background-color:white" class="text-button_active-underline">
</div>
<div style="background-color:white" class="text-button_idle-underline is-banner">
</div>
</div>
</div></a>
</div>
</div><button data-banner-item="close-button" aria-label="close announcement banner" class="announcement-banner_dismiss-button">
<div class="announcement-banner_icon w-embed">
<svg xmlns="http://www.w3.org/2000/svg" width="100%" height="100%" viewBox="0 0 24 24" fill="none" preserveAspectRatio="xMidYMid meet" aria-hidden="true" role="img">[... 583 characters folded ...]
</svg>
</div></button>
</div>
</div>
</div>
</div>
<div class="code">
<div class="cc_announcement-banner_code w-embed w-script">
<script>[... 874 characters folded ...]
</script>
</div>
</div>
<div class="cc_announcement-banner code w-embed">
<style>[... 149 characters folded ...]
</style>
</div>
<div class="cc_t-announcement-banner code w-embed w-script"><!-- banner.js
<script src="http://127.0.0.1:5500/_code/banner.js">
</script>
-->
<!-- original -->
<script>[... 1,760 characters folded ...]
</script>
</div>
</div>
<nav data-show-progress-bar="false" data-wf--section-header--variant="dark" class="header_wrap w-variant-354e2c60-bfb3-4013-cc30-d82c0d4535ca">
<div class="cc code">
<div class="cc_settings code w-embed">
<style>[... 7,227 characters folded ...]
</style>
</div>
<div class="cc-atoms code w-embed">
<style>[... 3,556 characters folded ...]
</style>
</div>
<div class="cc-molecules code w-embed">
<style>[... 6,097 characters folded ...]
</style>
</div>
<div class="cc_sections code w-embed">
<style>[... 10,068 characters folded ...]
</style>
</div>
<div class="cc-global code w-embed"><!-- Reset default button styles -->
<style>[... 226 characters folded ...]
</style>
<style>[... 2,269 characters folded ...]
</style>
</div>
<div class="cc_legacy_theming code w-embed">
<style>[... 13,734 characters folded ...]
</style>
Shown with 128 long blocks (scripts, styles, long tags) folded into a marker that says how many characters they hide; line breaks added before block tags because the source is minified; the pane stops after the first 200 words; the page is 313 KB.
Reading view the text a plain-fetch client can extract
title: Form Builder with AI Automation | Typeform
No H1 in the initial HTML
Skip to main content Connect Claude, ChatGPT, or any MCP-ready assistant to your Typeform account. Try it now Platform Platform Platform overview What is Typeform? Typeform AI Your AI know-pilot Typeform MCP New Use Typeform from your AI tools Growth Flow New Automated workflows for GTM teams Research Flow New AI-moderated research studies Contacts & Automations Automated workflows to grow your business Video engagement Interactive video forms Analytics and reporting Answers you can act on Integrations Connect all your apps Tools Form builder Survey maker Quiz maker Test maker Poll builder Application form builder Landing page builder NPS form builder Registration form builder Short form builder TEMPLATES Free form, survey, and quiz templates Choose one → Research Flow Run in-depth AI-moderated studies in hours Learn more → Solutions TEAMS Marketing For B2B and B2C marketing Product For product, UX, and research Human resources For HR, ops, and talent Customer success For CS and education USE CASES Lead generation Employee onboarding Employee satisfaction Employee engagement Customer feedback View all use cases → Plans Core Plans for everyone Growth New Plans for GTM teams Research Flow New Plans for research teams Talent Plans for HR and people teams Enterprise Plans for larger
826 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 1026 words of visible text; the first 200 are marked in the left pane. |
| llms.txt present and linked | Note present, not linked | 4720 bytes, 23 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 | 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 Organization, Person, PostalAddress | 3 schema.org types in JSON-LD blocks on the home page: Organization, Person, PostalAddress. |
| 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 typeform.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