> 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/geo-benchmarks.md).

# Understanding GEO Benchmarks

When you run a GEOReport audit, your website is scored across **four key benchmarks**. These benchmarks represent the factors AI search engines like **ChatGPT, Gemini, Claude**, **and Perplexity** look at before deciding: *“Is this site worth citing as an answer source?”*

If you’ve ever wondered why **Wikipedia or your competitor appears in AI results while you don’t**, the answer lies inside these benchmarks.

<table data-card-size="large" data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th><th data-hidden data-card-cover data-type="image">Cover image</th></tr></thead><tbody><tr><td><h4>GEO Health Score</h4></td><td><p></p><ul><li>GEO Health Benchmarks</li><li>Why GEO Heath Score matters for AI visibility?</li></ul></td><td><a href="/pages/mOTtSWmCaiEf6HPLDcSY">/pages/mOTtSWmCaiEf6HPLDcSY</a></td><td><a href="/files/pEXOoaKhF4vdNMr4knDk">/files/pEXOoaKhF4vdNMr4knDk</a></td></tr><tr><td><h4>Search Alignment</h4></td><td><p></p><ul><li>What is the Search Alignment benchmark?</li><li>Why Search Alignment matters for AI visibility?</li></ul></td><td><a href="/pages/eAHrp6DjImHzv34GVjzH">/pages/eAHrp6DjImHzv34GVjzH</a></td><td><a href="/files/8U0KhRGFA3UhodUWCWO7">/files/8U0KhRGFA3UhodUWCWO7</a></td></tr><tr><td><h4>Layout</h4></td><td><p></p><ul><li>What is the Layout benchmark?</li><li>Why Layout matters for AI visibility?</li></ul></td><td><a href="/pages/YPBFPK5xr9dbW5pTUKJL">/pages/YPBFPK5xr9dbW5pTUKJL</a></td><td><a href="/files/FSpcuhDRCeeLDOAtXWTH">/files/FSpcuhDRCeeLDOAtXWTH</a></td></tr><tr><td><h4>Readability</h4></td><td><p></p><ul><li>What is the Readability benchmark?</li><li>Why Readability matters for AI visibility?</li></ul></td><td><a href="/pages/gAixoSc3xx6ALfJxdpAl">/pages/gAixoSc3xx6ALfJxdpAl</a></td><td><a href="/files/1Fz38zXvZYu1Z31anuhv">/files/1Fz38zXvZYu1Z31anuhv</a></td></tr><tr><td><h4>Credibility</h4></td><td><p></p><ul><li>What is the Creadibility benchmark?</li><li>Why Creadibility matters for AI visibility?</li></ul></td><td><a href="/pages/kpdPgE2QjnKx6nIzhSRa">/pages/kpdPgE2QjnKx6nIzhSRa</a></td><td><a href="/files/BTKRRsprlCgoWUEJAOJF">/files/BTKRRsprlCgoWUEJAOJF</a></td></tr></tbody></table>


---

# 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/geo-benchmarks.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.