Noindex appeared
A single meta directive can erase a page from search. High-severity alerts fire the moment a watched page becomes noindex.
URL Monitoring · Scalar diffs only
Know when the page changes.
Not when the template reflows.
ToolTrace watches your URLs for structured changes: title, canonical, noindex, status code, JSON-LD type set, H1. Each change is classified low, medium, or high severity so your inbox stays signal.
- 8 structured signals per URL
- 3 severity levels, per-watch policy
- 15 min minimum check interval
- 200 watches per account
- Scalar diffs, no pixel noise
What you'll know
SEO changes you would otherwise miss.
A template edit that reflows the HTML is not a story. A canonical that disappeared the day organic traffic halved is. ToolTrace tells you the second one.
Canonical changed or disappeared
A silently rewritten canonical consolidates traffic onto the wrong URL. Any canonical change is recorded; a disappearance is high severity.
Status class changed
A watched page went from 200 to 404, 500, or stopped responding. Fetch failures and status-class transitions are flagged high severity so a bad deploy surfaces in minutes, not days.
Title or description changed
A rewritten title shifts click-through rate and ranking. Medium severity by default so a content update is noticed without becoming an incident.
JSON-LD type set changed
Structured data added, removed, or re-typed. Catches a developer who swapped Article for BlogPosting, or dropped Product markup from your catalog.
H1 or primary heading changed
Low severity by default, logged for reference. Combine with title changes to spot a page rewrite without being pulled into every edit.
URL monitoring guide
Scalar diffs are the right unit for SEO monitoring.
Pixel-diff and raw-HTML diff tools generate alert noise. ToolTrace compares a specific list of signals and classifies each change so your alert policy can target the ones that matter.
Why scalar diffs beat pixel and HTML diffs
Pixel-diff tools like Visualping fire on every CSS reflow, A/B test, and cookie banner redraw. Raw HTML diffs fire on every build hash, every reorder of inline styles, every tracking script change. Teams who adopted them end up muting the alerts, which defeats the point.
ToolTrace compares a short list of structured signals extracted from the HTML. A watched page can change its layout, its paragraphs, its scripts, and its cache headers without producing an alert. When the title, canonical, noindex, status, or JSON-LD type set changes, that is the alert.
What ToolTrace tracks per URL
Each check records a snapshot with these fields: HTTP status code, final URL (after redirects), elapsed fetch time, page title, meta description, canonical URL, robots meta tag and the derived noindex flag, first H1 text, the sorted deduplicated set of JSON-LD @type values across all script blocks, and the JSON-LD block count. The diff engine compares consecutive snapshots and records a diff when any of these moved.
Normalization is deliberate: whitespace-only differences in strings are ignored, and JSON-LD type lists are compared as sorted sets. A template edit that reorders script tags will not produce a diff; a schema change that adds FAQPage will.
How severity is assigned
High severity covers anything that breaks indexing or availability: noindex appeared, HTTP status changed class (2xx to 4xx/5xx or vice versa), canonical disappeared, final URL changed hostname, or the fetch failed outright. These are the changes that cost traffic within hours.
Medium severity covers changes a buyer should notice this week: title or meta description changed, canonical changed within the same hostname, JSON-LD type set added or removed a type, final URL changed path. These rarely require same-day action but should be seen.
Low severity covers cosmetic changes worth logging: H1 text changed, JSON-LD block count changed without a type-set change, HTTP status moved within the same class (200 to 201).
Alert policies without noise
Each watch has an alert policy. "Any change" sends an email for every recorded diff. "High-severity only" sends only when at least one changed field is high severity, which is the right default for watching your own production pages. "Record only" writes diffs to the dashboard without emailing, which is the right default for competitor monitoring where volume is high and urgency is low.
Diffs can be acknowledged from the dashboard. An acknowledged diff never re-alerts, so a resolved issue is not re-sent on the next scheduler tick.
Who uses this
SEO teams watch high-value pages for silent noindex or canonical regressions after deploys. Agencies watch client sites to catch template changes that broke structured data. Product teams watch pricing and feature pages so marketing hears about edits before customers do. Developers watch competitors' key pages for schema or messaging shifts.
The common thread: a short list of pages that matter, where a change should produce an email instead of being discovered weeks later in Search Console.
How ToolTrace monitoring compares
Visualping and similar pixel-diff tools are good at "did this page change at all" and bad at "did something that matters change". ToolTrace sits above them by comparing structured signals instead of rendered pixels, so cosmetic reflows do not produce alerts.
Conductor (formerly ContentKing) and enterprise SEO suites cover a superset of what ToolTrace monitors, with crawl orchestration, log analysis, and historical dashboards. They are the right choice at enterprise price points. ToolTrace is positioned for individual teams and agencies who need the SEO-focused subset at a developer-tool price.
Little Warden is the closest shape by philosophy, with a similar focus on structured signals. ToolTrace adds a unified credit pool shared with the rest of the ToolTrace APIs, a JSON-LD type set diff, and a scoring model that classifies severity automatically.
URL monitoring questions
How often can I check a URL?
From every 15 minutes up to every 30 days. The first check runs immediately after a watch is created so results arrive within a minute rather than an interval.
Does it send alerts for low-severity changes?
Only if you set the watch to "any change". The default "high-severity only" policy keeps the alerts actionable; the full diff log is always visible on the dashboard.
Does ToolTrace render JavaScript when checking a URL?
Not in the current scope. Checks use the fast static fetcher. If a scalar signal (title, canonical, meta robots, JSON-LD) only appears after JavaScript, raise this and we will prioritize a per-watch render toggle.
What happens when a watched page stops responding?
Fetch failures are recorded as a diff with a high severity level, and an alert fires if the policy allows. The watch is not paused automatically. If the URL keeps failing, the dashboard shows a consecutive-failure counter.
Can I monitor a competitor's page?
Yes. Competitor monitoring is a common pattern; set the alert policy to "record only" so a frequently-changing page does not flood your inbox, and review the diff log on your own schedule.
What is the price?
Each check costs 1 credit. A watch set to check daily costs 30 credits per month. See pricing for plan details.
Start monitoring