Latest / Wpfavs - Your favourite WordPress news / AI Site Builders vs. WordPress: What the Benchmarks Miss

Transcript

AI Site Builders vs. WordPress: What the Benchmarks Miss · Wpfavs - Your favourite WordPress news

• 0:13
  Welcome to Wpfavs.
• 0:16
  Today's question is whether AI site building makes WordPress obsolete.
• 0:20
  October 2026 gave us some fresh data on it.
• 0:23
  WebDevStudios ran a benchmark they call It Looks Done.
• 0:27
  Two websites that look identical in a screenshot.
• 0:31
  One was vibe coded with AI in four minutes.
• 0:34
  The other was built on WordPress.
• 0:36
  Their finding is that AI nails the top 20 percent, the layout and styling you can
• 0:41
  see.
• 0:42
  It misses the other 80 percent, which they break into fourteen production
• 0:45
  requirements.
• 0:46
  Fourteen things.
• 0:47
  Give us a few, because that's where this gets real.
• 0:50
  Keyboard accessibility, semantic markup, role based access control,
• 0:55
  caching layers, secure API routes, database structure, backward compatibility.
• 1:01
  None of it shows up in a screenshot.
• 1:04
  And their line stuck with me: the deeper you go, the more expensive these are to
• 1:09
  miss.
• 1:10
  WordPress has spent two decades building all of them.
• 1:13
  A fresh prompt starts at zero.
• 1:15
  I agree with the warning, but I want to challenge the framing.
• 1:18
  Is the contest really AI versus WordPress?
• 1:21
  If a prompt can produce a polished frontend in four minutes,
• 1:24
  then polish is cheap now.
• 1:26
  Nobody should be selling polish as the scarce thing anymore.
• 1:29
  Sure, but cheap polish is exactly the trap.
• 1:32
  Look at the 20i hosting survey of 600 people using AI coding tools.
• 1:37
  51.1 percent had very limited or no prior coding knowledge.
• 1:42
  Only 12.5 percent regularly wrote code before AI tools.
• 1:46
  And fewer than a third, 31.5 percent, have a professional developer review what the
• 1:52
  AI generated.
• 1:53
  And 9.3 percent deploy without verifying or testing it at all.
• 1:56
  That number made me stop.
• 1:58
  Right.
• 1:58
  Nearly one in ten shipping blind.
• 2:01
  When it comes to protecting a business, that's not a speed story,
• 2:04
  it's a liability story.
• 2:06
  47.7 percent said they adopt vibe coding mostly for speed and productivity.
• 2:12
  I get that.
• 2:13
  But speed without review is just a faster way to create technical debt.
• 2:17
  Okay, but hold on.
• 2:18
  Review is the missing piece in that survey, not the AI.
• 2:22
  Those people could also install twelve random plugins and never test a single one.
• 2:26
  Is the problem the tool or the absence of a process?
• 2:29
  Fair, and here's where I'd push back on myself.
• 2:32
  WordPress isn't magic either.
• 2:35
  NorthDuty audited 100 live WooCommerce stores pulled from agency portfolios,
• 2:40
  using read only checks.
• 2:42
  5 percent had reproducible public Store API or TLS configuration defects.
• 2:48
  Another 10 percent had broken browser interactions, like dead navigation menus,
• 2:53
  footers that didn't work, or broken cart and product links.
• 2:57
  So 15 percent of professionally showcased stores had something broken.
• 3:02
  That's the part I'd hammer.
• 3:04
  If agencies on a mature platform miss that, imagine an unreviewed generated site
• 3:09
  handling checkout.
• 3:10
  That's my point exactly.
• 3:12
  A mature platform gives you a floor, but you still have to test.
• 3:15
  Remove both the floor and the testing, and the risk compounds.
• 3:19
  I'll concede that.
• 3:20
  A platform with twenty years of plumbing beats a blank prompt on anything that takes
• 3:24
  money or personal data.
• 3:26
  My disagreement is about where the next fight happens.
• 3:29
  Because the market data doesn't look like obsolescence at all.
• 3:32
  Barn2 pulled W3Techs numbers for the top 10 million sites.
• 3:35
  WooCommerce powers 7.9 percent of all websites, Shopify 5.4 percent.
• 3:40
  Among eCommerce platforms, WooCommerce holds 47.7 percent and Shopify 32.1 percent.
• 3:46
  And Nettingale audited 4,096,194 homepages across 32 European countries and found
• 3:52
  47.6 percent, about 1.95 million sites, run WordPress.
• 3:57
  Estonia is highest at 59.4 percent, Czechia lowest at 34.5.
• 4:02
  So nobody is leaving.
• 4:03
  Even the lowest country is over a third.
• 4:05
  Exactly.
• 4:06
  WordPress isn't going obsolete.
• 4:09
  The risk is different.
• 4:10
  The reader of your site is changing.
• 4:12
  AI assistants and agents are retrieving your content, and if your site doesn't
• 4:16
  expose clean structure, it becomes invisible to them.
• 4:20
  That's the shift from optimizing for page views to optimizing for agent retrieval.
• 4:24
  That's where the tooling is catching up, and I like that it's practical.
• 4:27
  The WordPress Core AI team released the canonical MCP Adapter plugin on the
• 4:32
  directory, so a site can expose a standard Model Context Protocol server.
• 4:37
  And AI Plugin 1.4.0 added Markdown Feeds, which serve clean Markdown to language
• 4:43
  models alongside the normal HTML.
• 4:46
  Which is huge, because an agent doesn't care about your hero animation.
• 4:49
  It wants structure.
• 4:50
  Headings, schema, clean text.
• 4:52
  Strip away the styling and the JavaScript, and ask what's left.
• 4:56
  For a lot of sites, the answer is not much.
• 4:58
  And this is where I think the middle ground is real.
• 5:01
  Builders are shipping native AI agents, like the Divi 5 AI Agent and Beaver Builder
• 5:07
  AI.
• 5:08
  You get prompt driven speed, but the output lands inside a CMS where the other 80
• 5:13
  percent already exists.
• 5:15
  Permissions, caching, database schema, accessibility.
• 5:19
  You're not asking the model to reinvent them.
• 5:21
  I like that, with one caution.
• 5:23
  A builder agent is a game changer only if it respects the plumbing.
• 5:27
  Streamline your process, yes, but don't add plugin bloat to do it.
• 5:32
  Every new tool is another thing to maintain.
• 5:34
  Can I push on that?
• 5:35
  Some plugins now are the plumbing for agents.
• 5:38
  CrawlBrain, for example, launched as an AI site search that replaces the traditional
• 5:43
  search bar.
• 5:44
  Shoppers ask natural language questions and get answers straight from store content.
• 5:49
  That's a plugin earning its place.
• 5:51
  If it's tested and it answers from your own content, I'm fine with it.
• 5:56
  My rule is simple.
• 5:57
  Does it solve a real friction, and can you verify it?
• 6:00
  If not, skip it.
• 6:02
  So where do we land?
• 6:03
  I'd say vibe coding is a great way to sketch, and WordPress is where sketches become
• 6:07
  businesses.
• 6:08
  I'd add one thing.
• 6:09
  Being production ready now includes being machine readable.
• 6:12
  A site that passes the human screenshot test and fails the agent test is only half
• 6:17
  done.
• 6:17
  And my takeaway for anyone building this week: review everything,
• 6:20
  test your cart and your menus, and treat generated code like a draft.
• 6:25
  The 80 percent nobody sees is still the job.
• 6:28
  Thanks for listening to Wpfavs.