The WordPress reading setting can ask search engines not to index a development site. It is an indexing signal, not access control, so protect confidential staging content with an appropriate authentication mechanism as well.
IN THIS ARTICLE
01 Choose the intended visibility
For a private development copy, decide who should be able to open the site and how search engines should treat it. A noindex instruction does not stop a person with the URL from visiting, and it does not guarantee an immediate removal of a page that was already indexed.
Keep staging and production settings separate in your launch checklist. A copied database can carry development visibility settings into the public site if they are not reviewed.
02 Set and verify the preference
- Open Settings > Reading as an administrator.
- Review the Search engine visibility option and enable the discourage-indexing setting for the intended development site.
- Save the setting and inspect the public response or page source to confirm the expected indexing directive is present.
- Check any SEO plugin, server header or custom robots configuration that may add its own rules.
03 Prepare for launch
Before opening the production site to search engines, remove development-only access restrictions as intended and clear the discourage-indexing option. Then verify representative pages, including the homepage, a post and an important landing page.
Review the sitemap and canonical URLs so they point to the production domain. A correct checkbox does not repair a separate noindex rule in an SEO plugin or a staging URL embedded in canonical metadata.
Does discouraging search engines make the site private?
Search engines need to encounter the relevant instructions to act on them. Blocking a crawler from fetching a page can prevent it from seeing a page-level noindex directive, so avoid combining rules without understanding their effect.
If a live site is missing from search, check its actual directives before assuming the hosting service is at fault. If sensitive content was public, remove access and follow an appropriate removal process; waiting for indexing preferences alone is not a complete privacy response. Record the exact affected URLs and the time the setting changed when requesting assistance.