Page Not Accessible to Crawler

What This Means

The crawler was unable to retrieve the page — no HTTP response was received. This is distinct from HTTP error codes: rather than the server returning a 4xx or 5xx response, the connection itself failed. Causes include DNS resolution failure, connection timeout, TCP connection refused, TLS handshake failure, or the crawler being blocked at the network level.

Why It Matters for SEO

A page that cannot be accessed at all is completely invisible to search engines. It cannot be indexed, cannot accumulate ranking signals, and any internal links pointing to it deliver crawl budget to a dead end. This is an error-level check because inaccessibility is more severe than a standard HTTP error — there is not even a response to work with.

What the Platform Checks

The platform attempts a full HTTP connection to each discovered URL and records whether a valid HTTP response was received. Fires when the connection attempt fails entirely with no status code — timeout, connection refused, DNS failure, or similar network-level failure.

How to Fix It

• DNS failure: Check that the domain resolves correctly. Run dig yourdomain.com or nslookup yourdomain.com.
• Connection timeout: The server may be down, overloaded, or the crawler's IP may be rate-limited or blocked by a firewall rule.
• TLS errors: Check your SSL certificate validity (expiry, hostname mismatch, chain issues).
• Firewall/IP blocking: Ensure your WAF or CDN is not blocking crawlers based on user-agent or IP range. Allow Googlebot's published IP ranges.
• Specific page block: Check whether the URL pattern is blocked in robots.txt or via .htaccess for the crawler's user-agent.