What Is Noindex? Definition and Why It Matters

Noindex is a directive — most often placed in a page’s robots meta tag as meta name=”robots” content=”noindex”, or delivered as an HTTP header — telling search engines not to include that page in their search results, even if the page is otherwise perfectly crawlable.

When to use noindex on your own site

• Thank-you pages, internal search results, and account or checkout pages that offer no value to searchers.
• Filtered and sorted views that duplicate the content of a cleaner category page (faceted navigation).
• Thin pages you want to keep available for logged-in users or internal purposes, but don’t want competing for rankings (index bloat).
• Staging or test versions of pages that should never appear in search at all.

Why noindex matters when you’re buying links

This is where the concept becomes directly relevant to link building. If the page hosting your guest post or placement carries a noindex tag, it will not appear in search results, and over time its links are unlikely to be counted as part of the normal link graph search engines rely on. You can pay for a placement, see it published, and still get essentially nothing from it if the host page itself is noindexed — sometimes deliberately, on sites that quietly try to have it both ways with buyers.

How to check

Before approving any placement as complete, view the live page’s source code (or use a browser extension) and search for the word “noindex” in the head section. If it’s present, the placement should be flagged and resolved with the publisher before you consider the order finished (live-post checklist).

Noindex versus robots.txt — a distinction that trips people up

Robots.txt controls whether a page gets crawled at all; noindex controls whether a page that has been crawled gets indexed. These are not interchangeable. A page blocked entirely by robots.txt can never be crawled, which means a search engine never even sees its noindex tag — so blocking a page with robots.txt is not a reliable way to keep it out of search if it’s already linked to from elsewhere (robots.txt).

A worked example

Imagine a publisher runs a “sponsored content” section of their site that they’ve quietly noindexed to keep it from diluting their main blog’s perceived quality in search, while still selling placements in that section to unsuspecting buyers. A buyer who never checks the page source would see a live URL, a published article, and assume the placement is working exactly as intended — while in reality the page will never surface in search and its link is far less likely to be counted as part of the normal web graph.

Related terms

Robots.txt, canonical tag, guest post red flags.

Noindex and the “index, follow” alternative

It’s worth knowing that noindex and nofollow are independent settings, even though they’re often mentioned together. A page can be set to noindex, follow — meaning it won’t appear in search results itself, but its outbound links are still treated as active for crawling purposes. This combination is often the right choice for genuinely useful but non-canonical pages, such as certain filtered views, where you still want the links on the page to be discovered.

Temporary versus permanent noindex

Some pages are noindexed temporarily and deliberately — during a redesign, a content refresh, or before a page is genuinely ready. The risk is forgetting to remove the directive once the page is ready to go live, effectively hiding a finished page indefinitely by accident. Keeping a simple checklist for launches, including a noindex check, avoids this easy-to-miss mistake.

Noindex on paginated or duplicate-heavy sections

Large content archives, tag pages, and author pages are common candidates for noindex, since they often duplicate content already indexed elsewhere on more canonical pages. Applying noindex broadly across these low-value sections, while leaving genuinely unique content indexable, is a routine and effective way to keep an index focused on pages actually worth ranking.

Noindex and canonical tags used together incorrectly

Combining a noindex directive with a canonical tag pointing at a different URL sends a genuinely confusing, contradictory signal — you’re simultaneously saying “don’t index this” and “this page’s authority belongs to that other page.” Pick one clear approach per page rather than layering both mechanisms together without a specific reason.

Keep a short, explicit list of which page templates or sections are meant to carry noindex by design, so anyone reviewing the site later can distinguish an intentional directive from an accidental leftover.

When migrating platforms, explicitly re-verify every noindex directive survived the move correctly, since some CMS migrations silently drop meta tags that weren’t part of the standard content fields being transferred.

Where to go next

Make checking for noindex a standard step in your live-post checklist, and when sourcing new placements, look for publishers with a track record of clean, indexable pages on the marketplace.

Browse every term in the link building glossary.

Frequently asked questions