dare.co.uk 404 redirects report — 2026-05-17
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
- 636 total 404 hits in the last 24h across 50 distinct paths.
- 0 path(s) over the 50/day threshold needing a redirect decision.
- 39 bot-probe paths — leave 404 (per rule, security signal).
- 0 section-root paths — build index pages, not redirect.
Legacy editorial — decide redirect target
(9 path(s) · 136 total hits)
| Path | Hits | Action | Decision? |
|---|---|---|---|
/ip |
22 | examine + decide (rule applies) | |
/dare_session_report_2026-05-16 |
18 | examine + decide (rule applies) | |
/cf-fonts/v/newsreader/5.0.16/latin/opsz/italic.woff2 |
18 | examine + decide (rule applies) | |
/2026-05-16/ |
18 | examine + decide (rule applies) | |
/2026-05-17/ |
16 | examine + decide (rule applies) | |
/dare_seo_title_cleanup_2026-05-17 |
14 | examine + decide (rule applies) | |
/randkeyword.PhP7 |
11 | examine + decide (rule applies) | |
/phpinfo |
10 | examine + decide (rule applies) | |
/.well-known/ |
9 | examine + decide (rule applies) |
Favicon paths
(1 path(s) · 20 total hits)
| Path | Hits | Action | Decision? |
|---|---|---|---|
/apple-touch-icon-precomposed.png |
20 | already redirected — verify deploy lag |
Root — should never 404
(1 path(s) · 20 total hits)
| Path | Hits | Action | Decision? |
|---|---|---|---|
/ |
20 | investigate — should never 404 |
Bot-probe paths — leave 404
(39 path(s) · 460 total hits)
| Path | Hits | Action | Decision? |
|---|---|---|---|
/wp-login.php |
30 | leave 404 (security signal) | |
/wp-content/uploads/index.php |
19 | leave 404 (security signal) | |
/cdn-cgi/trace |
19 | leave 404 (security signal) | |
/wp-admin/wp.php |
19 | leave 404 (security signal) | |
/posts/cropped-ziiiro-celeste.jpeg |
18 | leave 404 (security signal) | |
/as.php |
17 | leave 404 (security signal) | |
/wp-json/wp/v2/users |
17 | leave 404 (security signal) | |
/aa.php |
16 | leave 404 (security signal) | |
/cdn-cgi/rum |
15 | leave 404 (security signal) | |
/rip.php |
15 | leave 404 (security signal) | |
/goods.php |
15 | leave 404 (security signal) | |
/themes.php |
13 | leave 404 (security signal) | |
/wp-admin/ |
13 | leave 404 (security signal) | |
/aaa.php |
13 | leave 404 (security signal) | |
/wp-admin/classwithtostring.php |
12 | leave 404 (security signal) | |
/wp-blink.php |
11 | leave 404 (security signal) | |
/x.php |
11 | leave 404 (security signal) | |
/chosen.php |
10 | leave 404 (security signal) | |
/bthil.php |
10 | leave 404 (security signal) | |
/wp-content/themes/pridmag/il.php |
9 | leave 404 (security signal) | |
/atex1.php |
9 | leave 404 (security signal) | |
/a7.php |
9 | leave 404 (security signal) | |
/ws54.php |
9 | leave 404 (security signal) | |
/index/function.php |
9 | leave 404 (security signal) | |
/function/function.php |
9 | leave 404 (security signal) | |
/php.php |
9 | leave 404 (security signal) | |
/adminfuns.php |
9 | leave 404 (security signal) | |
/wp-content/admin.php |
9 | leave 404 (security signal) | |
/term.php |
9 | leave 404 (security signal) | |
/cv.php |
9 | leave 404 (security signal) | |
/file.php |
8 | leave 404 (security signal) | |
/p.php |
8 | leave 404 (security signal) | |
/bless.php |
8 | leave 404 (security signal) | |
/wk/index.php |
8 | leave 404 (security signal) | |
/fone1.php |
8 | leave 404 (security signal) | |
/wp-content/index.php |
7 | leave 404 (security signal) | |
/222.php |
7 | leave 404 (security signal) | |
/NewFile.php |
7 | leave 404 (security signal) | |
/deepseek_d.php |
7 | 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-05-17 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.