Find Every Source
A noindex audit needs both HTML and response headers. Looking only at the page source can miss X-Robots-Tag headers added by a plugin, host, CDN, or middleware.
Problem
Audit WordPress noindex directives across meta robots, X-Robots-Tag headers, SEO plugin settings, templates, archives, staging controls, and sitemap conflicts.
Problem, cause, fix, verify
Problem
Important WordPress pages can be excluded from search when noindex directives remain in templates, SEO plugin settings, response headers, or staging safeguards.
Audience
WordPress administrators, agencies, SEO teams, and developers investigating pages excluded from search.
First check
A noindex audit needs both HTML and response headers. Looking only at the page source can miss X-Robots-Tag headers added by a plugin, host, CDN, or middleware.
Verify
WPlura Site Discovery Checker can help organize crawl and indexability evidence, while Diagnostics can keep the site-owner review tied to real WordPress settings and templates.
Editorial trust
On this page
Symptom
For: WordPress administrators, agencies, SEO teams, and developers investigating pages excluded from search.
Diagnosis
A noindex audit needs both HTML and response headers. Looking only at the page source can miss X-Robots-Tag headers added by a plugin, host, CDN, or middleware.
Robots.txt controls crawling, not reliable deindexing. If a URL is blocked from crawling, crawlers may not be able to see a noindex directive on the page itself.
An indexable sitemap should not list pages that declare noindex. That conflict wastes crawl attention and makes search reporting harder to interpret.
Not every noindex is a bug. Internal search results, thin archives, duplicate filters, staging pages, and unreviewed generated content often should remain accessible but excluded from search.
WPlura Site Discovery Checker can help organize crawl and indexability evidence, while Diagnostics can keep the site-owner review tied to real WordPress settings and templates.
Diagnosis
Escalate when noindex is set by production CDN headers, managed host rules, SEO plugin automation, staging controls, or a deliberate legal/privacy decision.
References