> For the complete documentation index, see [llms.txt](https://georeport.gitbook.io/georeport-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://georeport.gitbook.io/georeport-docs/managing-sites/metrics-and-tracking.md).

# Metrics & Tracking

Track metrics to measure your site's AI Visibility

***

### Track Your Metrics

The Site Manage section also provides **metrics over time**, such as:

* **Audited vs Crawled** → Are you auditing enough of your site’s total content? If only 10 out of 200 pages are audited, you may be missing weak spots.
* **Usage count** → Tracks how many audits you’ve used in your plan quota.
* **Progress history** → See if your site’s visibility is improving after fixes.

***

### **Why this matters?**

AI visibility isn’t static. A competitor improving their site, or a new AI model update, can drop your score even if nothing changed on your side. These metrics let you see whether you’re trending up or down.

**Example:**

* January → 10 pages audited, average score 6.1.
* March → 15 pages audited, average score 7.9.\
  You now have proof your fixes worked — and you can show it to your team or clients.

***

### FAQs

<details>

<summary><strong>What does “Usage count” mean?</strong></summary>

It shows how many audits you’ve run relative to your plan’s weekly limit. This helps you plan ahead e.g., saving audits for critical pages before a big content launch.

</details>

<details>

<summary> <strong>How often should I check progress history?</strong></summary>

AI visibility is relative. A competitor improving their structure or an AI model update can lower your visibility even if your site stayed the same.

</details>

<details>

<summary><strong>Why might my scores drop even if I didn’t change anything?</strong></summary>

Yes. Progress graphs and reports are especially useful for agencies to prove ongoing improvement over time.

</details>

<details>

<summary> <strong>Does GEOReport notify me when scores change significantly?</strong></summary>

Currently, you’ll need to re-run audits to track changes. Future updates may include automated alerts for major score shifts.

</details>

<details>

<summary><strong>If I fix a page but don’t see progress right away, does that mean the fix failed?</strong></summary>

Not necessarily. AI assistants may take time to re-train or re-prioritize sources. Continuous re-auditing helps confirm whether fixes are working.

</details>


---

# 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://georeport.gitbook.io/georeport-docs/managing-sites/metrics-and-tracking.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.