SEO

Noindex

Also called meta robots noindex, noindex tag

A directive in a page's head or headers that tells search engines to drop the URL from results.

Quick facts: Noindex

Category
SEO
Also called
meta robots noindex, noindex tag
Level
Intermediate
Affects
Which pages can rank, index size, crawl efficiency
Where to see it
Search Console URL Inspection, page source, Screaming Frog
In this article4
  1. How noindex works
  2. Why noindex matters
  3. Common mistakes with noindex
  4. How to act on it

How noindex works

Noindex is a directive carried in a page’s own response: either a meta robots tag in the HTML head, or an X-Robots-Tag in the HTTP headers, which is how non-HTML files such as PDFs are handled. A crawler fetches the page, reads the directive, and removes that URL from the index. The page still exists, still loads for visitors, and its links can still be followed — it simply stops being eligible to appear in results.

The detail that trips people up is that a crawler must be allowed to fetch the page before it can read the instruction. A URL disallowed in the site’s robots.txt file is never requested, so a noindex tag sitting inside it is never seen. Blocking a crawler and removing a page from the index are separate jobs, and doing both at once achieves neither.

Why noindex matters

Most websites produce far more URLs than anyone meant to publish: internal search results, tag and author archives, filtered product listings, thank-you pages, print versions, forgotten staging copies. Left in the index, these compete with the pages you actually want found, split signals across near-identical content, and spend crawler attention on addresses that will never earn a visit.

Noindex also protects pages that should exist but should not be discovered cold. A confirmation page is useful to the person who has just submitted a form and misleading to a stranger arriving from search — and every stranger who lands on it directly inflates your conversion counts with something that never happened.

Common mistakes with noindex

The costliest mistake is launching with the tag still switched on. WordPress carries a single setting that discourages search engines while a site is being built, and if it survives launch day every page ships with noindex and the site quietly stays invisible. Check it the hour the site goes live, not the week after.

The second is reaching for noindex when a canonical tag was the right tool. Two near-identical pages that both deserve to exist should point at one preferred version so their signals combine; noindex throws one of them away instead, links and all.

The third is treating it as privacy. A noindexed page is still public to anyone with the address, still readable, still shareable. If content must not be seen, it needs a password or a login, not a polite instruction to crawlers.

How to act on it

Decide indexability by template rather than page by page. Write down which types of URL on your site should be indexable — services, articles, locations, products — and which should not, then apply the rule in the template so new pages inherit the correct behaviour automatically. Page-level decisions taken one at a time drift within months.

Then verify rather than assume. Search Console’s URL Inspection tool reports what Google actually saw on the live address, which is the only account that counts, and a full crawl will surface any template that has picked up the directive by accident. Recheck after every migration, redesign or plugin change — this is routine work in any technical SEO review.

Do and do not

Do

  • Set indexability by template, not page by page
  • Confirm the launch checklist clears any development noindex
  • Verify with URL Inspection on the live address

Do not

  • Block a URL in robots.txt and noindex it together
  • Use noindex to keep private information off the web
  • Route internal links through pages you have noindexed

Questions people ask about this

Does noindex remove a page from Google straight away?

No. Google has to recrawl the page before it can act on the instruction, and how quickly that happens depends on how often it visits that URL. Frequently crawled pages update quickly; rarely visited ones can take considerably longer. If you need something gone urgently, use the removals tool in Search Console as a temporary measure while the tag does the permanent work.

Should I noindex a page or delete it?

It depends on whether the page still serves visitors. If people still use it — a policy page, a form confirmation, an internal reference — keep it and noindex it. If nothing links to it and nobody needs it, removing it and redirecting the address to the closest useful page is tidier, because it passes the value of any incoming links on to something live.

Does a noindexed page still pass value through its links?

Not dependably. A page kept out of the index for a long time is crawled less and less, and its links stop being a reliable route for search engines to discover or value other pages. Treat noindexed URLs as dead ends in your site structure: anything that matters should be reachable through links from pages that are themselves indexable.

Related terms

Found this useful?

Share it, or ask an AI to summarise it

Back to the glossary

Knowing the term is the easy part

Applying it to your own site and budget is the work. Book a call and I will tell you what actually applies to you.