No response or timeout

HighHigh priority, in Response codes

Short answer

No response or timeout means: these pages never answered, so neither visitors nor Google can load them. To fix it: check that the server is up and fast enough. Pages that take more than a few seconds need a faster server or caching.

By the SmooxSEO team. Updated on 16 November 2026.

What it means and why it matters

These pages never answered, so neither visitors nor Google can load them.

How to fix it

Check that the server is up and fast enough. Pages that take more than a few seconds need a faster server or caching.

Common causes

  • The server is too slow and the page takes longer than the crawler waits (often 20 to 30 seconds).
  • A firewall, rate limit or anti-bot service drops requests from crawlers without answering.
  • Heavy pages (huge database queries, reports, search results) that time out.
  • Network or DNS problems at the host.

How to spot it

Load the page in a private window and time it. Tools like PageSpeed Insights show the server response time (TTFB). Check whether your firewall or CDN logs blocked requests. SmooxSEO lists every page that didn't answer in time during the crawl.

Mistakes to avoid

  • Testing only from your own computer: the page may be cached for you but slow for crawlers.
  • Blocking all bots to "save resources": search engines and AI assistants then can't read your site.

How serious is it?

A page can't be found, indexed or trusted, or search engines can't read part of the site. Fix it soon: it costs traffic.

About response codes checks

What your server answers for each page: working pages (200), redirects (3xx), missing pages (4xx) and server errors (5xx). Search engines only show pages that answer correctly.

Find this problem on your site

SmooxSEO checks every page of your site for this problem and 311 others, lists the pages concerned, and tells you what to fix first.

Related response codes checks

All response codes checksAll 312 checks