How to Set Up Distill.io to Monitor a Page That Needs a Login

Short answer: If the page is already open and signed in on your computer, create the monitor from that page and run it on your local browser. The browser must remain available for local checks. If checks need to run while your computer is off, configure Distill’s cloud browser with a supported saved session, profile, or login macro, then select that cloud device for the monitor.

Cloud authentication depends on how the site handles login. Cookies can expire, and some interactive sign-in flows cannot be replayed in the cloud. Start locally when you are unsure; it uses the session you have already confirmed works.

1. Choose where Distill should check the page

Method	Where checks run	Best fit	Main limitation
Local browser	Your browser or app on your device	The page is already signed in and the device can stay available	Checks stop when the device or relevant app/browser is unavailable
Dedicated Cloud Device	A persistent browser in Distill’s cloud	Checks must continue when your computer is off	You must establish and maintain a usable login session
Profile with saved cookies	A cloud browser using a saved profile	The site accepts a reusable cookie session	Cookies may expire; profile availability depends on the plan
Macro	A cloud browser replaying recorded login steps	The login flow can be replayed with the available macro feature	Interactive steps such as some MFA or email confirmation may not work

Distill describes local monitoring as suitable for login-required pages that maintain an active session. Dedicated Cloud Devices preserve browser data such as cookies and local storage; Distill says they are included with paid plans. Macro and profile availability depends on the subscription. Check your account’s current feature access before choosing a cloud method.

2. Set up a local monitor from a signed-in browser

Install the Distill extension in the browser you will use for monitoring, then pin it for easy access.
Open the target page and sign in manually. Navigate to the exact page whose changes matter and confirm the relevant content is visible.
Open Distill and start creating a monitor from the current page.
Choose full-page monitoring or select the specific content region to watch. Prefer a stable, meaningful section—such as a status, price, or notice—over a whole page full of changing timestamps or navigation.
In the monitor options, choose the local browser/device that has the signed-in session.
Give the monitor a recognizable name, choose a check schedule and alert actions, and save it.
Keep the computer and the relevant browser or Distill app available when checks are due. If the page requires an active tab, leave it open or use the appropriate local app workflow.

When creating the monitor, verify that the preview contains the authenticated content, not a login form, loading placeholder, or access-denied message. That preview is the fastest way to catch a session or selection problem before relying on alerts.

3. Run authenticated checks in Distill’s cloud

Use a cloud option when monitoring must continue independently of your computer. First confirm that the site’s sign-in flow can be retained or replayed by the option you plan to use.

Option A: Dedicated Cloud Device

In Distill’s Watchlist, open Devices and add a Dedicated Cloud Device.
Open or configure its remote browser and sign in to the target site.
Confirm the protected page loads with the content visible. Close the device after the browser session has been saved, following Distill’s workflow.
Create the monitor and select that Dedicated Cloud Device as the device that will run checks.
Check the monitor’s first result and revisit the device to sign in again if the stored session later expires.

Option B: Profile and saved cookies

Create a Profile and open its remote browser.
Sign in to the site in that browser and save the cookies using Distill’s profile workflow.
Create a Webpage with profile monitor, select the saved profile, and choose the content to watch.
If checks later lose authentication, reopen the profile, sign in again, and save the cookies again.

Saved cookies are not permanent credentials. A site can invalidate them after a timeout, password change, security event, or its own session policy. Profile counts and access depend on the subscription plan.

Record the login interactions needed to reach the protected page using Distill’s macro workflow.
When creating the monitor, select the macro and let it reach the authenticated page.
Select the desired content after the macro has navigated to the right page, then save the monitor with the intended cloud device.
Review the first check to confirm the macro completed and the selected content is the signed-in page content.

Do not assume a macro can complete every login. Multi-factor prompts, CAPTCHA, email verification, and other interactive challenges may require a person. Distill has described a case where cloud macros could not automate email-based authentication and recommended local Chrome monitoring with the existing signed-in session. Treat that as an example of a limitation, not a guarantee about every site or login flow.

4. Select the right content and schedule

Monitor a specific region when only one value or section matters. This cuts down alerts caused by unrelated page changes.
Monitor the full page when changes anywhere on the page matter, accepting that navigation, counters, or rotating content may create noise.
Allow for delayed content. If the page fills in after initial navigation, configure an appropriate wait or delay where the monitor options allow it.
Choose a schedule that fits the change. A frequently updated page may need more frequent checks than a policy page. Consider the site’s access limits and your plan’s available options.
Set an alert action that reaches the person who can investigate the change. Test the path by checking monitor history and alert settings rather than assuming a missing notification means the page did not change.

For enterprise local-monitoring setups, Distill documents associating the monitor with the device’s Primary Workspace; use a shared workspace when teammates need to see and manage it. The workspace setting is per browser/device.

5. Troubleshoot failed checks and missed changes

