Quick answer
The Discourage search engines option asks crawlers not to index a site; it does not password-protect it. Staging needs actual access control when its content or data must remain private.
Before you start
Confirm whether you are reviewing production or staging. Record the site URL, Reading settings, SEO plugin, robots directives, and any host/CDN access rule. Avoid changing both environments from one shared configuration.
Steps
- On the intended WordPress site, open Settings, Reading and inspect the search-engine visibility choice. Production visibility should follow the owner's launch decision; staging should remain protected.
- Check the rendered page for robots meta and response-header directives, and inspect robots.txt. A plugin or server header can still add noindex even after the WordPress checkbox changes.
- Review whether public pages are accessible without a login and whether the sitemap lists the intended public URLs. Keep account, checkout, and private content out of indexable discovery where appropriate.
- After launch approval, verify the actual HTTPS pages and use the authorized search-console inspection workflow. Keep a dated record of the visibility changes.
Verify the result
The browser and crawler-facing signals should agree with the approved environment policy. Indexing and search-result updates are controlled by search engines and may not happen immediately.
Troubleshooting and recovery
If production remains excluded, inspect plugin and server directives before repeatedly toggling the checkbox. Never remove staging authentication merely to make a search inspection pass.
Related help
- Find and validate the sitemap used by your WordPress website
- Technical SEO reviews: scope and checks
- Protect a staging website with access control before adding real data
Official references
Reviewed October 31, 2026. Interfaces, vendor availability, and account features can change. Check your current account before making changes.
