MigrationWordPress
Migration failure path
WordPress staging noindex left live
A staging noindex problem is usually a signal mismatch, not a content problem. The fix starts by checking every layer that can tell crawlers to stay away: WordPress settings, SEO plugin output, HTTP headers, robots files, and staging leftovers.
TRIGGERS / WHEN
When this usually appears
- after pushing staging to production
- after a host migration
- after switching SEO plugins
- after using a staging or maintenance plugin
- after moving cache or CDN rules
ROOT PATHS / WHY
Where the failure often sits
- WordPress Reading setting discourages search engines
- SEO plugin noindex rules remain enabled
- X-Robots-Tag returns noindex
- robots.txt is misunderstood as indexing control
- staging plugin leftovers
- cache or CDN serves old noindex HTML
FIRST PASS
Checks closest to the symptom
WordPress Reading visibility
SEO plugin indexability settings
rendered robots meta
HTTP X-Robots-Tag
robots.txt behavior
cache and CDN freshness
SPRINT OUTPUT
Fix or implementation-ready path
- find every live noindex or blocking signal
- fix safe WordPress, plugin, header, cache, or robots conflicts
- verify selected URLs
- hand off remaining launch cleanup
VERIFICATION
The change needs a second measurement
- GSC URL Inspection
- rendered robots checks
- HTTP headers
- robots.txt review
- selected recrawl checks
USEFUL INPUT
What helps reproduce it
- current URL
- launch date
- affected URLs
- what changed recently
- WordPress, GSC, hosting, or CDN access
SCOPE BOUNDARY
What this path does not promise
- full migration project
- content rewrite
- backlinks
- ranking recovery guarantee
- all historical URL cleanup
RELATED FAILURE PATHS
Continue only when the symptom crosses a layer
START / Migration
Have the URL and one exact symptom?
The remaining technical context can stay collapsed unless it helps reproduce the failure.