There are four factors that will be affected by using a CDN, and Cloudflare in particular: Security, Speed, Local SEO, and Duplicate Content .
A CDN improves our security and availability against denial of service attacks (DDoS), a technique considered Negative SEO, but which is actually a widespread hacking practice.
It is based, in simple terms, on sending massive amounts of traffic to a server until the line is saturated and the server is unable to send data.
With CloudFlare, all the traffic that would normally
attack your server directly and crash it is automatically distributed across the entire network of servers. With all this traffic distributed, the effect is diluted and it is much harder to take down your server.
Speed , it is clear that Google considers any factor that improves the user experience very positively, and speed being one of the things that has the greatest impact on a satisfactory experience, it is clear that improving speed improves our positioning and the specialty of a CDN is precisely to improve our service speed.
By changing your hosting’s DNS to CloudFlare’s, the public IP address will no longer be Spanish.
Contrary to popular belief, IP address is not a factor for your Local SEO
The factors that really matter in local SEO are your TLD (i.e. whether your site is a .es or a .uk), your hreflang tags , and your audience declaration in Google Search Console.
Having your .es domain on a Finnish denmark email list server, if it has the same speed as a Spanish one, does not rank worse in Google Spain if everything else is well configured.
What it does do, at most, is reinforce your Local SEO in other parts of the globe by improving the speed of access to your information from there.
It is worth noting that this is an important point for any website with international scope.
We are left with the question of duplicate content .
It is clear that our static information digital marketplace: the biggest and cheapest showcase in the world resides on many servers spread across the planet, so it is normal for the question of duplicate content to arise.
The answer is that on a CDN there will be duplicate content, because you are making many copies of your site all over the network.
The question is whether this penalizes or not, and the answer is that it does not penalize , since the same content is always presented in the maldivian lads same URL regardless of the server that sends it to you, so it is identified as unique to search engines.
Of course, these detect that they come from
different IP addresses, but this happens even on websites on a classic hosting without us realizing it.
The key to avoiding duplicate content is proper canonization of our content. If we fail here, we will be penalized both on and off a CDN.
Correctly configuring Google Search If you are Console and using rel=”canonical” tags is the right way to avoid this.
Let’s assume a PDF and an HTML page with the same content.
The content of a PDF is indexed and Google would detect the same content in both.
PDF header , Google will perfectly understand that the PDF is a duplicate of “ content.html ” and will not index it.