DocsMonitoringTracked elements

Tracked elements. What is compared on every check.

Every check captures all elements. The project's What To Track settings decide which changes are logged, and each URL's alert settings decide which changes send an alert.

On this page

Elements

ElementWhat exactlyOn by default
Meta titleEvery <title>, compared by position (#1, #2…)Yes
Meta descriptionThe first meta name="description"Yes
H1 headingThe text of every <h1>, by positionYes
Canonical URLEvery link rel="canonical", by positionYes
Meta robotsThe first meta name="robots"Yes
HTTP | X-Robots-TagThe response headerYes
HTTP statusThe status of the first responseYes
Redirect URLThe Location of a 301, 302, 307 or 308Always
HTTP | LinkThe Link response headerNo
HTTP | Content-TypeThe response headerNo
Rel=alternate hreflangAll hreflang and href pairsNo
Noscript in headThe first <noscript> in <head>No
og:titlemeta property="og:title"No
Total linksNumber of <a href> linksYes
Nofollow linksNumber of links with rel="nofollow"Yes
JSON-LDEvery block, per schema type. See Structured dataYes
Code snippetsYour own text, found or not found. See Code snippetsPer snippet
robots.txtFull content and HTTP status. See robots.txt & sitemapsYes
Sitemaps (4 events)Added, removed, HTTP status, blockedWith robots.txt
Connection errorsDNS error, timeout, connection refused, other connection errors, blocked URLAlways

"On by default" refers to new projects created from the setup guide. The New project form starts with all elements on.

Also captured on every check

  • The raw HTML of the page, viewable in the check timeline.
  • The response time in milliseconds. See Response times.
  • The HTML size in bytes.
  • Whether Googlebot may crawl the URL according to robots.txt.

These are shown, but a change in them does not create a change entry or an alert.

How comparison works

  • Each check is compared with the last successful check of the same URL. The first check is the baseline and creates no changes.
  • Values are read from the HTML as the server sends it. JavaScript is not run, so content added by scripts in the browser is not seen.
  • Elements that can occur more than once, like titles, H1s and canonicals, are compared by position, so a second canonical shows up as its own change.
  • Connection errors are logged when a URL goes from reachable to unreachable.

Not tracked

To set expectations: Search Sentinel does not track Twitter/X cards, meta keywords, Open Graph tags other than og:title, H2 to H6, image alt text, the viewport or language, the full redirect chain, visual changes or screenshots, or content rendered by JavaScript. There is no full-HTML diff; changes are per element.