Crawl Budget: How Google Decides What to Crawl
On this page: Quick jump links to help you
- What Is Crawl Budget
- Why Crawl Budget Matters
- Factors That Affect Crawl Budget
- How to Check Your Crawl Budget
- Crawl Budget Optimization Strategies
- Common Crawl Budget Wasters
- Crawl Budget for Large and Enterprise Sites
- Monitoring and Maintaining Crawl Efficiency
- Frequently Asked Questions
Crawl budget is one of the most important—and most misunderstood—concepts in technical SEO. It is the number of URLs that Googlebot will fetch from your site within a given timeframe. Every time a search engine bot visits to discover and index content, it is drawing down that allowance. Understanding how much you have, and how to spend it well, can mean the difference between new content being indexed within hours and waiting weeks for crawling.
For small to medium-sized websites with clean architecture and reasonably fast load times, this is rarely a primary concern at all. Search engines will crawl your content frequently enough without any help from you. For large enterprise websites, e-commerce sites with tens of thousands of pages, or sites with duplicate content problems, however, crawl efficiency becomes critical. Waste means new content takes longer to be discovered, critical pages are crawled less frequently, and your overall search visibility suffers.
This guide covers what it is, why it matters, which factors affect it, how to monitor it and, most importantly, how to optimize it. By the end you will understand how to maximize your site's crawl efficiency and ensure search engines are spending their resources on your best content.
What Is Crawl Budget
Crawl budget is the number of URLs that Google (or other search engines) will crawl on your website per visit. Google uses a crawler called Googlebot to systematically visit web pages, discover new content, and update its index with the latest information. However, Googlebot doesn't have unlimited resources. Google has thousands of websites to crawl, so each site receives a finite amount of crawl attention.
Your site's share of it is determined by two key factors: crawl capacity (how much crawling Googlebot can technically handle on your site given bandwidth and server load) and crawl demand (how much Google wants to crawl your site based on its importance, update frequency, and other signals).
Crawl capacity is limited by your server's ability to handle bot requests without slowing down user access. If your server can't handle many simultaneous requests, it might request that Googlebot slow down crawling. If your server is fast and responsive, Googlebot can crawl more frequently.
Crawl demand is influenced by how frequently your content updates, how popular your site is, how much internal linking points to each page, and signals about content importance. Sites with frequent updates, high popularity, and good link profiles have higher crawl demand—Google wants to crawl them more often.
Think of it as a daily allowance. If yours is 10,000 URLs per day, Googlebot will crawl approximately 10,000 different URLs each day it visits your site. If you're wasting budget by having Googlebot crawl duplicate pages, broken links, and low-value URLs, you have fewer resources available for crawling your actual valuable content.
It's important to understand that crawl budget is NOT the same as indexation. Crawling comes first—Google visits and reads the page. Indexation happens when Google decides to add the page to its index after crawling it. You can crawl a page without indexing it (if it has noindex tags for example). Improving it helps ensure important content gets crawled, but it does not guarantee indexation.
Why Crawl Budget Matters
Understanding why it matters helps you prioritize your optimization efforts:
Faster Content Discovery: When new content is published on your site, Googlebot needs to discover it. If your allowance is limited and being spent on low-value pages, new important content might not be crawled for weeks. Once that waste is cleared, new content gets crawled within days or even hours, allowing it to be indexed and rank much faster.
Timely Updates: If you frequently update existing content (like prices, inventory, or article revisions), search engines need to recrawl those pages to discover the updates. If your allowance is constrained, frequently-updated pages will not be recrawled as often, and outdated information might appear in search results. Managing it well ensures that important pages are recrawled at appropriate intervals.
Full Site Indexation: For large sites, not all pages get indexed. With a limited allowance, only a portion of your site might be crawled regularly. Crawlability optimization ensures that the most important pages get priority crawling, improving the percentage of your site that's indexed.
Reduced Crawl Depth Issues: If your site has a deep directory structure, Googlebot might not reach the deepest pages because the allowance is exhausted on shallower layers. By removing that waste, you ensure pages at all levels of your hierarchy get discovered.
Avoiding Crawl Timeouts: For very large sites, Googlebot might time out before crawling the entire site if crawl is inefficient. Optimization helps Googlebot complete its crawl of your site more efficiently, preventing timeouts.
Better Resource Allocation: Every crawl request uses your server's resources and bandwidth. By trimming the waste, you reduce unnecessary crawling, which improves performance for actual users and reduces server load costs.
For large sites with thousands or millions of pages, this work is essential to ensuring critical content gets discovered and indexed. Even on smaller sites, managing it well is a mark of basic SEO professionalism.
Factors That Affect Crawl Budget
Multiple factors influence how much of it your site gets. Understanding them helps you know where to focus your optimization efforts:
| Factor | Impact | What It Means | How to Improve |
|---|---|---|---|
| Server Speed | High | Faster responses allow more crawling | Optimize page load times, server response time |
| Crawl Errors | High | 5xx errors slow crawling; timeouts waste budget | Fix 5xx errors; monitor server health |
| Site Size | High | Larger sites need more of it | Remove unnecessary pages; consolidate duplicates |
| Site Popularity/Authority | High | Popular sites get higher crawl demand | Build backlinks; improve brand presence |
| Update Frequency | Medium | Frequently updated sites get crawled more often | Regular content updates; sitemap updates |
| Internal Link Structure | Medium | Well-linked pages are crawled more often | Improve internal linking architecture |
| Duplicate Content | High | Duplicates waste fetches | Use canonicals; fix duplicate content issues |
| URL Parameters | Medium | Parameter variations create multiple crawlable URLs | Manage parameters; use canonical tags |
| Redirect Chains | Medium | Multiple redirects waste crawl requests | Fix redirects to be direct; use 301 for permanent changes |
| Robots.txt Blocking | Low | Blocked URLs aren't crawled but still count against requests | Use robots.txt efficiently; don't block necessary resources |
| Broken Links | Low-Medium | 404s and dead links waste crawl requests | Fix broken internal links; implement 301 redirects |
| XML Sitemaps | Low-Medium | Large, outdated sitemaps confuse crawl priorities | Keep sitemaps updated; remove deleted URLs |
| Noindex Tags | Medium | Pages marked noindex still get crawled but not indexed | Review noindex implementation; don't noindex pages you want indexed |
| Soft 404 Errors | Medium | Pages that look like 404s but return 200 confuse crawlers | Implement proper HTTP status codes |
| robots.txt Size | Low | Extremely large robots.txt files can affect parsing | Keep robots.txt concise; consolidate rules |
The most impactful factors are server speed, crawl errors, site size, and site popularity. Improving any of these has the biggest effect on crawl efficiency. Parameter variations, duplicate content, and redirect chains are secondary but still important optimization opportunities.
How to Check Your Crawl Budget
Before optimizing anything, you need to understand your current situation. Here is how to read it:
Google Search Console Stats Report: The most direct way to see your crawl activity is Google Search Console's Stats report. Go to Settings → Coverage & Crawl → Crawl Stats. This shows you: the total crawl requests per day (your approximate daily allowance), requests blocked by robots.txt, KB downloaded per day, peak crawl hour, and average response time. This data tells you how much Googlebot is visiting your site and how it's distributed across time.
Analyze Coverage Report: The Coverage report in Google Search Console shows you: how many pages are indexed, how many are excluded (and why), and how many have errors. If you have high exclusion rates—particularly "Duplicate, Google chose different canonical" or "Excluded by robots.txt"—you are likely wasting fetches.
Monitor Page Crawl Frequency: Use the URL Inspection tool in Google Search Console to check individual pages. The inspection results show you when the page was last crawled and when it's scheduled to be crawled next. Pages you update frequently should be crawled more often. If important pages are not being crawled regularly, you have a crawl efficiency issue.
Server Log Analysis: Analyze your server logs to see Googlebot's crawl patterns. Look at the User-Agent "Googlebot" in your logs and track which URLs are being crawled, how often, and what response codes are being returned. Large numbers of 404s or 5xx errors being crawled indicate wasted fetches. Web server log analysis tools or Google Cloud Console can help analyze this data.
Crawl Simulation Tools: Tools like Screaming Frog or other SEO crawlers can simulate crawling your site and show you what Googlebot might encounter. These tools help you understand your site's crawlability, identify crawl traps, and simulate your site structure from Googlebot's perspective.
Internal Link Depth Analysis: Use SEO tools to analyze how deep pages are from your homepage. If important pages are buried 5+ clicks deep, they might not be crawled as often. Analyze your internal link structure to see if pages are appropriately linked.
XML Sitemap Analysis: Review your XML sitemaps to ensure they're only including important pages. If your sitemaps include thousands of duplicate, low-quality, or outdated pages, you are directing fetches toward waste. Clean up sitemaps to focus on important content.
Crawl Budget Optimization Strategies
Once you understand your current situation, implement these strategies:
Improve Server Speed and Response Time: This is often the highest-impact optimization. Faster page load times allow Googlebot to crawl more pages per visit. Work with your hosting provider or technical team to optimize server response times. Reduce TTFB (Time to First Byte), implement caching, and optimize server resources. Every millisecond improvement allows more crawling in your budget.
Fix Crawl Errors: Monitor your server logs and Google Search Console for crawl errors. Fix 5xx server errors immediately—these slow down crawling significantly. Address timeouts and high-latency pages. Even one frequently-crawled page with slow response times can waste a significant share of the allowance.
Eliminate or Consolidate Duplicate Content: Duplicate content is a major source of wasted fetches. Implement canonical tags on duplicate pages or use 301 redirects to consolidate. Every instance of duplicate content represents a fetch that could have gone to unique content instead.
Remove Unnecessary URL Parameters: Parameter-based URLs create multiple paths to the same content. Remove unnecessary parameters. If sorting, filtering, or session IDs create parameter variations, consolidate them. Configure parameter handling in Google Search Console to tell Google which parameters should be consolidated.
Fix Redirect Chains: If a URL redirects to another URL that redirects again (A → B → C), Googlebot uses three crawl requests to reach the final content. Convert redirect chains into direct redirects (A → C directly). Use 301 redirects (not 302) for permanent redirects, and regularly audit your redirects.
Optimize Internal Link Structure: Ensure important pages are linked from your homepage or main navigation. Pages that are only reachable through deep directory structures or aren't internally linked won't be crawled as often. Improve your information architecture so important pages are accessible via shorter, direct paths.
Remove or Block Low-Value Content: Use robots.txt to block crawling of pages that don't need to be indexed: login pages, staging environments, duplicate archive pages, etc. This frees up capacity for important content. Be careful not to block important resources like CSS or JavaScript.
Clean Up Your Sitemaps: XML sitemaps should only include important, indexable pages. Remove deleted pages, redirect targets, and low-priority pages from your sitemaps. Update sitemaps regularly to reflect your current site structure. Large, outdated sitemaps can confuse crawl priorities.
Implement Dynamic Sitemaps: For large sites, implement sitemaps that dynamically exclude pages based on rules (pages with noindex tags, redirects, etc.). This ensures your sitemaps always reflect your actual crawlable content.
Improve Site Authority: Sites with higher authority and popularity are crawled more heavily. Build backlinks, improve brand presence, and establish topical authority. This signals to Google that your site is important and deserves more crawl resources.
Common Crawl Budget Wasters
Recognize and eliminate these common culprits, each of which quietly consumes fetches that should have gone somewhere better:
Infinite Parameter Variations: If your site generates new URLs for every combination of parameters (color=red&size=large&material=cotton, etc.), you've created infinite URLs from the same core content. Use canonical tags on these variations. Alternatively, limit indexable parameter combinations or use robots.txt to prevent crawling of low-value variations.
Print and PDF Versions: If every page has a printer-friendly or PDF version with a different URL, you're doubling your crawlable content. Use canonical tags on these versions pointing to the main page. Consider removing separate print versions entirely, relying on CSS print styles instead.
Pagination without Proper Structure: Pagination pages (page 2, page 3, etc.) with preview content on each page can consume a great many fetches. Use proper rel="next" and rel="prev" tags. Consider implementing a "view all" option for important content lists instead of multiple paginated pages.
Session-Based URLs: If your site appends session IDs to URLs, you're creating different URLs for the same content based on user sessions. Consolidate with canonical tags or configure your server to use cookies instead of URL parameters for sessions.
Infinite Scrolling Pages: Some JavaScript-heavy sites with infinite scrolling create new URLs as users scroll. Avoid this pattern where possible. If you must use it, ensure paginated alternatives exist for search engines.
Faceted Navigation Without Management: E-commerce and listing sites with extensive filters can create hundreds of thousands of faceted URLs. Use canonical tags on filtered results or block excessive filter combinations in robots.txt.
404 Errors on Frequently-Crawled URLs: If Googlebot continues to crawl URLs that consistently return 404 errors, they are wasting fetches. Remove these broken URLs from internal links and sitemaps, or implement 301 redirects to working pages.
Noindex Pages That Are Still Crawled: Pages with noindex tags still get crawled but not indexed—pure waste. If a page has noindex, block it from crawling entirely with robots.txt. If you don't want it indexed, you probably don't need it crawled either.
Staging and Dev Environments: If staging or development versions of your site are accessible to Googlebot, they are consuming fetches that should be going to production. Block these environments with robots.txt or authentication to prevent crawling.
Calendar Archives: Calendar-based archive systems (WordPress date archives) can create thousands of pages with minimal content. Consolidate calendar archives or block excessive archive depth with robots.txt.
Crawl Budget for Large and Enterprise Sites
Large sites and enterprise websites with hundreds of thousands or millions of pages face challenges the guidance above only partly covers:
Crawl Budget is More Critical: On a large site this is a constant consideration rather than a one-off cleanup. It is about the strategic allocation of a genuinely limited resource. You must make decisions about which pages are worth crawling and which aren't.
Prioritization Strategy: Develop a clear strategy for crawl prioritization. Identify your most important pages (revenue-generating products, key content, etc.) and ensure these get higher link authority and are easily crawlable. Less important content can have lower crawl priority.
Track Allocation by Section: Large sites often benefit from understanding how fetches are distributed across sections. If your e-commerce section is getting less attention than your blog, you may want to redistribute priorities. Use crawl analytics to understand which sections get attention.
Use Core Web Vitals Optimization: Technical SEO improvements like Core Web Vitals optimization directly raise crawl capacity. Faster pages allow more crawling, which makes performance work part of the strategy rather than separate from it.
Implement Efficient 404 Handling: Large sites accumulate broken links over time. Implement monitoring to identify and fix broken internal links before they accumulate into thousands of 404 crawls.
Content Archiving Strategy: For publishing sites, implement a strategy for archiving old content. Very old content might not need frequent crawling. Consider separate archive sections with lower crawl priority.
Version Management: If your site has multiple versions (language versions, device-optimized versions, etc.), use hreflang tags and appropriate canonical implementation to avoid crawling redundant versions.
Regular Crawl Audits: Large sites should conduct quarterly or monthly crawl audits using the strategies outlined above. Identify new crawl inefficiencies quickly before they accumulate into major waste.
Monitoring and Maintaining Crawl Efficiency
None of this is a one-time effort. Ongoing monitoring is what keeps a site efficient over time:
Regular Google Search Console Monitoring: Check the Crawl Stats report monthly. Look for trends in crawl requests. If crawl suddenly increases without site growth, you might have introduced crawlable duplicates or parameters. If crawl decreases despite adding content, your site might be becoming less crawlable.
Track Indexation Rates: Monitor what percentage of your site is indexed. If your indexed percentage is decreasing despite not removing content, crawl efficiency issues might be to blame. Monitor URL additions vs. indexed additions—a gap suggests crawlability problems.
Page Discovery Latency: When you publish new content, track how quickly it's crawled and indexed. Use the URL Inspection tool to see when recently-published content is crawled. If discovery is slow, taking weeks instead of days, this is very often the reason.
Automated Monitoring Setup: Implement monitoring alerts in your server infrastructure to notify you of: increased 5xx errors, slow response times, crawl drops, or unusual crawl patterns. Early detection allows quick response to problems.
Quarterly Crawl Efficiency Reviews: Every quarter, conduct a review of your crawl efficiency. Analyze server logs, check for new duplicates or parameters, verify sitemaps are current, and review internal link structure. Make improvements based on findings.
Update Sitemaps Automatically: Implement automated sitemap generation that includes only current, indexable content. Ensure sitemaps are updated whenever content is published or removed. Stale sitemaps pointing to deleted content waste fetches.
Performance Monitoring Integration: Integrate this monitoring with your performance monitoring. Improved page load times directly improve crawl capacity. Monitor Core Web Vitals and page speed metrics alongside crawl stats.
Cross-Functional Communication: Ensure your SEO, development, and infrastructure teams communicate about crawl issues. A developer might implement features that create parameter variations without realizing the crawl impact. Regular communication prevents these issues.
Work through the strategies above and you can be reasonably confident that Googlebot is spending its resources where they matter most: on your valuable, unique content. On large sites especially, crawl budget management is a standing responsibility rather than a project that directly impacts your search visibility and indexation performance.
Frequently asked questions
What is crawl budget in SEO?
It is the number of URLs a search engine will fetch from your site in a given period, and it is set by two independent limits: what your server can serve without degrading, and how much the engine actually wants from you. Neither is a setting you can switch on. You influence the first by making responses fast and cheap to produce, and the second by publishing pages worth returning for and pointing internal links at them.
How to check crawl budget in Google Search Console
Open Settings, then Crawl stats. The report covers the last 90 days of Googlebot activity: total requests, average response time, and a breakdown by file type, by purpose (discovery versus refresh) and by response code. Dividing total requests by 90 gives a rough daily rate, but the useful reading is the shape rather than the headline number. A rising share of 3xx and 4xx responses, or of parameter URLs, tells you where the fetches are going instead of your content.
Does crawl budget matter for small sites?
Usually not. Google's own guidance is that sites of a few thousand URLs are generally crawled efficiently without intervention. When a small site has an indexing problem the cause is almost always thin or duplicated content, or a blocking rule somewhere, rather than a shortage of fetches. Diagnose those first; the effort spent chasing fetch counts on a 200-page site is nearly always effort taken from something that would have moved the result.
Crawl capacity vs crawl demand: what is the difference?
Capacity is a ceiling your infrastructure imposes, meaning how many parallel connections Googlebot can open before your response times start to suffer. Demand is an appetite Google forms from popularity, freshness and internal prominence. Raising capacity on a site nothing wants to revisit changes very little, and raising demand on a server that already struggles simply produces slower responses and a lower ceiling. Work out which of the two is binding before spending on either.
How to fix wasted crawl budget
Find where the fetches are actually going, then remove the reason for them. Server logs and the Crawl stats report both show it. The recurring culprits are faceted and parameter URLs that multiply a handful of products into thousands of addresses, soft 404s that answer 200, redirect chains that spend two fetches to deliver one page, and stale sitemaps still advertising URLs that no longer exist. Canonical tags consolidate duplicates in the index, but the duplicate URLs still get fetched, so removing or blocking the pattern is what actually recovers the capacity. Our technical SEO service works this as a dependency chain rather than a checklist.
How does Googlebot decide what to crawl?
It works from a queue assembled out of your sitemaps, links it has already discovered, and pages it has seen change before, prioritised by how important and how fresh each URL looks. Internal links are the strongest lever you hold over that judgement: a page reachable in two clicks from the home page and cited from several related articles reads as important, while an orphan reachable only from a sitemap reads as an afterthought. This is why site hierarchy does as much for crawl frequency as any server change, and why large site SEO treats internal linking as a standing discipline rather than a launch task.
See where your site stands. The free AI-powered SEO audit is your first telemetry read.
Request your free auditSEO pricing calculatorBook a strategy call
Keep exploring this topic
This answer is part of the SEO FAQ.