A sitemap.xml built from the pages your site actually rendered, taken from the latest Vercel build rather than from the CMS.
Enter your site's base URL, for example https://example.com, and click Generate Sitemap. The paths come out of the most recent Vercel deployment's build log and are joined onto the base URL you gave.
Because the source is the build rather than Prismic, the result reflects what visitors and crawlers can reach. A page missing here that should exist is a build problem, and url_audit is the tab that explains which documents are affected.
Some paths are always dropped: /slice-simulator, /preview, _payload and _nuxt internals, and static asset requests.
Add your own by typing a path and clicking Add, or pressing enter. A leading slash is added if you leave it off. Each custom exclusion appears as a chip you can remove with the ×. Exclusions are matched against the generated paths, so adding /admin drops that section from the output. They apply on the next generate, and are not saved between visits to the tab.
The URL list is shown in full so you can check it before use, with a count at the top. Download sitemap.xml saves the generated file. Nothing is uploaded to your site - where the file goes is up to you, whether that is committing it to the repo or serving it from a route.
An empty result usually means the last deployment failed or produced no prerendered pages. Check the builds tab.
Vercel project ID and token. Prismic is not queried by this tab.