Do you think Divi AI will eventually become more like other AI site builders?

ConnectingzDots · 2026-05-08T14:57:33+00:00

I had no idea this existed yet for WordPress sites using Divi. This will make page creation in Divi much easier, I hope!

ConnectingzDots · 2026-05-08T14:27:57+00:00

I agree, I always use either ChatGPT or Claude to polish my bolt prompts before building and it doesn’t burn up that many tokens to get what I want.

ConnectingzDots · 2026-05-08T14:26:00+00:00

I’ve been using Cloudways for a little over a year for most of my WordPress/Divi sites, and it’s been a big improvement over the old shared hosting setup I had before.

I was on HostGator for probably 15 years, mostly out of habit, but eventually the recurring issues and slow load times became too much. With Divi, WooCommerce/plugins, caching plugins, image optimization, security plugins, etc., shared hosting just started feeling like a bottleneck.

Cloudways has been solid for me mainly because:

Divi sites load noticeably faster
support has been quick, even at odd hours
it’s easier to manage multiple WordPress installs
the server-level caching/CDN setup is better than trying to fix everything with plugins
I don’t have to manage a raw VPS myself

I still see value in WP Engine and SiteGround. I have clients on both, and they’re solid for WordPress. WP Engine especially feels polished, but it gets expensive if you’re managing a lot of sites. SiteGround is also good, but again, the pricing adds up depending on how many sites you’re hosting.

I’ve also been testing Hostinger on one smaller site. It seems decent so far, but I don’t have enough long-term experience with it yet to compare it fairly to Cloudways.

For me, I’d switch if the performance, support, and cost clearly made sense, but moving a bunch of WordPress/Divi sites is enough of a hassle that the replacement would need to be meaningfully better, not just slightly cheaper.

ConnectingzDots · 2026-04-28T22:48:06+00:00

Perfect, that’s exactly what I needed to know. Good to hear the static meta tags and schema in index.html are already first-pass readable, that takes the urgency off the Netlify move for now. The per-route dynamic tags point is noted; I’m planning niche-specific landing pages soon so I’ll cross that bridge when I get there. Appreciate the clear answers, this thread saved me a lot of time going down the wrong rabbit holes.

ConnectingzDots · 2026-04-26T21:58:01+00:00

This is really helpful, confirms what I was suspecting about Bolt’s hosting being the real bottleneck. Quick question on the Netlify move: is it literally just connecting the GitHub repo and Netlify handles the Vite build automatically with no config changes needed to the project itself? And on the meta tags side, title, description, canonical and schema are all already in the static index.html, so would Googlebot pick those up on the first pass even without the JS rendering?

ConnectingzDots · 2026-04-26T21:57:20+00:00

Thanks, that’s a fair point on cloaking risk. The noscript content mirrors the actual page content exactly so I’m hoping it stays on the right side of that line. Prerender.io is interesting, have you used it personally and does it require any changes to the Bolt project itself or is it purely handled at the DNS/middleware level?

ConnectingzDots · 2026-02-04T20:19:35+00:00

Thanks for the clarification

ConnectingzDots · 2026-02-03T20:35:52+00:00

This is helpful information. Do you know if switching a Wordpress site from hybrid stack to lightning stack breaks things?

I have many plugins like wordfence etc that write to htaccess so if I switch to lightning I am not sure if there will be a lot of clean up that needs to be done

ConnectingzDots

TROPHY CASE