Check permission.
Then check the capture.
A publicly readable page and a successful preview do not establish permission for recurring automated checks. Choose a source and workflow that its publisher permits.
Before creating a monitor
- Prefer a page you own, explicit permission from the publisher, or an official feed intended for subscription.
- Check the terms for the exact website and use. Marketplace regions and separate services may have different policies.
- Respect the publisher’s robots policy, rate limits and any restrictions attached to a feed or document. An allowed robots path is not, by itself, a grant of permission.
- Choose the smallest useful scope and a reasonable interval. Keep selected private content out of shared workspaces unless everyone with access is entitled to see it.
PageFluxer’s preview validates capture. It does not make a legal determination or certify that a website permits your intended monitoring. A site-specific guide is not a grant of permission or a partnership with the publisher.
When a check cannot capture the page
| Symptom | Next step |
|---|---|
| 403, access denied or CAPTCHA | Review the site’s policy and your permission. Pause recurring attempts when access is restricted. Do not treat a challenge page as the requested content. |
| 429 or rate limiting | Respect the publisher’s wait instructions and reduce request frequency. Repeated immediate retries do not establish access. |
| 404 or a moved page | Find the current official URL and review the monitor’s scope before changing it. A missing page is not automatically a meaningful content change. |
| Login page or expired session | For an authorised signed-in workflow, reconnect or sign in using the supported method, then verify the expected content in a fresh capture. |
| Loading shell or missing selected element | Check the selection and whether JavaScript is required. Use bounded loading controls only for content you are permitted to access. |
Failed checks keep the last successful capture. They do not prove that nothing changed during the gap. After recovery, compare timestamps as well as values; changes between successful observations may have been missed.
Active Cloud checks can retry with backoff. Review monitor health and pause a monitor if its access is no longer appropriate. See HTML and Browser checks for capture limits and Local browser health for device availability.
Cloud and Local change the execution environment
Cloud HTML reads a public response. Cloud Browser can render JavaScript within supported limits. Local runs through the connected desktop Chrome profile while that device is awake and online. A Cloud site connection is a separately approved session.
Switching methods does not remove a publisher’s restrictions. Do not use Local, a different IP address or recorded actions to evade a denied request. If an authorised workflow needs your normal browser session, test that setup and follow the publisher’s conditions.
Transfers preserve supported monitor history after confirmation, but they are not a remedy for missing permission. Older extension versions retain their existing capabilities; consult the extension changelog for supported controls.
Start with a suitable practice source
The PageFluxer practice page deliberately changes a fictional price. The example kit provides files to host at URLs you control. Books to Scrape explicitly provides a scraping sandbox.
For real publishing workflows, our GOV.UK walkthrough links the publisher’s explicit access policy. The WordPress release guide uses an official feed and explains the limits of that source. Recheck policies before setup; permission for one source is not permission for every page on a platform.