Deutsch
Types of monitoring

Change monitoring

Also known as: Änderungsüberwachung

Change monitoring (also called website change detection) is the automated comparison of a web page or file against its earlier version, with an alert when something differs. In SEO it is used to notice unplanned edits to elements that affect crawling, indexing and snippets.

How does change monitoring work?

A tool stores a snapshot of a page at a set interval and compares each new snapshot with the previous one. Visualping describes comparisons of the visual rendering, the text and the code. UptimeRobot’s tool lets users select one area of a page so that only changes in that area trigger an email. Some tools add a filter that judges whether a change matters.

Monitoring loop: measure, compare, alertA loop in six steps. 1 Fetch: request pages or data again. 2 Compare with the previous state, for example a changed title or status code 404 instead of 200. 3 Check a rule or threshold. Without a relevant deviation there is no alert, and the next fetch follows. With a deviation, 4 an alert goes to the responsible person, 5 review whether the change is real and intended, 6 fix. Then the next fetch begins. Schematic view based on practice.no relevant deviation → no alertdeviationnext fetch1 · Fetchrequest pages ordata again2 · Comparewith the previous state,e.g. status 200 → 4043 · Ruledoes a thresholdor rule match?4 · Alertnotify theresponsible person5 · Reviewreal change or falsealarm? Intended?6 · Fixfix the cause,verify the resultSchematic view based on practice. Each team sets its own interval and rules.
Monitoring loop based on practice: fetch again, compare with the previous state, check a rule or threshold. An alert follows only for a relevant deviation, then review and fix. This is not a standard; each team sets its own interval and rules. Schematic illustration.

Which changes matter for SEO?

Typical candidates are elements where a single edit can change how a page appears in search:

  • the robots.txt file and XML sitemaps
  • the title element and the meta description
  • the robots meta tag, for example an added noindex
  • canonical tags and hreflang annotations
  • visible main content, headings and internal links

Google states that the robots meta tag controls how a page is crawled and indexed, so a changed value can remove a page from search results.

Types of monitoring compared
TypeWhat is checked?Usual frequencyWhat it catches
Uptime monitoringwhether a URL is reachable and returns the expected status code within a time limitshort intervals, often minutesOutages and server errors (5xx), including at night. On 5xx and 429, Google temporarily slows down crawling.
Website monitoringUmbrella term for availability, load time and functions of a website, such as login or checkoutvaries by checkbroken user flows on pages that respond without errors themselves
Change monitoring (this term)Content of a page or file compared with the previous fetchset by the userchanges without an error code, such as a new title, a changed canonical or a removed text section
SEO monitoringsearch-relevant signals of many URLs: status codes, redirects, noindex, canonicals, robots.txt, sitemaps, contentregular crawls, usually daily to weeklya noindex after a release that visitors never see. Google drops such pages once it reads the tag while crawling.
Rank trackingPosition of the site for set keywords, per country, language, location and devicedaily to weeklydrops for single keywords in a fixed setup. Search Console instead shows the average topmost position across all impressions.
robots.txt monitoringContent, availability and status code of robots.txtregular, interval of your choicea new blocking rule such as Disallow: /. Google generally caches robots.txt for up to 24 hours.
Sitemap monitoringAvailability, format and listed URLs of XML sitemapsregular, interval of your choicesuddenly 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: .

Example

A robots.txt file is replaced during a deployment, and the staging version contains Disallow: /.

Code
- Disallow: /checkout/
+ Disallow: /

A change monitor that compares the file daily shows this difference and sends an alert, so the team can restore the file before more pages drop out of crawling.

Common mistakes

  • Comparing whole pages, which creates alerts for rotating banners, timestamps and ads.
  • Watching only the pages that were chosen at setup, so new templates remain unobserved.
  • Having no owner for an alert, so no one decides whether the change was intended.

Sources

  1. Website change detection – UptimeRobotuptimerobot.com
  2. Visualping – website change detectionvisualping.io
  3. How to monitor your website's performance and SEO metrics – Search Engine Landsearchengineland.com
  4. Von Google unterstützte Meta-Tags (Meta tags Google supports) – Google Search Centraldevelopers.google.com

Last updated: