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

# Technical Audit

> Find Website issues, review proposed fixes, and verify changes with a new Audit Run.

**Technical Audit** checks the Website within a configured scope. Its results are **Findings**: an **Issue** identifies a failed check or condition requiring correction; a **Recommendation** proposes an improvement. A **Fix** is a proposed change for a particular page or scope.

Technical Audit evidence comes from an Audit Run. It does not measure whether an AI Platform mentioned or cited your Brand.

## Review an Audit Run

<Steps>
  <Step title="Open Technical Audit">
    Choose the Project, then open **Technical Audit** from its navigation. Check when the latest Audit Run completed and how many pages it covered.
  </Step>

  <Step title="Check the scope">
    Review the Website entry point, allowed paths, and page limit. A page outside the configured scope will not appear in the results.
  </Step>

  <Step title="Investigate a Finding">
    Open **Issues** and choose its **Issues** or **Recommendations** view, or open **Pages** for a URL. Inspect the evidence and affected pages to understand the specific condition.
  </Step>

  <Step title="Review a Fix">
    If a Fix is available, review its proposed change for the affected page. Confirm it still applies to the current Website before using it.
  </Step>
</Steps>

## Verify a change you made

1. Make the change on the live Website and open the affected URL to confirm it is present.
2. In **Technical Audit**, select **Configure**. Check that the entry URL, allowed paths, exclusions, and page limit still include the affected page. Select **Save & run audit** if your Plan has a run available.
3. Wait for the new Audit Run to complete. In **History**, select the run before the change and the new run to see changes in AI Readiness and issue counts.
4. Return to **Issues** or **Pages** and inspect the affected URL in the latest result. A lower issue count alone does not prove the specific page passed its check.

For the full troubleshooting sequence, see [Check whether a Technical Audit fix worked](/how-to/check-a-technical-audit-fix).

An applied Fix status records a workflow decision. A later Audit Run checks the changed Website. If the page was excluded or not audited in the later run, do not treat a missing Finding as a verified fix.

<Info>
  Technical Audit runs can have a monthly limit. The product shows the reason if it cannot start another run. Running a new AI Analysis is a separate action and does not verify a Technical Audit Finding.
</Info>

## Use the results well

Start with Issues that affect important pages or repeat across many pages. Verify one representative URL before applying a repeated change broadly. Use the **Recommendations** view within **Issues** to consider suggested improvements separately from failed checks, and compare both against the latest live page.

<CardGroup cols={2}>
  <Card title="Check an audit fix" icon="circle-check" href="/how-to/check-a-technical-audit-fix">
    Compare two Audit Runs and inspect the affected page.
  </Card>

  <Card title="Review your first Analysis" icon="chart-line" href="/how-to/run-your-first-audit">
    Interpret visibility evidence separately from the Technical Audit.
  </Card>

  <Card title="Project Overview" icon="gauge" href="/features/dashboard">
    Return to the Project summary after reviewing the audit.
  </Card>
</CardGroup>


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