What does a noindex tag do?

It tells search engines not to include a page in their index, which means the page is removed from search results and cannot appear for any query. It does not stop the page from being crawled, does not delete it, and does not affect the pages that link to it.

Where is the noindex tag placed?

In one of two places. Either as a robots meta tag in the HTML head, written as , or as an X-Robots-Tag in the HTTP response header. The header version does not appear in the page source, so a source view alone will miss it.

What is the difference between noindex and disallow in robots.txt?

Noindex controls indexing and keeps a page out of search results. A robots.txt Disallow controls crawling and asks engines not to fetch the URL at all. They are not interchangeable: if you Disallow a page, Google cannot crawl it, so it cannot even read a noindex on that page. To remove a page from results, use noindex and keep the page crawlable.

Is noindex the same as nofollow?

No. Noindex keeps a page out of the index. Nofollow tells engines not to follow links or pass link value through them. They solve different problems and are often set independently.

When should I use a noindex tag?

On pages with no search value that you still want to exist, such as thank-you and confirmation pages, internal search results, staging environments, login and account pages, and genuine duplicate content. It becomes a problem only when it lands on a page you want ranking.

How can I make sure a noindex never slips onto an important page?

Manual checks work for a page you remember to inspect, but they rely on you looking. Deltio monitors the pages in your sitemap daily, reads the noindex signal in both the meta tag and the HTTP header, and alerts you on Slack the moment an indexable page becomes noindexed. Starter is £20 / €24 / $26 a month with a 14-day trial.

← Back to the blog

The Noindex Tag, Explained: What It Does and When to Use It

The noindex tag is one of the most useful instructions you can give a search engine, and one of the most dangerous when it lands in the wrong place. It quietly tells Google to leave a page out of its index, no error, no warning, no visible symptom. Here is what it actually does, where it lives, how it differs from the tags people confuse it with, and how to keep it from costing a client their rankings.

Deltio watches your client sites for a noindex that appears where it shouldn't, and alerts you on Slack the same day. From £20 a month.

What a noindex tag actually does

A noindex tag tells search engines not to include a page in their index. An indexed page is one that can appear in search results; a page carrying noindex is removed from that pool, so it stops showing up for any query, no matter how well it would otherwise rank.

It is worth being precise about what that means, because it is easy to overstate. A noindex does not block a page from being crawled, it does not delete the page, and it does not affect the pages that link to it. It does one narrow thing: it keeps this specific page out of search results. That narrowness is exactly why it is so easy to misplace and so hard to notice.

The two places a noindex can live

This is the part that trips people up, because there are two completely different ways to set a noindex, and one of them is invisible in the page source.

The robots meta tag. This sits in the HTML <head>, and looks like <meta name="robots" content="noindex">. You can see it by viewing the page source and searching for noindex.
The X-Robots-Tag HTTP header. This is sent in the server response, not in the HTML, so it never appears in the page source. It looks like X-Robots-Tag: noindex. You can only see it in the response headers, for example under the Network tab in your browser dev tools.

The header version is the one that catches teams out. A developer can add X-Robots-Tag: noindex at the server or CDN level, the HTML looks completely clean, and a source view tells you nothing is wrong. If you only ever check the page source, you will miss it every time.

Noindex vs nofollow vs disallow

These three get mixed up constantly, and confusing them leads to real mistakes. They are not interchangeable.

Instruction	Where it lives	What it controls	What it does
`noindex`	Meta tag or HTTP header	Indexing	Keeps the page out of search results
`nofollow`	Meta tag or link attribute	Link equity	Tells engines not to follow or pass value through links
`Disallow`	robots.txt	Crawling	Asks engines not to crawl the URL at all

The dangerous confusion is between noindex and Disallow. People sometimes add Disallow in robots.txt thinking it will remove a page from Google. It will not reliably do that. Worse, if you block a page in robots.txt, Google cannot crawl it, which means it cannot see a noindex on that page either. If your goal is to remove a page from results, the correct tool is noindex, and the page must stay crawlable so the engine can read that instruction.

