Empty, failed and no-value pages

Inspect the affected URLs

For a completed Cloud job, open Inspect and use the Empty pages or Failed pages tab to review individual URLs.

From the scraping jobs table, you can also select the linked number under Failed pages, Empty pages, or No value pages to open that inspection view directly.

For each affected page, Web Scraper can show:

  • The URL that was processed.
  • The failure reason, when available.
  • A preview of the page, when available.
  • The page HTML, available for download.

This information is useful because the HTTP request may have completed while the returned page was not the expected content. A screenshot can reveal an access-denied response, CAPTCHA, consent screen or another unexpected page state that would not be obvious from the sitemap configuration alone.

Failed page

Check the failure reason and available screenshot. Fast driver jobs do not produce screenshots.

Empty page

The page loaded, but no data was extracted. Check that the URL is valid, points to the expected page, and that the relevant selectors still match the page content.

No-value page

Matching elements were found, but no populated values reached the final dataset. Check the relevant selectors and the page layout.

Retries

Cloud automatically retries empty and failed pages without using additional page credits. If pages still fail after the retries, check the failure reason and the sitemap before running the job again.

Inspect the returned content

A page can load successfully but still show a consent page, login screen, bot challenge, empty page, or regional version. Check the returned content and extracted data, not just whether the page loaded.

Common Failed page reasons

Failed pages can include target-site HTTP 4xx/5xx responses and Web Scraper-specific reasons such as Timeout or a Website State Setup element that could not be found. CAPTCHA pages may be reported as CAPTCHA or surface through another access/error response.

See Troubleshoot Cloud scraping jobs for the failure-reason and HTTP-status reference.

Related