404 log

Under Content → Redirect & 404 → 404 Log, you'll find every URL whose request resulted in a genuine 404 response.

How the log fills up

As long as the Log 404 errors setting is enabled (default: on), every not-found path is captured automatically. There is exactly one entry per path: if the same path is requested again, only its hit counter is increased and the last-occurrence timestamp is updated — no duplicates are created.

Only genuine page loads (main requests) are captured, not Ajax or background requests. Certain path areas, such as API or asset paths, are never logged — see Excluded Paths for the full list.

Sorting

The list is sorted by frequency: paths with the most hits appear at the top. This is intentional, so you see the 404 errors causing the most damage first (lost traffic, poor user experience, potential SEO drawbacks).

Columns

If the log is empty, the list shows the hint "No 404 errors logged".

Reading it as a prioritization list

Work through the log from top to bottom:

1. Entries with a high hit count are the first candidates for a redirect
2. Entries whose "Last" timestamp is far in the past are usually less urgent
3. Obviously bogus or random bot paths (e.g. /wp-admin, /.env) can be ignored or simply deleted

For details on turning an entry directly into a redirect, see Fix from 404.

Deleting entries

Use the Delete entry action to permanently remove a 404 entry from the log. If the path is requested again afterwards, the plugin automatically creates a new entry.