A Brisbane cafe owner asked me last month, point blank, whether she should cancel her rebuild because AI can now generate websites in minutes. It is the same nervous question I hear from tradies in Perth and clinics in Melbourne: will AI kill Elementor, and am I investing in the wrong thing? Here is my honest answer as someone who ships client sites for a living: nobody knows what survives, but the smart money stays on websites the owner can actually run. She had already paid for two AI-generated concepts elsewhere, and both stalled the moment she asked for changes her team could make themselves.
Start with the one certainty nobody argues about. As long as a business needs to exist on the internet, it needs a website it controls: its domain, its content, its analytics, its path from search to enquiry. Generators and platforms rise and fall, but the owned website stays home base. So the question was never whether websites survive. It is which way of building one still makes sense three years from now. A redesign trend cannot take that away, and neither can a pricing change at some generator company.
The quiet advantage Elementor keeps is operability. The cafe owner changes the lunch menu text herself. The tradie swaps job photos from his phone. The clinic publishes a flu-season notice without lodging a ticket, waiting on a developer, or watching a deploy pipeline. That independence decides whether a small business website stays fresh or quietly rots, because every edit that costs money and waiting is an edit that never happens. The tradie swaps job photos from his phone between site visits. The clinic publishes a flu-season notice the same morning the doctors ask for it. That is why the third hot take grades fact: an owner-edited Elementor site outlives tool hype, because the person paying can understand it, edit it, move it, and hand it over.
Set that against what AI builders mostly ship today: custom code. The demo flies and the output can look sharp, especially when the prompt is simple and nobody looks under the hood. Then real life arrives and each change travels back through code, with hosting, dependencies, updates, and debugging sitting on whoever owns the repo. The ecosystem is heavier, the stages are more complex, and maintenance turns into a standing subscription to complexity. Fast to demo is not the same as cheap to own, and owners feel the gap within one quarter. That is why the first two hot takes both grade myth: the demo takes minutes but month two is regenerate, review, and redeploy for every change, and who edits the site in year two decides everything. Ask any owner living through it and they will describe the same slow drift: fewer updates, older photos, a contact form nobody trusts.
None of this is an argument for standing still. Elementor keeps adapting with AI-assisted building and the MCP layer for agent workflows, and WordPress keeps evolving underneath it. In practice that means your existing site gains new powers instead of needing a rebuild: drafts assembled with AI help, content operations through agents, and the same visual editing your team already knows. Tools that adapt survive and tools that freeze do not, so bet on the stack that moves. And judge every option by one test: can you, the person paying, understand the site, edit it, move it, and hand it over? Visual, structured, standard-based builds pass that test today. Your existing site gains new powers instead of facing a rebuild, which is exactly how healthy software is supposed to age.
When owners press me for a straight recommendation, I give them a two-question filter. First, who edits this site in year two, and with what skill? If the answer is your own team with no developers, visual wins by a mile. Second, what happens when the generator behind your site changes pricing, shuts down, or drifts? Exportable, standard, human-readable output is an exit plan. A rebuild you cannot open is a hostage situation with nice branding.
If you want a website your team can run without fear, see my portfolio and get in touch.
