> ## Documentation Index
> Fetch the complete documentation index at: https://docs.videntic.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Investigate a finding and verify the change

> Read a finding’s evidence and affected pages, then use Check live site to verify your fix.

> [!NOTE]
>
> **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.

<video controls preload="metadata" poster="https://juuuyyataunntdlftdao.supabase.co/storage/v1/object/public/guides/technical-audit/v4/investigation-poster.jpg" src="https://juuuyyataunntdlftdao.supabase.co/storage/v1/object/public/guides/technical-audit/v4/investigation.mp4">
  <track kind="captions" srcLang="en" label="English" src="https://docs.videntic.com/guides/technical-audit/v4/investigation-en.vtt" default />
</video>

> [!NOTE]
>
> 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.

> [card] [Open in Videntic](https://app.videntic.com/?utm_source=docs\&utm_medium=playbook\&utm_campaign=technical-audit-investigation)
>
> 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](https://docs.videntic.com/how-to/check-a-technical-audit-fix.md).

## Related playbooks

> [card] [Set your scope and read the audit](https://docs.videntic.com/playbooks/technical-audit/introduction.md)
>
> Check Audit settings, run the audit, and read AI Readiness first.

> [card] [Check a Technical Audit fix](https://docs.videntic.com/how-to/check-a-technical-audit-fix.md)
>
> The longer how-to for verifying a fix.

> [card] [Technical Audit](https://docs.videntic.com/features/geo-audit.md)
>
> The feature reference for Technical Audit.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.