Add your first monitor
Open Monitors and add a monitor. Enter a name and a public HTTP or HTTPS URL, and give it a client label so related sites stay together. A client label groups websites; it does not create a separate client account. Launch access supports up to 25 websites per workspace.
Choose the monitor type that fits the service. HTTP(S) monitors can set the request method, headers, body, expected status codes and a keyword that must appear in the response, and they report when the TLS certificate is close to expiry. TCP monitors check that a port accepts connections, DNS monitors check a record, and push monitors wait for a ping from your cron job or backup script.
Check intervals and retries
Each monitor has its own check interval, from every 5 minutes, and its own retry count. Retries let a brief network blip pass before an incident opens. Response time is measured from Sitequiet’s servers, so it reflects the server response and not a visitor’s full page load.
Set up an HTML form presence check
Add a page path such as /contact and a CSS selector such as form#contact. Sitequiet looks for the selector in the HTML the page returns.
The check does not execute JavaScript, submit an enquiry, or verify email or CRM delivery. A form that only appears after JavaScript runs may be reported as missing.
Incidents and alerts
When a monitor keeps failing after its retries, Sitequiet opens an incident. A passing check closes it again. Add channels in Notifications to receive downtime and recovery messages by email, Slack, Discord, Telegram, Microsoft Teams or a generic webhook.
Public status pages
Create a status page for a client in Status pages. The page is public at /status/your-slug, so share the link with your client instead of sending updates by hand.
Website analytics
Open Analytics, choose a website and copy the tracker snippet from its page into that site’s HTML. Sitequiet then records page views, visitors, referrers, browsers, operating systems, devices, countries, UTM campaign parameters and any custom events you send. Tell visitors about analytics in the client site’s own privacy notice.
Performance audits
Performance audits run through Google PageSpeed Insights and return Lighthouse scores for performance, accessibility, best practices and SEO. Treat them as lab measurements of a single page load.
Prepare a branded client report
Set your agency name, accent color and report footer in workspace settings. Open Reports, choose a website, and print the report or save it as a PDF. Demo reports use illustrative data.
Report email sends a branded HTML summary through Resend once a verified sender is configured for the deployment.
Teams and the API
Invite teammates from Team and give each one a role. The audit log records changes made in the workspace. Create a key in API keys to use the REST API from your own scripts, and keep the key secret.
Open workspace