Contents / Content monitoring

Advanced — blocked fetches, fetch channels and other settings

#Target refuses fetches

Typical symptoms: the watch keeps failing or returns a verification/blank page. Try, in order:

  1. Change UA / headers: the form lets you customize the User-Agent and other headers.
  2. Switch fetch channel: send requests through your proxy or your own node (see Vantage points & proxies).
  3. Raise the interval: frequent fetches trip risk controls — raise the interval to hourly.
  4. Change approach: if the page data comes from an API, use the API JSON method to read the endpoint directly (see Extraction rules).
Compliance note

Monitoring is only for pages you're entitled to access. Bypassing anti-bot measures or high-frequency scraping may violate the other site's terms and get IPs banned. WebCheck blocks internal/reserved addresses per safety rules.

#Other advanced items

Related: Alerts & notifications

← Content monitoring