The error "No: 'noindex' detected in 'X-Robots-Tag' HTTP header" indicates that your WordPress blog post is being blocked from indexing due to an X-Robots-Tag: noindex directive in the HTTP response header, even though the post appears in your sitemap. This prevents the post from showing up in search results. Below is a step-by-step guide to diagnose and resolve this issue.

Why This Happens

The X-Robots-Tag: noindex is an HTTP header that instructs search engines not to index a specific page or file, such as your blog post or sitemap. This can occur due to misconfigurations in your WordPress setup, server settings, plugins, or hosting environment. Since your post is included in the sitemap but marked as noindex, there’s likely a conflict or unintended setting applying the X-Robots-Tag. Steps to Fix the Issue

1. Verify the Issue
  • Use a search engine console tool to inspect the specific blog post URL.
  • Check the coverage section to confirm the error: "No: 'noindex' detected in 'X-Robots-Tag' HTTP header."
  • Verify that the sitemap is being processed correctly, despite the noindex tag.
2. Check WordPress Settings
  • Search Engine Visibility: In your WordPress dashboard, go to Settings > Reading. Ensure the option "Discourage search engines from indexing this site" is unchecked. If checked, uncheck it and save changes.
  • Post Settings: Edit the affected blog post. If using an SEO plugin:
    • For Yoast SEO: In the Yoast SEO meta box, go to the Advanced tab and ensure "Allow search engines to show this Post in search results?" is set to Yes.
    • For Rank Math: Go to Rank Math > Titles & Meta > Posts and ensure the Robots Meta settings allow indexing (no noindex box checked).
  • Save the post and check if the issue persists.
3. Inspect HTTP Headers
  • Use your browser’s developer tools:
    • Open the blog post, right-click, and select Inspect.
    • Go to the Network tab, refresh the page, and check the page’s request for Response Headers containing X-Robots-Tag: noindex.
  • Alternatively, use a command-line tool like curl to check headers:
    curl -I your-site.com/your-blog-post/

    Look for X-Robots-Tag: noindex in the output.
  • If the header is present, it’s likely set at the server level or by a plugin.
4. Check Server Configuration
  • Apache (.htaccess): If using Apache, check the .htaccess file in your WordPress root directory for:
    Header set X-Robots-Tag "noindex"

    Remove or comment out such lines (add # before the line) and save. Back up the file first.
  • NGINX: If using NGINX, check the server configuration file for:
    add_header X-Robots-Tag "noindex, nofollow";

    Remove or comment out this line and restart the server. Contact your hosting provider if you need access.
  • CDN: If using a CDN, check for rules setting X-Robots-Tag: noindex. Create a rule to remove the header for specific URLs (e.g., sitemap or blog post).
5. Review Plugins and Themes
  • SEO Plugins: Plugins like Yoast SEO, Rank Math, or All in One SEO might set noindex. Disable them temporarily to check if the header disappears, then review their settings.
  • Other Plugins: Security or caching plugins might add headers. Disable non-essential plugins and recheck headers.
  • Theme: Check your theme’s functions.php or header.php for:
    header("X-Robots-Tag: noindex, nofollow");

    Remove or modify it to allow indexing.
6. Check Sitemap Configuration
  • Confirm that the sitemap itself isn’t incorrectly set to noindex. This is normal for sitemaps (they shouldn’t be indexed), but it shouldn’t affect listed posts.
  • If using an SEO plugin:
    • For Yoast SEO: Go to SEO > General > Features and ensure XML sitemaps are enabled.
    • For Rank Math: Go to Rank Math > Sitemap Settings and verify posts are included.
7. Request a Recrawl
  • After changes, use a search engine console tool to inspect the blog post URL and request indexing.
  • It may take days or weeks for the recrawl to process.
8. Test and Monitor
  • Recheck the URL in the console tool to ensure the noindex header is gone and the page is indexable.
  • Monitor the Page Indexing Report to confirm the post is no longer excluded by noindex.
  • Use site audit tools to check for noindex issues site-wide.
Additional Notes
  • Sitemap and Noindex Conflict: Sitemaps typically include X-Robots-Tag: noindex, which is standard practice, but this directive shouldn’t apply to listed blog posts.
  • CDN Edge Case: CDNs might add X-Robots-Tag via security or bot-fighting settings. Check and adjust rules.
  • Staging Environment: Staging sites may have noindex set by default. Ensure your site is in production mode.
  • External Links: Posts linked externally might appear in search results despite noindex, but this is temporary.
If the Issue Persists
  • Contact your hosting provider to check for server-level headers.
  • Hire a developer to debug HTTP response headers.
  • Seek advice from SEO communities for specific guidance.