SEO

Noindex

Q: What does the noindex tag do?

The noindex tag (<meta name="robots" content="noindex">) tells search engines not to include a page in the index. Unlike a robots.txt disallow (which blocks crawling), the page is still crawled but is not shown in search results.

Q: When should noindex be used?

For pages with no search value: internal search results, filter URLs, thin-content categories, thank-you pages, user profiles with no public value, old campaign landing pages. These pages should remain usable but should not rank.

Q: What is the difference from a robots.txt disallow?

Noindex prevents indexing, disallow prevents crawling. An important consequence: a page blocked by disallow can still end up in the index (with a "no description" snippet) if other pages link to it. Noindex is more reliable for "please keep this out of the index".

Q: Combining noindex and disallow?

The two contradict each other. If a URL is blocked by disallow, Google cannot read the noindex meta tag in the HTML at all. Rule of thumb in practice: either noindex (without disallow) or disallow (without expecting deindexing). For reliable removal: noindex, then wait for deindexing, and only afterwards add a disallow if needed.

Also known as: robots noindex, meta robots noindex, index exclusion

Noindex is a directive with which website operators instruct search engines not to include a particular URL in the index. It is set either as an HTML meta tag (<meta name="robots" content="noindex">) in the <head> or as an HTTP header (X-Robots-Tag: noindex). Unlike a robots.txt disallow, it permits crawling of the page — Google sees the content but keeps it out of the index.

When noindex is the right choice

Internal login and account pages — users need to reach them, search engines do not.
Your own site's search results pages — otherwise endless mini-pages arise as duplicates.
Filter and tag overviews in shops or blogs without independent value.
Thin service pages that cannot be omitted but have no value in the index (contact confirmations, cookie overviews).
Staging and test environments — noindex plus IP restrictions as double protection.

Noindex vs robots.txt disallow

A common confusion: a robots.txt disallow forbids crawling — Google does not see the page but knows it exists (for example through internal links). The consequence: the URL can remain indexed without snippet text. Noindex, by contrast, permits crawling — Google reads the page but does not index it. Anyone who wants to remove a page from the search results needs noindex, not disallow. Anyone who also wants to save crawl budget combines both — but always in this order: first set noindex, wait until the page has left the index, and only then add the disallow.

Common noindex mistakes

Accidental noindex on live pages after a relaunch (a forgotten staging setting).
Noindex plus canonical on the same URL — a contradictory signal, both are devalued.
Blocking a noindex via robots.txt disallow — Google no longer sees the noindex and the page stays indexed.
Mass noindex in the sitemap — the sitemap signals "please index", the noindex says the opposite. Sitemaps should only contain indexable URLs.

Example from practice

Example: A WooCommerce shop has more than 8,000 indexed tag and filter URLs, all of which show thin content with no backlinks and no clicks in GSC. Applying noindex to all tag overviews and parameter filter pages reduces the indexed URLs from 11,300 to 2,800 after 8 weeks — the crawl frequency of the real product pages doubles, and new products appear in the index an average of 4 days sooner.

Frequently asked questions

What does the noindex tag do?

The noindex tag (<meta name="robots" content="noindex">) tells search engines not to include a page in the index. Unlike a robots.txt disallow (which blocks crawling), the page is still crawled but is not shown in search results.

When should noindex be used?

For pages with no search value: internal search results, filter URLs, thin-content categories, thank-you pages, user profiles with no public value, old campaign landing pages. These pages should remain usable but should not rank.

What is the difference from a robots.txt disallow?

Noindex prevents indexing, disallow prevents crawling. An important consequence: a page blocked by disallow can still end up in the index (with a "no description" snippet) if other pages link to it. Noindex is more reliable for "please keep this out of the index".

Combining noindex and disallow?

The two contradict each other. If a URL is blocked by disallow, Google cannot read the noindex meta tag in the HTML at all. Rule of thumb in practice: either noindex (without disallow) or disallow (without expecting deindexing). For reliable removal: noindex, then wait for deindexing, and only afterwards add a disallow if needed.

Used in Rankmio for

Noindex and robots audit in the technical SEO check

Go to the feature →

Last updated: 2026-06-17 · Browse all glossary entries