OVERVIEW
What is a sitemap monitor?
A sitemap monitor compares the URLs in the same XML sitemap across successful scans. It records additions and removals—not changes to a page's HTML, price, copy, or visual design—so you can quickly see which pages a site published or removed.
Because a structured URL list avoids much of the noise created by templates, ads, and dynamic content, additions are useful publication signals and removals are useful review signals. Use this sitemap monitor for your own release checks or a competitor watchlist, but verify the page before drawing conclusions about content, rankings, or strategy.
WORKFLOW
How sitemap monitoring works
Sitemap monitoring first saves the current URL list as a baseline. Later scans then have a previous state to compare against, so the first successful scan creates no historical changes.
- 01
Add a public sitemap
Enter a public HTTPS XML sitemap URL. The scanner reads its URL list, not every page's copy or visual design.
- 02
Establish a baseline
The first successful scan saves the current URLs, so existing pages are not reported as new.
- 03
Read the changes
Later scans run every six hours. Review saved URL additions and removals on the web or through MCP.
A sitemap change alert is created only when a later successful scan finds an addition or removal. No difference creates no empty event, and a fetch failure does not replace the last successful baseline.
OWN SITE
Use XML sitemap monitoring on your own site
Added URLs help a team confirm that articles, landing pages, products, or resources entered the sitemap. An unexpected removal prompts a review of the page, its redirects, and the sitemap generator. This alert makes the publishing check repeatable, although it does not replace a full technical SEO audit.
Before you start monitoring, run the free sitemap checker to confirm the file can be read.
COMPETITORS
Track competitor new pages with a sitemap monitor
A public competitor sitemap is a low-noise source of new-page leads. Added URLs may reveal landing pages, content topics, product collections, or comparisons; removed URLs may reflect consolidation, redirects, or expired campaigns. Each change is a lead to investigate, not proof of a strategy.
Classify the page first
Open the URL, identify its page type, and record its topic, audience, and purpose.
Add outside evidence
Use search results, site navigation, and backlinks to judge whether the change deserves further research.
The sitemap monitor supplies the URL signal; use the sitemap diff to choose pages for deeper research. For competitor acquisition research, continue with the backlink leaderboard.
DIFF
Sitemap diff: see exactly which URLs changed
Each sitemap comparison checks the current successful URL list against the previous successful baseline. Paid members can review additions separately from removals after signing in, while a failed fetch is never treated as an empty sitemap. Read the sitemap diff by URL path and page type, then open the relevant pages: a list change alone does not prove indexing, ranking, copy, or permanent-deletion status.
+ added https://example.org/resources/technical-seo-guide/
− removed https://example.org/archive/old-comparison/
MCP
Query sitemap changes through MCP
Connect Build or Skip in an MCP-compatible assistant to read your monitors, scan health and saved URL changes. Try: “Which pages were added across my monitors in the past 24 hours?” Filter by time or monitor and follow pagination for the complete result. Queries read saved data without triggering another scan. Changes remain private to their owner and are also available on the website.
Read the MCP setup guideSCOPE
Sitemap monitor vs website change monitor
The tools answer different questions. Sitemap monitoring checks a structured URL list; a page change tracker compares a page's copy, DOM, or visual result. Use the first to discover pages and the second to inspect changes inside a known page.
This tool: URL-list changes
Compares an XML sitemap and preserves its added and removed URL details.
Not included: full-page or visual monitoring
Does not detect changes to copy, DOM, prices, inventory, screenshots, or layout.
Choose the URL-list view when discovery matters, then open relevant pages with the research method suited to your question.
FAQ
Frequently asked questions
How do I monitor sitemap changes?
Add a public HTTPS XML sitemap. The first scan establishes a baseline; every six hours, later scans compare its URL list and record additions or removals.
Can I monitor a competitor sitemap?
Yes, if it is public. Added and removed URLs can reveal launches or retirements, but you must verify the page content and strategy yourself.
How do I track new pages on a website?
Monitor its public XML sitemap. New URLs appear in your private change history, which you can also query through MCP.
How can I check if a sitemap has been updated?
Check the latest successful scan and URL changes. An unchanged list creates no change record; lastmod timestamps are not evaluated.
How often does it scan?
The current interval is every six hours.
Does the first scan report new pages?
No. It only establishes a baseline, so existing URLs are not reported as new.
What changes can I view?
Paid members can view added and removed URLs for their own monitors after signing in.
Are private sitemaps or full-page changes supported?
No. Sources must be public HTTPS XML sitemaps; this feature does not monitor DOM, copy, or visual changes.