How to Set Up a Free Status Page for Your Website or API

Step by step

1. Monitor the services you want to show

   Add each public URL in Site Monitor with "Notify me when the site goes down" ticked — for example your homepage, app, and API health endpoint.

2. Open Status pages and click New status page

   Give the page a title (such as "Acme Systems Status"), choose a slug — that becomes its URL — and optionally add a short description.

3. Choose which sites to show

   Select the monitors that should appear. Each one shows its current status on the page.

4. Share the link

   Your status page is live at sitemonitor.dev/status/<your-slug>. Link to it from your app's footer, help centre, or error pages.

5. Embed it on your own site (optional)

   Open your public status page and use "Copy embed code" to get a short HTML snippet. Paste it into any page on your site to show live status there.

You choose which alerts each URL sends — downtime, content changes, slow responses — and we email you when they happen.

What you'll need

• A free Site Monitor account
• At least one monitored URL
• A name and slug for the page

Why have a status page at all?

When something breaks, users check whether it's just them. Without a status page they open support tickets, post on social media, or simply leave. A status page answers the question immediately and shows that you know about the problem.

It also helps when nothing is wrong: a user who sees every service working knows to look at their own connection or settings instead.

What to put on it

Show the things your users actually depend on, named the way they think about them: "Website", "Dashboard", "API", "Checkout". Leave out internal services they've never heard of.

A short description at the top — what the page covers and how to contact you — saves questions later. Keep the title simple and recognisable, such as "Acme Status", so users who land on it from a search know they're in the right place.

Plans and limits

The Free plan includes a public status page along with 10 monitored URLs. Paid plans allow more status pages, faster checks, and response-time alerts.

Where to link your status page from

Put the link wherever users go when something seems wrong: your help centre or docs, the footer of your website and app, your support email auto-reply, and your error pages. Many teams also mention it in onboarding emails so customers know it exists before they need it.

If you'd rather keep visitors on your own domain, embed the status widget on a page such as yoursite.com/status. The embed code includes a small credit link and shows the same live status as the public page.

Keeping it accurate

A status page is only useful if it reflects reality. Because Site Monitor's status page is driven by the same checks that send your downtime alerts, it updates on its own — there's no manual "all systems operational" switch to forget.

Monitor the URLs that best represent what users experience. A health endpoint that returns 200 while the sign-in page is broken will give a misleadingly green status, so include at least one real user-facing page alongside any API checks, and use the "Response body must contain" option to confirm key text is present.

Communicating during an outage

The status page shows users that something is wrong; your words tell them what you're doing about it. When an outage starts, acknowledge it quickly in the channels your users already watch — social media, a banner in your app, or a reply on your support inbox — and link to the status page so people can follow along without asking.

Keep updates short and factual: what's affected, what isn't, and when you'll post next. When it's resolved, say so, and if the cause is something users should know about, explain it briefly. Being open about problems is what makes a status page build trust rather than just report failures.

Frequently asked questions

Related

• Features: Status pages
• Features: Uptime monitoring
• Guides: Check if a website is down
• Use cases: Agencies