You can have the best status page in the world — clear components, fast updates, uptime history, AI-drafted incident comms — and none of it matters if your customers don't know it exists.

The most common reason customers email "is it down?" during an outage isn't that you didn't post an update. It's that they never thought to look for a status page, or couldn't find it when they did.

Discoverability isn't about marketing. It's about making sure that when something breaks, the path from "something's wrong" to "oh, they know about it" is as short as possible.

Start With the URL

Your status page URL should be predictable and memorable. When a customer is staring at error screens, they're going to guess before they search.

The standard: status.yourcompany.com

This is the convention. Customers who've used any SaaS product before will try this instinctively. If your company is Acme, they'll type status.acme.com into their browser before they do anything else.

A subdomain is better than a path (yourcompany.com/status) for two reasons:

It works when your main site is down. If your app and marketing site share infrastructure and that infrastructure is having issues, status.yourcompany.com can be hosted separately and stay up. A path on your main domain goes down with everything else.
It's easier to remember and share. "Check status dot acme dot com" is something a support agent can say in a chat. "Check acme dot com slash status" is clunkier and less intuitive.

If you can't use a custom domain, a branded subdomain like acme.pagecalm.com still works — it's predictable enough that you can share it and customers will remember it.

Link It From Your App

The most important link to your status page is inside your product. That's where customers are when they notice something is broken.

Places to add the link:

App footer. Every page of your product should have a "Status" link in the footer. It's unobtrusive when things are working and discoverable when they're not.
Help or support menu. If your app has a "?" icon or help dropdown, add "System Status" as an option. This is where customers go when something seems wrong.
Error pages. Your 500 and 503 error pages should link directly to your status page. This is the highest-intent moment — the customer just hit an error and wants to know if it's you or them.
Login page. If login is down, your app is inaccessible. The login page is the only touchpoint you have. Add a small "System Status" link.

The error page link is the most impactful and the most commonly missed. When your product throws a 500, the default error page usually says something like "Something went wrong." Adding a single line — "Check our status page at status.yourcompany.com for updates" — redirects frustrated customers to a place where they can get answers instead of writing support tickets.

Link It From Your Website

Your marketing site should also link to the status page, but in fewer places:

Footer. Standard practice. Every SaaS website footer includes Privacy, Terms, Docs — add Status to that row.
Documentation. If you have a docs site, include a "System Status" link in the navigation or sidebar.

You don't need a prominent link in your main navigation or hero section. The status page is a utility — it should be findable, not featured.

Tell Customers It Exists

Linking isn't enough. You need to tell customers about the status page at least once, so they know to look for it in the future.

When to mention it:

Onboarding emails. Include a line in your welcome email: "If you ever want to check whether our service is running normally, visit [status page link]." One sentence, early in the relationship.
During incidents. If you communicate outages via email or in-app banners, always include the status page link: "Follow live updates at status.yourcompany.com." This trains customers to check the status page first next time.
In your support replies. When a customer emails about an active incident, your reply should include: "You can follow live updates and subscribe to notifications at [link]." Every support interaction is a chance to redirect future tickets.

The goal is simple: the next time something breaks, at least some of your customers think "let me check the status page" before they think "let me email support."

Enable Subscriptions

A discoverable status page is good. A status page that pushes updates to subscribers is better.

The subscribe form on your status page is the most underrated feature for reducing support load. Customers who subscribe get notified when incidents are created, updated, and resolved. They never have to check the page again — the information comes to them.

But subscriptions only work if customers know they exist. The subscribe form should be:

Visible without scrolling on the status page itself
Mentioned in incident emails — "Subscribe at [link] to get notified of future incidents"
Mentioned in your onboarding — "Subscribe to our status page to get notified if anything goes down"

Every subscriber is one fewer person who emails support during the next outage.

The Checklist

Here's the full list. You don't need all of these on day one, but aim for the first five:

The first three take ten minutes and cover the highest-intent moments. Everything else is incremental.

How to Know It's Working

Track one metric: how many support tickets mention "is it down?" during your next outage. If the answer is zero, your status page is discoverable. If the answer is "all of them," your customers didn't know where to look.

A good status page that nobody can find is just a dashboard for your own team. A good status page that customers check first is a trust machine that works 24/7.

PageCalm helps small teams run status pages with AI-powered incident updates that sound human and ship fast. Try it free — no credit card required.

How to Make Your Status Page Discoverable