Here is how to fix 404 errors in Google Search Console: fix the Not found (404) URLs that someone still asks for, and leave the rest alone. A 404 needs fixing when the URL is in your sitemap, is linked from your own pages or from other sites, or used to bring search traffic. Restore the page if it was deleted by mistake, 301 redirect it to its closest replacement if the content moved, and take it out of your sitemap and internal links if it is gone for good. A page you removed on purpose can keep answering 404 (or 410): Google says that does not hurt the rest of your site.
The URLs are in Indexing > Pages, in the Not found (404) row of Why pages aren't indexed. Below: the steps, which 404s matter, what Validate fix does, and what we found across 1,513 sites.
What does Not found (404) mean in Google Search Console?
Not found (404) means Googlebot requested the URL and your server answered with HTTP status 404: there is no page at this address. Google does not index such a URL, and if it was indexed before, Google removes it once a crawl gets the 404, according to its documentation on how HTTP status codes affect its crawlers. A URL that answers 410 (Gone) is reported the same way, since Google treats 410s like 404s.
Search Console shows the same verdict in several places, in different words:
| Where you see it | Exact wording | What it tells you |
|---|---|---|
| Page indexing report (Indexing > Pages) | Not found (404), a row in Why pages aren't indexed | Google got a 404 for these URLs. The details page lists up to 1,000 examples with their last crawl date. |
| URL Inspection, indexed result | URL is not on Google, with Page is not indexed: Not found (404) | Google's last crawl of the URL got a 404. The Page fetch field shows the failure. |
| URL Inspection, Test live URL | URL is not available to Google, with Page cannot be indexed: Not found (404) | Your server answers 404 right now. |
| Older guides and screenshots | Submitted URL not found (404) | The old Index Coverage report's name for a sitemap URL that returned 404. Today it is listed as Not found (404). |
Google's help text for this status says "Google discovered this URL without any explicit request or sitemap." Do not read too much into that line: sitemap URLs land in the same row. To see only the 404s you submitted, change the filter above the chart from All known pages to All submitted pages. That view covers what the old Submitted URL not found (404) status covered, and it is the list to fix first.
Why does Google Search Console show 404 errors?
Because Google found the URL somewhere and tried it. Google keeps the URLs it discovers and recrawls them from time to time, so a 404 appears when a known URL stops working, or when Google follows a link to an address that never worked. The usual sources:
- Your sitemap still lists a page you deleted or moved.
- Your own pages link to it: a menu, an old post, a footer.
- Other sites link to it, sometimes with a typo in the address.
- Addresses nobody meant to create: URLs Googlebot picked up from JavaScript, broken links a CMS generated, mangled copies made by scrapers. Google's 404 help page says you can safely ignore 404s for URLs that should not exist on your site.
To see where Google found a URL, inspect it. The Discovery part of the Page indexing section lists the Sitemaps that contain the URL and a Referring page Google may have used to find it. An empty Referring page does not prove that nothing links there: Google says the data may simply not be available to the tool.
Are 404 errors bad for SEO?
Not for the rest of your site. Google's 404 help page says "404s don't harm your site's indexing or ranking", and the Search Central blog post Do 404 errors hurt my site? calls them "a perfectly normal part of the web" and says they do not affect how your site's other pages perform in search. The Crawl Stats report help adds that it is "not possible, worthwhile, or even desirable to fix all 404 errors on your site". They do not slow down crawling either: Google says 4xx codes other than 429 "have no effect on crawl rate", and its crawl budget guide recommends a 404 or 410 for removed pages, since a 404 is "a strong signal not to crawl that URL again".
What a 404 does cost is the page itself and whatever still points to it:
- The URL leaves the index, so it cannot rank or bring clicks.
- Old links lead to an error. Visitors who follow your links, other sites' links or a bookmark land on a 404 instead of the content they came for.
- Dead sitemap URLs send Google to pages you gave up on. Google asks you to include the URLs you want to see in its search results, and a deleted page is not one of them.
So the job is not to empty the report. It is to find the few 404s where one of these costs is real.
Which 404 errors should you fix?
Fix a 404 when someone still asks for the URL. Google's own rule in the Page indexing report help is narrower: "we recommend fixing only 404 errors that you link to yourself or list in a sitemap." Use this table for each URL:
| The 404 URL is | Fix it? | What to do |
|---|---|---|
| Listed in your sitemap | Yes | Restore it, redirect it or take it out of the sitemap |
| Linked from your own pages | Yes | Point the link at the right page, or remove the link |
| A page deleted by mistake or broken by a site update | Yes | Restore it at the same URL |
| A page that moved to a new URL | Yes | 301 redirect it to the new URL |
| Linked from other sites, or it used to get clicks | Usually | 301 redirect it to the closest equivalent page, if one exists |
| A common misspelling of one of your URLs | Optional | 301 redirect it to the correct page |
| Deleted on purpose, with nothing to replace it | No | Leave it as 404 or 410, and remove it from your sitemap and links |
| An address that never existed (junk, scraped or broken links) | No | Ignore it |
Two checks place a URL in the table. In Performance > Search results, open the Pages tab with a long date range: a URL with clicks had searchers. And the URL Inspection Discovery fields show whether your sitemap or a known page leads to it. For links from other sites, use a backlink tool: Search Console's Links report shows only a sample of links and can leave out pages that are not indexed. Not sure a page should come back at all? Our guide to keeping, updating or removing outdated content helps you decide.
How to find 404 errors in Google Search Console
Use the Page indexing report, filtered to your sitemap first:
- In Google Search Console, pick the property and open Pages, the Page indexing report, from the Indexing group of the left menu.
- Above the chart, swap All known pages for All submitted pages, so the report covers only URLs listed in the sitemaps you submitted (in the Sitemaps report or in robots.txt).
- Under Why pages aren't indexed, click Not found (404). No such row means no 404s in this view in the past month.
- The details page lists up to 1,000 example URLs with their last crawl date. Click Export to sort them by folder or template in a spreadsheet.
- Click the inspect icon next to a URL to open it in URL Inspection. Check Discovery, then click Test live URL to see what your server answers today.
- Switch the filter to Unsubmitted pages only for the 404s Google found through links. Most of these can stay as they are; look for addresses your own site links to and pages that moved.
Keep two limits in mind. The report "shows only URLs that have shown 404 errors in the past month" and stops at 1,000 examples. And it cannot show a 404 that Googlebot has not requested yet, which matters more than it sounds (see our data below). A site crawler fills the gap for your own links: it reports every internal link that leads to a 404.
For the crawler's side, open Settings > Crawl stats > Open report and look at the crawl responses. Google's help lists Not found (404) there under "Possibly good response codes", and the report counts requests, not URLs. Those requests include the images, scripts and other files your pages load from your site, so a 404 there can be a missing file rather than a missing page. A 404 for robots.txt is a good response: it only means you have no robots.txt file. The report exists only for Domain properties and root-level URL-prefix properties.
How to fix 404 errors, step by step
Start with the sitemap list, then the URLs your own pages link to, then anything with backlinks or past clicks.
- Restore pages deleted by mistake, at the same URL. Look for the content in your CMS trash or revision history, in a backup, or in the Wayback Machine.
- 301 redirect moved pages to their closest replacement, in one hop (the list below the steps shows where to add one). Not to the homepage: Google's 404 help page calls that a soft 404, which can confuse users and search engines. The old URL then moves to Page with redirect, which is the expected state.
- Take dead URLs out of your sitemap. Regenerate it in your CMS or SEO plugin rather than editing it by hand (our guide on how to make a sitemap shows where each platform builds it), then run it through the free sitemap checker to confirm the file is valid and lists what you expect.
- Fix internal links. Point menus, footers and posts at the final address instead of relying on the redirect.
- Leave intentional 404s alone. For content you removed on purpose with no replacement, 404 or 410 is the right answer. Do not block those URLs in robots.txt: Google then cannot see the 404, and its 404 help page lists robots.txt blocking among the things not to do. Do give the visitors who still arrive a useful 404 page, with a search box and links to your main sections: Google's 2011 post notes that you can "return a 404 response code while serving whatever content you want".
- Check every fix. Paste up to 10 old URLs into the free redirect checker. A moved page should show one permanent redirect (301 or 308) to a page that answers 200, and a removed page should answer 404 or 410. Then run Test live URL on a few of them; our URL Inspection tool guide explains each field.
- Ask Google to recrawl the pages that matter. Inspect each restored page and redirect target and click Request indexing. Search Console limits how many requests you can make per day, so start with the pages that had traffic. Our guide to Request Indexing in Search Console covers the limit and the messages you will see.
Where to add a 301 redirect
Most platforms have a redirect screen, so you rarely need to edit server files:
- WordPress: a redirect plugin such as Redirection, set up under Tools > Redirection.
- Shopify: Content > Menus > View URL Redirects > Create URL redirect, as Shopify's help describes.
- Wix: SEO & GEO in your dashboard, then URL Redirect Manager under Tools and settings. Wix adds a 301 by itself when you change a page's URL slug, but not for Wix Blog pages.
- Squarespace: the Developer tools panel, then URL mappings, one line per redirect in the form
/old-url -> /new-url 301(Squarespace help). - Next.js: a
redirectsentry innext.config.jswithpermanent: true, which sends a 308. Google lists 301 and 308 alike as permanent redirects. - Anything else: your host's, server's or CDN's redirect rules.
404 vs 410: which should a deleted page return?
Either one. Google's HTTP status documentation says all 4xx errors except 429 are treated the same, and its 404 help page says "Google treats 410s (Gone) the same as 404s (Not found)". A 410 states that the removal is deliberate and permanent, which is the more precise answer for content you deleted on purpose, so use it where your server or CMS makes it easy. Converting old 404s to 410s is not worth the time.
| 404 Not Found | 410 Gone | |
|---|---|---|
| What your server sends | 404 | 410 |
| What it tells Google | Nothing exists at this URL | The page is gone and will not come back |
| Indexed? | No | No |
| How Google crawls it afterwards | Less and less often | Same as 404 |
| Right answer for | A page that does not exist | A page you removed for good |
The answer to avoid is a third one: a "not found" page that answers 200. Google then reports a soft 404, and its crawl budget guide says such pages keep being crawled and waste crawl budget. Our guide to soft 404s sets the two side by side and shows how to find and fix them.
What happens after you click Validate fix?
Validate fix asks Google to recheck the URLs in a row. Open the Not found (404) details page and click it: Search Console checks a few URLs right away, works through the rest and emails you about the progress. Google says validation "typically takes up to about two weeks, but in some cases can take much longer".
Use it when every URL in the row is fixed. A page you deleted on purpose still answers 404, so Google can count it as a remaining instance, and validation stops "when Google finds a single remaining instance of that issue". When the row mixes fixed URLs with intentional 404s, first filter the report to a sitemap that lists the fixed URLs but not the intentional 404s: Google says validation then applies "only to items in the sitemap at the time you requested validation". Or skip validation. You lose nothing: Google "updates your instance count whenever it crawls a page with known issues, whether or not you explicitly requested fix validation". A validation you do start moves from Started to Looking good to Passed, or to Failed, where See details shows the URL that failed.
What you see afterwards:
- Redirected URLs move to Page with redirect, and Google judges the target URL on its own.
- Restored pages leave the row after Google recrawls them; Request indexing speeds that up.
- Deleted pages stay while Googlebot keeps trying them. Google says it "will crawl it less and less often" and "there is no way to tell Googlebot to permanently forget a URL", so a deleted page can leave the report and come back later. That is normal.
- The Removals tool does not clear the report, Google's 404 help page says. It only hides a URL from search results, for about six months.
How common are 404 errors in sitemaps? Data from 1,513 sites
Rare. We looked at 1,513 sites connected to IndexMachine on November 11, 2026, and at the 1,239,239 sitemap URLs on them that have a URL Inspection state: 2,930 of those URLs (0.24%) were Not found (404), on 84 of the sites (5.6%). Each state is the page's latest URL Inspection result, so some are days old and some older. On most of these sites, IndexMachine had not requested indexing for any page, so these Search Console numbers mostly show sites as they stand on their own. Aggregate counts only, with no site or URL named.
How the 2,930 were spread across the 84 sites:
| Not found (404) sitemap URLs on the site | Sites | Not found (404) URLs in total |
|---|---|---|
| 1 | 38 | 38 |
| 2 to 5 | 30 | 76 |
| 6 to 20 | 7 | 57 |
| More than 20 | 9 | 2,759 |
38 of the 84 sites had exactly one such URL, and the median affected site had 2: a leftover you can remove from the sitemap or replace with the final URL. The 9 sites with more than 20 held 94% of all of them. When dozens of 404s sit in one sitemap, look for what the URLs share (a folder, a template, an old URL pattern) before you fix them one by one.
Live 404s vs what Search Console last said
A 404 reaches the report only after Googlebot requests the URL again. For 23,131 sitemap URLs on 105 of these sites, we also have the HTTP status code each one answered between October 31 and November 11, 2026. 844 of them (3.6%) answered 404 or 410, on 20 of the 105 sites (19%), and another 9.0% redirected. Here is what the latest URL Inspection result said about the 844. Nearly all of these results date from before the URL was found answering 404 or 410, so they show what Search Console last said, not necessarily what the report lists today:
| Latest URL Inspection state | Sitemap URLs answering 404 or 410 | Share | Sites |
|---|---|---|---|
| URL is unknown to Google | 346 | 41.0% | 5 |
| Discovered or Crawled - currently not indexed | 291 | 34.5% | 6 |
| Submitted and indexed | 113 | 13.4% | 13 |
| Not found (404) | 74 | 8.8% | 8 |
| Another state, or no state yet | 20 | 2.4% | 5 |
What it shows:
- On 12 of the 20 sites, not one of these URLs was Not found (404). By URL count, 74 of the 844 (8.8%) were.
- 113 (13.4%) were Submitted and indexed. In those results, Google's last crawl of the 97 with a crawl date was between July 19 and September 23, 2026, 6 to 16 weeks before they were found answering 404 or 410. Until Googlebot comes back, such a page can stay in search, and a click on it lands on an error.
- 346 (41.0%) were unknown to Google. Google had no record of them, so Search Console had nothing to report.
- Most affected sites had only a few. 10 of the 20 sites had one or two, and on 15 of the 20 they were under 5% of the URLs with a status. The 8 sites with 6 or more held 97.5% of them.
It works the other way too: among the same 23,131 URLs, 127 were Not found (404) in their latest URL Inspection result, and 53 of those no longer answered 404 or 410. This sample is smaller than the Search Console one, most of its sites have indexing turned on, and a few sites hold most of the 844, so treat the exact shares as an indication. The lesson holds either way: when you delete or move pages, check those sitemap URLs the same day instead of waiting for the report.
Find out when a page starts returning 404
The Page indexing report can tell you about a 404 weeks late, and only for URLs Googlebot has tried again. Turn indexing on in IndexMachine and its 404 alerts tell you when a page in your sitemap starts returning 404, so a broken page does not sit unnoticed until Google recrawls it. Once it is fixed, you skip the trip to URL Inspection: restored pages and new redirect targets are picked up from your sitemap automatically and get Google's own Request Indexing in your Search Console, on autopilot, from the IndexMachine Chrome extension, using your full daily Google quota on every site. None of it goes to pages Google already shows as indexed, each requested page is tracked until it is on Google, and every other engine gets unlimited IndexNow. Of 1,841 pages requested, 1,418 (77%) were on Google, typically in about 3 days by our first check. Daily reports and a weekly email report come with it; pay once for lifetime access or subscribe.
See which sitemap pages Google reports as Not found (404)
Connect Search Console to a free IndexMachine account to see which of your sitemap pages Google lists as Not found (404) or has left out, and why. When you are ready, turn on daily Request Indexing in your own Search Console, unlimited IndexNow and 404 alerts.
FAQs
What does "Page cannot be indexed: Not found (404)" mean?
It is the result of Test live URL in URL Inspection: Google fetched the page just now and your server answered 404. Restore the page if it should exist, add a 301 redirect if it moved, or do nothing if you deleted it on purpose. The indexed result, Page is not indexed: Not found (404), describes Google's last crawl instead, which can be weeks old.
How long do 404 errors stay in Google Search Console?
Until about a month after Googlebot last gets a 404 for the URL: Google's 404 help says the errors "should be dropped from the report after about a month". Googlebot keeps retrying known URLs, less and less often, so an old 404 can drop out and come back. That is harmless.
Should I redirect all 404 pages to my homepage?
No. Google calls a redirect from a dead page to the homepage a soft 404, and visitors land on a page they did not ask for. Redirect a URL only to a page that replaces it, and let everything else return 404 or 410.
Why does Search Console show 404 errors for pages that never existed?
Because Google found links to them: a typo on another site, a broken link your CMS generated, a URL inside JavaScript, a scraper's mangled copy. Such 404s need no fix and leave the report on their own. Redirect one only if it is a common misspelling of a real page.
Why does Search Console still show a 404 after I fixed it?
Because the report reflects Google's last crawl, not your site today. Inspect the URL and compare the last crawl date with the date of your fix: if the crawl is older, Google has not seen the fix yet. Run Test live URL to confirm the page works now, click Request indexing if it matters, and allow time. Validation alone typically takes up to about two weeks.