|
This parameter indicates how 'deserving' the site is to be scanned .The factors that affect the demand for crawling (scanning) are different but are essentially of two typesopularity : URLs that are more popular tend to be crawled more often;Obsolescence / errors : Old, poorly updated pages containing errors and low metrics tend to be crawled less often.In essence, therefore, crawl budget is a parameter that summarizes these two values.Is the Crawl Budget important?Google is also very clear on this point.
For the majority of websites with a low number of Special Data pages (less than a thousand) and relatively infrequent updates (for example a blog, institutional sites, landing pages, showcase sites, etc.) this parameter has no influence , in as Google has no problem crawling the site.In fact we read on Google:First, we'd like to point out that crawl budget is not something most sites need to worry about. […] if a site has fewer than a few thousand URLs, most of the time it will be crawled efficiently.John Muller himself on his channel indicates that the crawl-budget factor is generally overrated and many webmasters have no reason to worry about it.John Muller's words on the crawl budgetHow to determine your site's crawl budgetTo determine your site's crawl budget you need to use your site's Google Search Console and access the crawl statistics section , as shown in the following image.
Crawl Statistics in the New Search ConsoleBy accessing this page you will find the statistics of access to our site by the Google spider, the famous Googlebot:Search Console Crawl StatisticsFrom the report described above, we can see that on average Google crawls 512 pages of our site every day. From this, I can understand that my monthly crawl budget is 512 * 30 = 15,360.Crawl speed can be subject to change and fluctuation but this number gives you an idea of how many pages of your site you can expect to crawl in a given period of time .If you need a more detailed analysis (for example how many times the Google bot accesses a specific page) the next step is to read your server logs.
|
|