Crawl budget optimization matters when Googlebot wastes requests on pages that don't deserve indexing or when your site is large enough that not everything gets crawled regularly. For sites under 5,000–10,000 pages with clean architecture, it's rarely the limiting factor. Focus here if you see important pages not getting crawled weekly or if you're running a large ecommerce or publishing site. Start by cutting waste. Identify and block low-value URLs: faceted navigation that creates thousands of filter combinations, paginated archives beyond page 5–10, session IDs or tracking parameters in URLs, old date-based archives with thin content, and infinite scroll or calendar pages. Use robots.txt to block entire sections if they add no search value, or noindex tags if you need internal linking but not indexing. Fix technical drags that burn crawl budget without delivering pages. Redirect chains force Googlebot through multiple hops—consolidate them to single 301s. Broken links return 404s or 500s but still consume requests. Slow server response times mean fewer pages crawled per session—aim for sub-200ms TTFB on HTML. Large page sizes with bloated JavaScript or unoptimized images slow the crawl; keep HTML under 500KB when possible. Use log file analysis to see what Googlebot actually crawls. Compare that against what you want indexed. If it's hitting old blog tags or weird parameter combinations instead of new product pages, you have a priority problem. Internal linking structure guides crawl priority—pages linked from the homepage or main nav get crawled more often. Sitemaps help but don't override robots.txt blocks or poor site architecture. At Ottawa SEO, we see crawl budget issues mostly on older sites with 15+ years of archives, ecommerce platforms with poor facet control, or WordPress sites running aggressive calendar or tag plugins. The fix is almost always subtractive—block or noindex the junk, don't try to force-feed Googlebot more pages. If your important pages update daily and show crawl dates within 48 hours in Search Console, you're fine.