> For the complete documentation index, see [llms.txt](https://docs.direqt-search.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.direqt-search.com/content-indexing/indexing-faqs.md).

# Indexing FAQs

How Direqt uses your content to power your search functionality

### What's an index?

An index is a database of all the searchable content on your website.&#x20;

### How do you index my content?

Our crawler visits each page that is accessible from the URL you provide and extracts body text and metadata.  The collected data is structured and stored in the search index. The index updates automatically at regular intervals to keep your content current.

### What content do you index?

We can index the content of the following file types:

* HTML Pages
* Images
* PDF Documents *(Enterprise Plans Only)*&#x20;

For each indexed URL, we attempt to extract key fields such as:

* Title&#x20;
* Description
* Author
* Publish Date&#x20;
* Body Text&#x20;

### What content is not indexed?

Some content on your site may not be included in your search index:

* Blocked Pages – If your site’s server permissions or redirects prevent access, those pages won’t be indexed.
* Protected Content – Pages behind logins, paywalls, or authentication barriers cannot be indexed.
* External Domains & Subdomains – We only index the domain you provide. For example, if you create an engine for `example.com`, pages on `blog.example.com` will **not** be included.

### How can I improve the quality of my index?

Refer to the [Indexing Best Practices](https://docs.direqt-search.com/content-indexing/indexing-best-practices.md) guide for tips on optimizing your site index.


---

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.direqt-search.com/content-indexing/indexing-faqs.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
