How to Take Scheduled Website Screenshots with PageCrawl.io

To schedule website screenshots with PageCrawl.io, configure the workspace schedule in Settings > Workspace > Scheduling, choose active weekdays and start/end hours, and confirm the workspace timezone. Then set the check frequency separately in each page’s editor. The schedule defines when checks may run; frequency defines how often each page is checked during those hours.

Workspace scheduling is a paid-plan feature according to PageCrawl’s help documentation. Checks pause outside the selected days and hours, then resume at the next active period. PageCrawl’s scheduling guide covers the workspace controls and page frequency settings.

1. Decide what you need to capture

Before setting a schedule, decide what a useful check looks like. A full-page screenshot can reveal broad layout changes, while visual tracking of a relevant image, chart, or page area can make a change easier to spot. For product pages, PageCrawl’s browser-extension guide also describes price and restock monitoring; parsed-value or content tracking may be more actionable than a screenshot when you care about one specific field.

• Layout or visual changes: use visual tracking for changes to page appearance, images, charts, or layout.
• A specific value: use parsed-value or content tracking when the monitored fact is more important than the overall appearance.
• Price or stock: choose the corresponding product-page monitoring mode where available.

A screenshot shows what the configured monitor captured. It does not guarantee that every page will render successfully: access restrictions, page behavior, and engine choice can affect the result.

2. Set the workspace schedule and timezone

1. Open PageCrawl’s workspace settings and go to Scheduling.
2. Set the workspace timezone first. This matters when teammates work in different regions or when the schedule is meant to align with local business hours.
3. Select the weekdays when checks may run.
4. Choose the active start and end hours, then save the schedule.

PageCrawl converts the selected schedule hours to UTC based on the workspace timezone. If the timezone is wrong, the checks can run at the wrong local time even when the selected hours appear correct. Confirm the timezone after changes to team or workspace settings.

Inactive days and hours pause checks. PageCrawl says checks resume automatically in the next active period; the schedule does not itself trigger a screenshot at the instant the window begins.

3. Set each page’s check frequency

Workspace hours and page frequency control different things. The workspace schedule sets the permitted checking window. The page editor’s frequency determines how often an individual page is checked within that window.

1. Open a monitored page’s editor.
2. Choose a frequency that fits the urgency of the change you want to detect.
3. Repeat for pages that need different monitoring cadence.

The PageCrawl help article lists choices from every two minutes through monthly, with plan-dependent minimum intervals. Its documented minimums are hourly on Free, every 15 minutes on Standard, every five minutes on Enterprise, and every two minutes on Ultimate. Plan limits and prices can change, so check the current PageCrawl pricing page before choosing a plan or relying on a particular interval.

When a page’s frequency is shorter than the active window, several checks may happen in that window. When the frequency is longer, a check may not occur at the window’s start. Choose frequency based on how quickly you need to detect a change, and account for the fact that notifications arrive after a scheduled check detects one.

4. Choose notifications and screenshot retention

Set up the notification or integration that fits the workflow. PageCrawl documents alerts after a scheduled check detects a change, so alert timing follows the check cadence and the page’s configured tracking mode. Its integrations documentation lists Dropbox sync for screenshots and captured history.

Retention is plan-dependent. The pricing information reviewed for this guide lists the last three screenshots on Free, 12 months on Standard, and unlimited screenshot storage on Enterprise and Ultimate. Check current plan details before treating PageCrawl as a long-term archive; plan features can change.

5. Check the schedule is doing what you expect

• Verify the workspace timezone and compare a planned check time in that timezone with UTC.
• Check the page editor to confirm its individual frequency.
• Confirm the page uses the intended tracking mode and that the monitored area or value is configured correctly.
• Allow for the next eligible check; a schedule window opening does not mean an alert is sent immediately.
• Review screenshot retention and notification destinations against the current plan.

PageCrawl documents Default, Stealth, and Fast browser-engine modes for different page situations. If a site’s behavior or access restrictions prevent a useful capture, review the engine guidance and the page’s monitoring setup. The documentation does not promise successful capture on every scheduled run.

