Findings · 2026-09-23 · By VSNARY | Emmanuel Orta
Correction: the owner's own scans came back locked
For a time the site owner's scans came back gated like a stranger's while the report page showed everything. No score or customer was affected. The lesson is about testing gated content.
On 23 September 2026 the owner of crawlcheck.io found that a scan run from the homepage came back the way a stranger's does, with the top finding in full and the rest locked, while the report page for the same scan opened in full. Two parts of the site decided separately who may see a full result, and one of them did not recognise the owner. Both now use one decision. No score, stored record or customer was affected.
What was seen #
On the evening of 23 September the owner reported that his access did not work on scans. The site recognised him everywhere else. A scan he ran from the homepage still returned the most severe finding in full and every other finding as a locked title. A second later, the report page for the same scan showed everything.
| Where | Owner's view before | After |
|---|---|---|
| Report page | full | unchanged |
| Scan result on the homepage | top finding in full, the rest locked | full |
| Anonymous visitor, either place | gated | gated, unchanged |
What was wrong #
The scan result and the report page each decided, in their own way, who may see a full result. The report page counted owner access; the scan result did not. Each was consistent with itself, and they disagreed with each other. The stored record was always complete, so nothing measured or saved was wrong, only what one screen showed.
What changed #
There is now one access decision, and every place that shows a result reads it. The fix was tested both ways before it shipped: the owner's scan had to come back in full, and an anonymous scan had to stay gated exactly as before. Both held, and the same two readings were repeated on the live site after release. What a licence opens is on the pricing page.
The lesson for anyone running gated content #
Request the same record, as the same person, through every route that returns it, and compare the results. Then add one request that should be refused. An unlock that passes only an allowed-reader test has not shown it is an unlock; it may be a gate that stopped working. Testing each surface on its own is how this hid: every existing test passed. It is the same rule as measuring the thing the label claims, not the label, and the same family as the paywall that said a site was clean.
Share this finding:LinkedInXEmailFollow Emmanuel on LinkedIn
Questions this post answers
Why did the owner's scans come back locked?
The scan result and the report page decided separately who may see a full result. The report page recognised owner access and the scan result did not, so the owner's scan was gated like a stranger's.
Did this change any score or stored record?
No. The stored record was always complete. Only what one screen showed the owner was affected.
Were paying customers affected?
No. Licence holders and signed-in customers were always recognised. The only reader wrongly refused was the site owner.
How should gated content be tested?
Request the same record as the same person through every route that returns it, and include one request that should be refused, so the test proves both that the gate opens for the right reader and stays shut for everyone else.
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, and placement is never for sale.
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.