Monitoring SEO changes When a release goes live, searchVIU checks what it has changed.

Page Watch checks your most important pages continuously, spread across the day. If a deployment changes noindex or the canonical, the alert usually arrives a few minutes after Page Watch has detected the change.

Request a demo
Over 40 signalsper page in Page WatchSecond fetchbefore every Page Watch alertFull crawlevery week, every URL
Page Watchbeispiel-shop.de · after the release
/no change
Ok
/zelte/no change
Ok
/zelte/2-personen/noindex since the release · checked twice
High
/zelte/4-personen/noindex since the release · checked twice
High
/wanderschuhe/damen/no change
Ok
Typical errors

A deployment changes more than planned

Releases bring new features. Along the way, they often change SEO signals that nobody thought of during testing.

TemplatesA new template sets the canonical differently or loses the structured data.
Filters and URLsChanged filter logic creates new URLs or sends old ones to error pages.
Scripts and metadataA script changes the title via JavaScript, or metadata gets lost during content updates.
Page Watch

As soon as the release is live, Page Watch is already checking

Depending on the project, Page Watch checks from 1,000 of your most important pages, spread across the day and with over 40 signals. If several pages suddenly show noindex after a release, this stands out long before a crawl would be finished. Before every alert, searchVIU fetches the page a second time.

More about SEO Change Monitoring
/zelte/2-personen/Page Watch · checked twice
<title>2-Personen-Zelte | Beispiel-Shop</title>
- <link rel="canonical" href="https://beispiel-shop.de/zelte/2-personen/">+ <link rel="canonical" href="https://beispiel-shop.de/zelte/">
Status code unchangedTitle unchangedRelease from Tuesday
After the release

Four checks run, each at its own interval

Page Watch covers your most important pages. Further checks run at their own pace for files and all other URLs.

Page Watch

most important pages, over 40 signals, including new external script hosts

continuously, spread across the day
robots.txt

every change per line and user agent

every 15 minutes
XML sitemaps

status, number of URLs, protocol limits

every day
Full crawl

every URL rendered and compared with the last crawl

every week
More about robots.txt monitoring
SEO Alerts

searchVIU reports the changes that have an impact

The full crawl compares every URL with the previous crawl. Each finding is weighted by the share of affected URLs and clicks. Errors that are already known do not trigger a new email.

  • Email, Slack, Teamsor via webhook into your systems
  • Severityper alert, based on impact
To the alert list
Alertsbeispiel-shop.de · crawl week 41
Canonical change on 312 product pagesFull crawl · 4% of clicks affected
High
New redirect chainsFull crawl · 0.8% of URLs
Medium
Minor changes18 URLs, held back without an email
Low
Before the release

Staging Monitoring is currently in its pilot phase

With Staging Monitoring, searchVIU also crawls your staging environment and reports SEO errors before the release goes live. The module is in its pilot phase and open to the first teams.

More about Staging Monitoring
One week later

After the release, all is quiet and you can prove it

  • Most important pages without findingsPage Watch, continuous
  • robots.txt unchangedchecked every 15 minutes
  • No new findings in the crawlcompared with the previous week
Week 42 · all quiet

Frequently asked questions about releases

How quickly does an alert arrive after a release?
That depends on the check. Page Watch spreads its fetches across the day. Every page is checked once a day, your most important pages three times. If Page Watch detects a change and the second fetch confirms it, the email usually arrives a few minutes later. searchVIU checks the robots.txt every 15 minutes and the sitemaps every day. Everything else shows up in the full crawl, which runs every week.
We test before every release. Why do we need searchVIU?
Tests check individual pages and flows before the go-live. searchVIU then checks the live website, with Page Watch on your most important pages and the full crawl on all URLs.
Will the team get emails with every deployment?
searchVIU reports what affects many URLs or many clicks. It holds back minor changes, and known errors do not trigger a new email. Every alert has a severity. View all alerts
Where do the alerts arrive?
By email, in Slack or in Teams. Via a webhook they also reach your own systems, for example the development team's ticket system.
Can the developers see what has changed?
Yes. Every Page Watch alert shows the page before and after. In addition, searchVIU stores a history with screenshots and HTML changes for every URL, for six months by default.
Which other situations does searchVIU cover?
For example relaunches, shop migrations and traffic drops. All use cases
Demo

Let's talk about your website.

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

  1. Request in three short steps
  2. Quick alignment on crawler access, NDA and Search Console
  3. Demo with your website and the demo project
  4. Start planned and supported together
  1. Website
  2. Needs
  3. Contact

Which website is it about?