Recovery steps

Standard recovery checklist when scans, entitlements, or billing get stuck.

Updated 2026-08-06

Use this checklist when you are unsure where to start. It consolidates scan pipeline recovery (crawl → analyze → probe via Trigger.dev), Free-plan gates, and Polar billing checks into one pass.

Standard recovery checklist

  1. 1

    Capture context

    Note project URL, scan ID, status, timestamps, and a screenshot of the error or billing page.

  2. 2

    Classify the problem

    Failed scan, slow/stuck, missing/gated results, or billing/entitlement. Use Troubleshooting overview cards if unsure.

  3. 3

    Verify the site publicly

    Confirm HTTPS, DNS, and SSL. Lift bot blocks that could stop crawl.

  4. 4

    Check plan entitlements

    If Free lifetime scan is used, upgrade to Pro Early Adopter (7-day free trial, then $50/year) via Polar before expecting new completed scans.

  5. 5

    Confirm Polar payment state

    Active subscription in the portal precedes app-side Pro features.

  6. 6

    Run one clean scan

    After fixes, start a single new scan. Prefer partial reports over endless retries when only probes are thin.

  7. 7

    Escalate

    If still broken, email support with the evidence pack below.

Evidence pack for support

  • Project URL (exact)
  • Scan ID (if known) or scan detail URL
  • Steps already tried (bulleted)
  • Screenshots of errors, status, or Polar portal
  • Approximate times (with timezone) of failures or charges

Do and don’t

  • Do treat partial probe coverage as usable output
  • Do fix reachability before blaming analysis quality
  • Do verify Polar before double-paying
  • Don’t expect guaranteed AI mentions from any scan
  • Don’t open many parallel scans on the same failing URL
  • Don’t send card numbers to support — use the Polar portal

Edge cases

  • Recovered site mid-scan — start a new scan; do not expect the failed run to resurrect.
  • Provider outage window — wait and rescan later; soft-skipped platforms refill when available.
  • Monitoring cadence — after Pro is active, confirm monitoring settings if weekly/daily rescans were expected.

When to contact support

After one full pass of this checklist without recovery — or immediately for duplicate charges and entitlement mismatches with proof of payment.

FAQ

How fast does support respond?

Response times vary with volume. Complete evidence packs (URL, scan ID, steps, screenshots) get the fastest path to a fix.

Can support re-run a scan for me?

Usually you can rescan yourself once the cause is fixed. Support may trigger investigation runs when diagnosing platform-side failures.

What if everything looks green but mentions are still zero?

That can be honest model behavior. Improve entities and answer-ready content, ship studio assets, and monitor — VisibleMax does not guarantee mentions.


Related: Scan failed · Common errors · Contact support

Related

Still stuck? Contact support with your project URL and what you already tried.