What visitors see

This is what a customer sees when they open your published status page.

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 says so ("Everything's working normally."). When something's wrong it names what's affected.

DomainDash chooses the headline in this order:

1. Your latest published update. If there's a live incident and you've posted a public update, your own words lead the page.
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 sentence written in advance describes the current verdict.

Whichever sentence leads, it never changes the per-site colours below it. Those always come 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 whether today's problem 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.

The "last updated" badge

A badge shows when the page was last rendered, so visitors can tell the information is current.

It refreshes itself

The public page keeps itself current. Roughly every 60 seconds it swaps in the latest status in place, without a full-page reload. A customer can leave the tab open during an incident and watch it move from Down 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. Unpublishing turns it back into a draft, so its link still opens for anyone who has it. (The subscribe option still only appears while a live incident has a published public update. See Letting visitors subscribe.)

Frequently asked questions

How often does the public page update?

The page refreshes itself roughly every 60 seconds, swapping in the latest status without a full reload. A "last updated" badge shows how fresh the page is.

What does "Responding slowly" mean on a status page?

It's the visitor-facing wording for a site that needs attention: it's responding, but more slowly than it should. On a public status page this is the sanctioned label; elsewhere in DomainDash the same condition shows as "Needs attention".

What is the Insights line at the top of the page?

On plans that include Insights, the headline can be an automatically written sentence summarising how things are, marked with a small grey "Insights" label. It never overrides the per-site colours: those always come from your live checks.

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