Sitemap monitoring is the regular, automatic check of a website’s XML sitemaps. It looks at availability, changes and the quality of the URLs inside, and sends an alert when something stands out.
What is checked?
- Availability: can the file be fetched with status 200?
- Size and format: Google allows at most 50 MB uncompressed or 50,000 URLs per sitemap and requires UTF-8. Larger sets are split across several files with a sitemap index.
- Content: does the sitemap list URLs that redirect, return errors, carry noindex or are blocked by robots.txt? These checks are common practice, not a Google rule.
- Change: how many URLs were added or removed, and is a whole section missing?
- Valid markup: does the XML parse without errors, and are there duplicate URLs?
| Type | What is checked? | Usual frequency | What it catches |
|---|---|---|---|
| Uptime monitoring | whether a URL is reachable and returns the expected status code within a time limit | short intervals, often minutes | Outages and server errors (5xx), including at night. On 5xx and 429, Google temporarily slows down crawling. |
| Website monitoring | Umbrella term for availability, load time and functions of a website, such as login or checkout | varies by check | broken user flows on pages that respond without errors themselves |
| Change monitoring | Content of a page or file compared with the previous fetch | set by the user | changes without an error code, such as a new title, a changed canonical or a removed text section |
| SEO monitoring | search-relevant signals of many URLs: status codes, redirects, noindex, canonicals, robots.txt, sitemaps, content | regular crawls, usually daily to weekly | a noindex after a release that visitors never see. Google drops such pages once it reads the tag while crawling. |
| Rank tracking | Position of the site for set keywords, per country, language, location and device | daily to weekly | drops for single keywords in a fixed setup. Search Console instead shows the average topmost position across all impressions. |
| robots.txt monitoring | Content, availability and status code of robots.txt | regular, interval of your choice | a new blocking rule such as Disallow: /. Google generally caches robots.txt for up to 24 hours. |
| Sitemap monitoring (this term) | Availability, format and listed URLs of XML sitemaps | regular, interval of your choice | suddenly missing URLs or whole sections. Google limits a sitemap to 50 MB (uncompressed) or 50,000 URLs. |
There is no standard for these types of monitoring. Scope, frequency and examples are based on practical experience and vary by tool. Statements about Google's behaviour (crawling on 5xx and 429, noindex, robots.txt caching, sitemap limits, position in Search Console) are backed by sources. Sources: Google Search Central: Wie sich HTTP-Statuscodes und Netzwerkfehler auf die Google Suche auswirken; Google Search Central: Indexierung mit noindex blockieren / Block indexing with noindex; Google Search Central: So interpretiert Google die robots.txt-Spezifikation; Google Search Central: Sitemap erstellen und einreichen / Build and submit a sitemap; Google Search Central: So funktioniert die Google Suche / How Google Search works; Search-Console-Hilfe: Leistungsbericht (Suche). Last checked: .
What Google looks at
Google ignores the <priority> and <changefreq> values. It uses <lastmod> when the value is consistently and verifiably accurate, meaning it reflects significant changes and not, say, a copyright year. A monitor can check whether the date only changes when content really changes.
According to vendor descriptions, some tools also track other sites’ sitemaps, for example to see which pages a competitor adds.
Example
After a release, half of the URLs are missing from the product sitemap. The count drops from 40,000 to 20,000 and triggers an alert. The example is invented.
Sources
- Build and submit a sitemap - Google Search Centraldevelopers.google.com
- Sitemap Monitoring - Oh Dearohdear.app
- Sitemap Monitoring - SEOTestingseotesting.com
Last updated: