What happens when a landing page drifts

An approved landing page is re-checked. The first pass stores a baseline. Later crawls compare against that baseline. If the page drifts, the product can mark review or pause linked campaigns.

This is destination monitoring, not a full browser audit. The crawler is lightweight. JavaScript is not a default blocker. Screenshots, when they exist, are optional evidence. They are not the decision.

What the first check rejects

Reject by default: URL shorteners, generic forwarding links, cloaking links, affiliate redirect chains, generic tracking redirect domains, and cross-host redirects unless the account has an explicit exception.

Allow by default: at most one same-host canonicalization, such as http to https, apex to www, or a trailing-slash fix that keeps the same offer.

The submitted click URL must point at the page being checked. Expected content is part of the submission. A missing restricted-category signal parks in requires_review. It does not silently pass.

What the later check compares

The monitor re-crawls the submitted URL and compares visible text hash, DOM hash, title, final URL, and redirect chain to the approved baseline.

Severity:

• informational: ordinary text or DOM change, same host, still matching the expected summary.
• review: material content mismatch, a failed crawl after a prior pass, or an uncertain safety signal.
• pause: forwarding appeared, the host changed, Safe Browsing flagged a threat, or the page looks like a bait-and-switch.

review or pause pauses linked local campaigns and line items. Material change also enqueues url.changed webhook rows for subscribers. Subscribe to webhooks if an agent is watching the account.

What this playbook is not

It is not a Playwright farm. It is not screenshot-diff QA. It is not a promise that every JavaScript offer mutation will be caught. Approve a landing page an agent submitted is the human review page when a check parks.