Crawl Budget

What crawl budget actually is — crawl capacity plus crawl demand — what wastes it, and the honest test for whether your site is big enough to need to care at all.

First published: Jun 22, 2026 · Last updated: Jul 17, 2026 · Advanced
demand #5 in Crawling#11 in How Search Works#71 in Technical SEO#95 on the site
1 evidence signal on this page

Crawl budget is how much a search engine can and wants to crawl your site — crawl capacity (what your server can take) times crawl demand (popularity and staleness). It's not a ranking factor: more crawling won't lift positions. Most sites never need to manage it — Mueller says 100k URLs usually won't move the needle, and Google's own guide tells small or same-day-crawled sites not to bother. It matters mainly at 1M+ pages, 10k+ pages changing daily, or when lots of URLs sit in 'Discovered – currently not indexed.' The biggest lever is removing waste (faceted nav, duplicates, soft 404s, infinite spaces) so the budget lands on URLs that matter.

TL;DR — Crawl budgetThe number of URLs an engine will crawl in a timeframe. = crawl capacity limitCrawl rate is how fast a search engine crawler fetches pages from your site — the number of simultaneous requests it makes and the delay between them. Google sets it automatically based on your server's health; it's the supply side of crawl budget, not a ranking factor. (what your server can take) × crawl demandCrawl demand is the 'want' side of crawl budget — how much a search engine wants to crawl a site or URL, driven by popularity, staleness, and perceived inventory (plus temporary spikes from site moves). It's distinct from crawl rate/capacity, the 'can' side. (popularity + staleness + perceived inventoryCrawl demand is the 'want' side of crawl budget — how much a search engine wants to crawl a site or URL, driven by popularity, staleness, and perceived inventory (plus temporary spikes from site moves). It's distinct from crawl rate/capacity, the 'can' side.). It’s an efficiency concern, not a ranking signal. Internally it’s scheduling by importance gated by host load, not a flat per-site quota. Most sites can ignore it — Mueller pegs 100k URLs as “usually not enough,” and Google tells same-day-crawled sites to skip the guide. It bites at ~1M+ pages (weekly change), 10k+ pages (daily change), or when “Discovered – currently not indexedStoring a crawled page in the search index so it can appear in results. Crawled is not the same as indexed — Google selects what to keep, and indexing isn't guaranteed.” balloons. The highest-leverage move is cutting waste — faceted nav, duplicates, soft 404sA soft 404 is a URL that returns a success status code (usually 200 OK) even though the page is empty, missing, or shows a 'not found' message. It isn't a status code a server sends — it's a label search engines apply after comparing the response code against the rendered content, and they treat the page like a 404 for indexing., infinite spaces — so the budget consolidates on URLs that matter.

The two-factor model

Google defines it cleanly: “The amount of time and resources that Google devotes to crawlingCrawling is how search engines use automated bots (like Googlebot and Bingbot) to discover URLs and download pages. A page has to be crawlable to be indexed, but crawling on its own isn't a ranking factor. a site is commonly called the site’s crawl budget and it’s determined by two main elements: crawl capacity limit and crawl demand.” The 2017 framing from Gary Illyes is the one-liner I still reach for: crawl budget is “the number of URLs GooglebotGooglebot is Google's web crawler — the software that fetches pages so Google can index and rank them. It comes in two variants, Googlebot Smartphone (primary, under mobile-first indexing) and Googlebot Desktop, and runs an evergreen Chromium renderer. can and wants to crawl.” Evidence for this claim Google defines crawl budget using crawl capacity limit and crawl demand. Scope: Google Search crawling for larger sites. Confidence: high · Verified: Google: Large site crawl budget guide Keep this scoped: crawl budget governs fetching, not indexingStoring a crawled page in the search index so it can appear in results. Crawled is not the same as indexed — Google selects what to keep, and indexing isn't guaranteed.. A crawled URL still goes through a separate indexing decision — folding the two together overstates what crawl budget controls.

