> ## Documentation Index
> Fetch the complete documentation index at: https://docs.use.observer/llms.txt
> Use this file to discover all available pages before exploring further.

# Status page renders blank

> Diagnose a public status page that returns 200 but shows no content blocks.

A status page that resolves to the right host but renders no
content is almost always one of three problems: the page exists
but has no blocks added, the metrics on the page have not yet
reported, or the page's access mode is gating the visitor.

## Step 1: confirm the page exists

In the console, open **Status pages** and verify the subdomain matches
the URL the visitor reaches. Subdomains are unique across Observer;
a typo on save produces a different URL than expected.

Some names are reserved (for example `admin`, `api`, `www`, `blog`);
the form rejects them.

## Step 2: confirm content blocks are present

Open the page in the builder. A page with the title and theme set
but no metrics added renders an empty body. In the **Metrics**
section, add at least one metric; in the **Layout** section, make
sure a section that shows it (for example **Individual metrics**) is
visible; then save.

A common variation: blocks were added but never saved. The
builder's draft state is local until **Save** commits it.

## Step 3: confirm the metrics are reporting

If the page has metric blocks but the visitor sees no values, open
each metric in the console and check the **Latest** column. If
the metric has not received a value, the agent has not yet
reported. Walk
[Metric shows no data](https://docs.use.observer/docs/troubleshooting/metric-shows-no-data.md).

## Step 4: confirm access mode

Under the page's **Access** tab, the access mode determines who
can see the page:

| Mode | Who sees content |
| - | - |
| Public | Anyone with the URL. |
| Password | Visitors with the page's shared password. |
| Google / Microsoft sign-in | Visitors who sign in with an allowed email or domain. See [Sign-in protected pages](https://docs.use.observer/docs/guides/sign-in-protected-pages.md). |
| IP allowlist | Visitors from configured IP ranges. |
| JWT (Bearer token) | Visitors with a valid JWT. |
| Customer-scoped (JWT + grant) | Visitors with a valid JWT for a customer that has access to this page. |

A page rendering blank for the operator while logged into the
console, but rendering content in an incognito window, often
points at a logged-in/logged-out cookie state. Open the page in a
new private window to check.

## Step 5: check the browser console

A specific failure mode: a page with strict custom CSS that
hides body content. Open the browser developer tools, network
tab, and confirm the document body returns 200 with markup.
Check the console tab for hydration errors. If custom CSS is the
cause, edit the page's **Custom CSS** section and remove the offending rules.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.