Operations and monitoring

Why it matters

A working installation can regress when a hostname, origin, redirect, middleware deployment, route template, or cache policy changes. Monitoring makes those failures visible before they become long-lived.

What you will learn

• How cache hits, misses, stale fallback, and quotas affect crawler responses.
• How to read render logs, timing, status codes, and response headers.
• How to monitor root/www routing and metadata used by social preview bots.

Learning path

• What uptime monitoring misses ↗

  Start with page health, content integrity, metadata, and crawler-readable output.

• Detect JavaScript soft 404s ↗

  Monitor valid and invalid canaries for error, homepage, and wrong-route content.

• Content freshness monitoring ↗

  Compare expected content across origin, rendered, and crawler-facing responses.

• Monitor every deployment ↗

  Run release-triggered checks for JavaScript SEO and crawler-response regressions.

• Website monitoring for agencies ↗

  Organize client sites, page contracts, alert ownership, evidence, and reporting.

• Post-installation monitoring ↗

  Build a repeatable verification schedule after setup.

• Cache freshness ↗

  Understand page updates, refreshes, and render usage.

• Logs and cache headers ↗

  Interpret URL, user agent, cache, timing, status, and timestamp fields.

• Root vs www mismatch ↗

  Diagnose DNS, redirect, canonical, and crawler-path differences.

• Social preview bots ↗

  Check Open Graph, card metadata, images, redirects, and external caches.

• HTTP checks, browser checks and saved workspace evidence ↗

  Choose the right website evidence by comparing a dated HTTP response, a browser observation and saved workspace records, with clear limits for each method.

• Separate technical monitoring incidents from content work ↗

  Route website findings to incident response, editorial work or evidence gathering by checking the failed behavior, customer impact and next responsible owner.

• Why request totals and render allowance do not match ↗

  Reconcile crawler activity with fresh-render usage by aligning event definitions, site scope and billing periods before treating different totals as an error.