What it does
The page updater bot runs in the background, queuing research passes for pages you specify. When it detects material changes in the sources, it opens a pull request with the updates. No live monitoring required.
Our own CMS freshness bot, the one that keeps our migration comparison pages current, runs this way.
How it works
The bot watches a set of pinned sources per page, fetches them on a schedule, and compares what it finds against the current content. It works primary sources first: the vendor's pricing page and changelog before review platforms, and community chatter last. When it detects a material difference, it opens a pull request with the exact before-and-after diff, each change carrying a quote and the source URL it came from. Nothing goes live automatically. The agent handles the research pass; a person reads the diff and makes the call on whether to merge.
Two rules keep the changes honest. Every edit must cite a source the bot actually fetched that run, or the edit is dropped. And it can correct a stale fact inside a criticism, but it is blocked from deleting the criticism itself, so a price update can never quietly soften a judgement.
What you get
The agent queues the research, drafts the changes in the background, and opens the pull request when changes are found. Your team reviews a sourced diff instead of monitoring sources manually. Our own version runs two scheduled passes: a weekly sweep verifying volatile claims across every comparison page, and a deeper rotation giving the stalest page a full research pass.
How we set it up
We build it in-house as part of our agentic workflows service. The setup covers identifying which pages and sources to watch, writing the comparison logic that matters for your content type, and configuring the review flow so changes land in a place your team already looks. Retainer clients get it running alongside the broader automation work.