Use cases

Six workflows for relaunches, releases and traffic drops

Here you will find six typical situations, explained step by step. Each one shows which data searchVIU provides and when you need it.

Six use cases

Whether you are rebuilding or running day to day, there is a workflow for it

Some occasions have a fixed date, such as the go-live of a relaunch. Others come up mid-week, when a release goes live or clicks suddenly drop.

Before and after a change-over

Securing a relaunchsearchVIU compares every URL of the live website with its target on the dev site and supports you through go-live.
See the relaunch process
Shop migrationProducts, categories and images get their new target, with suggestions by similarity and an export for the server.
See shop migration
International websitessearchVIU checks hreflang and robots.txt for every country version, across many hosts too.
See international websites

In day-to-day operation

Monitoring releasesPage Watch checks your most important pages continuously and reports when a deployment changes noindex or the canonical, for example.
See monitoring releases
Investigating a traffic dropsearchVIU lays clicks, rankings and changes to the website on top of each other. That helps you narrow down the cause faster.
See traffic drop
Managing AI botsThe bot matrix shows which AI bots your robots.txt blocks and how many Google clicks these blocked URLs get.
See managing AI bots
One project

One monitoring setup behind all six situations

All use cases work with the same data in one project. After a relaunch, monitoring simply continues in the same project, with no new setup.

weeklyfull crawl with over 100 checks
continuousPage Watch on your most important pages, spread across the day
15 minrobots.txt check interval
dailyXML sitemap check
More about SEO monitoring
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?