CrawlCheck

Agent view · Findings · 2026-11-13

A newsletter form that lost every sign-up

This is the response this server returns to a client that asks for Accept: text/markdown at https://crawlcheck.io/blog/a-newsletter-form-that-lost-every-sign-up: 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/a-newsletter-form-that-lost-every-sign-up>; 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
bytes11,038
words1,569
sha-2560abc1a8adffbf65124f3dc6aec1d5ad76b54c097ce9d7498cab24450b69af195
repr-digestsha-256=:Crwait/79lEk89xq7B1a12tUwJfOnXSYyrJEULaa8ZU=: ← matches the body shown
signature-inputsig1=("@authority";req "@path";req "repr-digest" "content-type");created=1795181429;expires=1795185029;keyid="1hHmE3fo1rg5Ig70wuFtJ5wBc7G-sUTgUJkxyPWFRps";alg="ed25519";nonce="2eG7NVghAqTsEgv7FYEVew";tag="crawlcheck-page"
signaturesig1=:HPrP6PIRfLhayEpRHa5jbHnyZ82gQB9OhJ1POdaP0wmARoO3isbhaqyLmKJsCt+L2Lx7zOKi+187a9n2cld4Cg==:
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-11-13 · By [VSNARY | Emmanuel Orta](/author)

# A newsletter form that lost every sign-up

The form looked fine and showed no error to us for as long as nobody tested it. Two small defects meant no address ever arrived.

On an online shop we run, the home page newsletter form had never worked from a browser. The email field had no name attribute, so the browser sent no address. The page was also cached with a security token that had expired, so every submit was rejected. We found it on 13 November 2026 by submitting the form ourselves. Fixing it took two changes: name the field, and fetch a fresh token when the form is sent.

On this page

- What was broken
- Why nobody noticed
- How we found it
- The fix
- Test yours in two minutes

Two defects: what the visitor saw, what actually happened

The email field had no name attribute

What the visitor saw

A normal field they could type in

What actually happened

The browser left the address out of the request

The cached page carried an expired security token

What the visitor saw

The same page as everyone else

What actually happened

The server rejected every submit as invalid

This is a case from one of our own sites, a small online shop. It is here because the same two defects are easy to have and hard to see.

## What was broken #

| Defect | What the visitor saw | What actually happened |
| --- | --- | --- |
| The email field had no name attribute | A normal field they could type in | The browser left the address out of the request |
| The cached page carried an expired security [token](/glossary/token) | The same page as everyone else | The server rejected every submit as invalid |

Either one alone would have lost the sign-up. Together they meant that nothing a visitor typed could reach the list.

## Why nobody noticed #

A form that fails this way does not throw an error anyone on the team sees. The page loads, the field accepts text, the button works. The subscriber list simply does not grow, and a list that does not grow looks like a marketing problem, not a broken form. We do not know how long it was in this state.

## How we found it #

We were auditing the site and submitted the form with a test address, then looked at the request the browser sent. The body had no email in it. Sending the address by hand with a fresh token worked, which separated the two causes.

## The fix #

The field now has a name and an autocomplete hint. When the form is submitted, a fresh token is fetched from an uncached copy of the page before the request goes on, so page caching and the form no longer fight each other. We tested it at phone and desktop widths and confirmed a sign-up arrives.

## Test yours in two minutes #

Open your site in a private window, as a visitor would get it from the cache. Open the browser's network panel, submit the form with an address you control, and check three things: the request body contains the address, the response is a success, and the address shows up where sign-ups are stored. Do this after every change to caching, and on every form that matters, including [the ones that send you mail](/blog/one-character-of-undeliverable-email).

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%2Fa-newsletter-form-that-lost-every-sign-up%3Futm_source%3Dlinkedin%26utm_medium%3Dsocial%26utm_campaign%3Dshare)[X](https://twitter.com/intent/tweet?url=https%3A%2F%2Fcrawlcheck.io%2Fblog%2Fa-newsletter-form-that-lost-every-sign-up%3Futm_source%3Dx%26utm_medium%3Dsocial%26utm_campaign%3Dshare&text=A%20newsletter%20form%20that%20lost%20every%20sign-up)[Email](mailto:?subject=A%20newsletter%20form%20that%20lost%20every%20sign-up&body=https%3A%2F%2Fcrawlcheck.io%2Fblog%2Fa-newsletter-form-that-lost-every-sign-up)[Follow Emmanuel on LinkedIn](https://www.linkedin.com/in/emmanuelorta)

## Questions this post answers

### Why would a form send nothing even though the field has text in it?

A browser only sends fields that have a name attribute. A field without one can be typed into but is left out of the request.

### How does page caching break a form?

Many forms carry a short-lived security token. If the page is cached, visitors get an old token, and the server rejects the submit once it has expired.

### How do I test a sign-up form properly?

Submit it from a private window with an address you control, check the request body in the network panel, and confirm the address arrives where sign-ups are stored.

### How long was the form broken?

We do not know. Nothing recorded the failures, which is the reason to test forms directly instead of waiting for an error.

## Related findings

[2026-09-30 Five days of our alerts went to an address with no mailbox After a mail move, our alert address had no mailbox. For five days every alert said sent and none arrived. Why checks passed, and](/blog/five-days-of-our-alerts-went-to-an-address-with-no-mailbox)[2026-08-28 Does llms.txt work? What is known and how to test it Does llms.txt work? What is verifiable, what we measured on our own site, and the server-log test with IP verification that answer](/guides/does-llms-txt-actually-work)[2026-10-15 Share of preflight, October 2026: 0 of 5,643 requests Seven connected sites verified 5,643 AI agent requests in October 2026 to date. None carried a CrawlCheck receipt; the 68 accepted](/blog/share-of-preflight-october-2026)

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.

**Registry:** [MCP: Operator](/registry/mcp/operator) · [MCP](/registry/mcp) · [AI policy](/registry/aipolicy) | **Pages:** [IP ranges](/data/ip-ranges) · [Contact](/contact) · [Conduct: Google notebooklm](/agents/conduct/google-notebooklm) | **Datasets:** [Technologies: Trustpilot](/datasets/technologies/trustpilot) · [Problems: Robots is HTML](/datasets/problems/robots-is-html) | **Blog:** [14 of 43 crawlers in our catalogue were classed wrong](/blog/fourteen-of-43-crawlers-in-our-catalogue-were-classed-wrong) | **Glossary:** [robots.txt](/glossary/robots-txt) · [Late interaction](/glossary/late-interaction) · [Navigational query](/glossary/navigational-query)

[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/a-newsletter-form-that-lost-every-sign-up.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.