Campaign Launch Monitoring
Don't Let Broken Pages Waste Your Ad Spend
You are spending real money to send people to your landing pages. A missing script, a redirect loop, or a page that quietly breaks mid-campaign means every click after that is wasted. Sitewatch checks your landing pages daily and on demand -- verifying every linked script, stylesheet, and image returns a valid response, catching redirect issues before they trap ad traffic, and alerting you the moment something goes wrong.
- Verify every JS, CSS, and image file on your landing pages loads correctly
- Detect redirect loops and host drift that send visitors to the wrong place
- SHA-256 page fingerprinting catches unexpected content changes mid-campaign
Landing page broken
Detected in daily check
Campaign LP affected
Recent activity
- /summer-sale — hero image 404 Not Found6:01 AM
- /summer-sale — main.js MIME mismatch (text/plain)6:01 AM
- /summer-sale — analytics.js script tag present, URL returns 2006:01 AM
- /summer-sale — page returns 200, HTML fingerprint unchanged6:01 AM
Why it matters
Every broken asset is a broken conversion
Broken assets kill conversions
A missing JS bundle breaks your signup form. A 404 CSS file leaves the page unstyled. Sitewatch sends HEAD requests to every script, stylesheet, and image linked in your landing page HTML, verifying each returns 200 with the correct MIME type.
Redirect issues waste clicks
Redirect loops trap visitors in a dead end. Host drift sends them to a domain you don't control. Sitewatch detects REDIRECT_LOOP and HOST_DRIFT issues so your ad budget goes where it should.
Page availability checks
A 5xx error on your landing page means every ad click is money lost. Sitewatch catches UNAVAILABLE pages and NON_HTML_PAGE responses so you know when something is fundamentally wrong, not when your client calls.
Script tag presence verification
Sitewatch parses your page HTML to extract every linked asset and verifies that analytics script tags are present and their source URLs return 200. This confirms scripts are correctly referenced, though it cannot verify runtime execution.
SHA-256 page fingerprinting
Sitewatch fingerprints the full page HTML using SHA-256. If the page content changes unexpectedly -- a CMS edit, a CDN purge, an accidental overwrite -- you will know before your next campaign report.
2-of-3 retry confirmation
Sitewatch confirms every issue with a 2-of-3 retry pattern before alerting. Transient glitches never wake anyone up. Only verified problems reach your Slack or inbox.
6
Issue types detected
2-of-3
Retry confirmation
5–30 min
Check intervals
Landing page checks
What Sitewatch catches on your campaign pages
Asset health
- ASSET_MISSING -- JavaScript, CSS, or image files returning 404 or other error codes
- ASSET_MIME_MISMATCH -- assets served with the wrong Content-Type header (e.g. JS served as text/plain)
- Script tag presence -- analytics scripts found in HTML with source URL returning 200
- UNAVAILABLE -- assets returning 5xx or failing at the network level
Page-level issues
- UNAVAILABLE -- landing page returning 5xx errors or completely unreachable
- REDIRECT_LOOP -- redirect chains that trap visitors in a loop
- HOST_DRIFT -- page redirecting to an unexpected domain
- NON_HTML_PAGE -- URL returning non-HTML content (e.g. JSON or a download)
- HTML fingerprint change -- unexpected content alteration detected via SHA-256 hash comparison
Simple setup
Four steps to protected landing pages
Add your campaign URLs
Enter your landing page URLs. Sitewatch fetches each page via HTTP, parses the HTML to extract every linked script, stylesheet, and image.
Daily checks run automatically
Every day at 6 AM UTC, Sitewatch re-fetches each page, sends HEAD requests to every linked asset, and compares the page's SHA-256 fingerprint against the baseline.
Issues confirmed with retries
When a problem is found, Sitewatch runs a 2-of-3 retry confirmation. Only verified issues become incidents. A 30-minute cooldown prevents repeat alerts for the same problem.
Alerts with evidence
Confirmed issues trigger alerts across your configured channels with the exact asset URL, HTTP status code, and issue type. Hit "Run Check Now" any time for an on-demand check before a launch.
Check your landing pages before the first click
Free plan. No credit card. Add your campaign URLs and run a check in under two minutes.
Why Sitewatch
Manual QA vs Sitewatch for campaign pages
| Feature | Manual QA | Sitewatch |
|---|---|---|
| Broken asset detection | Click through the page and hope you notice | Every linked JS, CSS, and image HEAD-requested automatically |
| Redirect issues | Test a few URLs by hand | REDIRECT_LOOP and HOST_DRIFT detected on every check |
| Page availability | Open the page once before launch | Daily checks plus on-demand catch outages mid-campaign |
| Script tag presence | View source and eyeball it | HTML parsed, script tags found, source URLs verified |
| Content changes | No visibility after launch | SHA-256 fingerprinting flags unexpected changes |
| Alert delivery | Someone has to remember to check | 6 channels with failure details |
Broken asset detection
Redirect issues
Page availability
Script tag presence
Content changes
Alert delivery
FAQ
Frequently asked questions
No. Sitewatch fetches your page HTML and checks that analytics script tags are present and that their source URLs return a 200 status. This confirms the scripts are correctly referenced in your page. Since Sitewatch does not execute JavaScript, it cannot verify that a pixel fires or sends events at runtime. For execution-level verification, use a browser-based tool like Google Tag Assistant alongside Sitewatch.
Check intervals are configurable -- from every 30 minutes on Free to every 5 minutes on Pro. On-demand checks are available from the dashboard and via deploy hooks, perfect for a final validation before launching a campaign or after making changes to a live page.
When an issue is detected, Sitewatch runs a 2-of-3 retry confirmation to rule out transient glitches. Confirmed issues become incidents with alerts sent across your configured channels, including the exact asset URL, HTTP status code, and issue type (e.g. ASSET_MISSING, REDIRECT_LOOP). A 30-minute cooldown prevents repeat alerts for the same problem.
Yes. Add your staging or preview URLs and run a check to validate all assets, redirects, and page availability before switching to production. This catches broken images or missing scripts before the first ad dollar is spent.
No. Sitewatch focuses on asset health, page availability, and redirect correctness. It does not measure load times, TTFB, or Core Web Vitals. For performance monitoring, pair it with a dedicated tool like Google PageSpeed Insights or a real-user monitoring solution.
Yes. You can add landing pages for multiple clients. Since alert settings are configured at the workspace level, agencies often use separate workspaces per client to keep alerts and monitoring data isolated. See our For Agencies page for more on multi-client workflows.
Explore more