How to Monitor Sitemap Changes and New URLs

Decide whether you need a new URL or a changed page.

A sitemap supplies URLs. A source watch can compare their identities with entries it has already seen. It does not automatically open every listed page or compare the content inside each one.

This distinction avoids a common disappointment: a URL’s content can change repeatedly while the sitemap still lists the same address. Conversely, a newly seen URL may have existed before it appeared in the monitored source.

Choose a source with the entries you need.

Look for a publisher’s RSS or Atom feed, or a Sitemap entry in its /robots.txt. Use the source URL itself. PageFluxer does not start from a homepage and crawl the entire site to discover feeds.

RSS and Atom often supply a title and a short description, making a phrase filter such as “senior developer” useful. A sitemap primarily identifies addresses, so a filter such as /careers/ or /release-notes/ matches the URL. It does not search the linked page’s text.

Sources must be public. Choose a smaller child sitemap when a large index exceeds the scan limits. Preview warnings describe what was actually scanned; do not assume a successful preview means the publisher lists every relevant page.

Save the known entries before watching for new ones.

1. Preview the exact source URL.

   Open Watch for new entries and paste the feed or sitemap. Any plan can try the preview; saving the recurring watch requires Pro or Business.

2. Choose the match.

   Select any new entry, or use a literal phrase. For a sitemap, select a URL phrase. For RSS/Atom, choose the supplied title, description, URL or supported combined fields.

3. Confirm the quiet baseline.

   Review the current entries, name and interval, then start watching. Entries already present are remembered without an alert. Future first-seen matches are the useful signal.

4. Review the new entry before following it.

   Check its address and source context. To detect later edits inside the new page, create an individual page monitor and verify its capture. The source watch does not do that automatically.

Read a new-entry example without confusing it with publication time.

The example kit includes before and after sitemap XML. Serve the before file at a public source URL you control, save its baseline, then replace the XML at the same URL with the after file. The first entry remains unchanged; the second URL is new to the source.

You can also preview PageFluxer’s public sitemap to see a real source. It lists this site’s published routes. This guide does not claim that your preview will contain a new entry or that a specific alert has occurred in your account.

Understand what does not trigger a new-entry alert.

Edits to an already known entry, changes to a sitemap’s modification date, disappearing entries and the return of a remembered URL do not create another new-entry alert. Use a page monitor for content revisions.

Feeds may show only recent items. A URL can appear and disappear between scans. Publisher ID changes can also make old content look new. Use the alert as a prompt to inspect the source, not as a complete publication ledger.

The current source scanner supports UTF-8 RSS 2.0, Atom and XML sitemaps, with bounded entries and same-origin child sitemaps. It does not support signed-in feeds, browser-only sources or unlimited crawling. Source watches use Cloud HTML checks, with intervals of 15 minutes or slower; Local source watches are not supported.

For a visible list of links on an ordinary webpage, use New items monitoring instead. A feed or sitemap is useful when the publisher already provides the structured source you need.