Noindex and Crawl Budget: What Actually Happens

Noindex is one of the most misunderstood directives in technical SEO. The common assumption: if you add noindex to a page, Google stops crawling it and passes no value to the pages it links to.

Neither part is correct.

Google’s documentation is clear that noindex tells the search engine not to index a page. It does not say anything about crawling, and it says nothing about link equity. The practical effect on crawl flow and internal link signals is a separate question from what most articles explain.

This article breaks down what actually happens when a page with active internal links gets a noindex directive, and what it means for how you audit and manage crawl budget.

About the author: Jay Dodiya is an SEO QA engineer at 24Squad who tracks indexation defects across client sites. The noindex misconceptions in this guide come directly from audit findings — the most common being teams who add noindex believing it will reduce crawl load, only to discover Googlebot is still crawling the pages and still following their links.

• Noindex stops indexing but not crawling: Googlebot will still visit and follow links on a noindexed page unless those links are also tagged with nofollow or the page is blocked at robots.txt.
• Noindex does not stop link equity passing: links on a noindexed page still pass PageRank to their targets, so a noindexed page that links to your key pages is not a neutral signal — it is still distributing equity.
• Adding noindex is not a crawl budget fix: if the goal is to stop Googlebot from consuming resources on a page, noindex alone does not achieve that; robots.txt Disallow is required to prevent crawling entirely.
• Robots.txt blocks reading the noindex directive: if a page is blocked at robots.txt, Googlebot cannot fetch it to see the noindex meta tag, which can create a confusing crawl loop.
• Audit noindexed pages for valuable inbound links: a page with strong external backlinks carrying noindex is still passing link equity through its outbound links — removing the noindex or blocking at robots.txt and using noindex together are separate decisions with different implications.

The short answer

Noindex tells Google: do not include this page in search results. It does not tell Google: do not crawl this page or do not follow links on this page.

Googlebot can and does crawl noindexed pages. It will also follow and pass link equity through links on those pages, unless those links are also tagged with nofollow.

The practical implication: adding noindex to a page is not a crawl budget fix. If the goal is to stop Googlebot from consuming resources on a page, noindex does not achieve that on its own.

What Google actually says

Google’s search Essentials documentation states that the noindex directive prevents a page from appearing in search results. It does not prevent crawling unless combined with nofollow or blocked at the robots.txt level.

The robots.txt approach is separate from the meta tag approach. If a page is blocked via robots.txt, Googlebot cannot even fetch the page to read the noindex directive. If the page is accessible but carries noindex in the HTML head, Googlebot can still visit, still read the noindex, and still choose to crawl or not crawl based on other signals.

This distinction matters when auditing why certain pages consume crawl budget despite being marked noindex.

What happens to a noindexed page that links to other pages

When a page carries noindex and Googlebot encounters it during crawling, the crawler will typically:

1. Read the page content and the noindex directive
2. Not index the page
3. Follow and crawl any links on the page unless those links carry nofollow

The link equity or PageRank associated with those links continues to flow. Noindex does not create a barrier to internal link signals. A page with noindex on it does not become a dead end in the crawl graph unless something else stops the crawl — such as nofollow, canonical pointing elsewhere, or robots.txt blocking.

This is why SEOs who use noindex as a substitute for proper crawl management often see unexpected results. Pages that should not be crawled continue to consume the crawl budget because noindex alone does not discourage crawling.

Common scenario: thin pages with internal links

The pattern appears often on large sites with thin content: archive pages, calendar pages, filtered views, paginated sequences, or pages that exist for navigation but hold little independent search value.

An SEO adds noindex to these pages to keep them out of search results. The intent is correct for index management. But the crawl flow is unaffected unless the implementation also addresses how Googlebot discovers and prioritizes these pages.

If a noindexed thin page has 50 internal links pointing to it from active content, Googlebot will continue to visit it regularly. The noindex directive prevents indexing. It does not reduce crawl frequency.

The practical check: look at Google Search Console’s crawl stats report. If low-value noindexed pages are consuming significant crawl requests, noindex alone is not the fix.

Log file analysis complements GSC crawl stats — log file analysis shows you the exact crawl frequency Googlebot applies to noindexed URLs versus high-value pages, letting you quantify the waste and target the right fix.

The noindex plus nofollow combination

