Ideas

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

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

(3 path(s) · 56 total hits)

Path Hits Action Decision?
/cf-fonts/v/newsreader/5.0.16/latin/opsz/italic.woff2 29 examine + decide (rule applies)
/ip 18 examine + decide (rule applies)
/randkeyword.PhP7 9 examine + decide (rule applies)

Legacy /category/* — decide redirect target

(1 path(s) · 10 total hits)

Path Hits Action Decision?
/category/observations/page/4/ 10 redirect to nearest archive page

Bot-probe paths — leave 404

(46 path(s) · 500 total hits)

Path Hits Action Decision?
/cdn-cgi/scripts/7d0fa10a/cloudflare-static/rocket-loader.min.js 29 leave 404 (security signal)
/cdn-cgi/rum 29 leave 404 (security signal)
/posts/cropped-ziiiro-celeste.jpeg 28 leave 404 (security signal)
/cdn-cgi/trace 27 leave 404 (security signal)
/wp-json/wp/v2/users 21 leave 404 (security signal)
/wp-login.php 15 leave 404 (security signal)
/wp-blog.php 13 leave 404 (security signal)
/chosen.php 12 leave 404 (security signal)
/wp-trackback.php 12 leave 404 (security signal)
/sf.php 12 leave 404 (security signal)
/as.php 12 leave 404 (security signal)
/wp-admin/js/widgets/ 11 leave 404 (security signal)
/0x.php 11 leave 404 (security signal)
/load.php 11 leave 404 (security signal)
/cdn-cgi/content 10 leave 404 (security signal)
/ms-edit.php 10 leave 404 (security signal)
/1.php 10 leave 404 (security signal)
/autoload_classmap.php 9 leave 404 (security signal)
/class-t.api.php 9 leave 404 (security signal)
/wp-content/plugins/ftde.php 9 leave 404 (security signal)
/wp-good.php 9 leave 404 (security signal)
/new.php 9 leave 404 (security signal)
/wp-content/plugins/hellopress/wp_filemanager.php 9 leave 404 (security signal)
/il.php 9 leave 404 (security signal)
/classwithtostring.php 8 leave 404 (security signal)
/x.php 8 leave 404 (security signal)
/users.php 8 leave 404 (security signal)
/wp-header-json.php 8 leave 404 (security signal)
/aa.php 8 leave 404 (security signal)
/term.php 8 leave 404 (security signal)
/a1.php 8 leave 404 (security signal)
/asw.php 8 leave 404 (security signal)
/akcc.php 8 leave 404 (security signal)
/a7.php 8 leave 404 (security signal)
/rip.php 7 leave 404 (security signal)
/wp-the.php 7 leave 404 (security signal)
/jga.php 7 leave 404 (security signal)
/wp-admin/images/admin.php 7 leave 404 (security signal)
/222.php 7 leave 404 (security signal)
/wp-content/plugins/WordPressCore/ 7 leave 404 (security signal)
/cjfuns.php 7 leave 404 (security signal)
/wp-includes/assets/index.php 7 leave 404 (security signal)
/alfa.php 7 leave 404 (security signal)
/ioxi-o.php 7 leave 404 (security signal)
/wp-2019.php 7 leave 404 (security signal)
/wp-content/themes/pridmag/il.php 7 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-31 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.

← /reportsSource: dare_404_redirects_2026-05-31.md · Rendered 2026-05-31 16:42