What is noindex?
Noindex is an instruction to exclude a fetched page or resource from search results. Google supports it in a robots meta tag for HTML and in an X-Robots-Tag response header. The URL must remain accessible to Googlebot so the instruction can be read. See Google’s noindex documentation.
It does not hide a page from visitors with its address. For a private account, confidential document or development environment, use access controls. Search exclusion and permission to read are different decisions.
When search exclusion is the right outcome
Begin with what the page does for its visitor. A public confirmation screen can be useful after a form submission without being a useful search destination. A service page that answers a customer’s question may need better content rather than exclusion.
Do not apply noindex to every archive, filter or short page by default. Review the actual content and search purpose. Excluding a page is not a promise that another page’s rankings will improve.
When several URLs show the same content and you want a preferred representative, consider canonicalization instead. Google’s canonical guidance discourages noindex as a way to select a canonical within a site. Excluding a URL and declaring a duplicate preference are different outcomes.
How to implement noindex
For an HTML page, place the meta element in the document’s head. For a PDF or another non-HTML resource, return the HTTP header. A header can also be used for HTML. These are illustrative syntax examples, not directives applied to this glossary page:
<!-- In the HTML document head -->
<meta name="robots" content="noindex">
# In the response headers for the intended resource
X-Robots-Tag: noindex
The robots meta and response-header specification also permits a Google-specific meta name, googlebot. Other search engines can interpret rules differently. Verify the behavior of a crawler you need to control rather than assuming identical support everywhere.
Combining directives
| Value | Documented purpose |
|---|---|
noindex | Exclude the fetched page from search results. |
noindex, nofollow | Exclude the page and add a page-wide instruction not to follow its links. |
none | Equivalent to noindex, nofollow in Google’s specification. |
Leaving out nofollow allows Google to use links for discovery. It does not establish a guaranteed amount of PageRank transfer. Keep a link-following instruction separate from a claim about measured ranking value.
Choose the control for the page’s purpose
| Intended outcome | Control to evaluate | Check first |
|---|---|---|
| Keep a public page available but out of search | Readable noindex meta tag or response header. | Googlebot can fetch the exact URL and see the instruction. |
| Identify a preferred duplicate | Canonical annotation or an appropriate permanent redirect. | The destination represents the same content. |
| Keep information private | Authentication or another effective access restriction. | Unauthorised visitors cannot retrieve the content. |
| Reduce unnecessary crawling of filter combinations | A considered robots.txt or navigation strategy. | Whether the goal is crawl prevention or removal of an indexed URL. |
The last case needs care. Google’s faceted-navigation guidance discusses preventing unnecessary filter crawling when those URLs need not be indexed. That recommendation does not mean blocking an already indexed page lets Google read a noindex tag. Keep an exclusion task separate from a crawl-volume task.
Illustrative noindex decisions
A confirmation page
A business has a public page thanking a visitor for an enquiry. The owner wants the page available after submission but absent from search. Review that route’s template and response headers, add the intended noindex instruction, and verify that ordinary service pages do not inherit it. This is an example, not a customer result.
A downloadable document
If a public PDF should be excluded, inspect the response for that PDF URL. An HTML meta tag on the page linking to it is not an implementation on the PDF itself. Confirm that the server or CDN returns the intended X-Robots-Tag for the document.
A development site
Decide whether the development content should be public at all. Noindex is not a substitute for protecting a private environment. Before launch, inspect the production configuration separately so a development setting is not carried into customer-facing pages.
Noindex vs robots.txt
Robots.txt controls crawling by cooperating crawlers. Noindex controls search exclusion after fetching. A sitemap or backlink does not override a robots.txt restriction and make the blocked page’s meta tag readable.
If Googlebot is blocked from fetching a URL, it cannot discover the noindex instruction there. A blocked URL can still appear in results. Do not combine a new crawl block with noindex and assume you have completed deindexing.
For urgent Google Search removal, an authorised owner can consider the Removals tool. Its block is temporary. It does not delete content from the internet or replace the steps needed for lasting exclusion. Do not promise immediate removal from adding a tag or submitting a request.
Checks before and after a noindex change
- Record the outcome. Write down which URL should be excluded, why, and who can reverse the decision.
- Find the controlling layer. Check the CMS setting, page template, server and CDN. Inspect both the HTML and headers rather than changing only the most visible field.
- Check crawl access. Review the applicable robots.txt group and any authentication or fetch failure.
- Check nearby pages. Inspect a page that should remain indexable. Confirm that a shared template change did not affect it.
- Compare observations. Keep the deployed response and change date alongside Search Console’s last-crawl details. A live page and an older indexed observation can differ.
Google’s Page indexing report guidance explains exclusion reasons and the difference between live inspection and earlier crawl observations. Use that evidence to investigate an unintended noindex, not a fixed deadline invented for every website.
Mistakes that change the intended result
A CMS toggle may affect a whole template rather than a single page. A response header may still exclude a page after its HTML tag has been removed. A stale cached response may also differ from the response you expect. Inspect what is served and record which configuration generated it.
Do not add a Noindex: line to robots.txt: Google does not support that implementation. Do not assume removing noindex guarantees indexing, either. Removing an exclusion rule makes the page eligible for consideration; it does not decide Google’s selection.
Questions about noindex
How long does noindex take to work?
Google must fetch the URL and read the instruction. There is no universal turnaround: Google’s documentation notes that revisiting some pages can take months. Investigate crawl access and the last observed response instead of promising a particular number of days.
Can an index tag override a noindex header?
Adding a permissive instruction is not a reliable repair for a conflicting exclusion rule. Google applies restrictive rules when instructions conflict. Find and remove the unintended noindex at the layer that serves it, then inspect the resulting HTML and response headers.
Related glossary terms
- Robots.txt: control crawling without confusing it with search exclusion.
- Meta robots tag: distinguish page-level indexing, link and snippet instructions.
- Canonical URL: choose a representative for duplicate content.
Sources and editorial note
This entry was revised with AI assistance using the official Google references linked beside their claims, checked on October 12, 2026. Examples are illustrative. No production configuration, Search Console account, indexing outcome or named expert approval was tested. The original publication date is retained; its historical provenance remains unverified.