Siteimp allows monitoring intervals down to one minute.

That limit is intentional. Siteimp includes monitoring, but Siteimp is not only a monitoring app. It is a full local-first website integrity application that also runs scans, collects page evidence, uses browser-based checks, runs Lighthouse, reviews accessibility signals, checks links and images, and writes scan results to a local database.

Monitoring has to live safely beside all of that work.

The one-minute minimum interval keeps monitoring predictable inside the larger application.

Why Siteimp uses a one-minute scheduler

Siteimp monitoring runs inside the full Siteimp desktop app.

That app has a lot of responsibilities. It can inspect websites, crawl pages, review links, check images, collect Lighthouse results, process accessibility findings, store scan artifacts, and help users review evidence across a whole site.

Because of that, Siteimp uses a monitoring scheduler designed for the larger application. The scheduler checks monitoring work on a one-minute rhythm instead of trying to run very frequent checks inside a heavier scanner.

That keeps the monitoring system simple, understandable, and predictable.

Why Siteimp does not use one-second monitoring intervals

One-second monitoring intervals are useful for some local monitoring situations, but they are not a good fit for the full Siteimp application.

A one-second interval means the app may need to check targets constantly while also handling other desktop work. In Siteimp, that other work can include large scans, browser automation, Lighthouse runs, accessibility processing, database writes, and user interface updates.

That would create an unnecessary conflict inside the larger product.

Siteimp is designed to collect website evidence. Monitoring is part of that evidence, but it is not the only job Siteimp has.

What the one-minute interval is good for

A one-minute monitoring interval is useful for practical website awareness.

It can help you notice:

  • whether a website is responding
  • whether an important URL is reachable
  • whether a target fails or recovers
  • whether response times drift over time
  • whether a monitored target returns unexpected status codes
  • whether final URLs change
  • whether a local or public endpoint has recurring problems

For many website integrity workflows, that is enough.

If you are scanning and maintaining websites, a one-minute monitoring interval can give useful context without turning the full scanner into a high-frequency monitoring engine.

When one minute is not enough

One minute is not enough for every monitoring job.

You may want shorter intervals when you are watching:

  • local development services
  • home lab tools
  • internal apps
  • local AI servers
  • staging systems
  • private network endpoints
  • short-lived failures
  • services that fail and recover quickly
  • systems where waiting one minute feels too slow

Those cases are real. They are also why Siteimp Watch exists.

Why Siteimp Watch can monitor faster

Siteimp Watch is built from the same monitoring idea, but it is a focused local monitoring app.

It does not need to load and coordinate the larger scanning stack used by Siteimp. It does not need to run full-site scans, launch Lighthouse for scan evidence, process image evidence, check page headings, or collect the broader website integrity data that Siteimp collects.

Because Watch has a narrower job, it can use a scheduler designed for faster checks.

In simple terms:

  • Siteimp monitors as part of a larger website integrity workflow.
  • Siteimp Watch monitors because monitoring is the main job.

That difference is why the interval limits are different.

Is the one-minute limit a bug?

No.

The one-minute minimum interval is part of Siteimp's product design.

Siteimp favours predictable monitoring inside a larger website scanner. It keeps monitoring useful without letting frequent checks compete with heavier scan work.

If you need faster local monitoring, use Siteimp Watch. It is designed for that narrower job.

Why not make Siteimp do both?

Siteimp could try to do everything, but that would make the product heavier and more complicated.

Siteimp already carries the machinery needed for website integrity scanning. Adding high-frequency monitoring inside that same application would create more resource contention, more scheduling complexity, and more confusing behavior during scans.

A separate product is cleaner.

Siteimp can focus on broad website evidence. Siteimp Watch can focus on fast local visibility.

That keeps both products easier to understand.

What happens during scans?

Siteimp pauses monitoring while a scan is running.

This is related to the one-minute interval decision. Scans can be heavy, and Siteimp gives them priority so scan results are collected as consistently as possible.

After the scan finishes, monitoring can continue on its normal schedule.

If you need monitoring that continues while Siteimp scans, Siteimp Watch is the better fit.

Should I use Siteimp Watch instead?

Use Siteimp Watch if monitoring is the main thing you need.

Siteimp Watch is better suited for:

  • shorter monitoring intervals
  • frequent local checks
  • internal tools
  • home lab services
  • staging environments
  • local applications
  • local-network targets
  • public websites checked from your own computer

Use Siteimp when you need the full website integrity workflow:

  • full-site scans
  • page evidence
  • Lighthouse results
  • accessibility findings
  • link checks
  • image checks
  • heading structure
  • sitemap and crawl differences
  • monitoring as part of broader website review

Some users may use both. Siteimp can inspect the website deeply. Siteimp Watch can watch important targets more frequently.

Is Siteimp Watch a cloud monitoring replacement?

No.

Siteimp Watch is local-first monitoring. It checks targets from the computer running Watch.

That is useful when you care about local visibility, internal tools, private network targets, staging systems, or endpoints your own computer can reach.

But local monitoring depends on the local machine. If the computer sleeps, shuts down, restarts, loses power, loses network access, or is interrupted by operating system behavior, monitoring can stop too.

If you need service-grade uptime monitoring that continues through sleep, restart, logout, power events, and local outages, use a dedicated infrastructure monitoring service.

Siteimp Watch can augment cloud monitoring. It is not a full replacement for it.

Where to go next

To learn more, read:

Siteimp uses a one-minute monitoring interval because it is a full website integrity scanner with monitoring included. Siteimp Watch exists for the cases where focused, faster local monitoring is the job.