Crawl capacity limit (the supply side). This is “the maximum number of simultaneous parallel connections that Google can use to crawl a site, as well as the time delay between fetches.” It moves with your server’s health. Respond fast and clean and the limit rises; serve slow responses, 5xx errors, or 429s and GooglebotGooglebot is Google's web crawler — the software that fetches pages so Google can index and rank them. It comes in two variants, Googlebot Smartphone (primary, under mobile-first indexing) and Googlebot Desktop, and runs an evergreen Chromium renderer. backs off. In my How Search Works deck I list the same rate-limit triggers: server stability, slow responses, 5xx server errors, and 429429 Too Many Requests is an HTTP client-error status code that means a client sent too many requests in a given time window — a mechanism called rate limiting. Unlike other 4xx codes, Google treats 429 as a server-overload signal and slows crawling instead of removing content. (too many requests). This is the “can.”

Crawl demand (the demand side). Driven by popularity (how linked-to / important a URL is) and staleness (how long since it was last crawled, how often it changes). That same deck breaks demand into PageRankPageRank is Google's original recursive link-graph algorithm: a page's score depends on the scores of the pages linking to it, and in the published model each page's score is split across its outbound links (the simplified version: links are weighted votes). Google says it's evolved since launch but still part of its core ranking systems., how frequently the page changes, time since last crawl, and major site changes. Critically, Google flags perceived inventory as the lever you control most: “Without guidance from you, Google tries to crawl all or most of the URLs that it knows about on your site. If many of these URLs are duplicates, or you don’t want them crawled for some other reason… this wastes a lot of Google crawlingCrawling is how search engines use automated bots (like Googlebot and Bingbot) to discover URLs and download pages. A page has to be crawlable to be indexed, but crawling on its own isn't a ranking factor. time on your site. This is the factor that you can positively control the most.”

Demand sets the priority order; capacity determines how much of that ordered queue Googlebot can actually crawl. Source: Google Search Central

Crawl demand comes from popularity, genuine change, and the value of the URL inventory. It orders URLs in a priority queue. Crawl capacity comes from server response speed, stability, and error behavior. It limits how far Googlebot proceeds through that queue. Their interaction is the site's realized crawl budget, not a fixed daily URL quota.

© Patrick Stox LLC · CC BY 4.0 ·

A couple of structural facts that catch people out:

  • Budget is per hostname. https://www.example.com/ and https://code.example.com/ are two different hostnames, and therefore have separate crawl budgets.” Subdomains don’t share.
  • The different Googlebot types likely draw from one pool. In my own reporting, image, news, video, ads, and the rest appear to pull from the same per-site budget — I don’t have a current primary Google source pinning this down exactly, so treat it as a practitioner observation rather than documented policy. Either way, it’s worth checking the Crawl Stats reportA Google Search Console report (under Settings) that shows how Google has crawled your site over the last 90 days — total requests, download size, and average response time, broken down by response code, file type, Googlebot type, and purpose. It's only available for root-level properties (a Domain property or a URL-prefix property verified at the site's root).’s by-crawlerA crawler — also called a spider or bot — is an automated program that fetches web pages, extracts their links, and queues new URLs to visit. Search engines use crawlers to discover and download content for their index.-type breakdown if you suspect one type is elbowing out the rest.

What it really is internally: scheduling by importance

“Crawl budget” is an SEO-coined umbrella term. Internally it’s closer to scheduling gated by host load. As Illyes has described it, Google’s scheduler “sets a bucket of URLs in importance order and GoogleBot will crawl in that order based on the schedule the host load decided. If Google thinks your server can handle it, it will crawl the whole bucket, if not, it will stop.”

That reframes the whole topic. It isn’t a flat “you get N pages a day” quota — it’s a prioritized queue, and crawling tracks search demand. Illyes again: “If search demand goes down, then that also correlates to the crawl limit going down,” and “if you want to increase how much we crawl, then you somehow have to convince search that your stuff is worth fetching, which is basically what the scheduler is listening to.” The Search Relations team has explicitly called the “fixed daily page quota” idea a misconception.

Does your site actually have a crawl budget problem?

This is the most valuable section, so I’ll be blunt: most sites don’t need to worry about crawl budget. Google’s own guide opens with the de-escalation: “If your site doesn’t have a large number of pages that change rapidly, or if your pages seem to be crawled the same day that they are published, you don’t need to read this guide. For Google Search specifically, merely keeping your sitemapA sitemap is a file that lists the pages, images, videos, and other files on your site so search engines can discover them. It helps discovery, but submitting a sitemap doesn't guarantee crawling or indexing. up to date and checking your index coverage regularly is adequate.” Evidence for this claim Google says sites without many rapidly changing pages, or whose pages are crawled the day they publish, generally do not need crawl-budget guidance. Scope: Google's rough applicability guidance, not a guarantee for every site. Confidence: high · Verified: Google: Large site crawl budget guide

John Mueller gave the concrete number: “100k URLs is usually not enough to affect crawl budget (it’s <1/minute over 3 months).” If you’re under six figures of URLs and pages get crawled promptly, move on.

When it does matter, Google’s rough thresholds are:

  • Large sites — 1 million+ unique pages with content that changes moderately often (about weekly).
  • Medium or larger sites — 10,000+ unique pages with very rapidly changing content (daily).
  • Sites with a large portion of URLs classified as “Discovered – currently not indexed” in Search ConsoleGoogle's free tool for monitoring crawling, indexing, and search performance. — that’s the warning light that Google knows about URLs it isn’t getting to.

Google adds the disclaimer that “the numbers given here are a rough estimate… not exact thresholds.” And even on big sites, the nuance from my own work holds: it’s usually new, poorly-linked, or static pages that lag — not your popular ones.

Does crawl budget affect rankings? No.

Crawling is necessary to rank, but it is not a ranking signal. Google in 2017: “An increased crawl rateCrawl rate is how fast a search engine crawler fetches pages from your site — the number of simultaneous requests it makes and the delay between them. Google sets it automatically based on your server's health; it's the supply side of crawl budget, not a ranking factor. will not necessarily lead to better positions in Search results. Google uses hundreds of signals to rank the results, and while crawling is necessary for being in the results, it’s not a ranking signal.” I put it the same way in my Ahrefs guide: “More crawling doesn’t mean you’ll rank better, but if your pages aren’t crawled and indexed they aren’t going to rank at all.” Treat crawl budget as an efficiency problem, full stop.

What wastes crawl budget

Illyes published the canonical list of low-value-add URLs “in order of significance”:

  1. Faceted navigationFaceted navigation (faceted search, product filtering) lets visitors refine a list of products or content by attribute — price, color, size, brand, rating. The SEO problem: each filter combination can spawn a distinct crawlable URL, turning a small catalog into millions of near-duplicate pages that waste crawl budget and dilute ranking signals. and session identifiers — the #1 culprit, especially ecommerce filter/sort combinations that multiply URLs combinatorially.
  2. On-site duplicate contentThe same or very similar primary content reachable at more than one URL. There's no general duplicate content penalty — the real costs are possible signal dilution, the wrong URL getting chosen, and less-efficient crawling. — the classic technical variants: HTTP vs HTTPSHTTPS is the encrypted version of HTTP — it uses TLS to authenticate the server and protect data in transit between a browser and a website. Google announced it as a lightweight ranking signal in 2014 and today conditionally prefers HTTPS pages as canonical; Chrome marks plain HTTP pages 'Not Secure.', non-www vs www, trailing slashA trailing slash is the forward slash (/) at the end of a URL — example.com/page/ versus example.com/page. Except at the bare root domain, the two versions are different URLs to search engines, so you pick one format and enforce it. vs not, uppercase vs lowercase, default/index pages, and URL parametersThe `?key=value` data tacked onto the end of a URL after a question mark — used for tracking, sessions, filtering, sorting, and search — and one of the biggest sources of duplicate URLs and wasted crawling in SEO.. (Roughly 60% of the web is duplicate content, by Google’s own internal estimate.)
  3. Soft error pagessoft 404sA soft 404 is a URL that returns a success status code (usually 200 OK) even though the page is empty, missing, or shows a 'not found' message. It isn't a status code a server sends — it's a label search engines apply after comparing the response code against the rendered content, and they treat the page like a 404 for indexing. that return 200 keep getting crawled.
  4. Hacked pages.
  5. Infinite spaces and proxies — calendars, infinite-scroll paginationPagination splits a large set of content — product listings, blog archives, search results — across multiple sequentially numbered URLs. For SEO, each paginated page should be crawlable, indexable, and self-canonical; Google no longer uses rel=prev/next, but Bing still does. that duplicates, faceted combinations; the classic spider-trap patterns.
  6. Low-quality and spam content.

