BugWP logo BugWP
Back to Community
Home / Community / Plugin → Seopress – on-site seo

Resolving 'noindex' and X-Robots-Tag Conflicts in SEOPress

35 threads Sep 10, 2025 Plugin → Seopress – on-site seo

Content

Many users of the 'SEOPress – On-site SEO' plugin encounter issues where their pages are incorrectly marked with a noindex tag or an X-Robots-Tag: noindex HTTP header, preventing search engines from indexing their content. This guide will help you understand why this happens and how to resolve the most common causes.

Why Your Pages Might Be Marked as 'noindex'

The 'noindex' instruction tells search engines not to include a page in their search results. This can be communicated in two primary ways:

  1. Meta Robots Tag: An HTML tag placed in the <head> section of your page (e.g., <meta name='robots' content='noindex' />).
  2. X-Robots-Tag HTTP Header: A directive sent by your web server in the page's HTTP response headers.

Confusion often arises because multiple settings within WordPress, your theme, and other plugins can influence these outputs.

Common Causes and Solutions

1. Conflicting Global Settings in SEOPress

The most frequent cause is a global setting that overrides individual page configurations.

How to Fix It:

  • Navigate to SEOPress > Titles & Metas.
  • Carefully review every tab (Single Post Types, Archives, Taxonomies, etc.).
  • Ensure that the "Index this page" option is selected for the post types and archives you want to be indexed. If "Do not index this page" is checked, it will apply globally.
  • Save your changes and clear any site or server cache.

2. Individual Page/Post Settings

Even if global settings are correct, a noindex directive might be enabled on a specific page.

How to Fix It:

  • Edit the page or post that is not being indexed.
  • Scroll down to the SEOPress meta box and click on the Advanced tab.
  • Verify that the checkbox for "Do not display this page in search engine results / XML sitemaps (noindex)" is unchecked.
  • Update the page.

3. X-Robots-Tag HTTP Header (Server or Plugin Conflict)

If Google Search Console reports a noindex detected in the X-Robots-Tag http header, the issue often originates from a source other than SEOPress. The 'SEOPress – On-site SEO' team has stated they do not add this header except for their XML sitemaps.

How to Fix It:

  • Identify the Culprit: This header is typically added by server configuration (e.g., Apache/.htaccess, Nginx) or another SEO/caching plugin.
  • Plugin Conflict Test: Deactivate all plugins except SEOPress. Check if the issue persists. If it resolves, reactivate your plugins one by one to find which one is causing the conflict.
  • Theme Conflict Test: Temporarily switch to a default WordPress theme (like Twenty Twenty-Four) to see if your theme is adding the header.
  • Server Configuration: Contact your web hosting provider and ask them to check the server configuration for any rules that might be adding an X-Robots-Tag: noindex header to your pages.

4. Duplicate Meta Robots Tags

Some themes or plugins output their own meta robots tags, creating a conflict. Search engines may react unpredictably when they encounter multiple tags.

How to Fix It:

  • View the page source of an affected page (Right-click > View Page Source).
  • Search for meta name="robots" or meta name='robots'.
  • If you find more than one tag, you must disable the duplicate output. Check your theme's settings for any built-in SEO options and disable them. Perform a plugin conflict test as described above to find the plugin causing the duplicate tag.

5. Sitemap Specific Issues

If your sitemaps.xml is reported as having a noindex tag, ensure you are using the absolute URL to your sitemap in your robots.txt file (e.g., Sitemap: https://yourwebsite.com/sitemaps.xml). Flushing your WordPress permalinks (by visiting Settings > Permalinks and clicking "Save Changes") can also resolve 404 errors for the sitemap.

Key Takeaways

  • Always check SEOPress > Titles & Metas global settings first.
  • The X-Robots-Tag HTTP header is usually not set by SEOPress for pages and posts—look for conflicts elsewhere.
  • Indexing can take days or weeks after resolving these issues. Use Google Search Console's "URL Inspection" tool to request re-indexing.
  • Systematic troubleshooting by deactivating plugins and switching themes is the most effective way to identify conflicts.

By methodically working through these common causes, you can regain control over your site's indexing and resolve frustrating noindex problems.

Related Support Threads Support