Sébastien Laframboise

Using noindex in WordPress without removing an important page from the results

Using noindex in WordPress without removing an important page from the results

The directive noindex WordPress is used to ask search engines not to display a URL in their results. It’s useful, but it should serve a specific purpose. An important page that gets visits, links, or conversions should not be excluded automatically.

Before enabling this directive, ask yourself a simple question: do you want this URL to be discoverable in search? If the answer is yes, keep it indexable. If the answer is no, first check whether a redirect, a canonical tag, or removal would be more appropriate.

What noindex actually does in WordPress

On an HTML page, noindex usually appears as a robots tag in the source code. Google states that this rule asks crawlers not to show the page in results. For it to be read, however, the crawler must be able to access the URL. A URL blocked by robots.txt prevents the crawler from discovering its noindex directive.

See Google's documentation on robots tags and the X-Robots-Tag header to understand this principle. It also notes that the HTTP X-Robots-Tag header is suitable for non-HTML files, such as certain PDFs or media.

The noindex directive does not make a page private. A visitor who has the address can still access it, unless you add a real access restriction. For confidential content, use password protection, authentication, or remove the content from the server instead.

When to use noindex WordPress

Use noindex for a URL that is accessible but has no standalone value in search results. The goal is not to reduce the number of indexed pages at all costs. It’s to prevent temporary, low-value, or purely functional pages from taking the place of useful pages.

Internal search results pages

Pages generated by internal search often show lists that change with the query. They typically aren’t stable landing pages. In Yoast SEO, search pages and 404 pages are already set to noindex, follow by default. The procedure and available settings are described in the guide How to noindex URLs by Yoast.

Archives that don’t help the reader

A tag archive with a single post, a date archive with no editorial value, or an empty author archive may not deserve to appear in Google. However, don’t hide all archives without review. A well-structured category archive can become an excellent navigation and discovery page.

Before changing archives, make sure their role is clear. The article on organizing WordPress categories and tags can help you distinguish a useful taxonomy from a redundant archive.

Temporary or limited-access content

A campaign page that should remain accessible after it ends, a public working document, or a thank-you page can justify noindex. This decision is relevant only if the page is not intended to attract organic search.

By contrast, a service page, product sheet, article, local homepage, or strategic category page should usually remain indexable. Even a low-traffic page can meet a specific intent and gain value over time.

When noindex is not the right solution

Many issues look like they require noindex but actually need a different action. Making this distinction prevents accidentally removing a page that should remain visible.

SituationGenerally appropriate solution
Two URLs display the same or very similar contentUse a canonical tag pointing to the preferred URL.
An old page has been permanently replacedCreate a redirect 301 to the new relevant page.
The page should no longer exist and no replacement makes senseRemove it and return an appropriate 404 or 410 status.
Content must be restricted to authorized usersProtect access; noindex alone is not sufficient.
You only want to remove a URL from the XML sitemapReview sitemap inclusion without assuming noindex is required.

Google advises against using noindex to choose a canonical version among internal duplicates. A tag rel="canonical" is intended to indicate the preferred version, while noindex removes the page entirely from results. See Google's documentation on URL duplicate consolidation before addressing duplication.

Similarly, robots.txt mainly controls crawling. It does not guarantee a URL will disappear from results. Google explains why in its robots.txt beginners guide. So avoid combining a robots.txt block and noindex on the same page when your goal is deindexing.

How to apply noindex safely

Start with a single URL. Making a change across a content type or taxonomy can affect far more pages than expected. If your SEO plugin offers per-content settings, use them first to validate the intended effect.

Apply noindex to a specific page

  1. Open the relevant page, post, product, or taxonomy term in WordPress.
  2. Check its public URL and purpose. Confirm it’s not an important acquisition, sales, or support page.
  3. In your SEO plugin, choose the option that prevents search engines from displaying this content in results.
  4. Save the change, then open the URL in a private window.
  5. View the source code and look for noindex.

With Yoast SEO, the individual setting is in the Advanced tab of the sidebar or the Yoast box. Yoast’s guide notes this applies to posts, pages, products, categories, and tags. Don’t reflexively check nofollow: noindex is usually sufficient when you only want to remove the URL from results.

Exclude a content type or an archive

A global setting is appropriate only when all targeted URLs serve the same role. For example, you might exclude date archives on a site where they simply duplicate lists of posts. However, don’t noindex all categories if your categories function as useful topical pages.

Also keep the sitemap consistent with that decision. Google recommends including the URLs you want to appear in its results. So verify the outcome with our method to fix WordPress XML sitemap.

Checks to do after the change

A correct directive in WordPress doesn’t always cause immediate removal. Google must crawl the URL again to read the tag. Don’t remove the noindex too quickly because the old result can remain visible for some time.

  • Open the public page and check its source code. Look for a tag containing name="robots" and noindex.
  • Make sure robots.txt is not blocking the URL. Otherwise, Google won’t be able to read the directive.
  • Ensure the page returns a normal HTTP status if you want it to remain accessible.
  • Review internal links. Keep links that are useful to visitors, even if the page is noindex.
  • In Search Console, use URL Inspection to check the status Google sees.

If you haven’t connected your site to this tool yet, follow the steps to add WordPress to Google Search Console and verify ownership. .

Avoid costly mistakes

The biggest mistake is putting an important page in noindex because it seems too similar to another. If the two pages serve different needs, instead improve their content, titles, and internal links. If only one version should remain, use a canonical or a redirect as appropriate.

Also avoid the global setting «discourage search engines from indexing this site» on a production site. That option is mainly intended for development environments or sites that shouldn’t yet appear in results. After a migration or launch, always check that this setting is no longer active.

Finally, keep a short list of URLs set to noindex and the reason. You can then reassess exclusions during a redesign, an SEO plugin change, or an audit. This record reduces the risk that a page that became strategic remains hidden by oversight.