Agent view · Findings · 2026-09-30
Eight contradictions in our own copy, rechecked
This is the response this server returns to a client that asks for Accept: text/markdown at https://crawlcheck.io/blog/eight-contradictions-in-our-own-copy-rechecked: 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.
| status | 200 |
|---|---|
| content-type | text/markdown; charset=utf-8 |
| vary | Accept |
| 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/eight-contradictions-in-our-own-copy-rechecked>; rel="cite-as", <https://crawlcheck.io/.well-known/http-message-signatures-directory>; rel="http-message-signatures-directory" |
| cache-control | public, max-age=900, stale-while-revalidate=2400 |
| bytes | 12,982 |
| words | 1,836 |
| sha-256 | 1d3290b9e426245870f286c6172daeebf106284cd9d33e0cea8442b0f957b8cb |
| repr-digest | sha-256=:HTKQueQmJFhw8obGFy2u6/EGKEzZ0z4M6oRCsPlXuMs=: ← matches the body shown |
| signature-input | sig1=("@authority";req "@path";req "repr-digest" "content-type");created=1795183083;expires=1795186683;keyid="1hHmE3fo1rg5Ig70wuFtJ5wBc7G-sUTgUJkxyPWFRps";alg="ed25519";nonce="q328vXj_rmRxW3lwI-czrw";tag="crawlcheck-page" |
| signature | sig1=:5vco5mEKwOu/8ILw6TCIqSLfhOMlh77mh0WK9v4Wmblf8/t6yX6mS7g+0hrlaRkHfxV1NyJSvsEAmAVezfCuCw==: |
| verified | yes — 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) # Eight contradictions in our own copy, rechecked An outside audit listed eight places where crawlcheck.io contradicted itself. Rechecked against the live site: which were real, which were two truths read as one, and the one still wrong. On 25 September 2026 an outside audit listed eight self-contradictions in crawlcheck.io's copy. Rechecked against the live site, three were two true statements read as one false one and are now stated together, two were real and were fixed, two were consistent as written, and one was still false: a post claiming no scanned domain is ever named in anything CrawlCheck publishes, although the directory and registry name sites. That sentence is now scoped correctly. On this page - The one that was still wrong - Why two true statements read as a contradiction - The two real ones - The lesson for your own site Eight claims from the audit, and where each stands 1. The count of crawler identities differed between pages What the copy says now One figure everywhere, from one source State fixed 2. Measured sections and scored sections gave two different numbers What the copy says now Both numbers, said together State two truths, now in one place 3. Agency 'no daily cap' versus a monthly API quota What the copy says now The cap-free scanning is on the site; the quota belongs to the API product State two products 4. 'No scanned domain is ever named' versus a directory that names domains What the copy says now Scoped to the article and the dataset's aggregate figures State was false; corrected 5. Report 'regenerates' versus a retention period What the copy says now One sentence states both State two truths, now in one place 6. 'Every request identifies as CrawlCheck' versus fetches under named crawler user-agents What the copy says now The policy page lists every identity sent State fixed 23 September 7. Agency versus a larger plan called Network What the copy says now More than 40 domains: Network, quoted State consistent 8. App 'in build' versus an installable web app What the copy says now In build for iPhone and Android; no web app manifest is served State consistent as written On 25 September an outside audit listed eight places where the site's own copy contradicted itself. Each was rechecked against the live site, not from memory of what had been fixed. | # | The audit's claim | What the copy says now | State | | --- | --- | --- | --- | | 1 | The count of crawler identities differed between pages | One figure everywhere, from one source | fixed | | 2 | Measured sections and scored sections gave two different numbers | Both numbers, said together | two truths, now in one place | | 3 | Agency 'no daily cap' versus a monthly API quota | The cap-free scanning is on the site; the quota belongs to the API product | two products | | 4 | 'No scanned domain is ever named' versus a directory that names domains | Scoped to the article and the dataset's aggregate figures | was false; corrected | | 5 | Report 'regenerates' versus a retention period | One sentence states both | two truths, now in one place | | 6 | 'Every request identifies as CrawlCheck' versus fetches under named crawler user-agents | The policy page lists every identity sent | fixed 23 September | | 7 | Agency versus a larger plan called Network | More than 40 domains: Network, quoted | consistent | | 8 | App 'in build' versus an installable web app | In build for iPhone and Android; no web app manifest is served | consistent as written | ## The one that was still wrong # The post on [what a crawler actually receives](/blog/what-a-crawler-actually-receives) said no scanned domain is ever named in anything CrawlCheck publishes. That stopped being true on 10 September, when the [directory](/directory) and the [registry](/registry) began listing sites by name with their grades. The sentence now says the article and the dataset's aggregate figures name no site, and that the directory and registry do, by a stated method with a dispute route. ## Why two true statements read as a contradiction # Items two, three and five were each correct on their own page. A reader who meets them on different pages cannot tell they are compatible, so the audit's instinct was right. The fix was to put both halves in one sentence. ## The two real ones # The policy page said CrawlCheck identifies itself on every request. It does not: comparing what crawlers receive means fetching under their names. The [policy page](/policy) now lists the identities used. The identity count had drifted between pages as the list grew; it is now one figure wherever it is printed. 19 ## The lesson for your own site # A number printed on more than one page will drift unless every page reads it from one source. A claim that begins *never* or *every* has to be checked against every feature, not only the one it was written beside. The rest of that week's changes are in [the 29 September release notes](/blog/release-notes-29-september-2026-finding-states-sitemap-index-trust-center). 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%2Feight-contradictions-in-our-own-copy-rechecked%3Futm_source%3Dlinkedin%26utm_medium%3Dsocial%26utm_campaign%3Dshare)[X](https://twitter.com/intent/tweet?url=https%3A%2F%2Fcrawlcheck.io%2Fblog%2Feight-contradictions-in-our-own-copy-rechecked%3Futm_source%3Dx%26utm_medium%3Dsocial%26utm_campaign%3Dshare&text=Eight%20contradictions%20in%20our%20own%20copy%2C%20rechecked)[Email](mailto:?subject=Eight%20contradictions%20in%20our%20own%20copy%2C%20rechecked&body=https%3A%2F%2Fcrawlcheck.io%2Fblog%2Feight-contradictions-in-our-own-copy-rechecked)[Follow Emmanuel on LinkedIn](https://www.linkedin.com/in/emmanuelorta) ## Questions this post answers ### How many of the eight contradictions were real? Two were real and fixed, one was still false when rechecked and was corrected, three were two true statements read as one false one and are now stated together, and two were consistent as written. ### Which claim was still wrong? A post said no scanned domain is ever named in anything CrawlCheck publishes. The directory and registry name sites, so the sentence was scoped to the article and the dataset's aggregate figures. ### Does CrawlCheck identify itself on every request? No. To compare what different crawlers receive, it fetches pages under the user-agent strings of named crawlers. The policy page lists them. ### How do you stop a number contradicting itself across pages? Print it from one source everywhere it appears. A hand-typed copy of a changing number will drift as soon as the number changes. ## Related findings [2026-09-01 Seven site types, and the report checks we corrected We ran seven very different sites through every graded check and found some failing sites for non-defects. Which checks changed, a](/blog/we-read-every-scored-row-against-seven-sites-here-is-what-we-unscored)[2026-10-07 Eight weeks of AI crawlers on one site: who was really who 24,627 verified crawler requests to crawlcheck.io in eight weeks: who was real, which names only came forged, and what verified ag](/blog/eight-weeks-of-agent-conduct-who-was-really-who)[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) 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:** [IP ranges](/data/ip-ranges) · [Keys](/keys) · [/](/) · [Listing check](/listing-check) | **Glossary:** [Anchor text](/glossary/anchor-text) · [Hard binding](/glossary/hard-binding) · [TechArticle](/glossary/techarticle) | **Directory:** [Category: AI visibility monitoring](/directory/category/ai-visibility-monitoring) | **Registry:** [centralbuickgmctruck.com](/registry/centralbuickgmctruck.com) · [ecomdly.com](/registry/ecomdly.com) · [kokorikoshoes.gr](/registry/kokorikoshoes.gr) · [prokerala.com](/registry/prokerala.com) [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/eight-contradictions-in-our-own-copy-rechecked.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.