Alert list

Every alert has a reason, and you find all of them here.

This page shows when searchVIU alerts you and how often it checks. You also see which changes deliberately trigger no email.

Request a demo To SEO alerts

Four monitors

Each of the four monitors runs at its own pace.

The alerts come from four monitors. Each one checks at its own rhythm.

Weekly11 crawl alerts
after every full crawl

Continuous45 Page Watch signals
throughout the day

15 minutes16 robots.txt events
on all hosts

Daily4 sitemap alerts
for all sitemaps

As of 6 October 2026. The list grows with the product.

How searchVIU filters

Every finding is weighted, and known issues stay quiet.

An email only goes out when something is new and has a noticeable impact. Everything else stays visible in the report.

Impact countsThe share of affected URLs and clicks determines the severity.
Only new issues trigger the emailErrors from earlier crawls are collected in the report.
Same pages, one lineIf an error hits the same pages in several checks, it appears as one bundled entry.
Second check in Page WatchEvery change is fetched a second time. Fluctuating signals only go to the log.
Alert on change of statesearchVIU reports a robots.txt state once, with at most one email per run and project.
Growth stays quietIf a sitemap or its file grows, there is no alert.

Raw findings after matching

Held back, already known from earlier crawlsReport
Minor changes with small impactin the email
Needs attentiontriggers the email

Schematic, based on a customer project. Out of many raw findings, only a few real new problems remained.

The list

All alerts at a glance

Sorted by monitor, with trigger, severity and example. Crawl alerts and Page Watch use the levels High, Medium and Low. robots.txt and XML sitemaps use the levels Critical, Warning and Info.

Crawl alerts

After every full crawl, so every week.

Alert	Trigger	Severity	Example
Pages lost (now 4xx/5xx)	A page that was reachable in the last crawl now responds with 4xx or 5xx.	Low to High	A category page with rankings has returned 404 since the last crawl.
Pages lost (redirect to an error)	A previously reachable page now redirects to a target that responds with 4xx or 5xx.	Low to High	/product-a/ has redirected to a 404 page since the deployment.
Redirect removed	A URL that used to redirect now responds with 4xx or 5xx.	Low to High	An old campaign URL with backlinks now returns 404 instead of the redirect.
Redirect to an unrelated target	A previously reachable page now redirects, and the target is clearly different in content (semantic comparison).	Low to High	After the relaunch, a product page redirects to the homepage instead of the successor product.
Canonical switches from self-reference to another URL	A page's canonical used to point to itself and now points to another URL.	Low to High	After a template update, all guide articles point to the overview page via canonical.
noindex newly set in the robots meta tag	A page's robots meta tag switches from index to noindex.	Low to High	After a release, 300 product pages carry noindex.
noindex newly set in the X-Robots-Tag header	A page's X-Robots-Tag HTTP header switches to noindex.	Low to High	A changed server configuration sets noindex in the header for an entire directory.
Newly blocked by robots.txt	A page is now blocked by the robots.txt.	Low to High	A new Disallow rule accidentally blocks all filter pages with traffic.
Page no longer linked internally	A page that used to be linked internally can no longer be reached via links in the current crawl.	Low to High	After a navigation rebuild, a subcategory can only be reached via the sitemap.
Ranking keywords missing from the title	Important search terms of the page (from GSC) are no longer in the title.	Low to High	After shortening, the main keyword is missing from a category page's title.
New SEO issues on existing pages	A check from the list of checks fires on a page that responded with 200 in both crawls and had passed the check before.	Severity of the respective check	After a template update, the H1 is missing on 40 guide pages.

Page Watch

Continuously, throughout the day, on your most important pages. Every change is confirmed by a second fetch before the alert. Page Watch reports important pages individually and others when issues accumulate. Page Watch also checks signals marked “log only”, but they trigger no email.

Signal	Trigger	Severity	Notification	Example
Server error (5xx)	A previously reachable page responds with 5xx.	Low to High	single page	After a deployment, the homepage returns 503. The second fetch confirms it.
Page responds with 4xx	A previously reachable page responds with 4xx.	Low to High	single page	–
Soft 404	The page suddenly looks like an error page but returns status 200.	Low to High	single page	–
New redirect	A page that used to respond directly now redirects.	Low to High	single page	–
Redirect to another host	The page now redirects to another domain or subdomain.	Low to High	single page	–
Redirect loop	The page is stuck in a redirect loop.	Low to High	when it accumulates	–
JavaScript redirect	The page newly redirects via JavaScript.	Low to High	when it accumulates	–
Meta refresh redirect	The page newly redirects via meta refresh.	Low to High	when it accumulates	–
Switch from HTTPS to HTTP	The page is suddenly delivered unencrypted.	Low to High	single page	–
Password field on an HTTP page	A password field appears on an unencrypted page.	Low to High	single page	–
noindex newly set	The page suddenly carries noindex.	Low to High	single page	A top category page suddenly carries noindex. The second fetch confirms it. The email usually arrives a few minutes after Page Watch detects the change.
noindex set by JavaScript	JavaScript sets noindex after rendering.	Low to High	single page	–
Blocked by robots.txt	The page is now blocked in the robots.txt.	Low to High	single page	–
Canonical to another host	The canonical suddenly points to another domain.	Low to High	single page	–
Canonical changed	The canonical suddenly points to another path.	Low to High	single page	–
Canonical missing	The canonical has disappeared.	Low to High	when it accumulates	–
Multiple canonicals	The page suddenly delivers several canonical tags.	Low to High	when it accumulates	–
Canonical changed by JavaScript	JavaScript changes the canonical after rendering.	Low to High	when it accumulates	–
hreflang removed	The hreflang annotations have disappeared.	Low to High	when it accumulates	–
hreflang self-reference missing	The self-reference in the hreflang set is missing.	Low to High	when it accumulates	–
nofollow newly set	The page newly carries nofollow.	–	log only	–
Title missing	The title has disappeared.	Low to High	single page	–
Multiple titles	The page suddenly delivers several title elements.	Low to High	single page	–
Top search term gone from the title	One of the page's most important search terms (from GSC) is no longer in the title.	Low to High	single page	After a CMS update, the main search term is missing from the title of a top category page.
Title changed	The title has changed.	–	log only	–
Title changed by JavaScript	JavaScript changes the title after rendering.	–	log only	–
Main content collapsed	The text of the page shrinks sharply.	Low to High	single page	After a release, the product description of a top page is empty and only the navigation remains.
Error text in the content	An error text appears in the content.	Low to High	when it accumulates	–
Extraction returns nothing	A project-specific extraction (e.g. price, availability) no longer finds anything.	Low to High	single page	–
H1 missing	The H1 has disappeared.	Low to High	when it accumulates	–
Meta description missing	The meta description has disappeared.	–	log only	–
Structured data removed	The structured data has disappeared.	Low to High	when it accumulates	–
Structured data invalid	The structured data (JSON-LD) can no longer be read.	Low to High	when it accumulates	–
Internal links collapsed	The number of internal links drops sharply.	Low to High	when it accumulates	–
Viewport missing	The viewport meta tag has disappeared.	–	log only	–
html lang missing	The lang attribute has disappeared.	–	log only	–
Certificate/TLS error	A certificate or TLS error occurs during the fetch.	Low to High	single page	–
Mixed content	The HTTPS page newly loads resources over HTTP.	Low to High	when it accumulates	–
New external script host	The page loads scripts from a host that did not appear before.	Low to High	single page	A script from an unknown domain suddenly loads on the checkout entry page.
Suspicious links	Suspicious links appear on the page.	Low to High	when it accumulates	–
Main CSS/JS broken	The main stylesheet or script no longer loads.	Low to High	when it accumulates	–
Response time spike	The response time jumps.	Low to High	when it accumulates	–
HTML size spike	The HTML suddenly gets much larger.	–	log only	–
Rise in console errors	The number of console errors jumps.	–	log only	–
Analytics tag missing	The analytics tracking has disappeared from the page.	Low to High	when it accumulates	–

