dare.co.uk 404 redirects report — 2026-05-21
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
- 336 total 404 hits in the last 24h across 50 distinct paths.
- 0 path(s) over the 50/day threshold needing a redirect decision.
- 38 bot-probe paths — leave 404 (per rule, security signal).
- 0 section-root paths — build index pages, not redirect.
Legacy editorial — decide redirect target
(12 path(s) · 97 total hits)
| Path | Hits | Action | Decision? |
|---|---|---|---|
/ip |
21 | examine + decide (rule applies) | |
/topics/daring-acts/ |
13 | examine + decide (rule applies) | |
/topics/climbing/ |
12 | examine + decide (rule applies) | |
/daring-acts/archive/ |
12 | examine + decide (rule applies) | |
/author-sitemap.xml |
8 | examine + decide (rule applies) | |
/topics/mariah%E2%80%99s-penthouse/ |
6 | examine + decide (rule applies) | |
/.aws/credentials |
5 | examine + decide (rule applies) | |
/rss/ |
4 | examine + decide (rule applies) | |
/daring-acts/defying-gravity/ |
4 | examine + decide (rule applies) | |
/file-manager/initialize |
4 | examine + decide (rule applies) | |
/topics/photography/ |
4 | examine + decide (rule applies) | |
/topics/audi-q5/ |
4 | examine + decide (rule applies) |
Bot-probe paths — leave 404
(38 path(s) · 239 total hits)
| Path | Hits | Action | Decision? |
|---|---|---|---|
/wp-json/wp/v2/users |
34 | leave 404 (security signal) | |
/wp-json/ |
9 | leave 404 (security signal) | |
/feed/ |
9 | leave 404 (security signal) | |
/wp-json/wp/v2/posts |
8 | leave 404 (security signal) | |
/wp-json/youzer/v1/members |
7 | leave 404 (security signal) | |
/wp-json/bbp-api/v1/users |
7 | leave 404 (security signal) | |
/wp-json/buddypress/v1/members |
7 | leave 404 (security signal) | |
/init.php |
7 | leave 404 (security signal) | |
/wp-json/peepso/v1/members |
7 | leave 404 (security signal) | |
/wp-json/learnpress/v1/users |
6 | leave 404 (security signal) | |
/wp-json/ultimate-member/v1/users |
6 | leave 404 (security signal) | |
/wp-json/lp/v1/users |
6 | leave 404 (security signal) | |
/wp-json/wc/v3/customers |
6 | leave 404 (security signal) | |
/wp-json/wp/v2/comments |
6 | leave 404 (security signal) | |
/wp-json/wp/v2/media |
6 | leave 404 (security signal) | |
/wp-json/ldlms/v2/users |
6 | leave 404 (security signal) | |
/wp-json/tutor/v1/students |
6 | leave 404 (security signal) | |
/wp-json/buddyboss/v1/members |
6 | leave 404 (security signal) | |
/author/admin/page/5/ |
6 | leave 404 (security signal) | |
/wp-json/wpuf/v1/users |
6 | leave 404 (security signal) | |
/wp-sitemap-users-1.xml |
5 | leave 404 (security signal) | |
/wp-json/mepr/v1/members |
5 | leave 404 (security signal) | |
/wp-json/um/v1/users |
5 | leave 404 (security signal) | |
/wp-json/webmention/1.0 |
5 | leave 404 (security signal) | |
/readme.html |
5 | leave 404 (security signal) | |
/wp-json/oembed/1.0/embed |
5 | leave 404 (security signal) | |
/BDKR28WP.php |
4 | leave 404 (security signal) | |
/phpinfo2.php |
4 | leave 404 (security signal) | |
/feed/atom/ |
4 | leave 404 (security signal) | |
/wp-login.php |
4 | leave 404 (security signal) | |
/bolt.php |
4 | leave 404 (security signal) | |
/wp-info.php |
4 | leave 404 (security signal) | |
/getir.php |
4 | leave 404 (security signal) | |
/cdn-cgi/trace |
4 | leave 404 (security signal) | |
/feed/rss/ |
4 | leave 404 (security signal) | |
/wp-admin/includes/index.php |
4 | leave 404 (security signal) | |
/sadcut1.php |
4 | leave 404 (security signal) | |
/php_info.php |
4 | 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-21 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.