SEO practices for Content Delivery Network (CDN)

As per Google, a site’s load time can have an impact on its search ranking. A content delivery network or CDN plays an important role in maximizing speed under the given constraints. SEO process offers a set of challenges for CDN domains. These SEO issues can be tackled by configuring your site and CDN properly to prevent the scenario of losing more than you can gain. Here are some of the SEO best practices for using a CDN that should allow them to get the benefit of a CDN without the risk of losing all of the traffic from Google Image Search and elsewhere.

Using ‘Rel Canonical’ on Pages hosted by CDN


Usually, a CDN is a popular way of caching or hosting website resources like CSS, images, video files, JavaScript etc that are bulky in size. But the user may run into duplicate content issues if they try to host the full site on a content delivery network. A case in point is- if the before CDN URL of a page is, the after CDN URL page would be similar to Hence, now we have a case where two different URLs point to the same page and would lead to SEO problems with respect to duplicate content. To tackle this, the user has to understand that making use if a relative path may not be the best way to go about it in this case. Rather, the need is to have an absolute path. Thus, users can make use of the ‘rel canonical’ tag. This can bypass the whole duplicate content issue by using the as an absolute or canonical URL path on the cdn page. The same process can then be applied on all the pages hosted on the CDN server throughout. Using this method will aid Google in identifying the ideal URL path that the user wants to be used, indexed and shown while searching. This also provides you the major benefit of avoiding losing the existing rankings od search engines and link juice from pages indexed before.

CDN setup in tools like Google Webmaster Tools (GWT)

Make use of Google Webmaster Tools and Bing Webmaster Tools to set up and verify your CDN sub-domain. This takes care of many things Vis-à-vis- if the user is concerned about the CDN’s IP address being out of the country targeted, they can put the geographic target in GWT. It also lets you to use the URL removal tool if required, among other things. Thus, these tools help you to get a further grip on the geographical target and even if the location of your CDN provider’s IP address is a different one than your own place, it wouldn’t’ make any difference. This is critical if you do not want search engines to target a geographically different location automatically (which would mean your CDN provider’s IP address) than your location. It is a commonly known fact that search engines give preference to websites that are locally hosted. Also, in GWT, setting up your domain and verifying it is not tough at all. You can block or remove specific URLs depending on your needs and preferences as well, either pre-CDN or post-CDN. Overall, this adds value to your endeavor.

Make use of Your Own Sub-domain


It is highly advised to set up a sub-domain for your content rather than letting CDN host it. When your own sub-domain is created and used, the service is kept proprietary to you, pointing the resources based on CDN to your own domain i.e. instead of This has multiple benefits- your authority over the site increases a lot, is more secure, makes it seem professional, makes it more appealing to look at and most importantly, increases the page speed. etc. ultimately all of this impacts your SEO rankings. You can check with your service provider if they would let you have this option by installing the service on your personal sub-domain. You can set up a lot of CDN service that way. Some services, like CloudFlare, perform more like reverse proxy for your whole domain so nothing actually changes URL-wise anyway.

Maintain File paths and names

It is critical and highly recommended to preserve and maintain a list of all the file names even after having transferred some content to CDN. If tomorrow, you have a change of mind and want to switch back to the original host server, you wouldn’t have to revise the files again. In short, keep the same files naming conventions you had before the CDN. For example, if an image was at and you go to a CDN that renames it or changes the folder structure (e.g. you may run into some issues if the old URLs have not been redirected. This is a very common problem and can lead to a lot of time wastage. So it is always better to have a list of the original names. If the before-CDN path to the file was at the new address at the CDN should be something like: This would pay in the long run by avoiding useless 404 type problems.

Make use of the popular CDNs even if the cost is more


One of the most important considerations is to go for quality and not quantity. It is any day better to use reputable service providers like MaxCDN, Akamai and Amazon Cloudfront. They have been in business for a long time now and have proven to be amongst the best there is today. They are reliable and provide quality work. And a little extra cost on the wallet right now is much better than tons of regret tomorrow right?


When implementing CDN services, it comes with a challenge that the website images may get de-indexed by Google because of the CNAME based CDN URLs. However, with these steps enumerated above, we can get Google to index our site images once again.

Leave a Reply

Your email address will not be published. Required fields are marked *