The Complete Guide to Migrating Hugo from Netlify to Cloudflare Workers

After a bit of a fight with abusive crawlers pretending to be BingBot, which started draining the 100GB allowance on my Free (legacy) Netlify account, I decided that I would move the fight to a different playground – Cloudflare. I have been thinking about moving from Netlify to Cloudflare for over two years, but with all the transitions surrounding Cloudflare Pages, I have been waiting until the dust settles and the path with Cloudflare Workers finally becomes the default option. Now, it is time to try again. With my limited options (on Netlify’s free tier) in the fight against bots, and after reading the post 99% of My Website Traffic Is Bots alongside recent features introduced for this purpose on Cloudflare, I decided it would be worthwhile to test the waters and see how it goes. Despite my legacy Netlify Free accounts for a couple of my projects being quite generous, any new project I create requires me to use their credit-based pricing model, which is not nearly as forgiving. This is why I started exploring Cloudflare, especially since all my domains are already managed through it. There were several differences and challenges that I needed to resolve along the way (such as contact forms and redirects). For this reason, I am documenting the process in the form of a journal – both for my own reference and for anyone else looking to take this path.