SEO guard · part of Edge SEO
An update wrecks your SEO?
You hear about it within minutes.
An accidental noindex, missing titles, or a page with Google traffic that suddenly returns 404. The edge sees it on the next visit, emails you and your team, and you fix it with one click at the edge. While your developer solves the cause.
It happens to the best teams
A new plugin, a theme update or a deploy on a Friday afternoon. Suddenly your category pages have noindex, or your product titles are empty. Google picks that up within a few days, and you only notice when revenue is already dropping. An SEO tool notices on its next crawl. A CDN doesn't look at SEO at all.
- The edge watches alongEvery page the edge serves, it compares with what it saw before. No extra crawler, and no load on your server.
- An email within minutesTo you and your team, with the number of Google clicks at stake for each page. So you know right away what comes first.
- One-click fixBack in Google, the old title restored or the canonical corrected. At the edge, so it takes effect immediately, even while your developer is still working.
- Suddenly noindexFix: back in Google
/categorie/hardloopschoenen/1,240 clicks - Title missingFix: old title restored
/product/trail-pro-2/310 clicks - Page with Google traffic returns 404Redirect
/sale/zomer/95 clicks
One click, and it's right again.
While your developer looks for the cause, the edge puts the correct value back. Your site itself doesn't change. Once the error is fixed, you remove the rule.
<meta name="robots" content="noindex">
<title></title>
<link rel="canonical" href="/categorie/hardloopschoenen/">Google removes the page from the results. 1,240 clicks per month at stake.
<meta name="robots" content="index, follow">
<title>Hardloopschoenen kopen | Gratis retour</title>
<link rel="canonical" href="/categorie/hardloopschoenen/">Back in Google, with the old title. Your whole team got the alert.
example
Six things an update can break
- Unwanted noindexA page that was allowed in Google and now has noindex, set on the page itself or through the X-Robots-Tag.
- Missing titlesIf there was a title and it's now empty, you'll know. The old title is ready to put back.
- Wrong canonicalsIf a page suddenly points to another page as the real version, it often disappears from Google.
- 404 on pages with trafficWith Search Console connected: pages that got clicks from Google and no longer exist.
- Whole team informedThe alert goes to the owner and all team members, including your developer or agency.
- No noiseChanges you make to the edge yourself don't count. If it was intended, choose Looks right. If it resolves by itself, the alert closes.
Honest
There are tools that crawl your site regularly and report changes. The difference: the watchdog looks at every page that is actually served, weighs it against your own Google clicks and fixes it right away at the edge. It doesn't replace a good test before a deploy, but it catches what slips through anyway.
Frequently asked questions
Do I need to install anything?
No. The monitor is part of Edge SEO and works as soon as your site runs through the edge. For the 404 alerts with clicks, you connect Search Console.
How fast is "within minutes"?
As soon as a visitor or search engine requests the page and the edge checks it again, the alert is ready. We bundle the email for a few minutes, so you get one email instead of dozens.
What exactly does "restore" do?
The edge sets the correct value again at the edge: index instead of noindex, the old title or a canonical to the page itself. Your site itself does not change. If your developer has fixed the error, you can remove the rule.
Won't I get a flood of alerts?
No. We report it once per page, and anything you changed at the edge yourself does not count. Pages with the most clicks are at the top.
Everything works together
See it on your own site
Put your site behind the edge for free and watch what it does. Your DNS, your hosting and your visitors won't notice a thing.