> For the complete documentation index, see [llms.txt](https://help.rankability.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.rankability.com/audit/site-auditor-guide.md).

# Using Site Auditor

Crawl a client site, filter pages and issues, review duplicate content, and export the page inventory.

## Start a crawl

1. Open **Audit → Site Auditor**.
2. Confirm the domain and crawl settings shown.
3. Review the estimated scope and start the crawl.

## Review results

Use the Pages and Duplicate content tabs. Page data can include status, indexability, title, meta description, H1, canonical, word count, crawl depth, redirect information, and target keyword context.

## Work with findings

Filter by severity or problem, open the affected page, compare pages where offered, and hide a reviewed known non-issue. Hiding a finding changes its review state; it does not fix the website.

## Costs

Site crawling uses 1 credit per 5 pages. AI keyword identification uses 25 credits for a page only when that identification is needed and succeeds.

## Export

Use CSV export for the current page inventory or filtered workflow supported by the page.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.rankability.com/audit/site-auditor-guide.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.