Monitor progress
Rescans, Pro weekly monitoring, before/after verification, and what real improvement looks like.
Updated 2026-08-06
Monitoring is the See / Prove cadence after you ship fixes. On Free you establish a baseline with one lifetime completed scan. On VisibleMax Pro Early Adopter, you rescan on demand and can enable weekly monitoring to keep the Infrared Signal current.
Why monitoring matters
- Sites regress (robots changes, template bugs, deleted pages).
- Competitors publish comparison content that shifts probe outcomes.
- AI provider behavior and key-gated coverage evolve over time.
- Stakeholders need before/after proof, not anecdotes.
On-demand rescans (Pro)
After publishing fixes, run a new scan from the project in /app. Compare score band, findings, and probe-oriented outcomes against the previous completed run. History depth is a Pro entitlement (Free history is limited to the single baseline).
- 1
Confirm production reflects the fix
Hard-refresh the live URL, check HTML, and validate with /tools if relevant.
- 2
Start a rescan
Trigger a new pipeline run. Wait for crawl → analyze → probe to finish (~minutes in typical cases).
- 3
Diff deliberately
Look for movement in score, closed findings, and new weaknesses. Update the weekly plan with what remains.
Weekly monitoring (Pro)
Pro can enable monitoring on a weekly cadence. Weekly rescans catch silent regressions and keep the execution plan honest without relying on someone to remember to click scan.
- Enable monitoring from project/workspace settings when the entitlement is active.
- Expect monitoring rescans to consume monitoring quota (Pro includes weekly cadence with plan safeguards).
- Review weekly outputs the same way you review an on-demand report — prioritize new weaknesses first.
What improvement looks like
| Signal | Healthy movement | Caution |
|---|---|---|
| Score / band | Weak → Moderate or Moderate → Strong after structural ships | Chasing single-point noise without shipped changes |
| Findings | High-severity items close; evidence URLs reflect new content | Findings “disappear” because pages 404’d |
| Probes | More accurate brand representation on buyer prompts over multiple runs | One lucky mention on a single provider |
| Attribution | AI referral visits/conversions appear after vm.js is installed | Assuming all organic traffic is AI-driven |
Verify before/after
- Snapshot the baseline public report (
/r/[slug]) before major changes. - Ship a bounded set of fixes with dates.
- Rescan on Pro; compare score, findings, and probe coverage notes.
- Share the new public report and call out what changed.
- Feed remaining gaps into the next weekly plan.
When not to rescan yet
- Drafts exist only in CMS preview and are not public.
- DNS/TLS is mid-cutover.
- You have not changed anything since the last completed scan.
- A scan is already running.
How often should I rescan manually?
After meaningful production changes, or at least weekly if you are actively shipping the plan. With weekly monitoring enabled, use on-demand scans for immediate verification after large releases.
Why did my score stay flat after publishing a blog post?
A single post may not move crawl/entity/answer-coverage dimensions much. Structural fixes (schema, entity pages, robots, FAQ coverage) usually move the instrument more than isolated articles.
Do monitoring runs probe every platform?
They use the same key-gated probe design as on-demand scans. Early-phase runs may center on DeepSeek + Gemini when those keys are set.
Can agencies monitor multiple client sites?
Free and Pro Early Adopter both center on one project per workspace at launch. Use separate workspaces only when you intentionally need isolated brands or billing.
Related
Still stuck? Contact support with your project URL and what you already tried.