The problem this solves
Lifecycle emails are written once and trusted forever. The welcome series, the nurture track, the onboarding sequence: they were checked carefully the week they shipped, and they have been sending on autopilot ever since, through every website redesign, pricing change, and page migration your company has shipped since. The emails still say what they said; the pages behind their links have moved on. Nobody owns the intersection, so nobody checks it.
The decay is invisible precisely because these sends are automated. A campaign email with a broken link fails loudly the day it sends, while a nurture email with a broken link fails quietly forever, a few clicks at a time, each one a subscriber who trusted the sequence at exactly the moment it embarrassed you. Offer drift is subtler and worse: the email promises a free trial, the page now says book a demo, and the subscriber who clicked experiences your brand contradicting itself.
This mission audits the intersection on a schedule. It takes every destination link in your lifecycle flows, visits each one in a real browser, and reports three things per link: does the page work, does it load clean, and does it still say what the email says it says. Each verdict comes with a screenshot, so fixing the failures requires no further investigation.
How the mission runs
- Inventory the destinations. The mission collects every destination URL from the lifecycle emails you provide, deduplicated across flows, with a note of which email and which link position each URL serves. One page serving six emails is checked once and reported six times.
- Visit each in a real browser. Every destination is loaded fresh in the rendered browser, scripts executing, redirects followed, exactly as a subscriber's click would experience it. Read-only by construction: the browser observes and never clicks, types, or submits.
- Check health: status, errors, failures. Each visit records whether the page resolved, every console error thrown during load, and every request that failed, including the tracking parameters that were meant to attribute the click. A page can render prettily while its analytics quietly drop your attribution.
- Check the promise against the page. The page's content is read against the email copy that links to it: the offer named, the price stated, the action promised. Drift is flagged with both sides quoted, so the fix decision, update the email or the page, is made with the evidence in view.
- Deliver the evidence file. A CSV lands with one row per email-link pair: destination, health verdict, errors found, promise-match verdict, and a link to the full-page screenshot captured during the visit. Failures sort to the top.
The prompt
This is the exact objective the agent receives. Swap the obvious placeholders for your own domain, segment or channel and run it as-is from the console, Slack, or the API.
What comes back
A complete click-check of your lifecycle program: per-link health and promise-match verdicts in a CSV with failures ranked first, and a screenshot of every destination as it stood at check time. Run on a schedule, it turns link rot and offer drift from a permanent silent leak into a weekly maintenance item.
Make it yours
- Run it in mobile emulation as well, since most lifecycle clicks happen on phones and pages fail differently at phone width.
- Trigger a run automatically after every site migration or pricing change, the two events that break nurture destinations in bulk.
- Extend the check to your transactional emails, where a broken destination costs a signup or a payment rather than a click.
Frequently asked questions
How is this different from the link checker in my email tool?
Link checkers confirm a URL returns a status code. This mission loads the page in a real browser and reads it: a destination can return 200 while throwing script errors, dropping its tracking, or promising something different from the email that sent the click, and only a rendered visit catches those.
What counts as offer drift?
Any material mismatch between what the email promises and what the page delivers: a renamed offer, a changed price, a free trial that became a demo request, a discontinued lead magnet. The report quotes both sides for each flag, so judgment calls stay quick and human.
How often should this run?
Monthly suits most programs, since lifecycle flows change rarely while websites change constantly. Teams shipping frequent site changes run it after each release instead, which converts the check from an audit into a regression test for the email program.