// work · 01 / 05

WordPress to Webflow,
behind Cloudflare.

Hosting bandwidth from about 100 GB a day to about 500 MB, without leaving Webflow.

// clientHunterbrook, with Scaler Marketing

// typeMigration

// stackWebflow, Cloudflare

// roleLead developer

// year2026

// screen figures changed, text figures real
// 01
The problem
Hunterbrook is a news site, and its articles have to go out on time. On WordPress, plugins kept breaking and editing was a struggle. They asked Scaler Marketing to help keep WordPress running, and Scaler suggested moving to Webflow.
// 02
The move
I led the build from start to finish. About 120 articles moved across, with 301 redirects from the old URLs, and the site went live in June. Nobody knew its real traffic, because it had never had analytics. Two weeks after launch, the Webflow dashboard showed just over 1 TB used in 16 days, on a plan that includes 50 GB a month.
// 03
The fix
About 99% of the requests were automated: search engines, news monitors and scrapers. They had been hitting the WordPress site too, and nobody was billed for them. Webflow upgrades a site automatically after a second month over its limit, so I had until the billing date on 18 July. I put Cloudflare in front, so most requests are answered from its cache. Every image is now fetched from Webflow once and served from a copy after that. I also closed two routes scrapers were using to get round Cloudflare. The last fix went live on 16 July.
// 04
The result
Bandwidth went from about 100 GB a day to about 500 MB, about 99.5% less. The chart is Webflow's running total, so a flat line means almost nothing new is being served. In mid-September a bot found a way round the cache. I added another security patch to the Cloudflare Worker, and the line went flat again. Most days land between 200 and 600 MB, depending on what gets published. The site is still on Webflow, on the 50 GB plan it launched with. Cloudflare now takes 4 to 6 million requests a day, about 6 to 7 TB a month.

// what i did

Keep Webflow. Put Cloudflare in front.

I led Hunterbrook's move from WordPress to Webflow for Scaler Marketing, then put Cloudflare in front when the traffic showed up. Most requests now stop at Cloudflare's cache, and the site runs on the same Webflow plan it launched with.