When a noindex is the right call

Used deliberately, noindex is good hygiene. Reasonable places for it include:

Thank-you and confirmation pages that have no search value
Internal search result pages, which can generate endless thin URLs
Staging and development environments you do not want indexed
Genuine duplicate or low-value pages you would rather keep out of results
Admin, login, and account pages

In all of these, keeping the page out of the index is the point, and nothing breaks.

When a noindex quietly costs you rankings

The trouble starts when a noindex lands on a page you very much want ranking, and nobody notices. This happens more often than people expect, usually by accident: a staging configuration copied to production, a CMS or SEO plugin flipping a setting, a theme update, or a developer who added it to a section under construction and forgot to remove it at launch.

The page keeps loading. It looks perfect to a human. Meanwhile Google recrawls it, sees the noindex, and drops it from results. By the time the traffic graph makes it obvious, weeks have passed. The fix takes two minutes; the delay in spotting it is where all the damage is. If you want the operational side of this, we go deeper in how to catch a noindex in production.

How to keep a noindex from going rogue

You can check a single page by hand whenever you think of it: view the source for a meta robots tag, check the response headers for an X-Robots-Tag, or use the URL Inspection tool in Google Search Console, which will tell you plainly if a page is "Excluded by noindex tag." All of these work.

The catch is that they all depend on you deciding to look. A noindex added on a Friday does not announce itself. Across a portfolio of client sites you do not control, remembering to inspect every important page is not a plan.

That is the gap Deltio fills. It checks the pages in your sitemap on a daily cycle and reads their indexing signals, including noindex in both the meta tag and the HTTP header. When a page that was indexable yesterday carries a noindex today, you get a plain-language alert on Slack naming the page and the site. You find out the same day, while it is still a quick fix, instead of finding out from a monthly report. Deltio does the same for the related signals that fail just as quietly: robots.txt changes, canonicals pointing somewhere new, and URLs dropping out of the sitemap. If you want alerts scoped to exactly these events, see SEO change alerts.

The short version

A noindex tag keeps a page out of search results, lives in either the HTML head or the HTTP header, and is not the same as nofollow or a robots.txt Disallow. It is a precise, useful tool when you mean it, and an expensive silent failure when you don't. The difference between the two is whether someone finds out the day it appears or the month after.

Add your first client site, connect Slack, and Deltio starts watching the same day. Start your 14-day trial and make sure the next stray noindex reaches you first.

Frequently asked questions

What does a noindex tag do?: It tells search engines not to include a page in their index, which means the page is removed from search results and cannot appear for any query. It does not stop the page from being crawled, does not delete it, and does not affect the pages that link to it.
Where is the noindex tag placed?: In one of two places. Either as a robots meta tag in the HTML head, written as <meta name="robots" content="noindex">, or as an X-Robots-Tag in the HTTP response header. The header version does not appear in the page source, so a source view alone will miss it.
What is the difference between noindex and disallow in robots.txt?: Noindex controls indexing and keeps a page out of search results. A robots.txt Disallow controls crawling and asks engines not to fetch the URL at all. They are not interchangeable: if you Disallow a page, Google cannot crawl it, so it cannot even read a noindex on that page. To remove a page from results, use noindex and keep the page crawlable.
Is noindex the same as nofollow?: No. Noindex keeps a page out of the index. Nofollow tells engines not to follow links or pass link value through them. They solve different problems and are often set independently.
When should I use a noindex tag?: On pages with no search value that you still want to exist, such as thank-you and confirmation pages, internal search results, staging environments, login and account pages, and genuine duplicate content. It becomes a problem only when it lands on a page you want ranking.
How can I make sure a noindex never slips onto an important page?: Manual checks work for a page you remember to inspect, but they rely on you looking. Deltio monitors the pages in your sitemap daily, reads the noindex signal in both the meta tag and the HTTP header, and alerts you on Slack the moment an indexable page becomes noindexed. Starter is £20 / €24 / $26 a month with a 14-day trial.