New Structured data tracking, field by field

Know a page changed before your rankings do.

A release removes a canonical, a plugin update rewrites the robots.txt, a tag manager change drops the analytics code. Search Sentinel checks your URLs, compares every check with the last one and tells you exactly what changed, where you work.

7 days freeno credit card23+ elements per URL

6 URLs watched · last check 2 min ago
Example ShopChange historyCore Web Vitals

Projects

Example Shop 6

Client: Travel Co 48

Competitors 12

Docs site 20

Project

Monitored URLs

Search Console

Domain health

Checks today

144

Changes

3

LCP p75

2.1s

/products/running-shoes/canonical changed · 09:14changed200
/robots.txt+ Disallow: /products/ · 09:14blocked200
/checkout/snippet gtag('config') present · 09:20ok200
/category/sale/redirects to /sale/ · 08:55301301
/blog/LCP 2.1s → 3.4s · weekly CrUXover200
Compared on every check title & meta description rel=canonical robots meta & X-Robots-Tag hreflang JSON-LD status & redirects robots.txt LCP INP CLS

01

The old and the new value, next to each other

Every check is stored as a snapshot and compared with the one before. When an element changes you see exactly what it was and what it is now, not a vague "something changed".

  • 23+ elements: title, description, H1, canonical, meta robots, X-Robots-Tag, status, redirects, headers, hreflang, og:title, link counts and more.
  • Raw HTML of every check, to look back at a page as it was.
  • Filter history by element and date range.
URL monitoring
search sentinel · change history
# illustrative changes, not real output
09:14  /products/running-shoes/
       canonical  - /products/running-shoes/
                  + /products/

09:14  /robots.txt
       + Disallow: /products/
       [bad]  section blocked for Googlebot

10:02  /checkout/
       title  - Checkout | Example Shop
              + Secure checkout | Example Shop

sent to #seo-alerts and 2 e-mail addresses

02

Core Web Vitals from real Chrome users

Field data from the Chrome UX Report for every URL, on phone and desktop, refreshed every week after Google publishes it. Set thresholds per project and get an alert when a metric turns poor, regresses week over week or month over month, or its share of good visits drops.

  • LCP, INP, CLS, FCP and TTFB at the 75th percentile.
  • Phone and desktop, with up to 40 weeks of history from the first day.
  • Origin fallback when a URL has too little traffic for URL-level data.
  • Per-metric switches: LCP, INP and CLS alert by default; FCP and TTFB when you switch them on.
Core Web Vitals
/blog/ · phone · p75

LCP

3.4s

INP

160ms

CLS

0.04

LCP, last 16 weeks

poor above 4.0s · week over week +12% · alert sent to e-mail and Slack

03

Is the tracking code still there after the release?

Tell Search Sentinel which code belongs on a page, like the GA4 tag, a GTM container or a pixel. Every check looks for it in the HTML, and you hear about it the moment a snippet goes missing, or turns up where it was missing before.

  • Exact text match on the page's HTML: code, a link, a phrase.
  • Add to many URLs at once, or while adding the URLs.
  • Found or not found, with the HTML source highlighted.
Code snippets
snippets · /checkout/
Snippetlast foundnow
gtag('config', 'G-ABC1234567'09:20found
GTM-K7Q2XQ09:20found
cookiebanner.min.js08:20not found
connect.facebook.net/en_US/fbevents.js09:20found
"@type": "Product"09:20found

elements

23+

compared on every check of every URL

channels

5

e-mail, Slack, Teams, Google Chat and webhooks

vitals

5

LCP, INP, CLS, FCP and TTFB from the Chrome UX Report

trial

7days

free, without a credit card

Getting started

Four steps, a few minutes.

Start with the templates that earn the money: one URL per template is often enough to catch a broken release.

Read the quick start
  1. Create a project. One per site or per client. A single-domain project can connect Google Search Console and adds domain health checks.
  2. Add URLs. One by one, as a list, or picked from your Search Console pages in the setup guide.
  3. Choose what to track. The elements that matter, code snippets, Core Web Vitals, and how often each URL is checked: hourly up to once a year.
  4. Set up alerts. E-mail, Slack, Microsoft Teams, Google Chat or a webhook, per URL or per project.

Questions about Search Sentinel.

All questions
How is this different from a crawler?

A crawl tells you what a site looks like today. Search Sentinel watches a fixed set of URLs over time and tells you what changed and when. Use a crawler for an audit, and Search Sentinel to make sure the audit's fixes stay fixed.

Who is it for?

SEOs who want to know when a title, canonical or robots.txt changes; developers who need to know that tracking code survived a release; and agencies that look after many client sites at once.

Is there a free trial?

Yes: 7 days, no credit card, with 5 URLs and 50 checks to try everything. See pricing for the plans after the trial.

Will the checks show up in my analytics or get blocked?

Checks are plain HTTP requests for the HTML; they do not run JavaScript, so analytics tools do not count them. If a firewall blocks the crawler, allowlist your account's user agent: SearchSentinel.app followed by your crawler ID. See the crawler.

Put your money pages on watch. Before the next release.

Add the templates that matter, choose where alerts go, and let it check while you work on something else.

7 days free, no credit card