> For the complete documentation index, see [llms.txt](https://docs.dat-hub.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dat-hub.com/integrations/sources/website-crawler-sitemap.md).

# Website Crawler Sitemap

## Overview

The Website Crawler Sitemap source connector allows you to extract site structure and visual relationships between pages from Websites into your desired vector database.

## Configuration Options

* **Name:** This field represents the name you want to assign to the actor instance responsible for managing the Website Crawler Sitemap source. Choose a descriptive and unique name to easily identify this instance within your data activation tool (dat).
* **Site URL:** Enter the Site URL. like [https://www.example.com](https://www.example.com/).
* **Sitemap URL:** If available, enter the path to the sitemap. If left untouched, sitemap will be attempted to read from <https://www.example.com/sitemap>.

## Supported streams

The following streams are supported for this source:

* crawler\_sitemap


---

# 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.dat-hub.com/integrations/sources/website-crawler-sitemap.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.