Back to changelogConsoleKit / Changelog / Monitoring
Monitoring
Page history that explains itself
Changes makes the difference between two crawls easier to read, verify, and act on.
A page history should answer more than whether something changed. It should show what moved, where it moved, and whether the observation is trustworthy enough to act on.
What changed
Readable change evidence
Heading, metadata, link, schema, and technical observations now use subtype-specific language instead of asking you to decode raw payloads.
Transport stays distinct
Redirects, errors, status changes, and response timing are shown separately from content changes so one does not imply the other.
History keeps its context
The exact page versions behind an observation remain available, making it easier to move from a summary to a confident comparison.
Keep goingSee all releases