CrawlCheck

Agent view · Findings · 2026-09-30

Our extension read a page as 36.5% JavaScript. It was zero.

This is the response this server returns to a client that asks for Accept: text/markdown at https://crawlcheck.io/blog/the-page-our-extension-read-as-36-percent-javascript-was-zero: fetched when you opened this page, shown byte for byte. An assistant, a crawler that negotiates markdown, or anything reading our feed gets exactly this. The markdown leaves signed (RFC 9421, key in our key directory), so a crawler can prove the page it read is the page this server sent; the check is shown below.

status200
content-typetext/markdown; charset=utf-8
varyAccept
link<https://crawlcheck.io/llms.txt>; rel="describedby"; type="text/plain", <https://crawlcheck.io/.well-known/api-catalog>; rel="service-desc"; type="application/linkset+json", <https://crawlcheck.io/blog/the-page-our-extension-read-as-36-percent-javascript-was-zero>; rel="cite-as", <https://crawlcheck.io/.well-known/http-message-signatures-directory>; rel="http-message-signatures-directory"
cache-controlpublic, max-age=900, stale-while-revalidate=2400
bytes12,130
words1,688
sha-25639f5acd8749049eeb233a03488becf0653a40ff34cdc4508a9755dda19218401
repr-digestsha-256=:OfWs2HSQSe6yM6A0iL7PBlOkD/NM3EUIqXVd2hkhhAE=: ← matches the body shown
signature-inputsig1=("@authority";req "@path";req "repr-digest" "content-type");created=1795183083;expires=1795186683;keyid="1hHmE3fo1rg5Ig70wuFtJ5wBc7G-sUTgUJkxyPWFRps";alg="ed25519";nonce="_1sXCHwkWb8hEw3HOOryeQ";tag="crawlcheck-page"
signaturesig1=:NWUZfFNpXNynnswrXkvDMfaOg6OiFfzPTUGZSXakHZrBWfmqPp2ydCvn28wmZHHM4jP4jmZAQLOVRg8EaKzPBw==:
verifiedyes — signature by key 1hHmE3fo1rg5Ig70… from https://crawlcheck.io/.well-known/http-message-signatures-directory (directory valid), valid for 3600 more s. Checked here exactly as a crawler would; redo it yourself: https://crawlcheck.io/api/tool/wba
Findings · 2026-09-30 · By [VSNARY | Emmanuel Orta](/author)

# Our extension read a page as 36.5% JavaScript. It was zero.

The CrawlCheck browser extension overstated how much of a page needed JavaScript, for two reasons that both pushed the number up. Version 1.0.2 fixed both.

On 25 September 2026 the CrawlCheck browser extension reported 36.5 percent of a homepage as dependent on JavaScript. The true figure was zero: the same 2,850 words appeared in the raw HTML and the rendered page. Two causes, both inflating: punctuation written as HTML entities in the raw copy did not match the decoded characters in the browser, and the WordPress admin bar shown to a signed-in owner was counted as page text. Version 1.0.2 fixes both, and test pages read 49.9 and 100 percent as expected.

On this page

- What went wrong?
- Why was the wrong number believable?
- What does it mean for your own reading?

Reported JavaScript-only share at each step
as shipped in 1.0.1 36.5%

after full entity decode 11.9%

after admin bar removed 0%

test: injected paragraph 49.9%

test: empty shell, all text by script 100%

The extension compares the raw HTML a server sends with the page a browser shows after JavaScript runs. The text that only appears after rendering is the share a crawler that does not run JavaScript never sees. On 25 September it reported that share as 36.5 percent for a homepage on a site we run. The true figure was zero: 2,850 words in the raw HTML, the same 2,850 words in the rendered page.

## What went wrong? #

**Punctuation spelled two ways.** Raw WordPress HTML writes curly apostrophes, dashes and arrows as entities such as `&#8217;`. The browser shows the characters themselves. The extension did not decode all of these, so every sentence with an apostrophe looked different in the two copies and was counted as appearing only after rendering. Decoding every entity took the reading from 36.5 percent to 11.9.

**The person testing was signed in.** WordPress adds an admin bar for a signed-in owner. It is added by script and never served to visitors or crawlers, but the extension counted it as page text. Removing it took the reading from 11.9 percent to zero.

| Step | Reported JavaScript-only share | Cause |
| --- | --- | --- |
| as shipped in 1.0.1 | 36.5% | entities not decoded in the raw copy |
| after full entity decode | 11.9% | signed-in admin bar counted as page text |
| after admin bar removed | 0% | 2,850 of 2,850 words identical |
| test: injected paragraph | 49.9% | correct |
| test: empty shell, all text by script | 100% | correct |

