Skip to content
GrowInSearch
Menu

Continuous issue verification

Keep technical issues open until a later scan proves the problem is gone.

GrowInSearch Site Guard preserves technical and performance findings across scans, including affected URLs, DOM selectors, rendered code, resource paths and recommended fixes when available.

01

Exact diagnostic evidence

Technical findings can retain the affected page, public asset path, DOM selector, rendered HTML line, current code or Lighthouse resource data when the scan exposes it.

02

Handled is not the same as resolved

A user can mark an issue as fixed, but Site Guard keeps it in monitoring until a genuinely newer scan no longer detects the finding.

03

Historical issue lifecycle

First seen, last seen, severity and verified resolution remain visible so teams can distinguish recurring defects from one-time fixes.

04

Performance and technical checks together

Direct HTML diagnostics and supported Lighthouse/PageSpeed findings can feed the same verification workflow.

Frequently asked questions

Can GrowInSearch show my private Blade or React source file?

A public scan can identify the public page, rendered selector, rendered HTML and asset URLs. Mapping that evidence back to a private framework source file requires source-repository access.

What happens after I mark an issue fixed?

The issue moves to monitoring. A later scan must stop finding the same fingerprint before Site Guard marks it verified resolved.

Does Site Guard replace Lighthouse?

No. GrowInSearch can incorporate supported Lighthouse findings while also adding its own direct HTML and DOM diagnostics and issue history.

Every number labelled with its source.

When something cannot be measured, the report says so. Read how each check works.

Read the methodology