Monitor
Webflow monitor for the Fastly edge cache serving a 404 the day after publish, and the CMS-template change that silently broke the form post.
A Webflow site rarely goes hard-down. It goes wrong-the-day-after-publish because a designer-built CMS page started serving from the Fastly edge cache a stale 404 from the previous build. SiteGuardian watches the URLs a visitor types, on a minute cadence, before the next designer push tips a CMS page above threshold.
- Watches your Webflow home, CMS pages, and /form-success endpoints as separate URLs.
- Tight slow threshold on /contact and /form-success. 1.5 seconds is sane for most Webflow sites.
- Probes every minute on Pro. Fast enough to catch a designer publish that quietly cached a 404 at the Fastly edge.
- SSL expiry alerts on every plan. A certificate problem on a Webflow custom domain is a silent breakage.
- No Webflow code embed, no Webflow Logic hookup, no Fastly purge call.
How it works
Setup, in three beats.
Step 01
Add the URLs a visitor types first
Paste your Webflow home, your published CMS templates (one each), and your /form-success URL. Set a tight slow threshold on /contact (1.5 seconds is sane) and a slightly looser one on the home page. SiteGuardian starts probing inside the next minute, no Webflow codebase required.
Step 02
Let the minute cadence catch the designer-publish day
Webflow designers push routinely, sometimes daily. Most are fine; the ones that aren’t trip a 404 on a published CMS template after the Fastly edge cache picks up the prior build. SiteGuardian’s minute cadence catches the publish-broken CMS page within 60 seconds, not the morning’s form submissions report.
Step 03
Catch the form-submit silence before the /form-success endpoint stops answering
A /form-success endpoint that stops answering is the worst kind of Webflow failure — visitors submit forms, the inbox goes quiet, and the lead-list shows it the next morning. SiteGuardian catches the same minute it happens, with one short email naming the URL, the next probe ETA, and the prior-day baseline.
What the alert actually says
One email. One URL. One timestamp.
Your URL https://yourstudio.webflow.io/post/launch-announcement returned a 404 at 14:32 UTC, immediately after a CMS template publish. The probe will retry in 60 seconds.Frequently asked
The webflow monitor questions, answered flat.
Frequently asked
Related reading
Keep exploring.
Try it
Start monitoring my site.
Starter is $19 a month — one site, ten URLs, every-five-minute checks. Pro is $39 a month — three sites, fifty URLs, every-minute checks. Lifetime is $299 paid once and stays yours with every future update included.
Stay updated
Want us to email you when we ship a feature for this use case?