How to Read and Fix the "Not found (404)" Report in Google Search Console

Many site owners panic when Google Search Console shows hundreds of URLs under Not found (404). In most cases, that panic is unnecessary. Google treats 404 as a normal web response. The report becomes valuable only when you separate the URLs that matter from the ones that don't.

Where to find the report

Open Indexing → Pages in Search Console. Under "Why pages aren't indexed," click Not found (404). You will see a chart and a list of example URLs. The list is a sample, not necessarily every 404 Google has seen.

The same page also lists related statuses such as Soft 404 and Blocked due to other 4xx issue. These need different handling; see 404 vs Soft 404 vs 410 Explained.

Does a 404 in this report hurt rankings?

Not by itself. A missing URL does not lower the ranking of your other pages. The real risks are:

• an important page returning 404 by mistake,
• internal links, sitemaps or ads pointing to dead URLs,
• old URLs with backlinks or traffic that now lose their value.

Inspect URLs and find the source

Click a URL in the list and use Inspect URL. In the indexing details you may see where Google discovered it: a referring page or a sitemap. This tells you whether the problem is inside your site or outside it.

Then sort each URL into one of four groups:

• Should exist — Example: A live product returns 404 after a deploy — Action: Fix the page or route
• Moved — Example: Old category URL after a redesign — Action: 301 to the new equivalent
• Removed on purpose — Example: Discontinued product with no replacement — Action: Keep 404 or use 410
• Junk — Example: Spam URLs, random parameters, scraper paths — Action: Ignore

For moved content, use the closest relevant page, not the homepage. For e-commerce decisions, see Redirect Strategy for Discontinued Ecommerce Products.

Clean up internal sources

If the referring page is on your own site, fix the link at the source instead of adding a redirect. Also check:

• XML sitemap: remove URLs that return 404. A sitemap should list only live, indexable pages.
• Navigation and templates: a single broken link in a footer can produce thousands of reports.
• Hreflang and canonical tags: they should never point to a 404.

Use "Validate fix" correctly

After fixing a group, click Validate fix. Google will recrawl the affected URLs and update the status. Validation can take days or weeks, depending on the number of URLs and how often Google crawls your site.

Validation "failing" for URLs you intentionally removed is fine. Those are supposed to return 404.

Search Console is late; real-time logs are not

Search Console shows what Googlebot encountered, often with a delay. It does not show which 404s real users and ad clicks hit today. Combine it with live 404 logs to prioritize by actual traffic, as described in How to Find and Prioritize Broken Links.

Summary

Treat the "Not found (404)" report as a to-do list to filter, not an alarm. Fix pages that should exist, redirect moved URLs to relevant targets, clean up internal links and sitemaps, and ignore junk. Pair it with real-time 404 tracking in no404 to see which missing URLs are costing you visitors right now.