Keeping a staging site private with access control
A staging site containing private or unfinished material needs actual access control. Search exclusions can communicate indexing preferences but do not make a publicly reachable preview confidential.
Inventory preview access
List the staging hostname, deployment aliases and any preview routes that may be reachable directly. Test anonymously and record whether the intended authorization boundary is enforced. Do not include passwords or private page contents in the report. Check whether public navigation or metadata points to a preview URL.
Close the exposure and retest
Apply the appropriate access control for the environment, then test the direct preview address again without an authenticated session. Remove unintended public links to the preview. Keep staging restrictions separate from production rules so the public site does not inherit a private environment’s settings. Provider exclusion observations are a secondary check, not the security boundary.
Source guidance
Use the website analyzer to collect a starting set of observations, then verify the specific evidence described above.Frequently Asked Questions
Is noindex enough for confidential staging content?
No. Use authorization or another appropriate access-control mechanism. A search directive does not prevent someone from requesting an accessible URL.