robots.txt

Every 15 minutes, on all hosts of your crawl profiles. A state is reported once, when it changes.

Event	Trigger	Severity	Example
Website fully blocked	“User-agent: * / Disallow: /” is new in the robots.txt, so all bots without their own group are locked out.	Critical	After a deployment, the staging environment's robots.txt is live.
Bot newly blocked	A known bot is now blocked, with affected URLs and GSC clicks.	Critical for search bots and AI search bots, Warning for AI training bots, Info for fetches on user request	A new rule for all bots also blocks OAI-SearchBot. The page may then be missing from ChatGPT search.
Bot allowed again	A previously blocked bot is allowed again.	Info	After a fix, an AI search bot may access the site again.
robots.txt not reachable	The robots.txt cannot be fetched (network error), reported on a confirmed change of state.	Critical, Warning for derived www or apex variants	If the robots.txt is not reachable, Google initially stops crawling.
robots.txt returns a server error	The robots.txt responds with 5xx or 429.	Critical, Warning for derived variants	If the error lasts more than 12 hours, Google uses the last cached version, for up to 30 days.
robots.txt reachable again	After an outage, the robots.txt can be fetched again, with the outage duration.	Warning, with the outage duration for context	The outage lasted about 2 hours.
robots.txt status code changed	The HTTP status of the robots.txt changes, e.g. from 200 to 404.	Critical if existing rules are dropped, otherwise Warning	The robots.txt returns 404, so previous blocks (e.g. for session URLs) no longer apply.
HTML instead of robots.txt	An HTML page is delivered at /robots.txt, or /robots.txt redirects to one.	Warning if rules applied before, otherwise Info	After a relaunch, the robots.txt redirects to the homepage.
robots.txt content changed	Directives were added or removed, with a line-by-line diff.	Warning, Info for comment-only changes	2 lines added, 1 removed.
robots.txt too large	The file exceeds Google's limit of 500 KiB, and the rest is ignored.	Warning	–
Sitemap reference removed	A sitemap directive has disappeared from the robots.txt.	Warning	–
Sitemap reference added	A new sitemap directive is in the robots.txt.	Info	–
Content signal changed	The content signals for search, AI answers or AI training change.	Warning	–
HTTP and HTTPS variants differ	The HTTP and HTTPS variants deliver different robots.txt files.	Info	–
Ineffective directive	A newly added directive has no effect.	Info	–
Host new in monitoring	A host is checked for the first time.	Info	–

XML sitemaps

Daily, for all sitemaps of your domain. searchVIU deliberately does not report growth or file size.

Alert	Trigger	Severity	Example
Sitemap status change	A sitemap changes its HTTP status or can no longer be fetched.	Critical or Warning	The product sitemap has returned 404 since last night.
Drop in URLs	The number of URLs in a sitemap drops significantly.	Critical or Warning	Overnight, a sitemap contains 40 % fewer URLs.
Loss of coverage	The share of entries with lastmod, hreflang, images, videos or news drops significantly.	Warning	lastmod is suddenly missing from a third of the entries.
Sitemap back	A sitemap can be fetched again or reappears (distinguished from a new sitemap).	Info, report only	–

As of 6 October 2026. We do not publish the thresholds for the levels.

The alert arrives where your team works.

All alerts go out by email. On top come Slack, Teams and webhooks for your own systems.

EmailSlackMicrosoft TeamsWebhook

To the list of checks

Demo

Let's talk about your website.

In the demo, Michael shows you how searchVIU works. We use your website and a demo project.

Request in three short steps
Quick alignment on crawler access, NDA and Search Console
Demo with your website and the demo project
Start planned and supported together

Website
Needs
Contact

Which website is it about?

Website

Business email