Adding both noindex and nofollow in the meta tag:

<meta name="robots" content="noindex, nofollow">

This tells Google: do not index this page, and do not follow links on it. The crawling behavior changes — Googlebot will still attempt to crawl the URL to read the directive, but it will not pass link equity through the page’s links.

This is closer to what most practitioners assume noindex does by default. But even this combination does not stop Googlebot from requesting the page. It only controls what happens after the page is fetched.

For crawl budget management, the stronger option is often to block the URL at the robots.txt level. A Disallow: rule stops Googlebot from fetching the page entirely. The tradeoff is that Googlebot will also cannot see the noindex directive, so it may continue to crawl the URL if other signals point to it.

What this means for your audit workflow

When auditing a site for crawl efficiency, noindex alone is insufficient for managing low-value pages. The audit should separate three questions:

Is the page meant to be indexed? If yes, check title, meta description, content quality, and structured data. Noindex is not the tool here.

Is the page not meant to be indexed? If yes, confirm noindex is present and correctly formatted. Then check whether the page is still consuming meaningful crawl resources.

Is the page consuming crawl budget without contributing to search visibility? If yes, noindex alone is not the answer. Consider robots.txt blocking for pages that should never be crawled, or noindex, nofollow for pages that should be crawled but not indexed and not pass link equity.

The redirect chains audit workflow catches a related pattern: pages that redirect through multiple hops consume crawl budget on every visit, and the equity leakage compounds with each hop.

The combination approach matters. A page that is noindex but still followed means Googlebot will keep visiting it as long as other pages link to it. If those links are from thin or low-value sources, the crawl budget is being spent without return.

The internal linking implication

Noindexed pages that sit deep in a site architecture and receive links from other noindexed pages can form crawl traps. Googlebot enters the chain through a followed link, encounters noindex, does not index, but continues to follow links because they are not nofollowed.

If that chain of noindexed pages links back to high-value content, link equity still flows through the chain. But if the chain is long and the pages are isolated from indexed content, the crawl budget spent traversing the chain produces no indexing benefit.

The practical check: use a crawl tool to map which noindexed pages link to other noindexed pages. Identify chains where crawl is being consumed without producing indexed content.

When noindex is the right tool

Noindex is correct when:

• A page exists for functional purposes but has no search value (cart pages, thank-you pages, internal search results)
• A page is generated dynamically and cannot be properly optimized for search
• A page contains duplicate or near-duplicate content that should not compete in search results
• A page is behind a login or paywall and is not intended for search visibility

In all these cases, noindex prevents the page from appearing in search results. It does not prevent crawling unless paired with nofollow or robots.txt blocking.

The decision framework depends on what you are trying to achieve:

• Keep page out of search results only: noindex
• Keep page out of search results and stop passing link equity: noindex + nofollow
• Stop Googlebot from accessing the page entirely: robots.txt disallow (with the understanding that Googlebot cannot read any directives on that page)

The SEOKit24 angle

The useful thing SEOKit24 adds to this topic is the distinction between index management and crawl management. Most articles treat noindex as a solution for both. They are separate problems. Managing what Google indexes requires noindex. Managing what Googlebot crawls requires a different set of directives and architecture decisions.

Use the SEOKit24 SERP Preview to check whether noindexed pages are still appearing in unexpected search situations, and the Sitemap Validator to audit your robots.txt configuration.

Frequently asked questions

Does noindex stop Googlebot from crawling a page?

No. Noindex only prevents indexing. Googlebot can still crawl the page to read the directive. To stop crawling, use robots.txt blocking or add nofollow to the directive.

Does noindex stop PageRank from flowing through links on the page?

No. A noindexed page still passes link equity through its links unless those links also carry nofollow or the page is blocked at robots.txt level before the directive can be read.

Can a noindexed page still appear in Google search?

In most cases, no. If Googlebot reads the noindex directive, the page will not appear in search results. However, if the page is blocked at robots.txt, Googlebot cannot read the noindex directive and the page may still be indexed based on links from other pages.

Is noindex better than robots.txt blocking for low-value pages?

It depends on the goal. If the page should be crawled but not indexed, noindex is correct. If the page should not be crawled at all, robots.txt blocking is more efficient for crawl budget. Using both together creates the risk that Googlebot cannot read the noindex directive.