Log Actions

What you can do with recorded 404s — individually or in bulk — plus where the data lives and how to keep the table from growing forever.

For the list view, columns, statuses and filtering, see Logs.

• Row actions
• Bulk actions
• Exporting logs
• Where the data lives
• Keeping the table small

Row actions

Each row's overflow menu offers:

• View details — opens a modal with the full request context grouped into Request, Visit info and Settings sections, with the 404 path shown prominently above them.
• Custom redirect — opens the redirect editor pre-filled with the log's URL as the source.
  • If the log has no linked redirect, you create a new one and it gets linked to the log automatically.
  • If the log already has a linked redirect, the editor loads that redirect for editing in place.
  • The Source URL is locked to the log's 404 path in both cases — changing it would break the link.
• Mark as fixed — set the row's status to Fixed.
• Mark as ignored — set the row's status to Ignored.
• Reopen — flip a Fixed / Ignored row back to Open.
• Delete — remove the row from the log table. Permanent.

Bulk actions

Select rows with the checkboxes and the bulk action bar appears. You can mass-delete, mass-mark fixed/ignored, or mass-reopen the selection.

Exporting logs

To download the log table as a CSV — honouring your current search and status filters — install the Logs Exporter add-on. It adds an export control to this page.

Where the data lives

Every 404 ends up in the wp_404_to_301_logs table. The plugin writes via the Log action on template_redirect — see the 404_to_301_pre_log_insert filter if you need to alter the row payload before it lands.

Keeping the table small

The core plugin doesn't auto-prune. The Logs Cleaner add-on adds:

• Delete rows older than N days.
• Cap the table at N rows (oldest first).
• A scheduled cleaner that runs on a recurring interval.

The promo at the bottom of the Log settings tab links to it directly.