This is the fundamental first step with any Little Warden client check, adding the default checks with the root domain.
If the client has an SSL certificate, ensure that it is added with the https:// prefix rather than the http://.
Subdomains can be hosted on different servers, have different content management systems and different certificates, we highly recommend adding every subdomain (even internal ones) to Little Warden to ensure they display the correct response.
Adding some of the more valuable pages (valued either by traffic or conversion rate) can help to diagnose if anything has gone wrong. Our change logging of items like title tag and meta robots can give you a warning if things change.
Does the client own the .co.uk, .org, .us, .net version of the domain name? Even if they are not valid or just redirect to the main domain, they should be added and checked for both redirect status and domain expiration.
Whilst these domains may have robots.txt deny all or only be accessible on a VPN, a small mistake in a config can undo this and make them accessible to the the world, you can use Little Warden to ensure that these environments cause no issues.
Most agencies are setup so that a team member has responsibility for a certain amount of clients, Little Warden allows you to specify which team member gets alerts and notifications about which clients.
Has your client had any previous brand names (or acquired any companies)? Add the domains (and other related domains) to ensure that the redirects work and the domain name and certificates are up to date.
Some clients will redirect US traffic to another website or with the latest GDPR changes, they will redirect EU traffic to an explanation page, these can all be monitored with our geo redirect checking from up to 8 different countries.
When working with other teams, sometimes wires can get crossed and things can get changed without signoff or notification, using content checking you can ensure that doesn’t change without a heads up.