Content drift
The link still returns 200. The product is gone.
A dead link is the easy case. 4xx, 5xx, timeout, DNS failure. Every checker on earth finds it, including RotSweep, on every plan.
Three failure modes, only one of them obvious
RotSweep evaluates three questions, in order, on every sweep. The first two ship on Daily Sweep. The third is content drift: Deep Sweep, Full Sweep, Enterprise, or the €6 add-on. The full detection story is here.
Destination drift: the 301 that looks fine
A site reorganises and 301s your deep link to a category page, a regional homepage, or a marketing landing page. Follow the first hop and you see a 301. Follow it to the end and you see 200. Compare that final URL to the one you accepted as baseline and you have destination drift. RotSweep does this on every plan, not just the expensive one.
Content drift: the 200 that lied
Same URL. Same 200. The thing you linked to is gone. A product delisted and replaced with a cousin SKU. A documented endpoint rewritten. A cited figure quietly removed from a government table. A deal page that still loads and no longer carries the offer.
We fingerprint the meaningful part of the page — not the nav, not the ads, not the cookie banner — and flag when that fingerprint moves against the last baseline you accepted. How the fingerprint is built.
What we do not alert on
A price change is not an incident on its own; we record it and we do not alert on it. A blip is not an incident either: we re-check after about ten minutes before flagging. When a site legitimately moved, one click accepts the new destination and fingerprint as truth so the digest stays quiet.
If your current tool only asks “is it 200?”, it is answering a different question. RotSweep answers “is it still the page you meant?” That is the whole difference versus a broken-link checker, and versus a page you named in Visualping.