Missing Page Logs & Redirects

Missing Page Logs & Redirects stores one row per normalized URL path, with a hit counter and first/last seen timestamps. Every genuine WordPress 404 with a valid request URI increments the counter before the redirect decision; the row retains the latest request details and outcome. Its deterministic matching combines slug, token, path, title, and WordPress context signals. Administrator-approved examples can guide similar requests; blocked examples keep a normal 404 response.

• Missing Page Logs & Redirects > 404 Log: filter requests, inspect scoring, and open Create rule for a source URL.
• Missing Page Logs & Redirects > Rules: change destinations, switch positive/blocked rules, or delete a rule.
• Expand Automatic redirect settings in the log to change the default 0.82 confidence threshold.
• Normal redirects use HTTP 301 and need a 0.08 winner margin. Exact learned rules and a unique old slug bypass the margin.
• Posts, pages and public custom post types are supported. Private, draft, password-protected content, revisions and attachments are excluded.
• Create rule opens a separate form. Creating or editing rules does not change the log counter or snapshot.
• No cloud service, external AI, API key, IP-address logging, or frontend HTTP lookup.