Redirects & server responses
Pages failed to load
One of the 136 checks Lala SEO runs on every page of a site in a free audit.
- How serious
- Serious. Can stop pages from appearing in Google, or from working for visitors. Fix these first.
- Based on
- Industry standard: Google does not document this one, so the check follows established practice.
What is wrong
When our crawler tried to request your pages, the server failed to send them back. This means the pages exist but something went wrong during the fetch—perhaps a timeout, a connection drop, a server error, or a temporary outage. Unlike a 404 error, where the page genuinely does not exist, a fetch error suggests the page is there but unreachable at the moment we checked.
Why it costs you
Search engines cannot index pages they cannot retrieve. If Google's crawler hits the same fetch errors, those pages stay out of search results. Visitors who find a link to your site from elsewhere will see error messages instead of your content. Even pages that worked yesterday can vanish from search visibility if they become intermittently unreachable.
How to fix it
Check your server logs to find what went wrong when we tried to fetch each page—look for timeout messages, 5xx errors, or connection resets. Fix any server-side issues (misconfigured redirects, resource limits, or crashing processes). If the errors are intermittent, set up monitoring to alert you when pages stop responding. Test the affected URLs yourself in your browser and from outside your network to confirm they load reliably. Once fixed, request a recrawl in Google Search Console so the search engine retries indexing.
What the audit tests
- The page answered our request instead of failing outright (DNS, TLS, timeout)
Check your site
Run a free audit of up to 300 pages. No card needed.
Start a free audit