The cost is concrete: “Wasting server resources on pages like these will drain crawl activity from pages that do actually have value, which may cause a significant delay in discovering great content on a site.” On top of the list, long redirect chainsA → B → C instead of A → C. Each hop loses link equity and adds latency. “have a negative effect on crawling,” and slow, heavy pages make every fetch more expensive.

How to optimize it

The whole game is consolidating the budget onto URLs that matter:

  • Consolidate duplicates. Google: “Consolidate duplicate content to focus crawling on unique content rather than unique URLs.” Pick one host, one protocol, one trailing-slash convention; canonicalize; handle parameters.
  • Block truly worthless paths with robots.txt — but only paths you never want crawled. For faceted navigation, the usual options are blocking the parameter paths in robots.txt or using a # instead of a ? so the URLs aren’t crawlable in the first place.
  • Don’t use noindex to save budget. Google: “Don’t use noindexNoindex is a directive that tells search engines to keep a page out of their index, so it won't appear in search results. It works only on pages a crawler can actually fetch — a page blocked in robots.txt can never be noindexed., as Google will still request, but then drop the page when it sees a noindex meta tag or header in the HTTP response, wasting crawling time.” The request still costs you. Block at robots.txt if you never want it fetched.
  • Don’t expect robots.txt to reallocate budget. “Google won’t shift this newly available crawl budget to other pages unless Google is already hitting your site’s serving limit.” Blocking junk is good hygiene, but it doesn’t hand the freed-up crawls to your good pages unless you were capacity-bound.
  • Fix soft 404s; return real 404/410 for gone pages. “A 404 status code is a strong signal not to crawl that URL again.”
  • Shorten redirectA redirect sends browsers and crawlers from a requested URL to a different one. An HTTP redirect specifically is a 3xx status code paired with a Location header; meta refresh and JavaScript redirects achieve a similar navigation without being a 3xx response themselves. Permanent redirects (301/308) are Google's signal the target should be canonical; temporary ones (302/303/307) aren't. chains, keep sitemaps current (honest lastmod), and improve server speed.
  • Strengthen internal linksAn internal link is a hyperlink from one page on a website to another page on the same website. Internal links help search engines discover your pages and pass ranking signals (PageRank and anchor-text context) between them. to important and new pages — easier than anything else because you fully control it.

And the two — only two — ways Google says you can actually increase budget: “Add more server resources… [and] optimize your content’s quality.” Note the trap there: a faster server lifts the capacity ceiling, but if demand is low Google still crawls less. You need both.

How to measure it

  • GSC > Settings > Crawl Stats report — total crawl requests over time, average response time, host statusThe at-a-glance availability indicator at the top of Google Search Console's Crawl Stats report. It shows whether Googlebot hit significant problems reaching your site in the last 90 days across three checks — robots.txt fetching, DNS resolution, and server connectivity., and breakdowns by response code, file type, and Googlebot type. This is Google’s own view of how it crawls you.
  • Server log file analysisLog file analysis is reading a web server's raw access logs to see exactly which URLs search engine crawlers actually requested, when, how often, and what status code they got. Unlike crawl tools or Search Console, logs are the unsampled, ground-truth record of what really happened. — the ground truth. Real Googlebot hits by URL pattern, so you can see crawl waste and uncrawled important pages. Verify the bot is genuinely Googlebot via reverse + forward DNS or Google’s published IP ranges (plenty of fake bots spoof the user-agent).
  • Discovered – currently not indexedA Google Search Console Page Indexing status meaning Google knows the URL exists but hasn't crawled it yet — the Last Crawl date is empty. Often a crawl-capacity or crawl-demand (site-quality) signal. in GSC — treat a growing pile here as a crawl-budget warning light: Google knows about the URLs but isn’t getting to them.
