Google typically has completely different crawling budgets / capacities to your photographs / information on a CDN

Google’s John Mueller has confirmed that for websites that host their images (or probably other files) on an external CDN, as we do here, Google will have separate server capacity (perhaps crawl budget) for your domain and the domain of the CDN .

Like the image above, it’s hosted on AWS and isn’t on that exact domain, so it gets its own crawling capacity from the Googlebot from the rest of the domain name.

John continued Twitter “If your images are on yoursite.somecdn.com and your content is on www.yoursite.com, we would try to keep track of server capacity for them separately.” He said the “exception” is “if it’s the same server, not much changes so we could merge it then”.

Here are these tweets:

(2/2) Will Google use our crawling budget for domains or will all images of all customers in the CDN share the budget of the CDN domain (image-cdn .com)? Or does Google treat known CDN domains differently?

– Benjamin Wingerter (@SEOuxIndianer) November 22, 2021

Just to make it clearer when your pictures are on your site. somecdn .com and your content on www. yoursite .com, we would try to keep track of server capacity for them separately. (Exception: if it’s the same server, not much changes, so we can then merge it)

– 🧀 John 🧀 (@JohnMu) November 22, 2021

I don’t know about them, but in general, CDNs are very easy to crawl because they are so well tuned to serve a certain type of content. It is usually a good idea to host static content on a CDN.

– 🧀 John 🧀 (@JohnMu) November 22, 2021

Very good additional argument for rewriting the CDN host name in our domain!

– Benjamin Wingerter (@SEOuxIndianer) November 22, 2021

Forum discussion at Twitter.