Every page has two audiences: the person looking at it and the machine reading over their shoulder. The semantic web asked publishers to mark meaning; today’s models scrape the human page; the next web must decide how machines act. Paste one URL to compare the human page, the HTTP response, and the browser-rendered result. Fetched server-side, honestly, as AadharshBot.
The machine web, 2026-08:56.0% of HTML requests are bots10.0% of desktop pages have llms.txt>10k public MCP servers$898K in x402 volume over 30 days
Try:
Compare puts Human, HTTP Machine, and Browser Run side by side. Predict the machine pane; the miss is the lesson.
Human view · the live page
Machine view
Server-rendered machine summary. JavaScript can enhance this into the full selected lens; this fragment is the no-script evidence floor.
Observed document observed
The minimum contract a machine can recover from this response.
url
https://en.wikipedia.org/wiki/Semantic_Web
title
Semantic Web - Wikipedia
response
200 OK
Lens field evidence
75/100
local standards mirror
13/100
content-type
text/html; charset=UTF-8
payload
431420 B
headings
23
fetched as
AadharshBot/1.0 (+https://aadhar.sh/bot)
Available surfaces human-only
Evidence found during the server-side inspection.
robots.txt
Selected state anatomy
View: both. The browser enhancement can open the complete lens without changing the URL.
Browser Run · Rendered
Browser Run view. Ask Cloudflare to open this URL in a real headless browser and return the rendered page, screenshot, Markdown, accessibility tree, and a clear WebMCP lab boundary.
This is opt-in: browser execution is slower and can run page JavaScript. Runtime WebMCP discovery is reported separately and requires the Chrome-beta lab.
200 OKComparetext/html; charset=UTF-8431420 B660 msfetched as AadharshBot/1.0 (+https://aadhar.sh/bot)