Skip to content

404 Monitor: Find and Fix Missing URLs

The 404 Monitor tracks every 404 error on your site so you can see which URLs visitors and search engines are trying to access. Instead of guessing what’s broken, you get a log of missing URLs with hit counts, referrers, and user agents. You can then turn those log entries into redirects or delete them once fixed.

Go to SEOvault AI > General > 404 Monitor.

When a visitor or bot requests a URL that doesn’t exist on your site, WordPress returns a 404 response. SEOvault AI captures these requests and logs them to a database table. The log includes:

  • URL — the missing path requested
  • Hits — how many times this URL has been accessed
  • Referrer — where the request came from (if available)
  • User Agent — the browser or bot that made the request
  • Last Accessed — when the 404 last occurred

The monitor has two logging modes:

  • Simple mode — logs only the URL and hit count. Lightweight, good for high-traffic sites.
  • Advanced mode — logs URL, hit count, referrer, and user agent. More detail for debugging.

You can also exclude certain URL patterns from logging (for example, if you know a particular path is always hit by bots and you don’t care about it).

The 404 Monitor table shows all logged 404 errors with pagination, sorting, and search.

  • Click column headers to sort by URL, hits, or last accessed date
  • Use the search box to filter by URL pattern
  • Adjust the page size from the “Screen Options” dropdown
  • Click Delete next to a single entry to remove it
  • Select multiple entries with checkboxes and choose Delete from the bulk actions dropdown
  • Clear all logs at once using the “Clear All Logs” button at the bottom of the tab

Delete entries when you have fixed the underlying issue (created a redirect, restored the content, or confirmed the URL is no longer relevant).

The most common workflow is converting a frequently-hit 404 into a redirect:

  1. Go to SEOvault AI > General > 404 Monitor
  2. Find the URL you want to redirect in the log table
  3. Click Redirect in the Actions column
  4. The Redirect Manager tab opens with the origin URL pre-filled
  5. Enter the target URL (where you want to send visitors instead)
  6. Choose the redirect type (301 for permanent, 302 for temporary)
  7. Click Add Redirect

The log entry remains in the 404 Monitor after you create the redirect — delete it manually if you want to clean up the list.

Configure logging behavior under the 404 Monitor tab:

Choose between Simple (URL + hits only) or Advanced (URL + hits + referrer + user agent). Advanced mode uses more database storage but gives you more context about where 404s are coming from.

Enable this to treat /page?param=value and /page as the same URL. Useful when tracking parameters create duplicate 404 entries for the same underlying path.

Add URL patterns to exclude from logging. For each exclusion rule:

  • Pattern — the text or regex to match
  • Comparison — how to match:
    • Contains — pattern appears anywhere in the URL
    • Exact — URL must match the pattern exactly
    • Starts with — URL begins with the pattern
    • Ends with — URL ends with the pattern
    • Regex — use a regular expression pattern

Use exclusions for paths you know are irrelevant (for example, /wp-content/plugins/old-plugin/ if you deliberately removed that plugin and don’t need to track attempts to access it).

Set the maximum number of log entries to keep. When the limit is reached, the oldest entries are automatically deleted. This prevents the log table from growing indefinitely on high-traffic sites. Set to 0 to disable automatic pruning.

The 404 Monitor automatically disables if another SEO plugin is active and detected as handling SEO output. This prevents duplicate logging and conflicts. If you see a warning on the Dashboard about another SEO plugin, either deactivate it or switch SEOvault AI to Disabled mode for the features you want the other plugin to handle.