Status page embed trust on a marketing site
A status page can build trust before a buyer talks to you. But you do not need a noisy footer widget or a fake “all systems operational” badge on every page.
For most small SaaS teams, a clear “System status” link in docs, onboarding, and support flows is enough.
Quick answer
StillOnline hosts public status pages at stillonline.tech/s/{id} and supports subscriber limits such as 50 Free, 100 Pro, and 500 Ultimate per status page on pricing. Use a simple System status link from your docs, help center, security questionnaire, or support macros; do not promise a native iframe or custom domain if you have not shipped it. For accessibility, link text should describe the destination, matching WCAG link purpose guidance and Google’s helpful content guidance.
Where the link belongs
Put the status link where someone has operational intent. A homepage footer is optional; support and docs are stronger.
| Placement | Good fit | Why |
|---|---|---|
| Help center | Yes | Users arrive during issues |
| API docs | Yes | Developers need status context |
| Security questionnaire | Yes | B2B buyers ask |
| Marketing footer | Maybe | Low intent, easy to ignore |
Badge-style copy
If you want a trust block on the marketing site, use copy plus a link:
“System status: see current availability and incident updates.”
That is honest and durable. It does not require a live widget, iframe, custom domain, or client-side polling on your marketing page.
When to show the link
Show it in onboarding emails, support macros, API docs, and incident replies. During an outage, link directly to the current incident post instead of sending customers to a generic landing page.
For subscribers, explain that public page subscribers receive incident update emails, while owner alerts are separate. See status page subscribers vs owner alerts.
Related guides
- Public status page guide
- Status page findability support docs
- Status page security questionnaire
- Status page subscribers vs owner alerts
FAQ
Does StillOnline provide a native status page iframe embed?
Do not assume that. Use a normal link to the public status page unless your product setup includes a shipped embed. A clear link is usually better for trust and accessibility.
Should I put a StillOnline status link in my footer?
You can, but docs and support flows are more useful. People look for status when something feels broken or when a buyer is checking reliability.
Can StillOnline use a custom domain for the status page?
Do not promise custom domains. StillOnline hosts the public URL at stillonline.tech/s/{id}; link to that page in your operational materials.
What copy should I use for a status page trust block?
Use plain copy like “System status: see current availability and incident updates.” Link it to your public StillOnline status page.