> For the complete documentation index, see [llms.txt](https://docs.frase.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.frase.io/get-started/run-your-first-audit.md).

# Run Your First Audit

Identify broken links, thin content, weak internal structure, missing metadata, and more and prioritize fixes.

{% embed url="<https://youtu.be/-T_B4kVJxvc>" %}

{% stepper %}
{% step %}

### Run the audit

Go to **Optimize → Audit** and click **New Audit** to start a crawl. You'll choose an audit type:

* **Full Site Audit** — crawls up to your plan's page limit for a complete site-wide picture.
* **Specific Section Audit** — crawls a defined set of pages. Faster, good for spot checks.
* **Custom URL List** — crawls only the pages you enter.

{% hint style="success" %}
For your first audit, run a **Full Site Audit** at the maximum pages your plan allows. You want the complete picture before you start making decisions.
{% endhint %}

Frase crawls your site the way a search engine does, checking technical issues, content quality, site structure, ranking opportunities, and keyword cannibalization.
{% endstep %}

{% step %}

### Read the results

**Site-wide findings** appear above your Pages table — start there, because a single site-wide fix often clears an issue across dozens of pages at once.

Below that, you have two views:

* **Pages** — every page in the crawl with its scores. Click a row to open the drawer and see the audit facts for that page.
* **Issues** — every problem found, grouped by severity. This is your task list.
  {% endstep %}

{% step %}

### Make fixes by priority

Findings are grouped into three priority levels:

{% hint style="danger" %}
**Critical** — fix these first. They're what's most likely to be hurting rankings or stopping pages from proper indexing.
{% endhint %}

{% hint style="warning" %}
**Warnings** — important but not urgent.&#x20;
{% endhint %}

{% hint style="success" %}
**Opportunities** — not problems, just untapped potential.&#x20;
{% endhint %}

Hit **Export** to download the fix pack, or use **Share** to send the full site health report to your team or a client.&#x20;

{% hint style="info" %}
You don't need to clear the whole list before moving on. Fix the critical items, then leave the rest running alongside your content work.&#x20;
{% endhint %}
{% endstep %}
{% endstepper %}

### Next steps

* For a deeper walkthrough of audits, [check out this article](https://docs.frase.io/core-workflows/audit-my-site).
* Not sure what to tackle first? Ask the [Frase Agent](/automations/meet-the-frase-agent.md) to read your audit findings and give you a plain-language action plan.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.frase.io/get-started/run-your-first-audit.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.