## Why was the wrong number believable? #

Both errors could only push the reading up, and a third of a page depending on JavaScript is a normal result on many modern sites. So the number looked like a finding, not a fault. It was caught only because we already knew the page was fully server-rendered. The lesson we keep relearning, as with [the image check that counted placeholders](/blog/our-scanner-counted-placeholders-not-photographs), is to test a new reading on a page whose true value you know before trusting it on one you do not.

## What does it mean for your own reading? #

If you use any tool that compares raw and rendered text on a WordPress site, sign out first or use a private window, so the admin bar is not counted. From version 1.0.2 the CrawlCheck extension handles both issues itself. It is still one browser at one moment, so a page that renders differently by screen size or session can read differently. For the crawler side, see [do AI crawlers render JavaScript](/guides/do-ai-crawlers-render-javascript).

**Live, as you read this:** the corpus now holds 570,959 domains across 9,163 scans. The figures in this piece were measured on the date above; this line is not.

CrawlCheck’s dataset when this page loaded: 570,959 sites measured.

Written by

[Emmanuel Orta](/author) · VSNARY

I build CrawlCheck and write everything published here, from measurements the verification layer took. Where a post got something wrong, the correction stays in the post.

[Every post, and where I got it wrong →](/author) · [Follow on LinkedIn →](https://www.linkedin.com/in/emmanuelorta)

Share this finding: [LinkedIn](https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2Fcrawlcheck.io%2Fblog%2Fthe-page-our-extension-read-as-36-percent-javascript-was-zero%3Futm_source%3Dlinkedin%26utm_medium%3Dsocial%26utm_campaign%3Dshare)[X](https://twitter.com/intent/tweet?url=https%3A%2F%2Fcrawlcheck.io%2Fblog%2Fthe-page-our-extension-read-as-36-percent-javascript-was-zero%3Futm_source%3Dx%26utm_medium%3Dsocial%26utm_campaign%3Dshare&text=Our%20extension%20read%20a%20page%20as%2036.5%25%20JavaScript.%20It%20was%20zero.)[Email](mailto:?subject=Our%20extension%20read%20a%20page%20as%2036.5%25%20JavaScript.%20It%20was%20zero.&body=https%3A%2F%2Fcrawlcheck.io%2Fblog%2Fthe-page-our-extension-read-as-36-percent-javascript-was-zero)[Follow Emmanuel on LinkedIn](https://www.linkedin.com/in/emmanuelorta)

## Questions this post answers

### What does the extension's JavaScript-only share measure?

The share of a page's visible text that appears in the rendered page but not in the raw HTML the server sent, which is the share a crawler that does not run JavaScript never sees.

### Why did it report 36.5 percent on a page that needed no JavaScript?

Punctuation written as HTML entities in the raw copy did not match the decoded characters in the browser, and the WordPress admin bar shown to a signed-in owner was counted as page text.

### What changed in version 1.0.2?

It decodes every entity in both copies, ignores differences that are only punctuation, and removes the admin bar before comparing.

### How was the fix tested?

On the original page, which now reads zero, and on two test pages: one with a paragraph added by script, which reads 49.9 percent, and one whose whole body is written by script, which reads 100 percent.

### Should I sign out before testing my own WordPress site?

Yes, with any raw-versus-rendered tool. The admin bar is only shown to signed-in users and is not what visitors or crawlers receive.

## Related findings

[2026-11-13 14 of 43 crawlers in our catalogue were classed wrong CrawlCheck classed 14 of 43 crawlers wrongly until 13 November 2026, including Amazonbot, msnbot and Yandex. What was wrong and wh](/blog/fourteen-of-43-crawlers-in-our-catalogue-were-classed-wrong)[2026-09-23 Sites measured is not people: what our own logs showed Our homepage figure counts measured domains, not people. A week of our own logs: crawlers on the pricing page, about six outside s](/blog/our-homepage-says-6557-sites-measured-six-people-ran-a-scan-this-week)[2026-11-14 One in four MCP hosts changed its tools in four days. Nothing told the agent. We re-read every public MCP server. 706 of 3,167 hosts changed their tool list in four days, and most changes kept the same versio](/blog/one-in-four-mcp-hosts-changed-its-tools-in-four-days)

The main product

Found this on your own site? **We fix it for $100.**

Scan free to see where you stand. The fix is one site, every finding implemented and re-measured, with a sealed before and after.

[Fix it all — $100](https://buy.stripe.com/4gM00j7OjawhdLEdyR2VG0v)
[What it covers](/pricing#fix) · [scan first, it is free](/)

Free browser extension

Check this on any site you open, **without leaving the page.**

CrawlCheck for Chrome grades every site you visit A–F and shows, from your own browser, what search engines and AI assistants are actually served. Free, no account.

[Add to Chrome — free](https://chromewebstore.google.com/detail/plgjengobhbdmbgckiiaaflgiepdbcpi?utm_source=crawlcheck.io&utm_medium=post)
[What it does](/extension)

Write for the library

Measured something yourself? **Submit an article.**

Send your finding, the data and the method. A person reads every submission and replies by email; accepted articles are published under your name with a link to your study. Free to submit. Articles are accepted on merit; no one can pay to have one published.

[Submit an article](/submit-finding#send)
[How it works](/submit-finding) · a reply within about a week

Spotted a mistake or a bug on this page? [Report an error](/report-error?k=article). Confirmed errors are fixed and logged on the [corrections page](/corrections).

## Comments

Comments are read before they appear. Nothing is published automatically, and no account is needed. An AI agent with a published signing key can post without the queue: it signs the request and the signature is checked against its own domain ([how](/api/comment/signed)). Those appear at once, marked *verified*.

Send for review

Writing about this? [Facts, live figures and marks](/press) — every number on that page is dated and traceable to a scan.

[All findings](/blog) · [The dataset](/data) · [How the dataset works](/policy)

We read your site the way crawlers do, from our own network, and every report says exactly what was asked for and what came back. [Who runs this](/author) · [Press kit](/press) · [Videos](/videos) · [Evidence for disputes](/evidence) · [YouTube](https://www.youtube.com/@crawlcheck) · [hello@crawlcheck.io](mailto:hello@crawlcheck.io)

#### How we measure, and our own machine files

CrawlCheck reads every site as itself. Its crawler-identity tests send named user-agent strings from its own network, never from an operator’s published range, so a site that verifies crawlers can tell them apart; every report says so. Results reflect what an anonymous non-browser client receives. [What we collect and how to opt out](/policy) · [how every report is timestamped](/proof) · [who runs this](/author) · [press kit](/press) · [hello@crawlcheck.io](mailto:hello@crawlcheck.io).

**Second vantage:** the [browser extension](/extension) measures what crawlers are served from your own address and after your JavaScript runs — the half this server cannot see. From 1.0.0 it sends the domain you ask about, on one button, and anonymous usage counts you can switch off; from 1.0.3 a footer switch turns off the hostname lookup for the grade on the icon; from 1.0.4 a share switch, on by default, sends a signed Two-vantages reading (status, size, words and a hash per identity; never page text); from 1.0.16 chips send the hostnames of search results and AI citations while the chips and grade switches are on; from 1.0.17 a readings switch, on by default, sends one signed page reading a day (numbers, the hostname and the page address with the query removed; never in incognito; at most 40 a day) and only while the share and grade switches are also on. Earlier versions send nothing.

**Our own machine layer for the agentic web:** [llms.txt](/llms.txt) · [llms-full.txt](/llms-full.txt) · [agents.md](/agents.md) · [SKILL.md](/SKILL.md) · [entitymap.json](/entitymap.json) · [media kit](/.well-known/media-kit.json) · [MCP server card](/.well-known/mcp/server-card.json) · [API catalog](/.well-known/api-catalog) · [OpenAPI](/openapi.json) · [robots.txt](/robots.txt) · [sitemap.xml](/sitemap.xml) · [security.txt](/.well-known/security.txt) — every one named in robots.txt, which is exactly what we check for on yours.

**Pages:** [SDK](/sdk) · [Certificates](/certificates) · [Next.js](/fix/nextjs) · [Conduct: Storebot google](/agents/conduct/storebot-google) | **Registry:** [MCP: Operator](/registry/mcp/operator) · [MCP](/registry/mcp) · [theassemblync.com](/registry/theassemblync.com) · [Trade: Plumbing](/registry/trade/plumbing) | **Datasets:** [Oregon](/datasets/state/oregon) · [Technologies: Optimizely](/datasets/technologies/optimizely) · [Problems: Declared sitemap refused](/datasets/problems/declared-sitemap-refused) | **Blog:** [A newsletter form that lost every sign-up](/blog/a-newsletter-form-that-lost-every-sign-up)

[Contact](/contact) · [Partnerships](/partnerships) · [Terms of service](/terms) · [Refund policy](/refunds) · [Trust center](/trust) · [Subprocessors](/subprocessors) · [Changelog](/changelog) · [Report an error](/report-error)

Same body as a file: /blog/the-page-our-extension-read-as-36-percent-javascript-was-zero.md · as data: /feed.json · what we tell agents site-wide: /llms.txt, /agents.md. To see any other site this way, from your own browser, after its JavaScript runs: the browser extension.