404 Pages Report

What the report shows

The 404 Pages tab lists every request to your site that ended with an HTTP 404 (Not Found) response during the selected date range. Each line represents one distinct URL that visitors (or bots) tried to reach but that WordPress could not serve.

ColumnMeaning
URLThe path that was requested. It is always shown relative to your site root – e.g. /privacy-and-policy instead of the full https://example.com/privacy-and-policy.
ViewsHow many times that exact URL returned a 404 in the chosen period. A “view” is one HTTP request, whether it came from a human visitor or a crawler.

Why does it matter?

This report lets you detect broken or outdated links, missing media files, and malicious scans in one place so you can fix or mitigate them quickly.

Typical reasons you see entries here

  1. Deleted or renamed content – A post you removed or changed its slug is still being linked from somewhere.
  2. Typos in internal links – A wrong character in a menu, button, or shortcode.
  3. External links beyond your control – Another site linked to the wrong address.
  4. Missing media – Images or downloads referenced in posts but deleted from the Media Library.
  5. Automated scans – Bots guessing paths like /wp-login.php, /old‑admin/, etc. (Numbers can be high but usually harmless.)

What to do when you see many 404 pages

ScenarioRecommended action
Legitimate page movedCreate a 301 redirect from the old URL to the new one (plugins like Redirection, or your server/hosting panel).
URL is a typo in your own siteEdit the post/page/menu and correct the link.
External site linking wronglyLeave a redirect in place or contact the site owner to update their link.
Deleted content that should stay goneLet it return 404, but serve a helpful custom 404 page explaining the change.
Bots probing strange pathsNo action usually needed; if excessive, consider blocking IP ranges or using a firewall rule.

Rule of thumb: If a 404 should resolve to real content for genuine visitors, redirect or recreate the content. If it is only a bot probe, you can safely ignore it.

Troubleshooting workflow

  1. Sort by Views to surface the busiest broken URLs first.
  2. Copy the URL and paste it in your browser – do you expect the page to exist?
  3. Search your own site for that slug to find internal links.
  4. Apply the relevant fix from the table above.
  5. Re‑check the report after your next crawl cycle to confirm views drop.

6. FAQ / Support snippets

“Why does the report show image files like /wp-content/uploads/2017/05/Page-1.png?”
That file is referenced somewhere (a post, a theme thumbnail, or a hotlink from another site) but has been removed or renamed. Restore the image or update the reference.

“The same path appears thousands of times – is that bad for SEO?”
Search engines are tolerant of some 404s. Focus on URLs that should exist. Mass bot scans do not usually affect rankings, but fixing genuine broken links does help crawl budget and user experience.

7. Best practices to keep the list clean

Let’s get started
Take your business to next level

Become part of our growing family of +600,000 users and get the tools you need to make smart choices for your website. Simple, powerful insights are just a click away.