Indexing control · 12 Nov 2026 · 6 min read
Noindex tag: what it does and when to use it
A noindex tag asks search engines to keep one page out of their results. On the right pages it tidies your presence in search. On the wrong ones it removes pages that earn you business.
The short answer
A noindex tag is a rule, added as a robots meta tag or an HTTP header, that tells search engines not to show a page in their results. Google drops the page after it next crawls it and reads the rule. The page must stay crawlable, so do not also block it in robots.txt. Use noindex for pages with no search value.
What a noindex tag does
A noindex tag is a rule that tells search engines not to include a page in their index. Google's documentation says that once it crawls the page and reads the rule, it drops the page from Search results entirely, even if other sites link to it. The page itself stays live. A visitor who has the address, or who follows a link on your site, can still open it.
The rule comes in two forms, and Google treats them the same way. One is a meta tag in the head of an HTML page. The other is an X-Robots-Tag header that the server sends with the page. The header is the way to apply the rule to files that have no HTML head, such as PDFs.
How to noindex a page
For an ordinary page, add this line inside the head section: <meta name="robots" content="noindex">. The name robots speaks to every search engine that supports the rule. Change the name to googlebot if you want to address Google's crawlers only.
Most site owners never edit code for this. Many platforms and SEO plugins provide a checkbox, often worded as hiding the page from search engines. The setting differs by platform, so check your platform's documentation. After you save, view the live page's source, or use the URL Inspection tool, to confirm the tag is in the HTML the server really sends. For PDFs and images, ask whoever manages your server to send an X-Robots-Tag header with the value noindex for those files.
Do not rely on JavaScript to add or remove the rule. Google's documentation warns that when it sees noindex it may skip rendering, so removing the rule with JavaScript later may not work. Put the rule in the HTML the server sends and leave it there for as long as you want it.
Noindex and robots.txt: the order of events
The two controls act at different moments, which is why they are so often confused. A crawler visiting your site does the following.
- It reads the robots.txt file for the site.
- If the page is allowed, it fetches the page and reads any noindex rule in the HTML or the headers.
- The search engine then removes the page from its index, or declines to add it.
If robots.txt stops step two, step three has nothing to act on. The page can still appear in results with little more than its address, if other pages link to it. Google's help for the Page indexing report gives the same advice: to keep a page out of the index, remove the robots.txt block and use noindex. Google also does not support a noindex rule written inside the robots.txt file.
Robots.txt controls fetching, and noindex controls showing. Pick the one that matches your goal. To stop crawlers spending time on a section, use robots.txt. To keep a page out of results, use noindex and let the page be crawled. Neither rule is security, so anything private needs a login.
Which pages should be noindexed?
The answer depends on the site, but these page types are the usual candidates.
| Page type | Why people noindex it | Check first |
|---|---|---|
| Internal search result pages | They create endless near-empty address variants | Whether any of them match a search people really make |
| Thin tag and archive pages | They repeat snippets of posts and add nothing new | Whether improving them would be better than hiding them |
| Landing pages built for paid campaigns | They duplicate organic pages and exist for ad traffic | Whether a canonical tag would do the job |
| Thank-you and confirmation pages | Visitors should arrive only after an action | That the page is not linked from public pages |
| Account, cart and checkout pages | They are personal and have no search value | That private data sits behind a login, which protects it far better than a noindex rule |
| Staging and test copies | They duplicate the live site | Password protection, which does more than noindex |
| Downloads such as PDFs | The reader should get them through a form | The X-Robots-Tag header on those files |
Campaign landing pages sit between two channels, and the guide to SEO versus SEM explains how organic and paid search relate. Whatever the page type, decide on purpose and keep a list, because a noindex rule is easy to add and easy to forget.
Pages you should not noindex
Do not noindex a page merely because it is weak. A thin page that targets a search you could win is better improved than hidden. Before you hide anything, ask how realistic the search is, and the guide to judging keyword difficulty shows how to do that. Weak structure is another common reason a page looks thin, and the guide to heading tags explains how to organise one so that readers and search engines can follow it.
Do not use noindex as a substitute for a redirect. When a page has been replaced, send visitors and links to the new page with a redirect. Do not use it to handle duplicates you want to combine either, because a canonical tag or a redirect points to the version you prefer, and noindex does not. The guide to duplicate content and canonical tags compares the options.
Do not use noindex for pages that no longer exist. A deleted page should return a proper not found response, and the guide to finding and fixing broken links and 404 errors covers how to handle them. Finally, leave your home page, service pages, product pages and any page that brings in enquiries well alone. Those are the pages a stray noindex hurts most.
Mistakes that hide the wrong pages
- A rule left over from the build. Many platforms offer a site-wide setting that discourages search engines during development. If nobody switches it off at launch, every page stays hidden.
- Noindex plus a robots.txt block on the same page. The crawler cannot read the rule, so the page may stay in results.
- Noindex on a page that is also listed in the XML sitemap. The sitemap asks for the page to be found and the page asks to be left out. Remove one of the two.
- A template-wide change. A rule added to the template for one page type can spread to a whole section without anyone noticing.
- Using noindex to save crawling. Google's crawl guidance says it still requests the page before it drops it, so noindex does not reduce crawling.
How long removal takes and how to check it
Noindex takes effect the next time Google crawls the page and reads the rule. Google's documentation says a page that still shows up probably has not been recrawled since you added the rule, and that revisits can take months depending on how important the page is. The URL Inspection tool lets you ask for a recrawl, and it can show the HTML Google received.
The Page indexing report in Search Console lists pages with the reason Excluded by 'noindex' tag. Review that list after every release. Every address on it should be there on purpose. Other search engines may read the rule differently, so check their own documentation if they matter to you.
A noindex review is one part of a wider technical check. The search engine optimisation service page from Liftup Technologies lists the SEO services the team provides.
Related guides
- SEO services
- Broken links and 404 errors how to find and fix
- Duplicate content and canonical tags explained
- Heading tags how to structure a page
- Push notifications when and how to use them
- Xml sitemap and robots txt what they do
Questions and answers
What is a noindex tag?
It is a rule, added as a robots meta tag in the page head or as an HTTP header, that tells search engines not to show the page in results. Google applies it after it next crawls the page. The page stays reachable for anyone with the address.
What is the difference between noindex and robots.txt?
Robots.txt asks crawlers not to fetch addresses. Noindex asks search engines not to show a page they have fetched. If robots.txt blocks a page, the crawler never reads the noindex rule, so use noindex alone when the aim is to keep the page out of results.
Which pages should be noindexed?
Pages with no value as a search result, such as internal search results, thin archive pages, thank-you pages, account pages and test copies. Do not noindex pages that bring in enquiries or sales, and do not use it as a replacement for a redirect.
How long does it take for a noindexed page to disappear from Google?
It disappears after Google next crawls the page and reads the rule. Google says revisits can take months for some pages. You can ask for a recrawl with the URL Inspection tool, but you cannot set a date.
Can I noindex a PDF or an image?
Yes. Files without an HTML head cannot carry a meta tag, so the server sends an X-Robots-Tag header with the value noindex for those files instead. Ask your host or developer to add it.
Does noindex stop Google crawling the page?
No. Google still requests the page, and then drops it once it reads the rule. If your aim is to reduce crawling of a section, robots.txt is the tool for that, not noindex.
Will noindex hide my page on other search engines?
Other search engines may interpret the rule differently, so a page might still appear on one of them. Check the documentation of each engine whose results matter to you.
Tell us what you are building.
A short call, a written plan and a fixed quote. No obligation.