Migration
WordPress
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.
When this usually happens
Common triggers
- after pushing staging to production
- after a host migration
- after switching SEO plugins
- after using a staging or maintenance plugin
- after moving cache/CDN rules from staging
Common causes
Where the failure path often sits
- WordPress Reading setting discourages search engines
- SEO plugin noindex rules remain enabled
- X-Robots-Tag headers return noindex
- robots.txt is misunderstood as an indexing control
- staging plugin leftovers still block crawlers
- cache or CDN serves old noindex HTML
What I check first
The first checks stay close to the symptom
WordPress Reading visibility setting
SEO plugin indexability settings
rendered robots meta tag
HTTP X-Robots-Tag headers
robots.txt behavior
cache/CDN freshness after launch
First sprint scope
What the first sprint includes
- find every live noindex or blocking signal
- fix safe WordPress, plugin, header, cache, or robots conflicts
- verify selected URLs in GSC and rendered HTML
- hand off what remains outside the launch cleanup
Verification
How the fix is checked
GSC URL Inspection
rendered HTML robots checks
HTTP header checks
robots.txt review
selected URL recrawl checks
What I need from you
Useful intake details
- current URL
- launch date
- affected URLs
- what changed recently
- WordPress admin, GSC, hosting, or CDN access if implementation is needed
What is not included
Scope boundary
- full migration project
- content rewrite
- backlinks
- ranking recovery guarantee
- all historical URL cleanup
Price anchor
Small diagnostics usually start around $350. Focused WordPress technical sprints usually land between $650 and $1,500+.
See pricing bandsRelated WordPress problems
First sprint intake
Send the URL, the exact symptom, and what changed recently.
A useful first message includes the WordPress URL, affected pages, recent changes, plugin stack, and which tools you can grant access to.