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

# Check whether a Technical Audit fix worked

> Run the audit again and verify the original Finding on the affected page.

After changing your Website, use a new **Audit Run** to check the result. Marking a **Fix** as applied records your team's action; it does not test the live page. A new AI **Analysis** measures different evidence and cannot confirm that a Technical Audit Finding is resolved.

## Before you run again

1. Open the original Finding under **Technical Audit → Issues**. If it was a Recommendation, switch to **Recommendations** within that tab; you can also find the affected URL under **Pages**. Note the check and its evidence.
2. Open that URL on the live Website. Confirm the intended change is visible there. If you use a deployment or cache, finish that process first.
3. Select **Configure** in Technical Audit. Check the entry URL, allowed paths, exclusions, subdomains, and page limit. The affected page must remain in the **Audit Scope** for the later result to verify it.

## Run and compare

**1. Start a new Audit Run**

In **Configure**, select **Save & run audit**. The product shows an error if a run cannot start, including when the Plan's allowance is exhausted. Wait until the new run finishes.

**2. Compare the two runs**

Open **History** and select the run before the change and the new run. Review the issue counts, **Resolved** total, and changed issue types. Check how many pages were discovered and audited in each run before interpreting the difference.

**3. Inspect the affected page**

Return to **Issues** or **Pages** in the latest run. Look for the original check and URL. If the page was audited and the Finding is absent, the later run did not detect that condition on that page. If the Finding remains, open its latest evidence and compare it with the live URL.

## If the result is unclear

| What you see | What to check next |
| - | - |
| The issue count fell, but you cannot find the page | Check the entry URL, allowed paths, exclusions, subdomains, page limit, and number of audited pages. A page outside the later Audit Scope is not a verified fix. |
| The same Finding remains on the page | Confirm the change is live at the exact audited URL, then read the new evidence. Redirects, cached content, or a different page version can change what the audit receives. |
| AI Readiness changed, but the Finding did not | Read the other changes between runs. AI Readiness is a summary of multiple checks and can move for reasons unrelated to your change. |
| The run did not start | Read the error shown in Technical Audit. If it names a Plan limit, wait for the allowance to renew or review [Plans](/billing/plans.md). |

If you changed the **Audit Scope** or the audit methodology changed between runs, compare the page-level evidence before attributing a score or count change to your fix.

> **[Technical Audit](/features/geo-audit.md)**
>
> Understand Findings, scope, and the audit workspace.

> **[Review your first Analysis](/how-to/run-your-first-audit.md)**
>
> Interpret AI visibility evidence separately.


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