Quick Diagnosis
Find whether noindex comes from HTML, HTTP headers, WordPress visibility, or an SEO plugin.
Problem
WordPress Page Is Noindex Unexpectedly
Diagnose accidental noindex on WordPress pages by checking SEO plugin settings, page visibility, robots meta, headers, templates, and staging protections.
Problem
An important public page sends a noindex directive or is otherwise excluded from indexing.
For: Site owners and SEO teams who found important pages excluded from search.
Workflow
What to review
Do Not Overcorrect
Some pages should remain noindex, such as search results, private reports, and account flows.
Search & DiscoverySeverity: MediumLast reviewed: 2026-09-16
Diagnosis
Symptoms, causes, checks, and fixes
Symptoms
- Search tools report noindex.
- Important pages do not appear in sitemap.
- Robots meta or X-Robots-Tag says noindex.
- A staging/privacy setting leaked to production.
Most Common Causes
- SEO plugin noindex setting.
- WordPress discourages search engines setting.
- Password/private/draft status.
- Header rule at server/CDN.
- Template-level robots meta.
How To Confirm The Cause
- Inspect rendered HTML robots meta.
- Check response headers for X-Robots-Tag.
- Review page, content type, and SEO plugin settings.
- Confirm site visibility settings.
Fixes
- Remove noindex from the correct owner.
- Publish the page if it should be public.
- Remove staging protections from production.
- Purge cache after changes.
How To Verify The Fix
- Confirm noindex is gone from HTML and headers.
- Check sitemap membership.
- Use URL inspection tools after deployment.
When To Contact Support
Escalate to SEO plugin, theme, or hosting support depending on where the directive is injected.
References
Official references
Continue