CrawlCheck

Findings · 2026-10-14 · By

An access rule on one path locked our customers out

On 14 October 2026 an access rule meant for staff-only pages also covered customer sign-in, which shared the same address. For an hour, the Sign in link on 247 pages led to a login customers could not pass.

On 14 October 2026, from 10:56 to 11:56 AM MDT, CrawlCheck customers who clicked Sign in reached a login they could not pass. An access rule added to protect staff-only pages also covered customer sign-in, because both used the same address, and a path rule covers everything beneath that path. A sweep of the site's links found the 247 affected pages. Customer sign-in moved to its own address, /signin, along with its form and sign-in email. No data was exposed; the failure only refused access.

Which addresses one path rule covers
The path itself
Covered by the rule?
Yes
A page below it that a form posts to
Covered by the rule?
Yes
A page below it that an emailed link opens
Covered by the rule?
Yes
A different path that only starts with the same letters
Covered by the rule?
No

An access gate in front of chosen paths stops a request before it reaches the site unless the visitor passes the gate's own login. On 14 October 2026 we added one to protect pages only staff should see. For an hour it also locked out the people who pay us.

What did a customer see? #

From 10:56 AM Mountain Time, a customer who clicked Sign in in the site header was sent to the gate's login page, which asked for an email address it would never accept. Customer sign-in, the form it posts to and the address the emailed sign-in link opens all lived under the same path as the staff pages being protected.

Why did one rule catch both? #

A path rule covers that path and everything below it, not every address that starts with the same letters. We tested its reach afterwards, signed out, from outside our network:

Address, relative to the protected pathCovered by the rule?
The path itselfYes
A page below it that a form posts toYes
A page below it that an emailed link opensYes
A different path that only starts with the same lettersNo

That is the right behaviour, and path gates generally work this way. The vendor's documentation on Access application paths describes the inheritance: when no more specific rule exists, a deeper path takes the rules of its parent. It is exactly what caught the customer pages.

How was it found, and what changed? #

Mountain Time, 14 OctWhat happened
10:56 AMAccess rule added for staff-only pages
Just before noonA sweep of every page and all 4,433 internal links finds the Sign in link on 247 pages redirecting to another company's login page
11:56 AMCustomer sign-in moves to /signin; every link, redirect, form and the sign-in email move with it

Not a customer report: the sweep was run before a site rebuild, and a public link that redirects to another domain's login stands out in it (how to run that kind of sweep). The fix was checked by outcome: /signin answers 200 with its forms, the translated pages link to it, and no customer page links to the old address. Anyone with an old bookmark should use /signin. Reports, licence keys and data were never exposed; the failure refused access, it did not grant any.

What should you check before gating a path? #

  1. List every route under the path, including the ones a form posts to and the ones an email links to. No page links to those, so they are the easiest to forget.
  2. Give staff and customers different addresses. A shared sign-in page means any wall in front of one is a wall in front of both.
  3. Fetch your own site signed out after any access change, every page and every link. A public link that redirects to another domain's login page is the signal.
  4. Prefer a specific path to a short one. The shorter the protected path, the more lives under it.

For what a crawler gets when a gate or firewall answers instead of your site, see HTTP status codes for crawlers.

This is one of the corrections CrawlCheck publishes when its own output was wrong. All of them are listed together.

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

Share this finding:LinkedInXEmailFollow Emmanuel on LinkedIn

Questions this post answers

Does a path-based access rule cover subpaths?

Yes. In our test a rule on one path also gated the pages beneath it, including a form target and an emailed-link address, while a different path that only shared the first letters reached the site normally. The vendor's documentation says a deeper path inherits its parent's rules when no more specific rule exists.

Why could CrawlCheck customers not sign in on 14 October 2026?

From 10:56 to 11:56 AM MDT, customer sign-in shared an address with staff-only pages that had just been put behind an access rule. Customer sign-in moved to its own address.

Where do I sign in to CrawlCheck?

At crawlcheck.io/signin.

Was any customer data exposed?

No. The failure only refused access to the sign-in page; it did not grant access to anything. Reports, licence keys and data were unaffected.

How do I avoid gating customer pages by accident?

List every route under each path you protect, including form targets and links sent by email, keep staff and customer sign-in on different paths, and fetch your whole site signed out after any access change.

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