> ## Knowledge Base Index
> Fetch the complete knowledge base index at: https://help.banana.tech/sitemap.xml
> Use this file to discover available pages before exploring further.
> Pure-Markdown content can be obtained by appending a '.md' suffix to the content URLs listed in the sitemap (without the trailing slash).

# Sitemap.xml

### Choose which pages search engines should discover through your sitemaps.

The website uses a sitemap index to organize the individual sitemap files generated for each language. From the page settings panel, you can choose whether each page should be included and configure its **Priority** and **Frequency** values.

You can view the sitemap index at: www.yourdomain.com/sitemap_index.xml

The sitemap index contains a separate sitemap for each language available on the website. These language-specific files follow this structure: www.yourdomain.com/language/sitemap_language.xml

For example: www.yourdomain.com/en/sitemap_en.xml

Each language sitemap lists the pages included for that specific language.

A sitemap helps search engines discover URLs, but it does not guarantee that every included page will be crawled or indexed.

|| sitemap.xml helps search engines discover indexable URLs, robots.txt communicates crawler access rules, and llms.txt provides AI assistants with a curated summary and a selection of useful links.


## Include or exclude a page

Activate **Include in sitemap.xml** for public, canonical pages that you want search engines to discover.

You may want to exclude pages that are private, duplicated, redirected, unavailable, temporary, or not intended to be discovered through the sitemap.

Removing a page from the sitemap does not prevent it from appearing in search results. Search engines may still discover it through internal or external links. If a page must not be indexed, its indexing settings must also be configured appropriately in robots.txt.

For example, if a landing page was created for a private or temporary campaign and should not appear in search results, exclude it from the sitemap and make sure it is also configured not to be indexed.


## Priority

**Priority** indicates the relative importance assigned to a page compared with other pages on the same site. In the sitemap file, this value is represented by `<priority>`.

The value ranges from `0.0` to `1.0`:

* `1.0` means highest priority.
* `0.5` is the default priority.
* `0.0` means lowest priority.

As a general reference, you can use:

* `1.0` for the homepage.
* `0.8` or `0.9` for main navigation pages, such as Rooms, Offers, Restaurants, or Location.
* `0.8` or `0.9` for important landing pages used in campaigns, paid traffic, or direct conversion flows.
* `0.6` or `0.7` for important subpages, such as room detail pages or offer detail pages.
* `0.3` to `0.5` for secondary pages or temporary landing pages.
* `0.1` or `0.2` for legal pages or pages with low search importance.

Priority is relative to the other pages on the same website. Setting every page to `1.0` does not make them rank higher.

Priority is an optional sitemap value. Some crawlers may use it as a hint, but Google currently ignores it.


## Frequency

**Frequency** indicates how often a page is expected to change. In the sitemap file, this value is represented by `<changefreq>`.

Available values are:

* `always`: The page changes every time it is accessed.
* `hourly`: The page may change several times a day.
* `daily`: The page may change every day.
* `weekly`: The page may change every week.
* `monthly`: The page may change every month.
* `yearly`: The page rarely changes.
* `never`: The page is archived and is not expected to change.

Choose the value that best represents how often the page content is normally updated. This value does not control how often a search engine visits the page.

Frequency is also an optional sitemap value. Some crawlers may treat it as a hint, but Google currently ignores it.