Publishing
How publishing works
The editor is your working draft. The public status page only changes when you publish.
What actually goes live
Publishing takes the safe public fields from your project and stores them as the live public snapshot.
Changing branding, layout, maintenance, annotations, support links, or monitor selection in the editor does not change the public page until publish runs again.
The public page uses published configurations, not the current unsaved editor draft.
Publishing keeps the secret monitoring API key out of the client-facing payload.
Typical flow
1
Edit the project in the editor until the preview looks correct.
2
Click Publish.
3
Statuscode writes a fresh public snapshot for the live site.
4
Refresh the public URL to confirm the change landed.
Why a live page may look stale
This is usually one of only a few things.
You changed the draft but did not publish again.
You published the project, but you are still looking at an older custom-domain setup that has not finished connecting.
The monitor provider returned older or missing data, so the page structure changed but the service state did not.
Mental model
Editor
Your working draft and setup state.
Publish
Copies the safe public parts into the live snapshot.
Public page
Always renders the latest published snapshot, not random draft changes.
Was this helpful?
Quick feedback helps improve the docs.