How to Configure Fluxguard Alerts for Website Changes

To configure Fluxguard alerts, add the page or site you want to monitor, let its first crawl establish a baseline, choose the kinds of changes to detect, set a crawl schedule, and select email or webhook delivery. Detection and crawl settings are configured for the monitored site or session; email frequency is configured in Account Settings. A webhook can send detected-change data to your own endpoint.

1. Add a site and establish its baseline

Add the URL or site in Fluxguard and allow the initial crawl to finish.
Use the first capture as the reference state for later comparisons. Fluxguard’s setup material describes captures that can include a screenshot, HTML, extracted text, and a HAR network profile.
Review the captured page before tuning alerts. If the initial state is a consent overlay, an error page, or a partially loaded page, resolve the capture conditions first so later comparisons have a useful reference.

Fluxguard’s [FAQ](https://fluxguard.com/faq/) and [visual-change guide](https://fluxguard.com/how-to-guides/monitor-visual-changes/) explain the initial capture and baseline. For the general setup flow, see [Monitor website changes with Fluxguard](https://fluxguard.com/how-to-guides/monitor-website-changes-with-fluxguard/).

2. Open Session Settings

From the monitored site’s Session View, open the gear icon for Session Settings. The site menu in the dashboard also links to these settings. Look for controls for detection and crawl behavior. Fluxguard’s guides use more than one label for the detection area: one workflow calls it Detect, while the visual guide describes a Comparison tab. Follow the control in your account that selects what changes to compare.

Session Settings also contains crawl frequency and options for discovering or automatically monitoring new URLs, as described in the [Fluxguard FAQ](https://fluxguard.com/faq/).

3. Choose what counts as a change

Choose a comparison type based on what you need to catch. These modes answer different questions; the reviewed Fluxguard documentation does not publish accuracy comparisons between them.

Detection focus	Useful when you need to notice	Consider
Text	Changes to visible copy, notices, prices, dates, or specified phrases	Use keyword rules or remove recurring noise if broad text changes are too chatty.
HTML	Markup or content-structure changes	Dynamic markup can change even when the page appears equivalent to a person.
Visual	Changes in rendered appearance, including layout, styling, or imagery	Choose visual comparison when the rendered page is what matters. The visual guide describes selecting visual change in the Comparison area.
Network	Changes involving scripts, images, fonts, or other network resources	Third-party activity can add noise; use relevant exclusions or network blocks where available.

The general [monitoring walkthrough](https://fluxguard.com/how-to-guides/monitor-website-changes-with-fluxguard/) and [web console guide](https://fluxguard.com/how-to-guides/understand-fluxguard-web-console/) describe comparison and detection options.

Monitor particular keywords

For alerts tied to particular words or phrases, use the text-change detection controls and their advanced options. The keyword guide describes selecting additions or deletions for listed terms. It advises keeping the list to no more than 50 keywords or phrases and describes excluding recurring words that otherwise create noise. Be precise about what should trigger an alert: additions, deletions, or both.

See [Monitor changes to specific keywords](https://fluxguard.com/how-to-guides/monitor-changes-to-specific-keywords-on-any-website/) for the documented workflow.

Reduce noisy changes

Use inclusion or exclusion filters to focus on relevant page areas, and network blocks to exclude irrelevant third-party activity where appropriate. These filters can make the signal easier to review, but they also narrow what is observed. After changing a filter, inspect later captures to make sure the content you care about is still included. Fluxguard’s [how-to index](https://fluxguard.com/how-to-guides/) and [console guide](https://fluxguard.com/how-to-guides/understand-fluxguard-web-console/) cover these controls.

4. Set the crawl schedule

Crawl frequency determines when Fluxguard can observe a change. In Session Settings, open the Crawl controls and select an available interval appropriate to how quickly you need to know. Fluxguard’s frequency guide gives examples such as every 15 minutes, every hour, every day, or every month.

Very fast schedules may require Fluxguard to verify the monitored site. The guide says verification is needed for fast crawl frequencies and instructs users to contact Fluxguard from the domain. Do not assume every account or site can use every interval. See [Monitor website changes every minute, hour, day, or other frequency](https://fluxguard.com/how-to-guides/monitor-website-changes-every-minute-hour-day-or-other-frequency/).

Balance detection speed and load

Use a faster interval when a delay before detection has a real operational cost.
Use a slower interval for pages where daily or weekly awareness is sufficient.
For broad site monitoring, consider how discovered or automatically monitored URLs affect the number of pages being crawled.
Keep in mind that an alert cannot arrive before a crawl observes the change, regardless of email or webhook settings.

The source material does not establish plan limits, crawl performance benchmarks, or a universal recommended interval. Choose based on the page’s change rate, the impact of a missed change, and the schedule available to your account.

5. Configure email alerts

Open Account Settings.
Find the email notification frequency control.
Choose an available cadence, such as immediate delivery, a daily summary, or a weekly summary.
Review any account-level category settings that limit which kinds of site changes appear in email.

Fluxguard says daily summary email is the default and that the cadence can be changed in Account Settings. A crawl may detect a change before a scheduled summary email arrives; the crawl interval and email interval are separate settings. See the [FAQ](https://fluxguard.com/faq/) and [visual-change guide](https://fluxguard.com/how-to-guides/monitor-visual-changes/).

6. Send change notifications to a webhook

Use a webhook when a detected change needs to flow into a custom system, such as an internal review queue or notification service. Fluxguard’s webhook guide describes adding one or more endpoint URLs in Account Settings. When a change is detected, Fluxguard POSTs a JSON data package to the configured endpoint.

Prepare an endpoint that can receive POST requests and process the change notification.
Add the endpoint in Account Settings using Fluxguard’s webhook controls.
Have the receiver validate and record the incoming JSON, then return an appropriate response.
Use any artifact references in the notification to retrieve the files your workflow needs, such as HTML or screenshots.
Save required artifacts promptly. The guide says associated files may only be available for a limited time.

The webhook data package includes change fields and references to files; it does not embed all potentially large artifacts directly. Plan for endpoint availability, duplicate or retried delivery handling, payload validation, and timely artifact retrieval in your receiving application. These are prudent receiver design practices; Fluxguard’s guide does not specify a delivery retry policy or guarantee. Read [Use webhooks to integrate web-change notifications](https://fluxguard.com/how-to-guides/use-webhooks-to-integrate-web-change-notifications/).

Webhook receiver considerations

Keep the handler quick: record the notification and queue slower work such as downloading artifacts.
Handle partial failure: a notification may be recorded successfully even if an artifact URL later expires or a download fails; log that separately.
Protect the endpoint: use your normal endpoint authentication and request validation practices. The reviewed guide does not specify a particular signing scheme, so do not assume one.
Size for event volume: configure webhooks only when the receiver is ready to handle the expected detected-change volume.

7. Optional: use AI change filtering

Fluxguard documents account-level or site-level AI settings that can evaluate and summarize changes, including an option to alert only on changes considered important. Treat this as an additional filter: AI importance judgments are not proof that an alert is correct, and they do not replace choosing suitable detection rules. Review the resulting alerts and summaries against the changes that matter to your use case. See [Generative AI in Fluxguard](https://fluxguard.com/how-to-guides/generative-ai/).

8. Validate the alert path

Once the settings are in place, confirm the end-to-end workflow with a change you can recognize:

Check that the initial baseline represents the intended page state.
Confirm the selected comparison mode and any keyword or exclusion filters.
Verify that the crawl schedule is available for the site and account.
Review Account Settings for the intended email cadence or configured webhook endpoint.
Inspect a subsequent detected change in Fluxguard and confirm that the notification arrived where expected.
If using a webhook, confirm that your receiver recorded the notification and fetched any needed artifacts before they expire.

9. Troubleshooting

Symptom	Likely cause	What to check or do
No alert for a change	The next crawl has not run yet, or the selected detection mode/filter does not include that change.	Check the crawl schedule, baseline, comparison type, and inclusion/exclusion rules. A webhook or immediate email cannot report a change before a crawl detects it.
Too many alerts	Broad detection is surfacing dynamic content, recurring text, or third-party network activity.	Use relevant keyword rules, remove recurring noise, narrow page areas, or block irrelevant network activity. Recheck that important content remains monitored.
Keyword alert does not trigger	The configured rule may only watch additions or deletions, or the text may not match the listed phrase.	Review the advanced text-change options and whether additions, deletions, or both are selected. Keep the list focused; Fluxguard’s guide advises no more than 50 entries.
Visual alert differs from expected	The chosen comparison area may not be visual, or the baseline/capture state may not match the intended rendered page.	Check the initial screenshot, capture state, and visual comparison selection in the relevant settings area.
Fast crawl interval unavailable	Fast frequencies require site verification, and eligibility is not established for every account or site.	Follow Fluxguard’s verification instructions and contact Fluxguard from the monitored domain.
Email arrives later than the detected change	Email delivery is set to a summary cadence rather than immediate delivery.	Review Account Settings and choose an available faster notification cadence if offered.
Webhook receives no notification	No qualifying change has been detected, the endpoint is not configured correctly, or the receiving service is unavailable.	Check that a crawl detected a change, confirm the endpoint in Account Settings, and inspect your receiver’s request logs and availability.
Webhook notification arrives but an artifact is missing	The notification references a separate file, or the file is no longer available.	Fetch referenced files promptly and log artifact-download failures separately from notification processing.
Dashboard labels do not match a tutorial	Fluxguard’s tutorials describe the detection controls with different tab names.	Look for the setting that selects the comparison or detection strategy; the guides refer to both Detect and Comparison.

10. Cost and reliability notes

The reviewed Fluxguard sources do not establish current plan prices, crawl quotas, alert delivery guarantees, webhook retry behavior, or comparative accuracy figures. Check the current account and product details for limits that apply to your monitoring setup. For reliability, keep the monitored URL and baseline intentional, monitor the receiver if you rely on webhooks, and store artifacts you need while they are available.

Or skip the browser setup

If your workflow also needs screenshots on demand, ScreenshotNeo is a website screenshot API and MCP server for developers. It can capture a URL as PNG, JPEG, WebP, or PDF. Its API uses one GET request; 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)
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}`);

Cookie banners are accepted and removed before capture, and known consent platforms, newsletter popups, and chat widgets can be removed; each step can be turned off.
Bot checks, blank pages, timeouts, failed loads, and cache hits are not billed; response headers identify the page verdict and billing status.
An MCP server provides take_screenshot, get_page_info, and capture_pdf tools for AI agents.
The free plan includes 1,000 screenshots per month with no card. Paid plans start at $5 for 3,000 screenshots.

For a monitored site, Fluxguard alerts you when a crawl detects a change; ScreenshotNeo provides an on-demand screenshot capture that can help inspect a page state. They serve different parts of a website-change workflow.

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

Frequently asked questions

How can I receive an email when a web page changes?

Add the page, let its baseline crawl finish, enable the relevant detection mode, and configure email notifications in Account Settings. Fluxguard describes daily summary email as the default.

How soon after a change is detected will I receive an email?

That depends on the email frequency selected in Account Settings. Immediate delivery is an available choice described in the FAQ; a daily or weekly summary can arrive later. Detection itself still depends on the crawl schedule.

Can Fluxguard look for specific keyword changes?

Yes. Use text-change detection’s advanced options to choose additions or deletions for listed keywords or phrases. The official guide recommends no more than 50.

Can I get change alerts in my own application?

Yes. Configure a webhook endpoint in Account Settings to receive a JSON POST when a change is detected. Retrieve referenced artifacts promptly if your workflow needs them.

Does changing email frequency make the site crawl more often?

No. Crawl frequency controls when Fluxguard checks the page; email frequency controls how often notification email is sent. Configure each in its respective settings.