Common problems and fixes

Symptom	Likely cause	What to check
No check outside selected hours	The workspace schedule pauses checks outside active days and hours.	Confirm the intended days and window; checks should resume at the next active period.
Checks run at an unexpected local time	The workspace timezone may be incorrect; schedule hours are converted to UTC from it.	Verify the workspace timezone, then review the selected hours.
No alert at the schedule’s start time	The schedule controls eligibility, while page frequency controls cadence. Alerts follow a detected change.	Check the page frequency and wait for its next eligible check.
A screenshot is missing or does not show the expected page	Page behavior, access restrictions, rendering, or monitor configuration may affect capture.	Review the page URL and tracking mode, then consult PageCrawl’s engine-selection guidance for Default, Stealth, and Fast modes.
Older screenshots are unavailable	The plan may have limited screenshot retention.	Check current retention terms and use an integration such as Dropbox sync if it suits your archive workflow.
The desired frequency is unavailable	Minimum check intervals vary by plan.	Compare the current plan limits with the cadence you need before changing the schedule.

Performance, reliability, and cost considerations

Cadence and detection delay: more frequent checks can shorten the time before a change is detected, while a narrow workspace window limits when checks may run. Choose the slowest cadence that still meets the monitoring need, and remember that alert delivery follows detection rather than the window opening.

Reliability: schedule settings govern when checks can run; they do not guarantee that a site will be accessible or render identically on every run. Page restrictions and monitor configuration can matter. Use the engine guidance when a page behaves differently from expected, and avoid treating an individual screenshot as proof that every visitor sees the same result.

Cost and plan fit: workspace scheduling is documented as a paid feature. Compare the current page limits, monthly checks, minimum frequency, retention, and schedule availability for each plan. The plan details cited here are from PageCrawl’s published materials accessed for this guide and should be rechecked before purchase.

Or skip the browser setup

If you need a screenshot on demand or want to build capture into your own scheduler, ScreenshotNeo provides a website screenshot API and MCP server. A scheduled task can call its endpoint once per target URL. See the ScreenshotNeo API documentation for request options.

curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webp

import requests

r = requests.get(
    "https://api.screenshotneo.com/v1/shot",
    params={"access_key": "YOUR_API_KEY", "url": "https://stripe.com"},
    timeout=90,
)
r.raise_for_status()
open("shot.webp", "wb").write(r.content)

const q = new URLSearchParams({ access_key: 'YOUR_API_KEY', url: 'https://stripe.com' });
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);
if (!res.ok) throw new Error(`Screenshot request failed: ${res.status}`);
await Bun.write('shot.webp', res);

Replace the example URL with the page you want to capture. Keep the API key in a secret store or environment variable in production rather than committing it to source control. The request returns an image or PDF according to the requested format and options. ScreenshotNeo removes cookie and consent banners, newsletter popups, and chat widgets before capture; each cleanup step can be turned off. Bot checks and CAPTCHAs, blank pages, timeouts, failed loads, and cache hits are not billed, and response headers report the page verdict and billing status. Its MCP server offers take_screenshot, get_page_info, and capture_pdf for AI agents.

ScreenshotNeo includes 1,000 screenshots per month free with no card; paid plans start at $5 for 3,000 screenshots. Every feature is available on every plan. Sign up free for ScreenshotNeo.

FAQ

Does a PageCrawl schedule apply to every page?

The schedule is configured at workspace level. Each page has its own check-frequency setting in its editor.

Does a check run as soon as the active window opens?

Not necessarily. The schedule sets allowed hours; page frequency controls when a check is due.

How long are PageCrawl screenshots kept?

The reviewed pricing page lists three screenshots on Free, 12 months on Standard, and unlimited storage on Enterprise and Ultimate. Confirm current plan terms before depending on a retention period.

Can I schedule a daily summary instead of checking pages?

PageCrawl documents scheduled reports as a separate feature that bundles detected changes into digests. Reports and page-check schedules serve different purposes, and the help article identifies reports as paid.