How noindex works
A noindex directive is placed either in a meta tag in the page head or in an HTTP header. When a crawler visits and sees it, the page is dropped from the index after reprocessing. The crawler must be allowed to fetch the page, so do not also block it in robots.txt.
Pages that often deserve it
Thank-you and confirmation pages, login and account screens, internal search results, cart and checkout pages, staging or test copies, duplicate printer-friendly versions, and thin tag or date archives are typical candidates. Pages made only for ad campaigns that duplicate your main content may also qualify.
If a page is useful to visitors but adds nothing for search, noindex is a tidy solution.
Pages that should never have it
Your home page, main service pages, contact page, location pages, and any article you want found in search must stay indexable. A common accident is leaving the Discourage search engines box ticked in WordPress after launch, which adds a site-wide noindex. Developers also add it to staging sites, then copy it to the live version.
Noindex, nofollow and the follow question
Noindex can be combined with a nofollow instruction, which tells crawlers not to follow links on the page. Usually you do not need that. Over time, search engines treat long-term noindex pages as not followed anyway. For most small sites, plain noindex is enough.
For files such as PDFs, which have no head section, use an X-Robots-Tag header set by the server.
Audit and recovery
After launches and migrations, search your key pages for noindex in the source, or use the URL Inspection tool, which reports whether indexing is allowed. The Pages report in Search Console lists pages excluded by a noindex tag, so you can confirm they are the ones you intended.
If you removed a tag by mistake, fix it, request indexing for the important pages and be patient. It may take days or weeks for results to return.
A launch-day checklist
On launch day, confirm the reading setting that discourages indexing is off, view the source of the home page and one service page for any noindex, and check that the staging site is blocked or password protected rather than copied wholesale. Look at your Pages report a week later for unexpected exclusions.
A short note in your launch plan that says who removes the staging block, and when, prevents the most common noindex accident in small site relaunches.
If you use a maintenance mode plugin during a rebuild, check that it does not add a noindex or a temporary status code that lingers after you turn it off. Visit the live site in a private window and look at the page source, not just the appearance.
Remember that removal takes time in both directions. A page that was noindexed for months may take a while to return, so avoid toggling the tag casually on pages that matter.
Common questions
Noindex or robots.txt: which should I use?
Use noindex to keep a page out of results. Robots.txt controls crawling and cannot reliably remove pages.
How long does noindex take to work?
It takes effect after the page is next crawled, which can be days or longer.
Can I noindex a page and still link to it?
Yes. Visitors can still reach it.
This guide is general information. Search engines change how they work and their guidelines; check Google's current documentation for your situation. Nobody can guarantee a ranking.