What we shipped
We built change detection between crawls. When a crawl loads, it now compares the site against the previous completed crawl and writes one dated, append-only record per page and change kind, inside the same load run.
Why it is important
Crawls previously captured a snapshot; they now also capture what changed since the last completed crawl, recorded automatically as part of the run. Our team reviews the recorded changes before any action is taken.
How it benefits the client
More accurate and faster work: changes to a client's site are recorded per page and per kind of change, so our team can spot them without manually comparing crawls.
What is next in the pipeline
Updating developer tickets and client status updates automatically whenever a crawl runs and finds that we fixed something from the previous week
How it fits our agentic journey as an agency
Dated, structured records of site changes written inside automated runs give our tools and future agents dependable data to work from, with our people reviewing what the automation records.