Static site on Cloudflare Workers instead of WordPress - thoughts?

Most casino portals I see here run on WordPress, but I went a different route - built mine as a static site with a custom Node.js build system, deployed on Cloudflare Workers. No CMS, no database, just generated HTML at build time.

Trade-off is obviously less flexibility for non-technical updates, but page speed and hosting costs are basically unbeatable. Curious if anyone else here has moved away from WordPress for a casino portal, and how that's worked out long-term for content updates and SEO.

I think int he future now with AI I will be moving some of the projects away. coding is easiert than ever now and keeps gettiing better.

yeah right, might be the right decision. AI + a few skills in the IT will overcome. I learned as a job - IT + AI/KI nowadays, we used it daily at work too.

I actually also think this is the way to go going forward.
For me it is really just too much to "migrate" at this stage, so i am not sure I would really ever move away from WP completely. But most new pages I have now (especially review pages) are just HTML templates that work off a JSON dataset.
Also I have lots of custom plugins I created for myself which would be tricky to re-implement outside of WP.

Curious though, have you considered actually building a CMS around your implementation?

Good question - not really, mostly because the site is small enough that a build script handles it fine for now. All casino data lives in one JSON file, and the build generates every page from templates referencing that file. Adding a new casino or country page is just a data + a few lines of generation logic, no admin UI needed.

Might revisit if the site grows large enough that non-technical updates become a bottleneck, but for now the simplicity of "edit JSON, run build, deploy" outweighs the overhead of building a proper CMS layer.

Went the exact same route, so I can speak to the long-term side you're asking about.

Content updates: the 'static is painful to edit' worry mostly disappears once you put a thin CMS or cabinet in front of the build. Non-technical edits go through that, the build regenerates the HTML, and bulk changes like new bonuses or new brands come from the data layer without touching your hand-written copy. In practice it's been easier to manage than the WordPress installs it replaced, not harder.

SEO: static has been a net positive. Speed and Core Web Vitals are unbeatable like you said, and as long as the build bakes in sitemaps, hreflang, schema and clean canonicals, you lose nothing versus WP on the SEO surface. If anything Google likes the fast clean HTML.

We actually migrated our own legacy WordPress casino portal (cryptocasino.ws) to a static build and it's held up fine long-term. That experience turned into a SaaS I run for casino and sportsbook sites. Posted a fuller writeup in Other Marketing Offers and the link's in my sig if it's useful, but happy to just compare notes here too.

Really helpful, thanks Franky. Good to hear the static approach holds up long-term rather than becoming a bottleneck. I'll keep the "thin CMS in front of the build" idea in mind if things scale - for now editing JSON directly is still fast enough.

Will check out the Site Generator too, appreciate the pointer.

Quick update on this — just rolled out a light/dark mode toggle. Using prefers-color-scheme for initial detection, then a manual override saved in localStorage that takes priority afterward. Kept it to CSS variable swaps only, no structural changes to the underlying components, which made maintaining parity between both themes way easier than I expected.
Happy to share more details if anyone's working on something similar.

The speed is great, but for me, the biggest relief of moving away from WordPress is the security. Not having to worry about SQL injections or vulnerable plugins is a huge weight off my shoulders. Do you find that you're getting less 'bot noise' in your logs now? Usually, once you remove the /wp-admin and /wp-login, most automated scanners just give up and move on to easier targets...

We use the same approach: Astro static build on Cloudflare Workers + Assets, no CMS, no DB, straight to HTML at build time.
Right now our data lives in markdown files with frontmatter, read at build time. I've been thinking about using SQLite instead, purely as a build-time data source (site stays static either way, not for runtime), mainly for easier querying/joins.

one thing that makes workers more interesting than plain static hosting for casino sites is geo. a worker can read the visitor country from the request (request.cf.country) and swap or hide offer blocks before the page is served, so a uk visitor never sees a brand that isn't licensed there, and there is no js flicker on the client.

it also helps to keep bonuses and offer data in kv or a small json the worker reads, instead of baking them into the html. then a bonus change is just a data update, not a full rebuild and deploy.

Quote:

---

Originally Posted by casinoinspector

Most casino portals I see here run on WordPress, but I went a different route - built mine as a static site with a custom Node.js build system, deployed on Cloudflare Workers. No CMS, no database, just generated HTML at build time.

Trade-off is obviously less flexibility for non-technical updates, but page speed and hosting costs are basically unbeatable. Curious if anyone else here has moved away from WordPress for a casino portal, and how that's worked out long-term for content updates and SEO.

---

I did this same thing some ways back for a site for another niche, artisan soap, i spend less than 3 euros and got a proper site up in less than 7 hours. i loved the stats of all the discovery bots, the thing if it was from a no context niche would dominate with proper content in no time.

Vercel has a bit more robust platyform than cloudflare is using next

The speed is a next level with such setup. WP is going to die slowly, imho. Just it's too overloaded with stuff for info sites.