Skip to main content
VaultDevLabs
Evidence guide

WordPress page noindex checker

How to check whether an important WordPress page is marked noindex and what to review before changing SEO settings.

Use Search Visibility ScannerRequest Site Rescue Review
Evidence before edits
No automatic changes
Clear next action
Decision map

01 · Observed signal

An important page is not appearing in Google even though it loads normally in a browser.

02 · Evidence to inspect

Check the page source and HTTP headers for robots noindex directives.

03 · Safe next move

Run the relevant diagnostic tool first so you have evidence before changing live site settings.

Start here

Understand the problem before changing the system.

A WordPress page can be live for users but still tell search engines not to index it. That can happen through SEO plugin settings, theme templates, HTTP headers, staging leftovers, or page-specific rules. The first job is to confirm the signal before changing broad site settings.

Signals

What the issue can look like.

  • 01An important page is not appearing in Google even though it loads normally in a browser.
  • 02Search Console reports Excluded by noindex tag or a similar indexing exclusion.
  • 03The page source or HTTP headers include a robots noindex directive.
  • 04Only certain pages, products, or templates are missing while the rest of the site appears normally.

Possible causes

What may have interrupted the expected path.

  • An SEO plugin has page-level noindex enabled for the affected content.
  • A template, theme, or custom field applies noindex to a whole content type.
  • Staging or privacy settings were copied to production during a migration.
  • A robots meta tag and an X-Robots-Tag HTTP header give different indexing instructions.

Evidence checks

What to verify first.

  • Check the page source and HTTP headers for robots noindex directives.
  • Review SEO plugin settings for the exact page, post type, taxonomy, and template involved.
  • Compare affected pages against similar pages that are indexable.
  • Use the Search Visibility Scanner to flag pages that may be hidden from search discovery.

What not to do

  • Do not remove every noindex rule on the site without checking why it exists.
  • Do not assume a page will rank just because the noindex signal is removed.
  • Do not edit robots.txt as the first fix if the actual block is a page-level meta or header directive.
  • Do not change production SEO settings without checking important templates and checkout/account pages.

Decision path

Move from signal to evidence to action.

Use the smallest safe step that resolves uncertainty. Implementation comes after the evidence is clear.

  1. 01Run the relevant diagnostic tool first so you have evidence before changing live site settings.
  2. 02Request a Site Rescue Review if the evidence is unclear, recurring, or affects pages that matter commercially.
  3. 03Custom fix work is quoted after review, once the likely cause and scope are clear.

Quick answer

What does this usually mean?

A WordPress page can be live for users but still tell search engines not to index it. That can happen through SEO plugin settings, theme templates, HTTP headers, staging leftovers, or page-specific rules. The first job is to confirm the signal before changing broad site settings.

First check

What should be checked first?

Check the page source and HTTP headers for robots noindex directives.

Need a human decision?

Check the evidence before changing a live system.

Start with the Search Visibility Scanner to confirm the noindex signal. If the source is unclear or affects important pages, request a Site Rescue Review before changing broad SEO settings.

Use Search Visibility ScannerRequest Site Rescue Review