Do I need to install anything or change my code?

No. Guard monitors your pages from the outside — you add the URLs that matter and verify ownership. There's no SDK, snippet, or code change required, so it works with any stack or framework.

How is this different from uptime monitoring?

Uptime tools only check that your server responds. Guard renders each page like a real browser and inspects the actual output — so it catches blank renders, missing content, broken CTAs, and killed SEO signals that still return a 200 OK.

How often does Guard scan my pages?

Guard scans each monitored page roughly every 30 minutes. Every scan re-renders the page, runs the full test suite, captures screenshots plus HTML and AI-readable Markdown, and compares the result against the previous scan.

Does it monitor whole domains or individual pages?

Individual pages. You choose exactly which URLs matter — homepage, pricing, signup, checkout, key landing pages — and Guard watches each one independently so a problem on one page is never hidden by a healthy one.

What do I get beyond the automated tests?

Lighthouse scoring over time, static file monitoring (robots.txt, sitemap.xml, llms.txt, favicons), weekly AI report cards, Google Search Console data, and index coverage — all tied to the same pages Guard already monitors.

Can I try it before paying?

Yes. Start a free 10-day trial with no credit card required, or run a free page audit first to see exactly what Guard checks on one of your live pages.

Product walkthrough

Inside DataJelly Guard

A guided tour of the Guard dashboard — how you configure pages, watch scans run, read results, manage alerts, and prove your site actually works.

Start free trial Browse the walkthrough

Scans every ~30 min30 automated testsLighthouse trackedStatic files watched

Step 1 — Config

Tell Guard which pages matter

Start by picking the URLs that drive your traffic, revenue, and signups. Guard scans each page independently so a regression on /pricing never gets hidden by a healthy /blog.

Add the pages that actually move your business — homepage, pricing, signup, checkout, key landing pages
Set scan cadence (every ~30 minutes) and choose which tests run per page
Configure alert thresholds and who gets notified
Everything is page-level, not domain-level

Add monitored pages, set scan cadence, and confirm domain ownership

Step 2 — Guard Queue

Watch scans run in real time

The Queue is your live view of what Guard is doing right now — pages waiting, pages running, pages finished. No mystery, no waiting blind.

Live status for every queued and in-flight scan
See which pages are next and how long each one took
Quickly trigger an on-demand scan after a deploy
Spot stuck or slow pages before they snowball

Live activity timeline with one swimlane per domain

Step 3 — Guard Pages

Per-page health at a glance

The Pages view rolls every page up to one health score. You see what is green, what is degrading, and what is on fire — sorted by impact, not alphabet.

Status, last scan, and current score per page
Trend sparkline so you can see drift before it becomes an incident
Click into any page for full history and evidence
Filter to only the pages with active issues

Scan activity timeline and pass / warn / fail counts per page

Step 4 — Latest Test Results

Every test, every page, every scan

Latest Test Results shows the most recent run for every page with a pass/fail breakdown per test. This is the granular truth layer when you need to answer "what exactly changed?"

Full pass / warn / fail grid for every test in the latest scan
Inspect the rendered HTML, screenshot, and AI markdown captured on each run
Compare against the previous scan to see what flipped
Drill into any failing test for evidence and fix guidance

Overall status donut, letter-grade page health, and scan activity

Step 5 — Active Alerts

Current incidents, ranked by severity

When a test crosses its threshold, Guard opens an alert. Active Alerts is your incident inbox — grouped, deduplicated, and ranked so you fix the bleeding first.

Severity badges (critical, major, warn) with occurrence counts
Evidence attached: screenshot, HTML diff, lighthouse delta
Group-by-test or group-by-page to see patterns
One click to open the full alert with timeline and history

1 / 2 views

Incident inbox: KPIs, 30-day activity, and top affected pages

Step 6 — Resolved Alerts

Your wins, with receipts

Resolved Alerts is the proof that Guard is working. Every fix is logged with a timestamp, a time-to-resolve, and the change that closed it out.

Simple view: recent wins, avg / median time to fix, top-fixed test types
Detailed view: full filterable table with grouping by issue title
Issue timeline chart from the full dataset, not just one page
Click any resolved item for the original alert and fix details

Resolutions over time, fixed-by-severity, and most-fixed check types

Step 7 — Test Definitions

Know exactly what Guard is checking

Test Definitions is the reference catalog of every check Guard runs — what it detects, why it matters, severity, and how to fix it when it trips.

Full library of render, content, SEO, and dependency tests
Severity, category, and human-readable SEO impact for each test
How-to-fix guidance written for engineers, not auditors
Search and filter to find the exact check you care about

Browse the full Test Catalog

Expand any test for common cause, how to fix, and SEO impact

Monitoring — Lighthouse Scores

Performance and SEO trends over time

Guard runs Lighthouse on every scan so you see the trend, not just one snapshot. When Performance drops from 92 to 58 after a deploy, you find out from us first.

Performance, SEO, Accessibility, and Best Practices tracked per page
Historical chart with deploy-aligned change markers
Alert when a score drops below your threshold
Drill into the raw Lighthouse report for any run

Average scores across all pages plus a per-run score heatmap

Monitoring — Static File Monitor

robots.txt, sitemap.xml, and the files Google relies on

Static File Monitor watches the files that quietly break SEO when they go missing or change shape — robots.txt, sitemap.xml, key assets, and more.

Status, last-modified, and size tracked for every watched file
Diff view when contents change unexpectedly
Catch 404s on sitemap.xml or accidental Disallow: / in robots.txt
Alerts the moment a critical file changes or disappears

By-file-type breakdown and a per-domain target table with HTTP status

Monitoring — Index Coverage

Know which pages Google actually indexed

Index Coverage closes the loop between "we shipped it" and "Google can find it." Guard pulls live coverage data for every URL so you can see what is indexed, what is excluded, and what is silently being dropped from search — before traffic does.

Per-URL index status pulled directly from Google — indexed, crawled-not-indexed, discovered-not-indexed, excluded
Catch noindex tags, canonical conflicts, and soft 404s the moment they appear
Spot whole sections of the site that never made it into the index
Prioritized fix list so you work on the pages that actually drive traffic first

1 / 3 views

Discovered vs indexed KPIs and the coverage timeline across crawls

Reporting — Weekly Report Cards

A weekly report card for every page

Every week Guard grades each of your important pages like a teacher — uptime, performance, SEO health, content integrity, and third-party reliability rolled into a clear letter grade. Share it with your team, your client, or your boss without writing a single summary.

Letter grade per page with the underlying metrics that drove it
Week-over-week deltas so improvements (and regressions) are obvious
Highlights the wins, lowlights the failures, and points to the exact tests behind each
Built for sharing — clean enough for a stakeholder, deep enough for an engineer