Skip to main content
Goal: Go from a finding’s evidence to the check that tells you whether a change worked.Who it’s for: People reviewing evidence before they change a website.Video: About 28 seconds.

​
Before you start

Confirm the Website and audit scope in your Project. Investigating a finding requires a completed audit; verifying a fix requires the change to be live.
This example Project includes real audit output from demonstration pages. Clicking Check live site does not mark a finding fixed.

​
Steps

1

Start from the evidence

Choose one finding and follow it from the evidence through verification.
2

Review the proposed fix

Read why it matters and how to fix it. Check that the fix makes sense for your site. Some fixes Videntic can make for you, with a preview you can undo.
3

Inspect Affected pages

Affected pages lists every page with the problem.
4

Check the live site

After you make the fix, click Check live site. It tests those pages again, without a new audit. If a page still fails, the finding stays open.

​
Expected result

You have reviewed the proposed fix and affected pages, made a supported change, and read the Check live site result. If a page still fails, the finding stays open.

Open in Videntic

Sign in first. Then open your Project and go to Technical Audit. Review audit findings.

​
If you get stuck

If a finding remains after a fix, confirm that the changed page is live and matches the affected URL before checking again. See the detailed guide.

Set your scope and read the audit

Check Audit settings, run the audit, and read AI Readiness first.

Check a Technical Audit fix

The longer how-to for verifying a fix.

Technical Audit

The feature reference for Technical Audit.
Last modified on November 5, 2026