CrawlCheck

Findings · 2026-11-13 · By

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.

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 #

DefectWhat the visitor sawWhat actually happened
The email field had no name attributeA normal field they could type inThe browser left the address out of the request
The cached page carried an expired security tokenThe same page as everyone elseThe 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.

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

Share this finding:LinkedInXEmailFollow Emmanuel on LinkedIn

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

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.

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.

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

How it works · a reply within about a week

Spotted a mistake or a bug on this page? Report an error. Confirmed errors are fixed and logged on the corrections page.

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). Those appear at once, marked verified.

Writing about this? Facts, live figures and marks — every number on that page is dated and traceable to a scan.

All findings · The dataset · How the dataset works