AI can build a website. A commercial website is something more.
At a glance
- AI can now build perfectly good websites for the right purposes, including campaign sites, portfolios, prototypes and microsites.
- Commercial websites are different. They are long-term digital assets that need to operate and evolve for years.
- Staff need to manage them without relying on a developer for every content change.
- They need to connect to other systems, including CRM, payments, recruitment, analytics and consent management.
- They need ongoing management covering security, performance, accessibility, backups, privacy and compliance.
- WordPress provides the underlying structure for content, users, permissions, APIs, integrations and bespoke functionality.
- AI may make that structure even more valuable, as AI search, semantic search and AI agents increasingly rely on structured, accessible information.
AI can build a website. Building and managing a long-term commercial digital asset is a different job.
AI can now build a perfectly decent website, and for the right project we’d have no hesitation in recommending it. The quality of the output has improved considerably, and a single-page marketing site, event or campaign microsite, prototype, portfolio, documentation site or other relatively simple project with little ongoing content management can be an excellent candidate for an AI-generated static build. It can be clean, responsive, fast and inexpensive to produce.
Most of the websites we work on, however, aren’t simply collections of web pages. They are long-term commercial and organisational assets that may remain in active use for many years, changing alongside the organisations they represent and becoming increasingly connected to other systems. Once you look at a website in those terms, the requirements are rather different.
A commercial website has a life after launch
The important distinction isn’t whether AI can produce attractive HTML, CSS and JavaScript, because it clearly can. The more interesting question is what happens to the website over the following three, five or ten years as staff change, new services are introduced, campaigns come and go, content grows and the organisation itself evolves.
For most of our clients, a website needs to be managed by people who aren’t developers. Marketing and communications teams need to publish news, create landing pages, advertise vacancies, add events and update services without asking someone technical to modify the underlying code. Larger organisations may also need different levels of access, approval processes and revision histories so that people can make changes without everybody having unrestricted control of the website.
At the same time, the website is likely to become connected to an increasing number of other systems. It may exchange information with a CRM, process payments, send transactional email, feed a recruitment or learning management system, run analytics and conversion tracking, manage consent and communicate with marketing platforms. All of those connections have to continue working as the website and the services around it change.
Security, performance, accessibility, backups, privacy and regulatory compliance also need ongoing attention. These aren’t really questions about how a website was built in the first place; they are questions about how an organisation owns, operates and takes responsibility for an important digital asset.
Why WordPress remains valuable
This is where we believe a mature content management system such as WordPress continues to make sense. It gives organisations a structured environment in which authorised staff can create, review and publish information without touching code, while developers can build and maintain the more complicated functionality underneath.
Importantly, the content itself can be structured using posts, custom post types, taxonomies and fields rather than existing simply as the markup required to display a particular page. That gives us much greater freedom to change how information is presented, reuse it elsewhere and integrate it with other systems as requirements develop.
WordPress also provides an established framework for users and permissions, APIs and bespoke development, together with an enormous ecosystem of existing integrations. It isn’t the right solution for every website, but for an organisation expecting its website to grow and change over several years, these characteristics make it much more than a convenient way of editing pages.
Of course, the platform still needs to be properly managed. Software changes, vulnerabilities are discovered, user accounts and permissions need reviewing, integrations need maintaining and performance needs monitoring. AI may make creating and maintaining parts of a website considerably easier, but it doesn’t remove the need for someone to understand the whole system and take responsibility for it.
AI may make structured websites more important
This is also why we think presenting AI and WordPress as competing approaches misses something important. AI isn’t simply changing the way websites are built; it is changing how their information is discovered, searched and potentially used by other systems.
AI crawlers are already retrieving website content, while AI-powered search is changing how people discover organisations and semantic search is changing what visitors expect when they search within a website. We are also beginning to see AI agents interact with applications and, where they have been specifically authorised to do so, perform actions rather than simply retrieve information.
In that environment, having well-structured content and an established application layer becomes useful. WordPress already provides structured content, APIs and a mature permissions system, while newer developments such as the WordPress Abilities API and MCP Adapter are creating controlled ways for authorised AI applications to interact with WordPress functionality.
Rather than making WordPress obsolete, therefore, AI could make a well-designed and properly managed WordPress website more valuable. The same underlying structure that allows a communications team to manage information today can help make that information searchable, reusable and accessible to new systems tomorrow.
Choosing the architecture for the job
None of this means that every website should use WordPress. If an organisation needs a temporary campaign site, a prototype, a portfolio or a straightforward information site that will rarely change, adding a full content management system may introduce complexity that serves little purpose. An AI-generated static site could be the simpler and better solution, and that is what we would recommend where it fits the requirement.
The calculation changes when the website is expected to become part of the organisation’s operational infrastructure. In those circumstances, we need to understand who will update it next year, how access will be controlled, which other systems it needs to communicate with, who will be responsible for security and compliance, and how the website and its content will adapt as requirements and technologies change.
We’re enthusiastic about AI and increasingly use it within our own work, while also helping clients understand developments in AI search, semantic search, AI crawlers, agents and technologies such as MCP. We expect AI to take care of more of the work involved in developing and managing websites, and we see that as a positive development.
For some projects, AI can already produce all the website you need. For an organisation investing in a website that will form an important part of its operations for many years, however, generating the website is only the beginning. Building, managing and continually developing a long-term commercial digital asset is a different job.
'
'