What Is noindex? How to Set It Up, When to Use It, and How It Differs from nofollow

noindex is a setting that tells search engines not to display a given page in search results. Not every page on your site belongs in the index. In fact, having large numbers of low-quality or duplicate pages indexed can work against your site's overall evaluation.

This article covers how noindex works, the two ways to implement it, when to use it and when not to, and how it differs from nofollow and robots.txt — the knowledge you actually need in practice.

What is noindex?

noindex is a rule that instructs search engines not to index a page — that is, not to register it in search results. When Googlebot crawls the page and reads the tag, Google drops that page entirely from its search results, regardless of whether other sites link to it.

The critical point is this: you allow crawling while refusing indexing. If a search engine cannot access the page, it cannot read the noindex instruction in the first place. Whether you understand this premise is what separates successful noindex management from failure.

When noindex doesn't work

A very common complaint is that a page stays in search results even after noindex has been set. There are two main causes.

• The page is blocked in robots.txt: if crawling is disallowed, Googlebot cannot fetch the page and therefore cannot read the noindex tag. As a result, the URL remains in the index.
• The page hasn't been recrawled yet: noindex only takes effect once Googlebot refetches the page. Depending on the page's importance, a revisit can take months.

If you need a page removed urgently, use the Removals tool in Search Console. You can also speed up processing by requesting a recrawl via the URL Inspection tool.

How to set up noindex

There are two ways to implement noindex. They have the same effect, so choose based on your content type and site setup. Note that specifying noindex in robots.txt is not supported by Google, so don't use that approach.

Method 1: Use a meta tag

For HTML pages, the standard approach is to place the following meta tag inside the head element.

<meta name="robots" content="noindex">

Setting the name attribute to robots targets every search engine that supports the rule. If you want it to apply only to Googlebot, change the name attribute to googlebot.

<meta name="googlebot" content="noindex">

To combine multiple rules, list them comma-separated. When instructions conflict, Google applies the more restrictive one.

<meta name="robots" content="noindex, nofollow">

Method 2: Use X-Robots-Tag

Files without an HTML head element — PDFs, images, videos — can't use a meta tag. In those cases, use the X-Robots-Tag HTTP response header.

X-Robots-Tag: noindex

X-Robots-Tag supports the same directives as the meta tag, with the added advantage that you can apply rules across an entire site through server configuration files (Apache's .htaccess, Nginx config, and so on). For example, you can apply noindex to every PDF file at once.

How to verify the setting is applied correctly

1. Use the URL Inspection tool in Search Console to check the HTML Googlebot actually retrieved
2. Monitor the "Excluded by 'noindex' tag" item in the Page Indexing report
3. Confirm the URL is not blocked in robots.txt

When to use noindex

Use noindex for pages you want crawled but kept out of search results. Typical cases include the following.

• Thank-you pages: form completion pages and similar, where arriving directly from search serves no purpose
• Internal search results pages: they generate URLs endlessly and are easily judged as low-quality duplicates
• Filter and sort parameter pages: the mass of near-identical URLs produced by faceted navigation
• Members-only and post-login pages: no need to surface them in search, and no benefit if they do appear
• Staging environments and test pages: content that duplicates production
• Thin pages such as tag archives: listing pages with almost no content
• Print-friendly pages and PDF versions: content that duplicates the main page

When not to use noindex

There are also cases where noindex is inappropriate, or actively harmful.

• Canonicalizing duplicate content: use the canonical tag to consolidate similar pages. Applying noindex means the page's equity can't be consolidated into the canonical URL.
• Pages referenced by a canonical: setting noindex on a URL you've designated as canonical sends contradictory instructions.
• URLs included in your sitemap: a sitemap signals "please index this." Including noindexed pages sends conflicting signals and wastes crawl budget.
• URLs already blocked in robots.txt: as covered above, the noindex won't be read and won't function.
• Pages that are merely temporarily low quality: if there's room to improve and grow them, fix the content first.

The difference from nofollow

noindex and nofollow are easily confused because the names look alike, but they control entirely different things.

• noindex: an instruction not to display the page itself in search results. Page-level index control.
• nofollow (page-level): an instruction not to follow any links on that page. It affects how linked destinations are evaluated.
• rel="nofollow" (link-level): applied to individual anchor tags, targeting only that specific link.

In short, noindex says "don't show this page," while nofollow says "don't go any further from this page." The two are independent, so links are still followed normally on a page set to noindex.

That said, page-level nofollow is rarely the right tool. It stops equity from flowing through every link on the page, navigation included. If you want to control specific links only, use the link-level rel attribute.

The difference from robots.txt

The distinction between noindex and robots.txt is another frequent source of confusion in technical SEO.

• robots.txt: controls crawling (access). It does not control indexing.
• noindex: controls what happens after the crawl (whether to index).

A URL blocked in robots.txt can still appear in search results if external sites link to it. In that case, the URL shows up with no snippet. The basic rule of thumb: use noindex when you definitely want something gone from search results, and robots.txt when you want to conserve crawl budget.

Using both at once is a classic failure pattern. Always follow this order: allow crawling → set noindex → confirm the page has disappeared from search results.

A noindex operations checklist

1. Confirm the target URL isn't blocked in robots.txt
2. Choose your method by content type — meta tag (HTML) or X-Robots-Tag (non-HTML)
3. Verify with the URL Inspection tool that the tag appears in the HTML Googlebot retrieved
4. Remove the target URL from your XML sitemap
5. Check that you haven't set noindex on a canonical destination
6. Monitor processing status continuously in the Page Indexing report
7. For urgent cases, also use the Removals tool in Search Console

Summary

noindex is a simple but powerful setting for deliberately excluding pages on your site from search results. The key points come down to three.

• For noindex to work, crawling must be allowed. Never combine it with a robots.txt block.
• nofollow controls links; noindex controls indexing. Their purposes are entirely different.
• Use canonical to consolidate duplicate content and noindex to exclude from search results — pick by purpose.

After setting it up, always confirm the status in Search Console, and audit periodically to make sure noindex hasn't been left on pages where you didn't intend it. Index loss from a misconfiguration produces large traffic losses before you notice.