TIP Find where crawler requests are being spent

A sitewide crawl total is not enough; separate live pages from redirects, gone URLs, and server errors before deciding what to fix.

Upload a representative access-log sample and inspect the exact paths behind wasted status groups with my free Log File Analyzer Free

  1. Include status, path, user-agent, and timestamp fields so the result can separate crawler activity by outcome.
  2. Verify crawler identity before counting requests under a Googlebot name.
  3. Fix the exact broken paths, redirect chains, and server errors instead of optimizing the aggregate crawl count.
This sample turns a vague crawl-budget concern into exact response groups and paths to investigate.

The finding reports that 64 of 129 Googlebot requests, or 49.6 percent, went to non-200 responses. It breaks that total into 40 requests to 404 or 410 URLs, 12 redirects, and 4 server errors, then directs the reader to the exact paths in the wasted-URL table.

Bing and other engines: “crawl efficiency”

Bing reframes the topic as crawl efficiency rather than budget. Fabrice Canel’s definition: “The crawl efficiency is how often we crawl and discover new and fresh content per page crawled.” The goal is to “crawl an URL only when the content has been added (URL not crawled before), updated (fresh on-page context or useful outbound links).” Bing’s blunt philosophy: “Less is more for SEO. Never forget that. Less URLs to crawl, better for SEO.”

Bing’s preferred fix is IndexNowIndexNow is an open push protocol that lets you instantly tell participating search engines (Bing, Yandex, Naver, Seznam, and Yep) which URLs you've added, changed, or removed via a simple HTTP request — and one submission is shared across all of them. Google does not use it. — push changed URLs so bingbotBingbot is Microsoft Bing's primary web crawler — the bot that discovers, fetches, and renders pages to build the Bing index. That index also powers Yahoo, DuckDuckGo, Ecosia, and Microsoft Copilot, so Bingbot's reach is far wider than Bing's own search-market share. doesn’t need exploratory crawls — and Crawl Control in Bing Webmaster ToolsMicrosoft's free portal for monitoring and improving how a site appears in Bing search — the peer to Google Search Console, plus IndexNow instant indexing, richer backlink data, and keyword volumes. Because Bing's index also feeds Microsoft Copilot, it doubles as a window into AI-search visibility., which lets you schedule when bingbot crawls by hour to protect server load. This is a real Google/Bing divergence worth noting: Google deprecated its old crawl-rate limiter in Search Console, while Bing still lets you actively shape the crawl schedule.

Crawl budget myths, corrected

  • “Every site should optimize crawl budget.” No — most shouldn’t. Same-day crawling and sub-100k URLs mean you’re fine.
  • “More crawling = better rankings.” No. Crawling is necessary but not a ranking signal.
  • “It’s a fixed daily page quota.” No — it’s importance-driven scheduling gated by host load.
  • “Use noindex to save budget.” No — Google still requests the page first.
  • “Block pages in robots.txt to give other pages more budget.” Generally no, unless you’re already at your serving limit.
  • “A faster server alone raises your budget.” It lifts the capacity ceiling only; low demand still means fewer crawls.

For the broader pipeline this sits inside — discovery, the crawl scheduler, renderingTurning HTML, CSS, and JavaScript into the final visual page and DOM., and how crawling differs from indexing — see the crawling hub. The sibling topics (crawl rate, crawl frequencyCrawl frequency is how often a search engine comes back to re-fetch a page it already knows about. Popular pages that change often get refreshed many times a day; stable pages can go weeks or months between crawls — and you influence it indirectly, not by setting a dial., spider trapsA spider trap (also called a crawler trap) is a site structure that generates an effectively infinite number of URLs — from faceted filters, calendars, session IDs, or redirect loops — so crawlers waste their budget on low-value, near-duplicate pages instead of your real content., and log file analysis) each go deeper on one piece of this.

Add an expert note

Pin an expert quote

New person? Create their unclaimed profile at /admin/experts/ → Pin a quote first.