> For the complete documentation index, see [llms.txt](https://docs.avada.io/seo-suite-help-center/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.avada.io/seo-suite-help-center/other-features/sitemap-generator/xml-sitemap.md).

# XML sitemap

{% hint style="info" %}
**Who can use this feature?**

* This feature is available for Pro and Enterprise plan users.
  {% endhint %}

An XML sitemap is a file that lists all the pages on a website, helping search engines like Google find and index them easily. 

It guides search engines like Google to the content you want noticed, improving visibility in search results.

We help you edit XML sitemap and manage sub sitemap & URLs.

{% hint style="info" %}
All Shopify stores automatically generate a sitemap.xml file here: `yourdomain.com/sitemap.xml.`
{% endhint %}

<details>

<summary>What is sub sitemap?</summary>

**A sub sitemap:** is a smaller, focused section of an XML sitemap that groups specific types of pages, like blog posts, product pages, or categories.&#x20;

Sub sitemap helps organize large websites by breaking down the sitemap into manageable parts, making it easier for search engines to crawl and understand content by topic or structure.

</details>

### Create & submit XML sitemap

{% stepper %}
{% step %}

#### Turn on XML sitemap

Go to SEO tools -> Click Sitemap generator -> Turn on XML sitemap
{% endstep %}

{% step %}

#### Manage sub sitemap

You can select sub sitemap and URL you want to include in sitemap.

In URL management, you can add or exclude each URL to sitemap.
{% endstep %}

{% step %}

#### Submit sitemap

Click Update for the latest sitemap -> Click Submit

{% hint style="info" %}
You need to connect your [Google Search Console](/seo-suite-help-center/other-features/google-search-consoles.md) account to submit sitemap.
{% endhint %}
{% endstep %}
{% endstepper %}

Follow this interactive guide to create & submit XML sitemap.

{% embed url="<https://app.arcade.software/share/Avlxv4n8tPDVOiiSYya7>" %}

{% hint style="info" %}
If you turn off XML sitemap (that has been submitted to Google Search Console), sitemap will stay in the GSC but all URLs in sitemap will be deleted.&#x20;
{% endhint %}

### Custom XML sitemap

{% stepper %}
{% step %}

#### In Settings, click Edit

{% endstep %}

{% step %}

#### Edit your settings

You have options to custom XML sitemap:

* Set URL count limit for each sub sitemap: Set a limit for the number of URL in each sitemap. If number of URLs in a sitemap exceeds limit, a new sub sitemap will be auto-created.
* Set rules to auto-exclude pages from sitemap
* Set auto-update frequency: Sitemap will be updated automatically when you add new pages to your site (products, collections or blog posts)
  {% endstep %}
  {% endstepper %}

Follow this interactive guide to set rules to custom XML sitemap.

{% embed url="<https://app.arcade.software/share/3TTRMh68vevOiA7HpgEL>" %}


---

# 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.avada.io/seo-suite-help-center/other-features/sitemap-generator/xml-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.