Page fetch failed: Server connection error

Q: Is Server connection error the same as Server error (5xx)?

No. With a 5xx error, your server answered with an error. With Server connection error, Google could not connect at all.

Google could not connect to your server at all. That is a problem for the whole site, not just this page.

What it means

Google's help says the server was unreachable, refused the connection, or failed to connect. Google never got to ask for the page.

Because Google can't reach the server, the live test stops here. Other pages on your site can have the same problem.

Server errors can be brief. Google's help notes that a live test can fail when normal crawling works, and the other way around.

Where it shows: In the live test. Availability says "Not available due to a site-wide issue", and Page fetch names the problem.

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

Get my free report

Common causes

A firewall, CDN, or security plugin blocks Google's requests.
The server was down, restarting, or overloaded.
Your DNS points to the wrong server, or an old one.
The server takes too long to accept a connection.

How to check which cause applies

Click Test live URL again in a few minutes. If it passes, the problem was brief.
Open Settings > Crawl stats in Search Console and look at host status for trouble reaching your server.
Check your server and firewall logs for blocked requests from Googlebot at the time of the test.
Ask your host whether its firewall or attack protection blocks crawlers.

How to fix it

Let verified Googlebot through your firewall, CDN, and bot protection.
Fix the server's uptime or capacity if it was down or overloaded.
Fix your DNS if it points to the wrong place.
Click Test live URL until Page fetch says Successful. Then click Request indexing for the pages you need back first.

Other site-wide Page fetch messages

Google's help lists these values for a site-wide problem in the live test:

DNS server unresponsive: often brief. Google's help says it can clear up in a few minutes.
DNS error: Host unknown: your DNS did not resolve the address. This can also be brief.
DNS error: Private IP provided: your DNS returned a private address, such as 10.0.0.1, that Google can't reach.
Server invalid response: the server sent a response Google could not read, such as a cut-off or badly compressed one.
Invalid server SSL certificate: Google won't test an https page until the certificate is valid.
Robots.txt unreachable: robots.txt exists but did not load, and Google won't crawl the site until it does.
Hostload exceeded: Google thinks your site is at its limit for crawl requests, and waits until the load drops.

With CrawlCoach

Paid plans check your site every day and email you when a page drops off Google, so a server problem that costs you pages does not go unseen. Google makes the final call on what it indexes.

Related Page indexing reasons

Server error (5xx): Your server showed an error when Google asked for the page.
Blocked due to access forbidden (403): The server turned Google away with 403 Forbidden.

Questions

What does "Page fetch failed: Server connection error" mean?

Google could not connect to your server. It never got to ask for the page. Check your firewall, server uptime, and DNS.

Is Server connection error the same as Server error (5xx)?

No. With a 5xx error, your server answered with an error. With Server connection error, Google could not connect at all.

What does "Not available due to a site-wide issue" mean?

The live test could not check the page because of a problem with the whole site, such as DNS, the server connection, or robots.txt. Page fetch says which one.

Sources

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

"Server connection error" in URL Inspection: what to check