What visitors see

When a customer opens your published status page, they get a clear, honest read on how your sites are doing — and one trustworthy place to look instead of emailing you. Here's what they see.

Plan availability

Status pages is available on Pro and Business. See the plan comparison.

The hero

At the top, your branding — logo, accent colour, and a soft glow — sits above a single plain-language headline summarising how things are. When everything's fine it reassures ("Everything's working normally."); when something's wrong it says so honestly and names what's affected.

The headline is chosen in a clear order of priority:

1. Your latest published update. If there's a live incident and you've posted a public update, your own words lead the page — customers hear from you, not a machine.
2. An Insights sentence. On plans that include Insights, and when there's no incident update to show, the headline can be an automatically written sentence summarising the situation, marked with a small grey Insights label.
3. A plain default. Otherwise, a clear, written-in-advance sentence describes the current verdict.

Whichever sentence leads, it never changes the per-site colours below it. Those always come straight from your live checks, so the words and the status can't disagree.

Per-site status

Below the hero, each site you've chosen appears with a status pill, shown by its display name or its domain. The public page uses three plain states:

• Healthy — the site is responding normally.
• Responding slowly — the site is up but slower than it should be. This is the one place in DomainDash where "Responding slowly" is the sanctioned label; elsewhere the same condition reads "Needs attention". It's the operator's attention the site needs, not the visitor's.
• Down — the site isn't responding.

The 90-day history

Each site shows a small sparkline of its status over the last 90 days, so visitors can see at a glance whether today's wobble is a one-off or part of a pattern. The most recent segment is today, and it stays live — if a site had a problem this morning and recovered this afternoon, today's segment keeps the worse status, so a recovery never quietly paints over an outage that already happened.

The "last updated" badge

A badge shows how fresh the page is — when it was last rendered — so visitors can trust they're looking at current information, not a stale snapshot.

It refreshes itself

The public page keeps itself current. Roughly every 60 seconds it quietly swaps in the latest status in place, without a jarring full-page reload. A customer can leave the tab open during an incident and watch it move from Down to recovering to Healthy on its own.

Drafts look different

While a page is still a draft, anyone with the link can see it, but search engines can't, it shows a preview banner, and it doesn't offer the subscribe option. Once you publish, the preview banner and search-engine block go away and the page becomes the real public view. (The subscribe option still only appears while an incident is live — see Letting visitors subscribe.)

Related

• Creating a status page to build and publish the page
• Letting visitors subscribe for the "email me when it's fixed" option
• Publishing public updates to put your own words at the top during an incident
• Insights for the plain-language summaries that can lead the hero
• Branding to make the page look like part of your site