Monitor Password-Protected Websites for Changes

This guide shows you how to automatically track password-protected websites for changes, so you get notified when a page updates without having to log in and check manually. You’ll need a web browser, a free account with a change-detection service, and the login credentials for the site you want to monitor.

What You’ll Need

A computer or phone with a modern web browser (Chrome, Firefox, Safari, or Edge).
A valid account on the website you want to monitor, with username and password.
A free or paid account with a change-detection service (examples: Visualping, Distill.io, or Changedetection.io).
An email address that you check regularly, or a Slack/Telegram account if you prefer notifications there.

Step-by-Step

Choose a change-detection service. Sign up for one that supports password-protected pages. Most free tiers allow a limited number of monitored pages and check intervals (e.g., every 24 hours).
Create a new monitor/watch. In the service’s dashboard, click the “New Monitor” or “Add Page” button. You’ll be asked for the URL of the page you want to track.
Enter the page URL. Copy the exact URL of the password-protected page (e.g., https://example.com/account/orders). Paste it into the monitor field.
Configure login credentials. Look for a section labeled “Authentication,” “Login,” or “Session.” Enter the username and password the service will use to log in. Some services support two-step login flows, but most just need the basic credentials.
Set the check frequency. Choose how often the service should check the page. Free plans often have a minimum interval of 24 hours. If you need more frequent checks, you may need a paid plan.
Select the type of change to detect. Most services offer two modes: “Visual” (compares screenshots) and “Text/Diff” (compares HTML content). For password-protected pages, text mode is usually more reliable because it ignores layout changes. Choose text mode if available.
Set up notifications. Enter your email address, or connect Slack/Telegram. Choose whether you want to be notified on every change or only once per day (to avoid alert fatigue).
Test the monitor. Many services have a “Test” button that runs a check immediately. Use it to verify that the service can log in successfully and see the page. If the test fails, check the credentials or try a different authentication method.
Save and activate. Save the monitor and wait for the first scheduled check. The service will compare the page content against a baseline snapshot taken during the first check.
Review the first alert. When you get a notification, log into the service to see what changed. The diff view will highlight added/removed text, so you can confirm the change is meaningful.

Common Mistakes

Using the wrong URL. Some sites have a login page that redirects after login. Make sure you’re monitoring the post-login page, not the login form itself.
Entering credentials in the wrong fields. Some services have separate “login URL” and “credentials” fields. If you only fill in the URL, the service may never log in.
Ignoring session expiration. Many sites expire sessions after a few days. The service should handle re-login automatically, but if it doesn’t, you’ll get false “page changed” alerts when the login page appears.
Choosing visual mode for dynamic pages. If the page has timestamps, ads, or random elements, visual mode will alert on every tiny change. Text mode with “ignore whitespace” is usually better.
Not testing after setup. Skipping the test step can leave you with a monitor that never works, and you won’t know until you miss an important update.

Tips

Use a dedicated email address for change notifications so they don’t get lost in your inbox.
If the site has two-factor authentication (2FA), most change-detection services cannot handle it. Look for a site that offers an API or a separate “read-only” access token.
For pages that require a multi-step login (e.g., first enter email, then password), use a service that supports custom login flows, or use a browser extension that records your session.
Set up a “keyword filter” if the service supports it. For example, you can monitor a page but only get alerted when a specific word like “back in stock” appears.
Check the service’s privacy policy. Your credentials are stored on their servers, so choose a reputable provider with HTTPS encryption.

Troubleshooting

Monitor shows “Login failed” or “Page not found.” First, manually log in with the same credentials to ensure they’re correct. Then, check if the site uses a login form that requires a CSRF token or a captcha. If so, the service may not be able to log in. Try a different service that supports headless browsers, or use a browser extension that captures cookies.

You get alerts for changes that aren’t real. This often happens with dynamic content like timestamps or user-specific greetings. Switch to text mode and enable “ignore whitespace” and “ignore numbers” if available. You can also set a “CSS selector” to monitor only a specific part of the page (e.g., the order status div).

No alerts at all. Check the service’s dashboard to see if the last check was successful. If it shows “error,” the site may be blocking the service’s IP or requiring JavaScript. Try a service that uses a real browser. Also, verify that your notification email isn’t in spam.

Session expires quickly. Some sites log out after 15 minutes. The service should re-login on each check, but if it doesn’t, look for a “re-login on each check” option. Alternatively, use a service that stores cookies and refreshes them automatically.

You’re monitoring a page that requires a click to load content. If the page uses infinite scroll or tabs, the service may only see the initial HTML. Use a “click” or “scroll” action in the monitor settings if the service supports it, or monitor a different URL that shows the full content.

Frequently Asked Questions

Can I monitor a site that uses two-factor authentication? Most change-detection services cannot handle 2FA because they cannot receive the code. If the site offers an API token or an app-specific password, you can use that instead. Otherwise, you may need to use a browser extension that records your logged-in session.

Is it legal to monitor a password-protected site? Generally, yes, as long as you have legitimate access to the account and you’re not scraping data for commercial purposes. Check the site’s terms of service—some prohibit automated access. Use the service responsibly and don’t overload the site with frequent checks.

How often can I check for free? Most free plans allow checks every 24 hours. Some offer 1-hour checks on a trial basis. For more frequent monitoring, you’ll likely need a paid plan.

What if the site changes its login page? If the login form changes (e.g., new field names), the service may fail to log in. You’ll need to update the monitor’s login settings. The service will usually show an error, so you’ll know to fix it.

Can I monitor multiple pages at once? Yes, most services allow you to create multiple monitors. Just be aware of the limits on your plan. Each monitor counts toward your total.

Will the service store my password securely? Reputable services encrypt credentials and use HTTPS. However, it’s wise to use a unique password for the site you’re monitoring, and change it periodically. Never use your main email password.

General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.

More in this bed

The whole Tech How-To bed →