> For the complete documentation index, see [llms.txt](https://docs.relevat.hu/supabase.js-bubble-plugin/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.relevat.hu/supabase.js-bubble-plugin/setup/supabase-data/create-xml-sitemap.md).

# Create XML Sitemap

The plugin can create a sitemap two ways. One Client Side and the Other is Server Side. 

#### Client-Side:

Found under the Data element. It uses the Output it recieved, meaning the list of things you've gotten from Supabase. 

![](/files/XW0AC7hbkkOgjoFTGik1)

* Field Name: this should be the exact name of the column name.
* URL: The Base URL for building the links. It can be a dynamic or static text like <https://myblog/posts/> and should end with a slash
* Send to Storage: It will automatically send the file to the bucket ready to be used. Make sure you have the RLS setup. It will also override the file existing already under that name.&#x20;
* Download File: Downloads the XML file generated
* Sitemap Name: name of the file/key, without the '.xml'

#### Server Side:

This is a separate action, which can and should be used as a Backend Workflow.\
![](/files/ZDmCAizKAnU2MQGI8hYv)

* Raw JSON Input: Will be the Raw JSON text coming from most likely an API call to Supabase.&#x20;
* Field Name: this should be the exact name of the column name.&#x20;
* URL: The Base URL for building the links. It can be a dynamic or static text like <https://myblog/posts/> and should end with a slash&#x20;
* Send to Storage: It will automatically send the file to the bucket ready to be used. It uses the Service Key for convenience so make sure to add that and it will also override the file existing already under that name.&#x20;
* Sitemap Name: name of the file/key, without the '.xml'

This action can be setup as a weekly on biweekly cron job, to update your Sitemap. I'd recommend to setup a recoursive Backend Workflow, where first using the API connector you get the response from Supabase, and pass the raw response to the action to update the file.&#x20;

Generated Sitemap in both cases will look something like this:&#x20;

```xml
<?xml version="1.0" encoding="UTF-8"?>
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
  <url>
    <loc>https://your.bubbleapps.io/slug-1</loc>
    <lastmod>2024-11-05T16:24:48.176Z</lastmod>
    <priority>0.5</priority>
  </url>
  <url>
    <loc>https://your.bubbleapps.io/slug-2</loc>
    <lastmod>2024-11-05T16:24:48.176Z</lastmod>
    <priority>0.5</priority>
  </url>
  <url>
    <loc>https://your.bubbleapps.io/slug-3</loc>
    <lastmod>2024-11-05T16:24:48.176Z</lastmod>
    <priority>0.5</priority>
  </url>
</urlset>
```


---

# 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.relevat.hu/supabase.js-bubble-plugin/setup/supabase-data/create-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.