One SEO plugin outputs index, allowing indexing, while another outputs noindex, prohibiting it. The page appears to be published, but the prohibition remains in the HTML head or in the server response header. Find the plugins, template, and server settings that output these tags. Remove the extra prohibition only from pages that should appear in search results.
Find all sources of the prohibition
When robots directives conflict, Google applies the more restrictive rule. Official documentation.
Start with the public page that is meant to be indexed. Ask a developer to retrieve all meta robots tags, separate tags for Google—meta googlebot—and the X-Robots-Tag response header. Don’t stop at the first index you find. Make a list of the sources: post settings, site-wide visibility settings in the content management system (CMS), a plugin, the theme, an intermediate server, and the content delivery network (CDN). Two identical tags alone don’t explain where the error is. If different plugins output them, changing one may leave the other’s prohibition in place. Find the setting that actually generates each value before disabling a component entirely.
HTML, a specific crawler, and the HTTP header
| Source of the robots directive | Tags found | Where to change the setting | What should remain in the HTML |
|---|---|---|---|
| Plugin A: index | Permissive directive | Check the other layers | One line is not enough |
| Plugin B: noindex | Restrictive directive | Find the setting | Remove it from the indexable service page |
| X-Robots-Tag: noindex | Server header | Check the configuration | Don’t overlook the header |
| Archive excluded from search | noindex is intentional | Preserve the directive | Don’t remove the archive prohibition |
Check the tags and the document header
Compare the source HTML with the HTML after scripts have run—the DOM. A plugin may output a value on the server, while a client-side component adds another element later. Record all values and when they appear. In Network, check the header for the document itself, not an image or API request. If the CDN adds X-Robots-Tag, changing a field in the CMS won’t fix it. Record the source next to every rule you find: CMS, theme, plugin, or server. Spoofing the User-Agent shows the server response for a test string, but does not prove how an actual search engine handles the page; record these observations separately.
Run this command in the browser console to retrieve the robots tags:
[...document.querySelectorAll('meta[name="robots"], meta[name="googlebot"]')].map(el => ({ робот: el.name, правило: el.content }));In Network, open the GET request for the document itself and look for X-Robots-Tag. With index and noindex, adding another index won’t help: Google applies the restrictive rule. Find the setting that creates the extra noindex.
Disable only the extra output
In a test scenario, disable only the second plugin’s robots output for a test service page, while keeping its other functions. Repeat the GET request and check the DOM. Then open an archive page that is intentionally set to noindex. If the archive has lost its directive, the change is too broad. Restore it and refine the rule. This lets you verify the specific source of noindex while preserving other SEO settings. For a server header, similarly change a specific route or condition rather than removing every X-Robots-Tag across the entire domain.
Check the plugin’s features before disabling it
An SEO plugin may generate the browser tab title (title), preferred URL (canonical), sitemap, link preview data (Open Graph), and structured data. Disabling it entirely to address robots requires checking these dependencies. First consider changing the setting for the specific feature or removing the duplicate handler. After the change, compare the head of the test pages and the sitemap contents. If you decide to remove the plugin entirely, that is a separate scope of work and cannot be described as a small noindex fix. Keep the settings and a way to revert the change. Check drafts and utility pages: if the plugin excluded them automatically, those restrictions must remain in place after it is disabled.
Save the service page and archive in the CMS again
The public service page has no unintended noindex in the source HTML, DOM, or HTTP headers. The archive that was intentionally excluded still outputs noindex. A check after saving the post confirms that the second plugin does not reintroduce the conflict.
Also read: robots.txt, meta robots, and X-Robots-Tag: what’s the difference and when should you use each? and SEO checks after a CMS and plugin update. Website checks are available on the reChecker technical audit page.