dare.co.uk 404 redirects report — 2026-05-26

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

Legacy editorial — decide redirect target

(8 path(s) · 92 total hits)

Path Hits Action Decision?
/ip 60 examine + decide (rule applies) DECIDE
/ads.txt 7 examine + decide (rule applies)
/topics/mariah%E2%80%99s-penthouse/ 6 examine + decide (rule applies)
/wp/kawasaki-s1.jpeg 4 examine + decide (rule applies)
/daring-acts/archive/ 4 examine + decide (rule applies)
/wp/kawasaki-z750.jpeg 4 examine + decide (rule applies)
/2013/05/ 4 examine + decide (rule applies)
/daring-acts/defying-gravity/ 3 examine + decide (rule applies)

Bot-probe paths — leave 404

(42 path(s) · 198 total hits)

Path Hits Action Decision?
/wp-login.php 13 leave 404 (security signal)
/hplfuns.php 7 leave 404 (security signal)
/an.php 6 leave 404 (security signal)
/lock360.php 6 leave 404 (security signal)
/alfa.php 6 leave 404 (security signal)
/bb.php 6 leave 404 (security signal)
/wefile.php 6 leave 404 (security signal)
/a5.php 6 leave 404 (security signal)
/7.php 6 leave 404 (security signal)
/goods.php 6 leave 404 (security signal)
/atomlib.php 5 leave 404 (security signal)
/class-t.api.php 5 leave 404 (security signal)
/wk/index.php 5 leave 404 (security signal)
/wp-admin/ 5 leave 404 (security signal)
/xda.php 5 leave 404 (security signal)
/sid3.php 5 leave 404 (security signal)
/a1.php 5 leave 404 (security signal)
/wp-trackback.php 5 leave 404 (security signal)
/function/function.php 4 leave 404 (security signal)
/t.php 4 leave 404 (security signal)
/mass.php 4 leave 404 (security signal)
/wp-admin/includes/index.php 4 leave 404 (security signal)
/a7.php 4 leave 404 (security signal)
/Okxob.php 4 leave 404 (security signal)
/wp-admin/a.php 4 leave 404 (security signal)
/tmp.php 4 leave 404 (security signal)
/wp-su.php 4 leave 404 (security signal)
/xper1.php 4 leave 404 (security signal)
/xmrlpc.php 4 leave 404 (security signal)
/wp-content/uploads/index.php 4 leave 404 (security signal)
/aa.php 4 leave 404 (security signal)
/ss.php 4 leave 404 (security signal)
/g.php 4 leave 404 (security signal)
/ccou.php 4 leave 404 (security signal)
/ws80.php 4 leave 404 (security signal)
/moon.php 4 leave 404 (security signal)
/wp-wz.php 3 leave 404 (security signal)
/wp-update.php 3 leave 404 (security signal)
/ac.php 3 leave 404 (security signal)
/about.php 3 leave 404 (security signal)
/feed/ 3 leave 404 (security signal)
/wp4.php 3 leave 404 (security signal)

How to apply the decisions

For each row with DECIDE:

  1. Inspect the path — is it a real legacy URL (old article slug, external referrer link) or accidentally-popular bot noise?
  2. 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/
  3. Add a 301 to ~/Code/dare-co-uk/_redirects: /<path> /<target> 301
  4. 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-26 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):

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.

Source: dare_404_redirects_2026-05-26.md · Rendered 2026-05-26 17:10