Site availability and launch checks

Documentation / Site administration and domains

Whole-site visibility and individual page availability are separate controls. A public page inside a private website does not make that website public. A verified domain does not change either setting. Plan launch as an explicit administrative decision after reviewing the content and visitor experience.

Check visibility

Open Settings > General > Settings and review Site Visibility, whose choices include Private (default) and Public. Use an account authorized for the change. The agent API separately restricts whole-site visibility changes to a current super administrator with write scope.

Private production websites use an access gate. A private-preview link and its resulting browser cookie can let you see a site that an ordinary visitor cannot. Keep such links confidential and test launch in a fresh session without that access.

Review the launch surface

Verify the active domain mode, hosting attachment, DNS, and HTTPS for the intended hostnames.
Open the homepage and important nested routes. Check main navigation and language switching.
Review page-level public, draft, private, and disabled states. Confirm that unfinished content is not exposed.
Test forms, media, external links, and mobile layouts.
Check privacy and terms links, consent limitations, and the accuracy of legal disclosures.
Review SEO metadata, sharing images, and indexing choices separately from access controls.

Confirm the public result

After the approved visibility change, open the primary address as an ordinary visitor. Check a translated page and a direct page link, not only the homepage. Record any failed route before making further changes.

If the site still appears private, recheck the selected website and the saved value. If only one page fails, investigate that page's availability and route rather than toggling the entire site repeatedly. See legal and privacy, search visibility, and troubleshooting.