"Domain health is green but the live page is wrong"

Symptom

ops/domain_health.py (or the panel's own health screen) reports a domain as healthy, but a visitor sees an old button, a missing background video, or content that doesn't match what was just changed in the landing builder.

Cause

Domain health is a fixed checklist, not an exhaustive diff against what you edited: config reachability, published buttons matching what the database says should be published, and whether the published background video (still an unstable-CDN-versus-origin split for short windows after a rotation, see Landing-builder troubleshooting). It does not — and cannot — know what the previous content looked like, so it has no way to catch "this changed but the page didn't update."

The far more common cause is the draft/publish split itself: every landing-builder edit lands in a draft state first, and a visitor only ever sees the last published snapshot. An edit that "isn't showing up" almost always means it was never published, not that health checks missed something.

How to check

• Check /api/admin/config/dirty (or the builder's own "unpublished changes" indicator) for the domain — a dirty state means the edit is real but only in the panel's draft view.
• Landing-builder troubleshooting covers the publish step itself and its most common trap (browser/CDN caching after a genuine publish).
• If the domain is dirty-clean (published matches draft) and the live page is still wrong, that's a real health-check gap worth reporting — not an expected outcome.

What's next

The click is in our numbers but Club shows nothing — a different "looks fine here, wrong somewhere else" case, across products instead of across draft/publish.