Siteimp pauses monitoring while a scan is running.

That behavior is intentional. Siteimp includes local monitoring, but Siteimp is also a full website integrity scanner. When a scan starts, Siteimp gives the scan priority so it can collect page evidence, run browser-based checks, process Lighthouse results, inspect links and images, review accessibility signals, and write scan data without competing against scheduled monitoring work.

Monitoring is useful. But while a scan is running, scan quality and predictable desktop behavior matter more.

Why monitoring pauses during scans

Siteimp scans can do a lot of work.

Depending on the site and scan configuration, a scan may involve:

  • crawling pages
  • opening pages in a browser
  • running Lighthouse
  • collecting accessibility results
  • checking internal links
  • checking external links
  • checking images
  • reading page titles and metadata
  • inspecting headings
  • writing scan evidence to the local database
  • saving scan artifacts
  • updating the app interface as results arrive

That is very different from a simple monitoring check.

A monitoring check usually asks a narrower question:

Did this target respond, how long did it take, and what happened?

A scan asks a much larger question:

What can Siteimp learn about this website as a system?

Because those jobs are different, Siteimp pauses monitoring during scans instead of trying to run both workflows at the same time.

Why this protects scan quality

A scan is most useful when its evidence is collected as consistently as possible.

If monitoring continued during a scan, both systems could be trying to use app resources at the same time. That could make the scan slower, create noisier timing information, or make the app feel less predictable while heavier scan work is happening.

Siteimp pauses monitoring so the scan can focus on the website being inspected.

This helps protect:

  • scan stability
  • browser-based checks
  • Lighthouse runs
  • database writes
  • page-level evidence collection
  • app responsiveness
  • predictable scan behavior

The goal is not to make monitoring less important. The goal is to avoid making a large scan compete with recurring monitoring checks inside the same desktop app.

Why this protects monitoring results too

Pausing monitoring during scans also helps avoid misleading monitoring results.

A monitoring result is supposed to describe what happened when Siteimp checked a target. If the app is busy with heavy scan work at the same time, a slower check might reflect local app load instead of the monitored target.

That can make results harder to interpret.

For example, a slow response during a heavy scan might raise an awkward question:

Was the target slow, or was Siteimp busy?

By pausing monitoring during scans, Siteimp keeps the two workflows easier to understand. Scan results come from scans. Monitoring results come from monitoring checks.

What happens to monitoring while a scan runs

When a scan is running, Siteimp temporarily pauses scheduled monitoring work.

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

This means monitoring history may have a gap during the scan window. That gap is expected. It does not mean the monitored target failed, and it does not mean Siteimp lost data. It means monitoring was intentionally paused while the scan was active.

If you are reviewing monitoring history and see a quiet period that overlaps with a scan, treat that period as a scan pause rather than an uptime event.

Does this mean monitoring is broken?

No.

Monitoring is working as designed. Siteimp is choosing not to run monitoring checks while a scan is active.

That choice is part of the product design.

Siteimp is the full website integrity application. It includes monitoring, but its main job is to help you inspect websites, collect evidence, and understand site health across pages, links, images, accessibility, Lighthouse, headings, and related signals.

When Siteimp is scanning, it prioritizes the scan.

Why Siteimp Watch does not have the same limitation

Siteimp Watch is different.

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 that Siteimp uses.

Siteimp Watch does not need to run full-site scans, launch Lighthouse for page evidence, process image and link evidence, or collect the broader website integrity data that Siteimp collects.

Because Watch has a narrower job, it can use a scheduler designed for faster and more continuous monitoring.

In simple terms:

  • Siteimp pauses monitoring during scans because scanning is heavy work.
  • Siteimp Watch focuses on monitoring, so it can keep monitoring without competing against full scan work.

Should I use Siteimp Watch instead?

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

Siteimp Watch is better suited for:

  • frequent local checks
  • short monitoring intervals
  • local-network targets
  • internal tools
  • home lab services
  • staging environments
  • local applications
  • public sites you want to check from your own computer

Use Siteimp when you need the full website integrity workflow:

  • 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 products. Siteimp can inspect the website deeply. Siteimp Watch can monitor important targets more continuously.

Is Siteimp Watch a replacement for cloud monitoring?

No.

Siteimp Watch is local-first monitoring. It checks what the computer running Watch can reach.

That can be very useful, especially for internal tools, home lab services, private network targets, staging systems, or endpoints where local visibility matters.

But local monitoring depends on the local computer and local environment. If the computer sleeps, shuts down, loses network access, restarts, loses power, or is interrupted by operating system behavior, local 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.

How to think about the tradeoff

The tradeoff is simple.

Siteimp is larger because it does more.

Siteimp Watch is smaller because it does less.

That does not make one product better than the other. It makes them useful for different jobs.

Siteimp is the right tool when you want to inspect a website and collect evidence. Siteimp Watch is the right tool when you want focused local monitoring with fewer scan-related responsibilities.

Where to go next

To learn more, read:

Siteimp pauses monitoring during scans because it is protecting the heavier website inspection workflow. If you need focused monitoring without scan pauses, Siteimp Watch is built for that narrower job.