Rendered pages with screenshots

What this example returns

The dataset’s “Overview” view shows 14 columns: Page, Status, Change, Changed %, Title, Checked, Previous check, Last change, Checks, Changes, Screenshot, Before last change, Note, and Error. See every output field.

What each setting does

The input this example runs Website Change Monitor with. “Try this input” opens it in the console, where you can run it as-is or change any field first.

Pages to monitor startUrls

https://playwright.dev/, https://scrape.ly/store

Web pages to check. Each run compares every page with the version saved by the previous run of the same monitor and reports what changed. `url` (one address) and `urls` (a list) are accepted too.

Monitored area (CSS selector) contentSelector

main

Only watch this part of each page, e.g. `main`, `#price` or `.job-list li`. Every matching element is included. Leave empty to watch the whole page.

Monitor name monitorName

rendered-pages

Each monitor keeps its own history of page versions in your account. Runs with the same name continue the same history; use different names to watch the same page separately. Leave empty to use the saved task's own history (or `default` outside a task).

Render JavaScript renderJavaScript

Yes

Load pages in a real browser so content built by JavaScript is included. Slower than the default plain loading; the price per check stays the same.

Default: No → this example uses Yes

Save screenshots saveScreenshots

Yes

Save a PNG of the monitored area (or the whole page) on every check and keep the version from before the last change, with links in each row. Uses the browser; the price per check stays the same.

Default: No → this example uses Yes

Extra wait in the browser (seconds) waitSecs

1

Extra time to wait after the page has loaded, for content that appears late. Browser only.

Default: 0 → this example uses 1

{
  "startUrls": [
    {
      "url": "https://playwright.dev/"
    },
    {
      "url": "https://scrape.ly/store"
    }
  ],
  "contentSelector": "main",
  "renderJavaScript": true,
  "saveScreenshots": true,
  "waitSecs": 1,
  "monitorName": "rendered-pages"
}

What it costs

You pay for the events the actor reports, such as each result or page it produces. Platform usage is included in the event prices: compute, proxies, browser and storage cost nothing extra.

• Page checkfrom $0.0012One page loaded and compared with its previous version, whether it changed or not, also in the browser or with screenshots. Pages that cannot be checked are free.

Full pricing

When to use this example

From the Website Change Monitor readme:

Other ways to run Website Change Monitor

• Watch the main area of several pagesCompare the main content of pricing, docs and API pages with the last check, ignoring footers and clock times.
• Compare markup and send webhook alertsDetect markup changes on a news list and an API answer and post each change and each failed page to a webhook.

All examples of Website Change Monitor

About Website Change Monitor

Watch any web page, or just one part of it, for changes. Every run compares each page with the previous check and returns what changed: added and removed lines, a diff, change share, before and after content and optional screenshots, with webhook alerts for Slack, Teams or Discord.

Price:

from $1.20 / 1,000 results

Developer:

Querystone

Categories:

Developer tools, Automation, SEO tools

Website Change Monitor pageOutput fieldsPricing