noindex: requesting exclusion from the search index
Noindex instructs a search engine to exclude content from its index. It can be supplied in an HTML meta element or X-Robots-Tag HTTP response header. Google must access the page and read the instruction to apply it; noindex does not prevent visitors opening the URL.
Also known as: robots noindex · meta robots noindex · X-Robots-Tag noindex
At a glance
- Noindex concerns indexing and nofollow concerns links: they are separate instructions.
- Google cannot read a noindex instruction on a page blocked by robots.txt.
- Removing the instruction requires reprocessing; indexing is not an immediate promise.
On this page

What does noindex request?
It tells supporting search engines not to include the content in their index. Google's documentation explains that a detected instruction can remove the page from results even when other websites link to it.
This may suit a public page not intended for search. On an acquisition homepage, it can instead create an obstacle. The instruction should match the page's purpose.
The distinction between crawling and indexing is crucial: a crawler needs to read the response to learn that the page should not remain indexed.
Where can it appear?
An HTML page can include this in its head:
<meta name="robots" content="noindex">
A server can alternatively send:
X-Robots-Tag: noindex
Google's robots documentation describes both. Headers also work for resources such as PDFs without an HTML head.
These are illustrative instructions, not recommendations for the whole site. The CMS, application and server may produce rules separately. Inspect actual HTML and response headers rather than only a publishing-interface toggle.
The robots meta tag is the HTML container for page-level instructions; noindex is one possible instruction inside it. The same tag can also carry rules about following links or presenting snippets. Removing one noindex value therefore requires checking the remaining tags and headers rather than assuming every search restriction has disappeared.
How does nofollow differ?
Noindex concerns indexing; page-level nofollow separately concerns following the page's links. Neither automatically implies the other.
| Value | Requested behavior |
|---|---|
noindex | Exclude this page from the index. |
nofollow | Do not follow links on this page. |
noindex, nofollow | Apply both restrictions. |
Nofollow alone is not a removal method. Excluding a page from search does not inherently require nofollow too. Examine rules from all sources: one permissive tag may not override a restriction elsewhere.
Why does robots.txt not solve this?
Robots.txt governs fetching. Blocking the same URL prevents Google from reaching the response containing noindex. The address may remain known through other sources. Do not obstruct reading the instruction you need applied.
Noindex is not privacy protection. Confidential material needs authorization controls, since excluded pages may remain directly accessible.
A canonical URL addresses another purpose: selecting a preferred version. “Do not index” differs from “prefer this alternative.”
Example: a development restriction left on a homepage
Imagine a landscaping company's new site receiving noindex during testing. After launch, the homepage and form work, but a shared template still sends the restriction.
Normal browser behavior proves nothing about indexing permission. Inspect the actual homepage response. After repair, check service pages too while preserving intentionally restricted internal routes.
This fictional fault does not justify removing every exclusion from every route without considering purpose.
When will the fix be visible?
URL Inspection helps distinguish previously processed information from a live test. First verify that the served restriction is gone, then monitor index status separately.
Requesting recrawling guarantees neither immediate processing nor appearance. Removing noindex eliminates one obstacle without purchasing rankings or proving Google already uses the new version.
The separate nofollow entry covers page- and link-level qualification. URL inspection explains how to distinguish live responses from previously indexed state.