Skip to content
Menu
Check library

Pages that could not be fetched

Investigate failures affecting public pages or preventing a representative assessment. Preserve intentional restrictions and respect the server’s stated request limits.

What the findings mean

The page-fetch finding means an address could not be retrieved during the recorded inspection. Possible causes include DNS, TLS, timeouts, access restrictions, rate limits or a server response. Read the recorded error rather than treating every failure as a missing page.

What the evidence cannot establish

The finding does not establish that every visitor or search engine has the same problem. Content checks that could not run remain unmeasured, not passed. A restriction may be deliberate, and repeated attempts are not a repair.

How to prioritise

Investigate failures affecting public pages or preventing a representative assessment. Preserve intentional restrictions and respect the server’s stated request limits.

What to do

  1. Compare the affected address, time and failure type with the website’s server or CDN logs.
  2. Identify whether the fault is in the address, name lookup, certificate, server application or intended access policy.
  3. Correct the responsible component for content that should be public. Retain legitimate protection; respect Retry-After and other rate-limit signals.
  4. After the correction, check a small representative set before assessing a broader run.

Check the result

Confirm that the affected public pages return the intended content and response. In a later authorised check, verify that the pages were actually fetched and assessed. Keep intentional restrictions documented as such.

Need help with a particular finding?

Contact us →