Public uptime is social proof — and most teams hide it

Pick a SaaS landing page. Any SaaS landing page. Scroll past the hero, the feature grid, the testimonials, the pricing table, the FAQ. Look for a number that tells you whether the product is up right now.

Usually there isn't one. Sometimes there's a tiny status link in the footer, in mouse-grey, that takes you to a subdomain. Visitors do not click it. Visitors barely notice it.

Which is strange, because uptime is one of the few claims a SaaS makes that is verifiable on first contact. It is exactly the kind of signal that buyers reach for when they're deciding whether to trust a tool with their billing flow.

Trust signals are mostly performative

A landing page is full of claims. Reliable. Production-ready. Trusted by teams at scale. Customer logos. Testimonials. Stars from G2 and Capterra. All of those are real signals, but they share a property: they are stated, not shown. The visitor has to take you at your word.

A live status indicator is different. It is the difference between a chef telling you the kitchen is clean and a chef letting you see into the kitchen. The first asks for trust. The second confers it.

You buy from people who are unafraid to be checked.

Why teams hide it anyway

Three reasons, in roughly the order they actually appear:

1. The available widgets are ugly. The cheap monitoring tools render status badges that look like 2012 admin panels. Putting one in your footer feels like putting a hi-vis vest on a tuxedo.
2. The fear of red. Founders worry that a public status indicator will cost them deals on the rare day something is degraded. In practice, the opposite is true — buyers expect occasional dips and reward honesty.
3. Inertia. Nobody asked. The team is shipping features, the status page is a Q3 ticket, and the existing tool's status.acme.com subdomain is technically there, somewhere.

What a homepage status indicator actually does

You will probably never measure the conversion lift directly — the sample sizes for indie SaaS landing pages do not support it. What you will notice over time is a softer pattern: support tickets that would have started with "is your site down?" start with "I am seeing a 500 on the dashboard." Sales calls open with fewer trust questions. Visitors stop bouncing on the pricing page because they spotted the 99.97% — 90 days line just above it.

The status indicator is not the thing that closes the sale. It is one of a hundred small competence signals that decides whether the visitor stays long enough for any of the other ones to land.

How to do it without breaking your design

A few rules of thumb that have held up across the early Glimly installs:

• Put it in the footer, not the hero. The hero is for your value proposition. The footer is where competence signals land.
• Match the typography. A monospace caption that reads ALL SYSTEMS OPERATIONAL next to a thin status dot reads as deliberate. A vendor-branded chip with their colors does not.
• Show a number, not a smiley face. 99.97% — 90 days is verifiable. A green check is decorative.
• Link it to your status detail page or to the vendor. Visitors who care want to click. Do not strand them.

The Glimly Badge is built around exactly this — an SVG you can drop in a footer with one <img> tag, themed to match your site, with a discreet caption and a real percentage. The Card embed goes further when you want a /status section with per-service rows and 90-day bars.

The check

Open your landing page. Without scrolling to the footer or the docs, ask: would a stranger know whether this product is up right now?

If the answer is no, you are leaving one of the cheapest trust signals on the table. Fix it in three minutes.