Skip to main content
Goal: Confirm the audit covers the pages you intended, then read the score and one finding.Who it’s for: People setting up their first audit or reviewing its results.Video: About 36 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.
The video follows an example Project from Audit settings through its first audit results.

​
Steps

1

Start with Technical Audit

Technical Audit checks your pages for problems with access, structure and speed. This is what you see before your first audit.
2

Check Audit settings

Open Audit settings first. Check the start page and the sections it covers, then go back.
3

Run the audit

Click Run audit. It checks your pages as they come in. You can leave the page, and it keeps running.
4

Read AI Readiness

When it’s done, AI Readiness gives you a score. Read the note under it. One big access problem can cap the whole score.
5

Open one Fix first finding

Start with Fix first. Click Review fix to see the pages it affects.

​
Expected result

You have checked the start page and sections in Audit settings, run the audit, and opened a Fix first finding to review its affected pages.

Open in Videntic

Sign in first. Then open your Project and go to Technical Audit. Check Audit settings before running an audit.

​
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.

Investigate a finding and verify the change

Read the evidence, then check the live site.

Technical Audit

The feature reference for Technical Audit.

Run your first audit

The longer how-to for a first Audit Run.
Last modified on November 5, 2026