Not found (404)
The "Not found (404)" status in Google Search Console means Googlebot tried to fetch a URL and your server returned an HTTP 404 Not Found response. 404s are a normal part of the web - when a page is genuinely gone, returning a 404 is the right thing to do. The problem is not 404s themselves, it is 404s on URLs that shouldn't be 404ing: sitemap entries, internally linked URLs, and pages that should exist but don't due to a bug.
What this GSC status means
Googlebot sent an HTTP request for the URL and received a 404 response (or 410 Gone - Google groups them together). Google removes the URL from the index after a 404 persists across a few recrawls. The URL itself can continue to be recrawled for months, especially if it has external links, but it will not appear in search results. Google groups 404 detection sources: sometimes Google learned of the URL from a link on your site, a backlink, or an old sitemap entry.
Common causes
- Pages intentionally deleted (old products, expired promotions, removed blog posts) - correct behavior.
- URLs in your sitemap that point to pages that no longer exist - your sitemap was not regenerated.
- Internal links (in menus, footers, sidebars) pointing to URLs that changed or were removed.
- Broken backlinks from external sites pointing to URLs you never published.
- CMS or deployment bugs that accidentally removed pages or changed URL structure.
- Mistyped URLs from old blog posts, emails, or marketing campaigns.
- Localization bugs serving 404 for pages that exist in a different locale.
How it affects indexing
Genuine 404s are harmless - Google will drop them from the index and stop prioritizing them over time. But 404s cost when the URL still has incoming signals: valuable backlinks die, internal link equity leaks away, and URLs kept in sitemaps waste crawl budget. Unexpected 404s on pages you still want indexed represent direct traffic loss.
How to diagnose
In GSC, click "Not found (404)" to see the URL list and export it. For each URL, ask: should this page exist? Is the URL in your sitemap? Does it have backlinks (check Ahrefs, Semrush, or GSC Links report)? Is it still linked from anywhere on your site (Screaming Frog or a crawler will find internal linkers)? Test the URL with curl -I URL to confirm the status code is actually 404.
How to fix
1. Remove all 404 URLs from your sitemap.xml and regenerate it. 2. For URLs that should exist: restore the page or fix the bug causing the 404. Verify with curl that it returns 200. 3. For URLs with meaningful replacements: 301 redirect to the closest equivalent page (same intent, same topic). 4. For permanently removed pages with no equivalent: return 410 Gone instead of 404 - it signals "deliberately gone". 5. Update internal links - replace links to 404 URLs with links to live equivalents or remove them entirely. 6. Reach out for broken backlinks worth recovering - ask external sites to update their links to your live URL. 7. Leave genuine 404s alone - do not redirect every 404 to the homepage (creates soft 404 patterns). 8. Resubmit the sitemap in Search Console so Google re-reads the updated URL list.
"Google 404": What People Actually Mean
The search query "google 404" lands here from three distinct scenarios, each with a different fix path. Knowing which one applies saves an hour of wrong-direction work.
Scenario A: Google is reporting that one of your pages returns 404. This is the GSC "Not found (404)" status the rest of this page covers. The page used to be reachable; Google crawled it; now it 404s. Action: work through the 8-step fix list above.
Scenario B: A specific Google URL is itself returning 404. Almost always a stale link to a Google product page that was retired (Google+ communities, Google Hangouts pages, old Google Webmaster URLs that now redirect through Search Console, etc.). There is nothing you can do on your side except update or remove the dead Google link from your own content. The 404 is Google's, not yours.
Scenario C: Your "Google"-flavoured page (Google something tutorial, Google Ads landing page, etc.) is throwing 404 in Search Console. Often a routing or CMS issue specific to that URL — a slug that conflicts with a reserved path, a category that was renamed, or a redirect rule that points at itself. Test with curl -I, check your routing rules, and remove the broken URL from sitemap and internal links until the underlying conflict is fixed.
Note: Google's own indexed-search-results 404 page (the "404. That's an error" screen at google.com/<invalid-path>) is not a signal about your site. It is just Google's own UI returning a not-found response for an internal URL that doesn't exist.