> For the complete documentation index, see [llms.txt](https://docs.realmacsoftware.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.realmacsoftware.com/elements/site-quality/sitemap.xml.md).

# sitemap.xml

A sitemap provides search engines with a clear map of your website’s structure

Elements automatically generates a `sitemap.xml` file in the root of your website. By default, all new pages are included in the sitemap.

If you want to exclude a page, simply uncheck the Include in sitemap option in the Page Inspector.

### Sitemap Location

Once you've exported or published your website you will find the `sitemap.xml` file in the root folder of your website.

### Sitemap Benefits

A sitemap provides search engines with a clear map of your website’s structure, and using one comes with several key benefits:

#### ✅ Helps Search Engines Discover Pages

Sitemaps list all the important pages on your site, making it easier for search engines like Google to find and index them, especially if:

* Your site is new and has few external links
* Some pages are hard to discover through internal navigation alone

#### 🚀 Improves SEO

A well-maintained sitemap ensures that your most important content is noticed and crawled efficiently, which can improve how your site appears in search results.

#### 🧭 Gives You Control

You decide what gets included. Pages you don’t want indexed, like landing pages, test pages, or thank-you pages can be excluded.

### Ignored file types

Elements will not add Folders or the following file types to your sitemap.

{% code overflow="wrap" %}

```
md, markdown, txt, yaml, yml, toml, json, css, scss, sass, less, js, mjs, ts, jsx, tsx, map, log, lock, png, jpg, jpeg, gif, svg, webp, ico, xml, rss, atom, csv, pdf, zip
```

{% endcode %}


---

# 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.realmacsoftware.com/elements/site-quality/sitemap.xml.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.