Symptom	Likely cause	What to do
Forbidden, unauthorized, or login page in the result	The check has no valid authenticated session or expected cookies are missing	Open the chosen local browser, profile, or cloud device and confirm sign-in. Refresh the saved session; if cloud authentication is unsuitable, switch to a local check.
The monitor worked and then stopped	Saved cookies or the site session expired	Reauthenticate in the Profile or Dedicated Cloud Device and save the session again. Review the check error log for the actual response.
Cloud checks are blocked	The site rejects or restricts the cloud request	Try local monitoring from the signed-in browser. Do not keep rebuilding the monitor until you have confirmed the cloud request can reach the authenticated page.
The check succeeds but changes are missed	The selected region no longer matches, or content loads after the check reads the page	Inspect the monitor selection and current page structure. Select the updated content and add a suitable delay for late-loading content.
A page needing an active tab fails in the background	The page depends on an active browser tab or interactive browser state	Use Distill’s desktop app for a local check or investigate a cloud check if the site supports it.
Cloud login stops at MFA, CAPTCHA, or email verification	The flow requires interaction the selected automation cannot provide	Complete the login manually in a persistent supported session if possible, or monitor locally from an already authenticated browser.
Alerts do not arrive	The check may have failed, no selected content changed, or the alert action is misconfigured	Inspect the error log and check history first, then verify the selected region and alert action.

Distill’s troubleshooting guidance identifies authentication failures, blocked access, changed selections, and delayed content as distinct causes. Use the check error log to diagnose the cause before recreating a monitor.

6. Reliability, performance, and cost considerations

Device availability: local checks depend on the device and relevant app/browser being available. Cloud checks avoid that dependency, but rely on the cloud session remaining valid.
Session maintenance: plan for occasional reauthentication, especially with saved cookies. A monitor that was once authenticated can become stale without any change to its configuration.
Page readiness: complex pages may load content asynchronously. A check that runs too early can miss the content even when login succeeded; tune waits and verify the captured selection.
Signal quality: selecting only the part of the page that matters generally reduces irrelevant change detection. Dynamic advertisements, timestamps, and rotating content can otherwise create noisy results.
Site restrictions: a website may block cloud traffic or impose access controls. Use an authorized account and a monitoring method the site permits.
Plan fit: Distill documents plan-dependent access for profiles and macros, and says Dedicated Cloud Devices are included on paid plans. Confirm current plan entitlements and quotas in Distill before depending on a feature; this guide does not quote prices.

7. Or skip the browser setup

Distill watches for page changes over time. ScreenshotNeo is a website screenshot API and MCP server for developers: use it when you need a clean snapshot of an authenticated or public page, rather than an ongoing change monitor. It does not replace Distill’s scheduled change detection.

For a public page, this cURL request saves a WebP screenshot:

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

Python:

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)

Node.js:

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 import('node:fs/promises').then(fs => fs.writeFile('shot.webp', Buffer.from(await res.arrayBuffer())));

See the ScreenshotNeo API documentation for request options and authentication. These examples capture a URL; they do not sign in to a site on your behalf. ScreenshotNeo also supports custom headers and cookies for requests where the site accepts them, but interactive login flows may require a browser session and should not be assumed to work from a simple request.

ScreenshotNeo removes cookie and consent banners, newsletter popups, and chat widgets before capture. Bot checks, blank pages, failed loads, timeouts, and cache hits are not billed; response headers identify the page verdict and billing status. Its MCP server offers take_screenshot, get_page_info, and capture_pdf for AI agents. The Free plan includes 1,000 screenshots per month with no card; paid plans start at $5 for 3,000 screenshots. Every feature is available on every plan.

Create a free ScreenshotNeo account for 1,000 screenshots a month with no card.

8. Frequently asked questions

Can Distill monitor a page that requires a password?

Yes, if the check runs in a browser session that is authenticated. The simplest starting point is the local browser where you have already signed in.

Will local monitoring keep working if I close my computer?

No. Local checks depend on your device and the relevant browser or app being available. Use an appropriate cloud setup for checks that must run while the device is off.

Do saved cookies last forever?

No. A site can expire or invalidate them. Sign in again in the saved Profile or Dedicated Cloud Device and save the session again.

Can I use ScreenshotNeo instead of Distill for change alerts?

No. ScreenshotNeo returns screenshots or PDFs; it is useful for captures and agent workflows, while Distill is the option in this guide for monitoring changes over time.

Sources

Distill’s official materials referenced for this guide: “How to monitor webpages with login and password?”, “Dedicated Cloud Devices,” “Distill Chrome Extension – Monitor Website Changes,” “What is Distill?,” “Troubleshooting errors in checks,” “Running Local Monitors,” “Supported Platforms,” and “Why Didn’t I Get an Alert?” The research dossier supplied titles and findings but no source URLs, so links are not fabricated.