The Friday nobody got indexed anymore
You hear the story in every other agency: it is Friday afternoon, one last deploy before the weekend, and a forgotten Disallow: / from the staging config slips into the production robots.txt. Nobody notices: the site loads, tests are green, Slack is quiet. By Tuesday the SEO lead spots a visibility drop. By then Google has already started removing pages from the index.
The <meta name="robots" content="noindex"> variant is just as invisible in the browser, and just as effective. Same story for a stray X-Robots-Tag header from a CDN rule, or a canonical that suddenly points at the staging domain after a CMS update.
That is exactly what SEO Guard is now shipping in live24h to catch.
What SEO Guard watches
Four signals on every configured URL, continuously rather than only on demand:
robots.txtfor the configured user-agent<meta name="robots">including the full directive setX-Robots-TagHTTP header<link rel="canonical">
Every run produces a verdict (ok, warning, critical, fetch_failed, blocked_by_waf, rate_limited) and a diff against the baseline you marked as good. When something changes, you see the old and new value side by side.
Overview tab of an SEO check: verdict pill on the left, JS-rendered badge next to it, one glance tells you whether the page is indexable.
Deployment Watch: hourly instead of daily, with auto-off
Most SEO regressions happen in the 24 hours right after a release. That is why every check has a Deployment Watch toggle: once flipped on, the check runs hourly instead of daily for 24 hours and then turns itself off. You do not have to remember to reset anything.
Deployment Watch: hourly checks for 24 hours, with a countdown until automatic deactivation.
JS rendering on Business and up: see what Google actually sees
If you ship an SPA, you know the trap: the raw HTML is an empty <div id="app">, and the real content only arrives after JavaScript hydration. SEO Guard can optionally execute JavaScript and evaluate the rendered DOM, so you see exactly what Googlebot sees after rendering.
JS rendering costs more compute, so it lives on the Business plan and above and is capped by a clearly visible monthly quota. The quota widget in the wizard shows at any moment how many renderings you have left.
Wizard step 5: enable JS rendering, the quota widget shows how many renderings the current plan has left.
A companion to your SEO suite, not a replacement
SEO Guard is not trying to replace an SEO suite. Those products give you depth: backlink profiles, keyword rankings, competitor comparisons, on-page scoring. live24h does something different: 24/7 early warning for the few business-critical signals that can break between your weekly or monthly audit runs. The two tools complement each other: the audit report tells you what to improve structurally, SEO Guard tells you when your current setup is breaking right now.
Availability by plan
| Plan | SEO URLs | JS rendering |
|---|---|---|
| Free | — | — |
| Pro (9.90 EUR/month) | 5 URLs | — |
| Business (34.90 EUR/month) | 25 URLs | included (quota) |
| Agency (79 EUR/month) | 100 URLs | included (quota) |
| Enterprise | custom | custom |
Every plan ships with Deployment Watch, the full signal set, and our public bot identity for WAF allow-listing.
Get started
The full feature walkthrough with every wizard step, the history view, and alert-mail samples lives at /en/seo-monitoring/, and you can add your first SEO check straight from the dashboard: pick a URL, choose your signals, set a baseline, done.