Site Hush

Product version V1

Get started with website monitoring

Sign in with Google, create an account and check your first web address. Get started with Site Hush and choose when Slack receives notifications.

Updated

Add a public web address, run a check and read the result. Then connect Slack if you want notifications about confirmed incidents and recovery.

Sign in and create an account

  1. Open sign-in and choose Continue with Google.
  2. Select the Google identity you intend to use. If you have an invitation, your email address must match it.
  3. Enter an account name and time zone when the app shows Create your account. The time zone controls displayed times, not your language.
  4. Check the account selector before adding data.

Language is a personal preference. You can switch between English and Swedish without creating a new account.

If the app shows Access by invitation, it is running a limited pilot. Ask an account owner for an invitation and sign in with the invited email address. Signing in does not automatically let you create a separate account. You can continue using accounts you already have access to.

Add your first monitor

  1. Open Monitors and choose Add URL.
  2. Enter a name and a full public HTTP or HTTPS address. https://example.com/ is an example, not your own website.
  3. Choose an interval: 5 minutes is the default and shortest interval. Other options are 10, 15, 30 and 60 minutes.
  4. Review whether monitoring starts immediately and whether this monitor may send notifications.
  5. Choose Create and check now for an initial result. Test URL checks the address without saving a new monitor.

Private network addresses and unsafe destinations are rejected. Start with an important public page you are authorised to monitor.

Verify that it works

Read the latest check time, status code and observed error on the detail page. A successful HTTP check is a result at one moment, not a guarantee for every user journey.

Monitoring delayed describes the check chain, not a website outage. Read how incidents are verified before treating a failure as confirmed downtime.

If sign-in cannot be verified

Return to a clean sign-in page and start a new Google flow in one tab. Do not reuse an old callback or multiple simultaneous sign-in tabs. For repeated failures, share the error category with your operator, never cookie values.

Next step

Connect Slack and verify your test channel, or invite your team. Automatic sitemap sync and domain monitoring are upcoming features, not enabled in V1.