> For the complete documentation index, see [llms.txt](https://knowledge.magicworksitsolutions.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledge.magicworksitsolutions.com/knowledge/seo-aeo-geo-and-ai-search/trust-evidence.md).

# Trust and evidence

Why visible evidence, authorship and claims boundaries matter in AI-search visibility.

Strong retrieval is not only about technical accessibility. Sources also need to make their credibility legible.

Useful trust signals include:

* named authors or accountable organisations,
* clear editorial ownership,
* references where factual claims depend on external evidence,
* publication and update dates where relevant,
* correction mechanisms,
* transparent claims boundaries,
* and consistency between public pages.

For regulated, financial, medical, legal or safety-sensitive topics, governance should be stronger still.

Trust signals do not guarantee ranking or citation, but they reduce ambiguity about who is making the claim and why the source should be taken seriously.


---

# 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://knowledge.magicworksitsolutions.com/knowledge/seo-aeo-geo-and-ai-search/trust-evidence.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.
