dare.co.uk 404 redirects report — 2026-06-10
Daily top-50 404 paths from Cloudflare Analytics, last 24h. Operationalises feedback_404_redirect_threshold_rule — at ≥50 hits/day, examine and decide whether to redirect editorial 404s to a deserving archive page.
TL;DR
- 392 total 404 hits in the last 24h across 50 distinct paths.
- 0 path(s) over the 50/day threshold needing a redirect decision.
- 35 bot-probe paths — leave 404 (per rule, security signal).
- 0 section-root paths — build index pages, not redirect.
Legacy editorial — decide redirect target
(14 path(s) · 92 total hits)
| Path | Hits | Action | Decision? |
|---|---|---|---|
/cf-fonts/v/newsreader/5.2.10/latin/opsz/italic.woff2 |
20 | examine + decide (rule applies) | |
//site/wp-includes/wlwmanifest.xml |
6 | examine + decide (rule applies) | |
/login |
6 | examine + decide (rule applies) | |
//wp/wp-includes/wlwmanifest.xml |
6 | examine + decide (rule applies) | |
/contact-us |
6 | examine + decide (rule applies) | |
/sitemap.xml |
6 | examine + decide (rule applies) | |
/our-team |
6 | examine + decide (rule applies) | |
/team |
6 | examine + decide (rule applies) | |
/about-us |
6 | examine + decide (rule applies) | |
//web/wp-includes/wlwmanifest.xml |
5 | examine + decide (rule applies) | |
/sse |
5 | examine + decide (rule applies) | |
//2019/wp-includes/wlwmanifest.xml |
5 | examine + decide (rule applies) | |
/wp/marco-pierre-white.png |
5 | examine + decide (rule applies) | |
//wp1/wp-includes/wlwmanifest.xml |
4 | examine + decide (rule applies) |
Favicon paths
(1 path(s) · 11 total hits)
| Path | Hits | Action | Decision? |
|---|---|---|---|
/favicon.ico |
11 | already redirected — verify deploy lag |
Bot-probe paths — leave 404
(35 path(s) · 289 total hits)
| Path | Hits | Action | Decision? |
|---|---|---|---|
/wp-login.php |
21 | leave 404 (security signal) | |
/cdn-cgi/scripts/7d0fa10a/cloudflare-static/rocket-loader.min.js |
19 | leave 404 (security signal) | |
/posts/cropped-ziiiro-celeste.jpeg |
19 | leave 404 (security signal) | |
/cdn-cgi/rum |
19 | leave 404 (security signal) | |
/1.php |
14 | leave 404 (security signal) | |
/aaa.php |
13 | leave 404 (security signal) | |
/gecko-new.php |
12 | leave 404 (security signal) | |
/lock360.php |
10 | leave 404 (security signal) | |
/ioxi-o.php |
9 | leave 404 (security signal) | |
/defaults.php |
8 | leave 404 (security signal) | |
/default.php |
7 | leave 404 (security signal) | |
/randkeyword.php |
7 | leave 404 (security signal) | |
/a.php |
7 | leave 404 (security signal) | |
/configs.php |
7 | leave 404 (security signal) | |
/functions.php |
6 | leave 404 (security signal) | |
/update.php |
6 | leave 404 (security signal) | |
/edit.php |
6 | leave 404 (security signal) | |
/dr.php |
6 | leave 404 (security signal) | |
/ff.php |
6 | leave 404 (security signal) | |
/sitemaps.php |
6 | leave 404 (security signal) | |
/about.php |
6 | leave 404 (security signal) | |
/wp-2019.php |
6 | leave 404 (security signal) | |
/cdn-cgi/content |
6 | leave 404 (security signal) | |
/user.php |
6 | leave 404 (security signal) | |
/like.php |
6 | leave 404 (security signal) | |
/input.php |
6 | leave 404 (security signal) | |
/hehe.php |
5 | leave 404 (security signal) | |
/post.php |
5 | leave 404 (security signal) | |
/mac.php |
5 | leave 404 (security signal) | |
/cookie.php |
5 | leave 404 (security signal) | |
/menu.php |
5 | leave 404 (security signal) | |
/meta.php |
5 | leave 404 (security signal) | |
/ab.php |
5 | leave 404 (security signal) | |
/index.php |
5 | leave 404 (security signal) | |
/chosen.php |
5 | leave 404 (security signal) |
How to apply the decisions
For each row with DECIDE:
- Inspect the path — is it a real legacy URL (old article slug, external referrer link) or accidentally-popular bot noise?
- If editorial: pick a deserving target from the existing archive-page roots:
-
/methods-of-business-design/-/culture-means-thriving-teams/-/fields-notes-from-business-design/-/cinema/-/photography/-/observations/ - Add a 301 to
~/Code/dare-co-uk/_redirects:/<path> /<target> 301 - Commit + push; Cloudflare Pages redeploys in ~30s.
Bot-probe paths stay 404 — redirecting them rewards scanners. Section roots get index-page builds, not redirects, because the underlying content is stunning and deserves its own home.
Generated 2026-06-10 via dare_404_redirects_report.py. Companion to feedback_404_redirect_threshold_rule.
Automated recommendation — maturity ladder
Site housekeeping wants to become a scheduled script + intelligence engine. Criteria are set in the rule (feedback_404_redirect_threshold_rule); this report applies them. Maturity ladder for how the recommendations become action:
Today (v1 — ad-hoc) |
Tomorrow (v2 — programmatic + HITL) |
Future (v3 — decision engine) |
|---|---|---|
| Report generates daily, surfaces threshold hits | Report adds confidence score + suggested target per row, opens weekly PR with proposed _redirects edits |
Engine auto-applies high-confidence redirects, queues medium-confidence for weekly batch review, escalates ambiguous |
| Dan reviews report manually when alerted | Weekly cadence: 15 min review, approve/reject queued changes | Quarterly: review engine’s calibration + edit criteria |
_redirects edited by hand on a case-by-case basis |
_redirects PRs auto-drafted from approved rows |
_redirects PRs auto-merged for high-confidence; manual override always available |
Criteria the report already delineates (the substrate v2/v3 build on):
- Bot-probe paths → leave 404 (security signal; never reward scanners with 200)
- Section-root paths → build index page (stunning content earns its own home, not a redirect)
- Favicon paths → already-redirected verification (deploy-lag sanity check)
- Legacy editorial paths above threshold → DECIDE redirect target (the human-in-the-loop slot)
- Legacy editorial paths below threshold → monitor (wait for signal before spending decision budget)
v2 adds: a confidence score per editorial row (based on path-shape regex + historical hit pattern + the article corpus’ nearest-neighbour match for a sensible target), and a draft PR against _redirects per weekly cohort. v3 lets the engine merge the high-confidence cohort autonomously, with Dan reviewing the medium/low cohorts.
Each level inherits the same criteria — only the level of automation changes. The rule stays the source of truth; the engine becomes a faster applicator of it.