Run a Bounded QCDR Site Impact Scan Before Enabling a Rule

Site Impact Scan checks where the current Discovery find value or Target Fingerprint appears across a bounded set of same-site frontend pages. Use it before enabling a broad Rule to discover obvious additional matches or similar targets—not as proof that every page on the site is safe.

The scan is browser-driven, read-only, de-duplicated, and capped at 40 pages per run.

Choose a Target First

  1. Select output in Discovery and verify the QCDR find value.
  2. Open the Site Impact Scan panel.
  3. Review the automatic scope: current page plus published Joomla menu routes available in the current browser/user context.
  4. Optionally add up to 20 same-site URLs or paths, one per line.
  5. Choose Run Impact Scan.

Safety Filters and Bounds

QCDR rejects external origins, Joomla /administrator paths, obvious logout/delete/remove/destroy routes, and query parameters that look state-changing or CSRF/action-oriented. It strips QCDR's own private Discovery/Preview parameters and de-duplicates page paths before the 40-page cap is applied.

These are safety heuristics, not a promise that every custom GET route is side-effect-free. Add only frontend URLs you consider safe to request.

How Other Pages Are Fetched

Pages are requested with same-origin browser credentials, no-store caching, no-referrer behavior, and normal GET requests. QCDR follows redirects only while the final URL remains an allowed same-site frontend target. Non-HTML responses are rejected. Each fetched response is limited to 5 MB and has a 12-second abort timeout.

Understand EXACT and LIKELY

  • EXACT: the page contains the literal rendered find value, the normalized visible value, or an exact-enough fingerprint match.
  • LIKELY: no exact value was found, but fingerprint similarity reaches the Site Impact threshold of 45%.
  • NOT FOUND: neither exact nor sufficiently similar evidence was found.
  • ERROR: the page could not be safely fetched/analyzed.

Fingerprint scoring uses stable signals such as IDs, classes, selected attributes, text overlap, and parent context. Treat LIKELY as a review target, not as a confirmed Rule match.

Open a Result in Discovery

EXACT and LIKELY rows can be reopened in Discovery while the session authorization is valid. That lets you inspect the actual page instead of changing the Rule based only on an impact-scan score.

What the Scan Does Not Do

It does not activate, save, retarget, or execute a proposed unsaved Rule across those pages. It evaluates only the find value/fingerprint against fetched frontend output. After reviewing impact, save the Rule as Draft and use Preview/Rule Health on representative pages before enabling it.

Community Discussion

Want to compare workflows, share practical tips, or discuss how you use this QCDR feature? Visit the QC Dynamic Replacer Community. For private support, bug reports, account-specific issues, or feature requests, use the QuantaCade support system.