# AI and the WordPress vs static website decision: what really changed in 2026

> AI made finding WordPress plugin flaws cheaper and changed how sites are edited. The facts on security, AI agents, AI visibility and when to stay on WordPress.

- URL: https://nofpress.com/blog/ai-wordpress-vs-static-website/
- Language: en
- Published: 2026-11-02
- Author: Paweł Szmidt
- Other languages: [Polski](https://nofpress.pl/blog/wordpress-czy-strona-statyczna-ai/index.md), [Deutsch](https://nofpress.com/de/blog/ki-wordpress-oder-statische-website/index.md), [Français](https://nofpress.com/fr/blog/ia-wordpress-ou-site-statique/index.md), [Español](https://nofpress.com/es/blog/ia-wordpress-o-sitio-estatico/index.md)

---

**Artificial intelligence hasn't suddenly turned WordPress into a bad tool. What it has changed are two things that affect every website owner: how fast vulnerabilities are found and exploited, and how a website can be edited today.**

For a simple business website, blog or portfolio, both changes tend to favour a file-based website. For an online shop, a large editorial team or a site built around specific plugins — not necessarily. In this article we separate facts from marketing and show where the evidence is strong and where there simply isn't any.

If you're looking for a general comparison of the two architectures, start with the [Why static?](https://nofpress.com/why-static/) page. Here we stick strictly to the AI angle.

## What AI changed in WordPress security

This is the best-documented part of the topic.

### A core vulnerability found in about 10 hours

On 17 July 2026, WordPress 7.0.2, 6.9.5 and 6.8.6 were released with fixes for vulnerabilities dubbed wp2shell. Chained together, they allowed someone to take over a site running WordPress 6.9 or 7.0 without logging in. The fixes were shipped as forced automatic updates.[3] According to the company that discovered the flaw, it was found with the help of an AI model in about 10 hours, using about $25 worth of computing power. Public exploit code was circulating within a few hours of the fix, and mass campaigns started two days after it.[2] On 21 July, the US agency CISA added both vulnerabilities to its catalogue of vulnerabilities exploited in real-world attacks (Known Exploited Vulnerabilities).[4]

Some context is worth adding: according to its discoverers, this is the first such vulnerability in WordPress core in almost a decade.[2] The core itself is well looked after.

### Over 300 plugin vulnerabilities in 72 hours

Researchers from TrendAI and CHT Security demonstrated an automated, AI-based process that found more than 300 critical, previously unknown vulnerabilities in WordPress plugins in 72 hours — at an average of about $20 per vulnerability. Each one was verified manually and reported to the plugin authors.[5] One of the study's authors cautions that this doesn't mean you can easily find a $20 vulnerability in any WordPress site — the result depends on the quality of the code. Help Net Security points out that many plugins are maintained by individual volunteers with no security budget.

Sucuri describes something similar: a researcher using the Claude model reviewed dozens of plugins and confirmed 16 vulnerabilities. AI makes it possible to check far more code in the same amount of time, although some of the findings are false positives.[6]

### 5 hours to mass attacks, 46% of vulnerabilities unpatched

Patchstack's report on the state of WordPress security (2025 data) states:[1]

- 11,334 new vulnerabilities in the WordPress ecosystem, 42% more than the year before,
- 91% of them in plugins, 9% in themes and only 6 in core itself (all of low severity),
- 46% of vulnerabilities had no fix from the developer at the time of public disclosure,
- for heavily targeted vulnerabilities, the median time to mass exploitation was 5 hours,
- typical hosting protections (e.g. web application firewalls) blocked between 12% and 26% of attacks in Patchstack's tests.

Patchstack also warns that attackers have AI at their disposal that is getting better and better at finding and exploiting vulnerabilities on its own.[1] An example from this year: a critical vulnerability in Elementor Pro (CVE-2026-32475), which allowed files to be uploaded through a form without logging in, was fixed in August, and Wordfence blocked around 200,000 attempts to exploit it.[7]

### What this means for a small website owner

The most important change is **speed**. Finding vulnerabilities is cheaper and faster, and only hours pass between a vulnerability being disclosed and mass attacks. An "I'll update the plugins next week" approach is no longer enough, and a hosting firewall is no substitute for updates.

A static website isn't fully immune to this — accounts, the domain, hosting and the tools used to build the site also need protecting. But there are no plugins on the server for someone to attack within those few hours. We cover what a static website doesn't have, and what still needs securing, in more detail in our article [Critical PHP vulnerabilities](https://nofpress.com/blog/critical-php-vulnerabilities-wordpress-static-migration/).

## How AI assistants work with a file-based website and with WordPress

The second change concerns day-to-day work. AI coding assistants — Claude Code, Codex, GitHub Copilot — can make small changes to websites. To be upfront: **we haven't found any independent measurement** comparing the time or cost of such changes in WordPress and on a file-based website. That's why we describe mechanisms, not results.

### File-based website: change, preview, undo

When a website consists of text files (Markdown, templates, styles) in a Git repository, an AI assistant sees the whole site in one place. Tools such as Copilot, Codex and Claude Code work directly on the repository: they make changes on a separate branch and propose them for approval. In practice, this means that:

- before publishing, you can see exactly what will change (every sentence added and removed),
- you can view a preview of the changed site at a separate address,
- every change can be undone with a single command,
- you don't need to install an extra plugin with write permissions on the live website.

This is how we work on the NoFPress website: the content is Markdown files in Git, and the site is built into static files. More on the [How we built NoFPress](https://nofpress.com/built-with-nofpress/) page. This is our experience, not a study — but it shows that this model works day to day.

### WordPress and page builders: content in the database, layout in JSON

In WordPress, part of the site lives in the database and part in plugin settings. Page builders add another layer: Elementor stores the page layout as JSON data in a hidden database field.[8] This matters because, according to Web Almanac 2025 estimates, around 60% of WordPress sites use some kind of page builder, with Elementor the clear leader among them.[9] An AI assistant doesn't "see" such a page as plain text — it needs an additional access layer.

### What MCP offers in WordPress and Elementor today

That layer is MCP — a standard for connecting AI assistants to applications. As of November 2026:

- **Elementor MCP** connects Claude, Codex and Cursor to your site. Everything it creates is saved as drafts. However, editing existing layouts only works for the new layout type (V4, "atomic" elements); support for older, widget-based layouts (V3) has so far only been announced by the vendor. It requires Elementor 4.3.0+, and some features require the Pro plan.[10][11] If your site was built with older layouts, AI editing may not cover your existing pages today.
- **MCP Adapter** — the official WordPress plugin (version 0.7.1, more than 60,000 active installations) — doesn't add any AI features by itself; it only exposes selected site capabilities to assistants.[12] According to Elementor, it has no settings screen: the application password and the connection to the assistant have to be set up manually.[11]

## WordPress is moving into AI too — and taking it seriously

It would be dishonest to pretend that WordPress is standing still:

- **WordPress 6.9** added the Abilities API to core — a way of describing what a site can do for external tools. It was expanded in version 7.1, although the built-in abilities listed in the announcement are about reading information about the site, not editing content.[13]
- **WordPress 7.0** (May 2026) added an AI client to core, which lets WordPress communicate with generative models, along with a screen for configuring connections.[14]
- **The official AI plugin** (version 1.5.0) generates and edits images and, experimentally, things like alt text, titles, meta descriptions and translations. Nothing is enabled after installation, and it needs your own API key from a provider (e.g. Anthropic, Google or OpenAI). The plugin is free, but you usually pay the provider for using the models.[15]
- **WordPress.com** (the hosting service run by Automattic) has, since March 2026, allowed AI assistants to create and edit posts, pages, media and other content on paid plans — with drafts, a 30-day trash, an activity log and role permissions.[16]

This is real progress. For a small website owner, though, it has a flip side: each of these layers is one more thing to configure, update and secure, and some of them are still at an early stage (MCP Adapter is at version 0.x, and most of the AI plugin's features are experiments). In our view, for a typical small business this currently means more complexity rather than less — that's an assessment, not a measurement.

## Visibility in ChatGPT and Google AI: myths and facts

This is where it's easiest to exaggerate, including on the side of static website advocates.

### Google doesn't require special files

Google states plainly that there are no additional requirements for appearing in AI Overviews and AI Mode. You don't need to create new files "for AI", special markup or special structured data. What counts are the basics: a site that crawlers can access, important content in text form and a good user experience.[17] Google adds that an llms.txt file and Markdown versions are not needed for visibility in Search.[18]

An Ahrefs study of more than 137,000 domains found that around 97% of published llms.txt files didn't receive a single request in May 2026.[19] You can have such a file — our site publishes one too — but promising that it will improve visibility would be dishonest.

For ChatGPT, something else matters: pages blocked to the OAI-SearchBot crawler in robots.txt won't appear in ChatGPT search answers.[20] That's a matter of one line of configuration, not of architecture.

### HTML from the server — WordPress has it too

You often hear that AI crawlers don't run JavaScript. According to a Vercel analysis from December 2024, the major AI crawlers (except Gemini, which uses Google's infrastructure) indeed didn't.[21] That may have changed since. But this is an argument against sites that only build their content in the browser — not against WordPress. WordPress, like a static website, sends ready-made HTML. The difference may come from a specific site, e.g. content loaded by a script, not from the choice of CMS itself.

### Speed: WordPress fails Core Web Vitals most often

According to Web Almanac 2025, only 45% of mobile WordPress sites pass the Core Web Vitals assessment, compared with 74% on Wix and 85% on Duda.[9] In an HTTP Archive comparison from early 2026 discussed by Search Engine Journal, WordPress came last with around 49%, while sites built with Astro (a static site generator) reached 67%. The author notes, however, that Astro's lead may be down to simpler sites and may shrink as site complexity grows.[22]

Does speed translate into citations in ChatGPT? SE Ranking found a correlation: faster-loading pages were cited more often.[23] But that's a correlation, not proof of causation, and the study's author sells a tool for tracking visibility in ChatGPT. The honest conclusion: a fast site means a good user experience, which Google recommends. That it gives you an advantage in AI hasn't been shown by any study we were able to find.

## When to stay with WordPress

WordPress powers 39.5% of all websites,[24] has a huge ecosystem, and it's easy to find someone to work on it. Stay with it if:

- **you run a shop with many products, customer accounts and inventory** — WooCommerce has more than 7 million active installations,[25] and a static shop needs an external payment and order system,
- **you have an editorial team** — several people publishing every day, with roles, approvals and a schedule,
- **your website relies on specific plugins** with server-side logic: memberships, online courses, bookings,
- **you want to edit your website by chatting with AI, without GitHub** — solutions such as WordPress.com with access for assistants may be simpler for a non-technical person than working with a repository.

A well-maintained WordPress site can be fast and secure. In the age of AI, though, "well-maintained" means discipline: updates within hours, not weeks.

## Quick test: does your website need WordPress in 2026?

Answer "yes" or "no":

1. Do you sell products on your website with a shopping cart, customer accounts or stock levels?
2. Do more than two people publish content regularly, with approvals and roles?
3. Does your website depend on a plugin with server-side logic (bookings, memberships, courses)?
4. Does someone update plugins within hours of a security fix being announced?
5. Do you change content every day or almost every day?
6. Do you want to edit your website only by chatting with AI, without creating a GitHub account?

If you answer "no" to questions 1–3 and 5, your website is most likely a brochure site, a services page, a blog or a portfolio, changed a few times a month by one or two people. In that case AI tends to favour a file-based website: fewer components to patch in the race against attackers, and simpler work with an AI assistant. If you answer "yes" to any of questions 1–3, 5 or 6, WordPress may still be a good choice — and then question 4 becomes especially important.

If you're considering a switch, read [how a WordPress migration works step by step](https://nofpress.com/blog/wordpress-to-static/) and [how to leave WordPress without losing SEO](https://nofpress.com/blog/remove-wordpress-without-losing-seo/).

## Not sure what to choose? Let's check together

[Request a free audit](https://nofpress.com/#audit) and a person will review your website, plugins and the way you publish content. We'll tell you honestly whether migrating makes sense — and if your website should stay on WordPress, you'll hear that too.

## Sources

Information as of 2 November 2026.

1. [Patchstack — State of WordPress Security in 2026](https://patchstack.com/whitepaper/state-of-wordpress-security-in-2026/), updated 25 February 2026.
2. [Searchlight Cyber — wp2shell: discovering one of 2026's biggest zero-days](https://www.slcyber.io/blog/wp2shell-discovering-one-of-2026s-biggest-zero-days-and-the-future-of-exposure-management), 19 August 2026.
3. [WordPress.org — WordPress 7.0.2 Release](https://wordpress.org/news/2026/07/wordpress-7-0-2-release/), July 2026.
4. [CISA — CISA Adds Four Known Exploited Vulnerabilities to Catalog](https://www.cisa.gov/news-events/alerts/2026/07/21/cisa-adds-four-known-exploited-vulnerabilities-catalog), 21 July 2026.
5. [Help Net Security — AI finds WordPress plugin vulnerabilities](https://helpnetsecurity.com/2026/05/22/ai-wordpress-plugin-vulnerabilities), 22 May 2026.
6. [Sucuri — The illusion of a lock: how AI is changing the speed and scale of hands-on WordPress vulnerability research](https://blog.sucuri.net/2026/08/the-illusion-of-a-lock-how-ai-is-changing-the-speed-and-scale-of-hands-on-wordpress-vulnerability-research.html), 14 August 2026.
7. [BleepingComputer — Critical Elementor Pro flaw exploited to take over WordPress sites](https://www.bleepingcomputer.com/news/security/critical-elementor-pro-flaw-exploited-to-take-over-wordpress-sites/), 3 September 2026; see also [Wordfence — Elementor Pro: Unauthenticated Arbitrary File Upload via Upload Field Array Validation Bypass](https://www.wordfence.com/threat-intel/vulnerabilities/wordpress-plugins/elementor-pro/elementor-pro-421-unauthenticated-arbitrary-file-upload-via-upload-field-array-validation-bypass).
8. [Elementor Developers — Data Structure](https://developers.elementor.com/docs/data-structure/), accessed 2 November 2026.
9. [HTTP Archive — Web Almanac 2025, CMS chapter](https://almanac.httparchive.org/en/2025/cms), 15 January 2026.
10. [Elementor — MCP](https://elementor.com/mcp/), accessed 2 November 2026.
11. [Elementor — MCP for WordPress: what each option is and what to install](https://elementor.com/blog/mcp-for-wordpress-what-each-option-is-and-what-to-install/), 6 October 2026.
12. [WordPress.org — MCP Adapter plugin](https://wordpress.org/plugins/mcp-adapter/), version 0.7.1, accessed 2 November 2026.
13. [Make WordPress Core — Abilities API improvements in WordPress 7.1](https://make.wordpress.org/core/2026/07/31/abilities-api-improvements-in-wordpress-7-1/), 31 July 2026.
14. [WordPress.org — WordPress 7.0 "Armstrong"](https://wordpress.org/news/2026/05/armstrong/), 20 May 2026.
15. [WordPress.org — AI plugin](https://wordpress.org/plugins/ai/), version 1.5.0, accessed 2 November 2026.
16. [WordPress.com — Let AI agents manage your content](https://wordpress.com/blog/2026/03/20/ai-agent-manage-content/), 20 March 2026.
17. [Google Search Central — AI features and your website](https://developers.google.com/search/docs/appearance/ai-features), accessed 2 November 2026.
18. [Google Search Central — AI optimization guide](https://developers.google.com/search/docs/fundamentals/ai-optimization-guide), accessed 2 November 2026.
19. [Ahrefs — llms.txt study](https://ahrefs.com/blog/llmstxt-study/), 15 June 2026.
20. [OpenAI — Overview of OpenAI Crawlers](https://developers.openai.com/api/docs/bots), accessed 2 November 2026.
21. [Vercel — The rise of the AI crawler](https://vercel.com/blog/the-rise-of-the-ai-crawler), 17 December 2024.
22. [Search Engine Journal — Core Web Vitals: WordPress and Astro](https://www.searchenginejournal.com/core-web-vitals-wordpress-and-astro/575818/), 27 May 2026.
23. [SE Ranking — How to optimize for ChatGPT](https://seranking.com/blog/how-to-optimize-for-chatgpt/), 24 November 2025.
24. [W3Techs — Usage statistics of WordPress](https://w3techs.com/technologies/details/cm-wordpress), accessed 2 November 2026.
25. [WordPress.org — WooCommerce plugin](https://wordpress.org/plugins/woocommerce/), accessed 2 November 2026.
