Baseframe field notes
A successful response. The wrong page.
Own-site check · September 27, 2026
This example uses Baseframe Kinetics’ own public website. It is not a customer case study, a Shopify migration, or evidence of saved revenue.
The finding: a missing page looked successful
We requested a deliberately nonexistent path: /baseframe-missing-route-check-20260927/. The server returned HTTP 200 and the homepage title. The expected response was 404. A check that only looked for successful HTTP status would miss this mismatch.
Visitors need a clear missing-page message. Crawlers should receive a status that matches the requested content. No ranking or revenue impact was measured.
What we checked
| Request | Expected | Observed |
|---|---|---|
| Homepage | 200 | 200 |
| www /guides/ | 301 to apex, then 200 | 301 → 200 |
| Apex /guides/ | 200 | 200 |
| Deliberately missing path | 404 | 200, homepage content |
| Worker source path | 404 | 404 |
| Private archive path | 404 | 404 |
Correction and verification
We added a dedicated missing-page document. Cloudflare documents that sites without this document use a homepage fallback. The repeat check returned 404 for the missing path. The other five checks still matched their expected outcomes.
Download the timestamped before results (JSON). Download the timestamped repeat results (JSON). Inspect the pass fields and request chains rather than assuming a fix worked.
Limits of this example
Six selected requests are not a full crawl. These are point-in-time HTTP checks with a maximum of five redirects; they do not render JavaScript, measure search traffic, establish content relevance across a catalog, or prove every private path is protected. A merchant migration needs its own agreed URL inventory and destination expectations.