SEO monitoring that stops an update from hiding you from Google.
Relvato checks the settings that decide whether Google will index you at all — a stray noindex on the meta tag or X-Robots-Tag header, a robots.txt that blocks the whole site, a missing canonical — and fails loudly on the ones that drop you from search. It also flags a new search-engine ownership token — the sign of someone taking over your Search Console.
- ✓No site-wide noindex (meta tag or X-Robots-Tag header)
- ✓robots.txt doesn’t Disallow the whole site
- ✓A canonical URL is present
- ✓No new Google or Bing ownership verification you didn’t add
- ✓Re-checked on every change to the site
A single toggle — a staging noindex pushed live, a plugin that rewrites robots.txt — can quietly deindex your whole site, and you won’t see it until traffic craters weeks later. Relvato re-checks these on every change, so a self-inflicted SEO wound surfaces in minutes.
On WordPress, the most common accidental noindex is the “Discourage search engines” setting. When that's the cause, Relvato suggests re-enabling indexing, and you apply it with one click in WordPress → Relvato — undoable there too.
Why most search drops you can fix are self-inflicted — and why Bing matters more now that AI assistants draw on its index. Read our guide to SEO regression monitoring.
- Loads the homepage in a real browser and reads the meta robots tag and the X-Robots-Tag header.
- Fetches robots.txt and checks it doesn’t Disallow the whole site, and that a canonical link is present.
- A site-wide noindex or a Disallow: / is a hard fail — the exact settings that make Google drop you.
- Watches who can prove they own the site to Google, Bing, Yandex and Baidu: the verification meta tags on the homepage, TXT records on the domain, BingSiteAuth.xml and — with the WordPress plugin — the verification files at the site root. The tokens already there on the first run are taken as yours; one that appears later fails the monitor.
Do I need a plugin?
No — SEO integrity monitoring works on any site with a verified domain. On WordPress, the Relvato plugin (1.25.0 or later) also lets it see the verification files at the site root, which only the server can list.
What’s the most common cause?
A staging ‘noindex’ setting pushed to production, or a plugin/theme update that rewrites robots.txt.
Why watch Search Console verification tokens?
After a break-in, attackers often verify themselves as an owner in Google Search Console or Bing Webmaster Tools by adding their own token — a meta tag, a DNS record or an HTML file. From there they can submit spam sitemaps, ask Google to remove your real pages and read your search data. A token you didn’t add is the tell: Relvato flags it and says where to remove the owner. If it’s yours (a new SEO agency, say), ignore it once and it isn’t flagged again.
Put this monitor on autopilot.
Free forever on one site — 100 runs a month, started by you or weekly, no card. Pro re-runs your monitors by itself after every update.