Page fetch failed in Search Console: causes and fixes

Q: Does a failed page fetch remove my page from Google?

It can. Google's help says a page that fails with a 5xx error usually keeps its old version in search for a while, but a 4xx error usually drops it. Pages that keep failing are removed.

Google tried to get the page from your server and could not. The words after "Failed:" say why.

What it means

Page fetch says whether Google could get the page from your server on its last visit. Successful means it could. Failed means it could not, and the words after it name the reason.

When the fetch fails, Google can't read the page, so a new page stays off Google. For a page that is already on Google, Google's help says a 5xx failure usually keeps the old version in search for a while. A 4xx failure usually drops it.

A failure in the indexed result is from the last crawl. Your server may work fine now. The live test shows what happens today.

Where it shows: Page indexing > Crawl > Page fetch.

Which of your pages have this problem? Find out for free.

Get my free report

Common causes

The page is gone or moved without a redirect: Not found (404).
The server failed or took too long: Server error (5xx).
A firewall, CDN, or bot blocker turned Google away, often with Blocked due to access forbidden (403).
The redirects loop or run too long: Redirect error.
The page loads but looks empty or like an error page: Soft 404.
The page needs a login: Blocked due to unauthorized request (401).

How to check which cause applies

Expand Page indexing and read the words next to Page fetch.
Check the Last crawl date. The failure happened then.
Click Test live URL. If Page fetch now says Successful, the problem is fixed or was brief.
If the live test fails too, click View tested page > More info to see the HTTP response.
For server and access errors, open Settings > Crawl stats in Search Console and look at host status.

How to fix it

Find the reason in the list below and follow its fix.
Click Test live URL until Page fetch says Successful.
Click Request indexing. If many pages share the error, fix them all and click Validate fix in the Page indexing report.

Each Page fetch failure, and its fix

Failed: Not found (404)

The server said the page does not exist. If the page moved, add a 301 redirect to the new address. If it is gone on purpose, take it out of your sitemap and your links. Google's help says a 404 for a removed page is not a problem by itself.

Read the full guide: Not found (404)

Failed: Soft 404

The server said 200 OK, but the page looks like an error page or has almost nothing on it. Click Test live URL, then View tested page, and look at the screenshot. If the page is empty for Google, fix what loads the content. If the page should not exist, return 404 or 410.

Read the full guide: Soft 404

Failed: Server error (5xx)

Your server failed when Google asked for the page, or took too long. Check your server logs at the Last crawl time. Fix the error, or add capacity. Google crawls less when it sees many 5xx errors, and more again once pages load.

Read the full guide: Server error (5xx)

Failed: Redirect error

Google followed the page's redirects and gave up: a loop, a chain that is too long, or a bad address in the chain.

Read the full guide: Page fetch: Failed: Redirect error

Failed: Blocked due to access forbidden (403)

The server refused Google. Google's help points out that Googlebot never sends a login, so a 403 to Google is a mistake on the server. Check your firewall, CDN, and bot blocker, and let verified Googlebot through. Your host may need to do this.

Read the full guide: Blocked due to access forbidden (403)

Failed: Blocked due to unauthorized request (401)

The page asks for a login or password, and Google can't log in. Remove the login if the page should be public. If it is private, take it out of your sitemap.

Read the full guide: Blocked due to unauthorized request (401)

Failed: Blocked due to other 4xx issue

The server returned another 4xx error, such as 410 Gone. If the page is gone, take it out of your sitemap. If it should load, find out why the server returns the error.

Read the full guide: Blocked due to other 4xx issue

Failed: Blocked by robots.txt

Google did not try to fetch the page, because a robots.txt rule blocks it. Crawl allowed? says No: blocked by robots.txt.

Read the full guide: Crawl allowed? No: blocked by robots.txt

Internal error

Something went wrong on Google's side. Google's help says to wait a bit and try again. You may see the older label Crawl anomaly in forum posts. Google's current help does not list it. Treat it the same way: test again later, and check your server if it keeps happening.

Invalid URL

The Search Console API lists this state with no more detail. Check the address in your sitemap and links for spaces, broken characters, or a typo, and fix how your site builds it.

N/A

Google's help calls this a failure that doesn't fit any known reason, and says it has no more detail. Click Test live URL. If the live test works, click Request indexing. If it keeps happening, check your server logs for Google's visits.

Server connection error, DNS errors, and other site-wide problems

These show in the live test when Google can't reach your site at all, not just this page.

Read the full guide: Server connection error

When you can ignore it

The page is gone on purpose and nothing links to it, or it is a private page. Take it out of your sitemap, and the failure stops mattering.

With CrawlCoach

CrawlCoach reads the Page indexing reason and the page fetch result for each page it checks. It groups missing pages by reason, such as Server error (5xx) or Not found (404), so you can fix one cause for many pages at once. Google makes the final call on what it indexes.

Related Page indexing reasons

Not found (404): The page shows a 404 Not Found error.
Soft 404: The page loads, but Google thinks it looks like an error or an empty page.
Server error (5xx): Your server showed an error when Google asked for the page.
Redirect error: The redirects for this page are broken, too long, or go in a circle.
Blocked due to access forbidden (403): The server turned Google away with 403 Forbidden.
Blocked due to unauthorized request (401): The page needs a login, so Google can't read it.
Blocked due to other 4xx issue: The server showed a 4xx error other than 401, 403, or 404.

Questions

What does "Page fetch: Failed" mean?

Google tried to get the page from your server on its last visit and could not. The words after "Failed:" give the reason, such as Not found (404) or Server error (5xx).

Page fetch failed, but the page loads fine in my browser. Why?

Your browser is not Googlebot. A firewall or bot blocker can treat Google differently. The failure can also be from an earlier visit. Click Test live URL to see what Google gets now.

What does "Page fetch: N/A" mean?

Google's help calls it a failure that doesn't fit any known reason, with no more detail. Run the live test. If it passes, request indexing.

Does a failed page fetch remove my page from Google?

It can. Google's help says a page that fails with a 5xx error usually keeps its old version in search for a while, but a 4xx error usually drops it. Pages that keep failing are removed.

Sources

Checked on October 8, 2026. Google can change its tools and wording after that date.

"Page fetch: Failed" in URL Inspection: each reason and its fix