How often does Fluxguard capture and check a website?

Fluxguard does not have one universal capture interval. Its FAQ says newly monitored pages are crawled daily by default, but you can configure different schedules for different sessions or pages. Official materials list options from every 15 minutes through hourly, daily, and monthly; a separate tutorial describes schedules from every few minutes to weekly and manual runs. The pricing page currently advertises five-minute crawling on Premium. Faster schedules may require site verification, and actual availability depends on the account and settings. Fluxguard FAQ, frequency guide, pricing

What “how often” means

Four separate timings affect when you see a result. They are easy to confuse:

Timing	What it controls
Crawl schedule	How often Fluxguard starts a check of a monitored session or page. This is the configurable interval.
Processing speed	How quickly pages are processed after a crawl run starts. Fluxguard says it crawls about one page per minute under ordinary limits; speed varies, verified sites may be faster, and pages are processed sequentially.
Capture wait	An extra delay before a page is captured, useful when content loads slowly. Fluxguard documents up to nine additional seconds in session settings, or a page-level wait action.
Alert cadence	When email reports arrive. Daily summaries are the default described in the FAQ; account settings can change delivery to immediate or weekly.

These timings answer different questions. An hourly schedule does not guarantee that a multi-page session finishes in an hour, and an immediate email setting does not make the next crawl happen immediately. A capture wait can help a page render before its screenshot, but it does not change the interval between runs. See Fluxguard’s FAQ and guide to waiting before capture.

Available schedules and the daily default

Fluxguard’s FAQ describes daily crawling as the default for a newly monitored page. You can change the cadence in Session Settings under the Crawl tab, and sessions can have their own frequencies. Fluxguard’s frequency guide lists every 15 minutes, hourly, daily, and monthly. Its tutorial describes a broader range, from every few minutes to weekly, and says a crawl can also be started manually. The current pricing result advertises five-minute crawling for Premium; verify the live plan and account settings before relying on that cadence. Very fast schedules require verifying the monitored site by emailing Fluxguard from the site’s domain. Frequency guide, monitoring tutorial

Choose a cadence by change urgency

Schedule approach	Useful for	Tradeoff
Every few minutes or 15 minutes	Important pages where a change needs quick detection and the account is eligible.	More page checks consume more credits and can create alerts faster than a team can review them.
Hourly	Key pages that change regularly or need same-day awareness.	Higher credit use than daily checks.
Daily	General monitoring; this is the default described in the FAQ.	A change may remain undetected until the next scheduled crawl.
Weekly or monthly	Lower-priority or relatively static pages.	Changes can go unnoticed for longer.
Manual	One-off checks or a check after a known update.	Someone must start the crawl when it is needed.

Fluxguard recommends using different schedules for different priorities—for example, hourly checks for key pages and weekly checks for older press releases. Its FAQ also says you can specify a time range if you only want crawls during business hours. Fluxguard FAQ

How to change the crawl frequency

Open the monitored site’s session settings.
Open the Crawl tab.
Choose the frequency appropriate for that session, then save the setting.
Set separate schedules for sessions with different priorities, if needed.
If you need checks during a particular part of the day, set a crawl time range.
For very fast intervals, verify the monitored site as Fluxguard requires and confirm the desired interval is available to your account.

Fluxguard’s interface and account eligibility determine the exact choices available. Consult the official frequency guide for the current workflow.

Estimate credit use before making checks more frequent

Fluxguard says it charges one credit per page crawled. Its FAQ gives this example: 10 pages checked hourly use 240 credits per day, or 7,200 credits per month. That is the vendor’s example, not a universal estimate; your total depends on page count, schedule, and actual runs. Fluxguard FAQ

A simple planning formula based on that stated charging rule is:

estimated credits per day = pages crawled per run × runs per day
estimated credits per month = pages crawled per run × runs per day × days in month

For example, 10 pages crawled hourly means 10 × 24 = 240 credits each day. Before shortening an interval, count monitored pages and estimate the increase. Use the faster cadence for pages where quicker detection has a concrete benefit, and slower schedules for low-priority content. Fluxguard cautions that very rapid crawling across many pages can be expensive, produce noisy alerts, and exceed a team’s ability to act on them.

Capture timing versus detection timing

A scheduled crawl checks at its configured cadence, but the time until a change is detected also depends on when the change happens relative to the next run and how long the run takes. A change just after a crawl may wait nearly one full interval for the next scheduled check; a change just before a run may be found sooner. Multi-page runs can take longer because Fluxguard says pages are processed sequentially and the page load time matters.

If the page is captured before its important content appears, adjust the separate capture wait. Fluxguard documents up to nine extra seconds through the session-level “Wait Before Capturing” setting, or a page-level wait action. This helps with rendering delays; it does not increase crawl frequency. Fluxguard capture-wait guide

Or skip the browser setup

If you need a screenshot on demand rather than scheduled change monitoring, ScreenshotNeo is a website screenshot API and MCP server. One GET request returns a PNG, JPEG, WebP, or PDF. For example, capture a page as WebP with cURL:

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

See the ScreenshotNeo API documentation for request options. Cookie banners, popups, and chat widgets are removed before the shot; bot checks, blank pages, and failed loads are never billed. Its MCP server lets AI agents take screenshots. The free plan includes 1,000 screenshots a month with no card, and paid plans start at $5 for 3,000. Sign up for 1,000 free screenshots a month.

Troubleshooting schedule and capture problems

Symptom	Likely cause	What to check
A page is checked only once a day	Daily is the default described in the FAQ, or the session still has a daily schedule.	Open Session Settings → Crawl and review the frequency.
The desired very fast interval is unavailable	Fast crawling may require site verification or plan eligibility.	Verify the monitored site as instructed by Fluxguard and check the live plan settings.
A crawl takes longer than its interval	Interval and processing speed are different; pages are processed sequentially and load times vary.	Reduce the number of pages in that session or allow sufficient time for the run to finish.
The screenshot misses late-loading content	The page needs more time before capture.	Configure the session capture wait or add a page-level wait action; up to nine additional seconds are documented for the session setting.
Email arrives later than expected	Alert delivery cadence is separate from crawl timing; daily summaries are the default described by Fluxguard.	Review account notification settings and select an available delivery cadence.
Credit use or alerts are higher than expected	Many pages on a frequent schedule multiply crawl volume.	Estimate page checks per day, then lower the cadence for pages that do not need rapid detection.
Crawls happen outside the desired hours	No crawl time range is configured.	Set the time range in the account settings, as supported by Fluxguard.

FAQ

Does Fluxguard check every page daily by default?

The FAQ says a newly monitored page is crawled daily by default. Sessions can have different schedules, so verify the setting for the page or session you care about.

Is five-minute crawling available to everyone?

The pricing page currently advertises five-minute crawling on Premium. Fast frequencies require site verification, and current availability should be confirmed in the live pricing page and account.

Does an hourly schedule mean I receive an email every hour?

No. Crawl frequency and email alert cadence are separate. Fluxguard describes daily email summaries as the default and says notification timing can be changed in account settings.

How quickly will Fluxguard finish checking a site?

Fluxguard says it crawls about one page per minute under ordinary limits, with variable speed. Verified sites may be faster; the number of pages and their load times affect total processing time.

Can I check only during business hours?

Fluxguard’s FAQ says a crawl time range can be specified. Configure it in the account settings and confirm the resulting schedule for the session.