How to change your sitemap in Promptwatch

Your sitemap is the list of pages Promptwatch works from. It fills the page inventory under Site → Pages, it is what the weekly Health audit checks, and it is where Content Gap looks for pages to match against prompts. None of that runs until at least one sitemap has synced, so adding it is part of the initial setup, right after you set the project website. A sitemap is not the only way to fill the inventory: a connected Google Search Console property can add URLs too. Sitemap and Google Search Console explains how the two sources relate.

​

Where the sitemap settings live

Click Settings at the bottom of the rail. Settings opens on its first item, which is Sitemap under Project settings: the page is titled “Sitemap” with the description “Configure your sitemap URLs and crawler settings.” If the project has no sitemap and no pages from any other source yet, Site → Pages shows an empty state that reads “Add your sitemap to start monitoring pages” with a Setup sitemap button. That button takes you to the same settings page.

​

How to add a sitemap

1. Click Settings at the bottom of the rail. The Sitemap page under Project settings opens.
2. In the Sitemaps card, paste your sitemap URL into the field labelled Add a new sitemap, for example https://example.com/sitemap.xml. It has to be a valid URL.
3. Click Add.

Promptwatch syncs the sitemap straight away and reports the result in a toast: “Sitemap crawled: N URLs added.” If some URLs were skipped because they belong to a different domain, a second line reads “M URLs filtered (different domain).” If the sitemap is saved but the first sync fails, you get “Failed to add sitemap: …” and the URL stays in the list, so you can retry it with the refresh icon instead of adding it again. The sync only collects URLs. Crawling the content of those pages continues in the background, and the first weekly Health audit is scheduled once the project has URLs, so the inventory and the audit fill in after you add the sitemap, not at the moment you click Add.

​

The rules that decide what gets in

• The domain has to match: the sitemap’s root domain must be the same as the project website’s root domain, otherwise the add is rejected with “Failed to add sitemap: Sitemap URL must be on the same domain as the project website”. Subdomains of the same root are fine, so https://blog.example.com/sitemap.xml works for a project whose website is example.com. A project needs a website before it can take a sitemap.
• You can add more than one: the Sitemaps card accepts one or more sitemap XML URLs, each listed as its own row. Useful for sites that split their sitemap per section or language.
• Other subdomains are excluded by default: only URLs on the main host and its www variant are synced. The switch Allow different subdomains in sitemap sync on the same page includes URLs from other subdomains such as blog.example.com or shop.example.com.
• The page limit depends on your plan: Promptwatch crawls up to a plan-specific number of pages per organization, shared by all its projects, shown on the Pages page as “Page limit: X / Y”. On the Explore plan the Pages page is locked behind the “Monitor how AI crawlers index your site” overlay and no pages are crawled. See Plans and billing for the limits.
• Viewers can look but not change: the add, crawl and remove controls are disabled for project viewers.

​

What each listed sitemap shows

Each sitemap in the Sitemaps card is a row with its URL, when it was last synced (“Synced X ago”, or “Not synced yet” if the first sync has not completed), the number of URLs it contributed (“N URLs”), and two icon buttons: a refresh icon with the tooltip Crawl this sitemap and a trash icon with the tooltip Remove this sitemap.

​

How to change your sitemap

There is no edit control on a sitemap row. To move from an old sitemap URL to a new one, add the new one and remove the old one:

1. Add the new URL with Add, as above, and wait for the “Sitemap crawled” toast.
2. On the old sitemap’s row, click the trash icon (Remove this sitemap).
3. Confirm in the dialog titled “Remove this sitemap?”. It explains that the URL “will no longer be crawled for new pages. Pages already discovered from it stay in your list.” Click Remove.

Removing a sitemap only stops future syncs from it. It does not delete the pages it already discovered, so your inventory, audit history and page data stay intact. That is deliberate: a sitemap swap is usually a change of file location, not a change of site, and losing page history over it would reset every trend.

​

How to re-sync a sitemap

• Automatically, every day: sitemaps of organizations with an active or trialing subscription re-sync at 00:00 UTC, so pages you publish or remove show up in the inventory within a day as long as your sitemap file is up to date.
• On demand: click the refresh icon (Crawl this sitemap) on a row to sync it now, for example right after you publish a batch of pages.

A re-sync updates the list of URLs. The content crawl of each page and the weekly audit are separate processes with their own schedules; Site health covers how the audit runs and how to confirm a fix.

​

Other settings on the same page

Below the Sitemaps card, the page also has Verified Bot Mode and Slow Crawl Mode. Slow Crawl Mode is “Recommended for Shopify and other platforms that rate-limit crawlers”; the page warns that it can significantly increase how long crawling takes to complete, so leave it off unless your platform blocks the crawler.

​

After your sitemap has synced

Open Site → Pages to watch the inventory fill up and see which pages have been crawled. The first weekly audit lands on Site → Health once it completes. If you also use Google Search Console, connecting it lets you pull in URLs Google knows about that your sitemap misses; see Google Search Console.