> For the complete documentation index, see [llms.txt](https://docs.usereach.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.usereach.ai/understand-your-visibility/sources.md).

# Sources

Sources shows which domains and pages AI engines use when answering your monitored prompts.

## Domain view

Use the domain view to identify the publishers, communities, competitors, review sites, and other sources that shape AI answers in your market.

Compare citation volume with the number of prompts a domain influences. A source cited across many relevant prompts can be more strategically important than one with a high count concentrated in a single question.

## URL view

The URL view identifies the specific pages earning citations. Use it to study:

* content formats that appear repeatedly;
* pages from your own domain that already have authority;
* competitor pages that cover a gap; and
* third-party pages where outreach or contribution may be valuable.

## Prompt view

The prompt view works in the opposite direction: start with a question and see which sources support its answers. This is useful when planning content for a specific topic or buying decision.

## Trends

Use trends to distinguish persistent source authority from a short-lived spike. Keep the date range and engine filters consistent when comparing periods.

## Decide what to do next

* If your own pages are cited, protect and improve them.
* If competitors dominate, compare their coverage and evidence with yours.
* If third-party sources dominate, consider digital PR, partnerships, community participation, or expert contributions.
* If no source is consistently strong, there may be an opportunity to create the clearest reference on the topic.


---

# 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://docs.usereach.ai/understand-your-visibility/sources.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.
