{"id":7214,"date":"2026-04-02T17:01:45","date_gmt":"2026-04-02T15:01:45","guid":{"rendered":"https:\/\/www.2manydots.nl\/kenniscentrum\/ai-in-wordpress-kans-of-risico-voor-agencies"},"modified":"2026-04-02T18:09:11","modified_gmt":"2026-04-02T16:09:11","slug":"ai-in-wordpress-kans-of-risico-voor-agencies","status":"publish","type":"news_pt","link":"https:\/\/www.2manydots.nl\/en\/knowledge-center\/ai-in-wordpress-kans-of-risico-voor-agencies","title":{"rendered":"AI in WordPress: opportunity or risk for agencies?"},"content":{"rendered":"<p>The tools are getting smarter, the promises bigger. But what specifically does AI mean for a WordPress agency like 2manydots? We share our honest take: where we embrace AI, where we deliberately put the brakes on it, when we find it exciting, and why human work is making a difference right now.  <\/p>\n<h2 class=\"wp-block-heading\">The hype is fairly over, now the practice<\/h2>\n<p>Let&#8217;s face it: you can&#8217;t avoid it anymore. AI tools like Cursor, Claude Code and GitHub Copilot have become everyday tools in just a few years. And in the WordPress world, things are moving fast. <a href=\"https:\/\/automattic.com\/2024\/12\/09\/automattic-welcomes-wpai\/\" data-type=\"link\" data-id=\"https:\/\/automattic.com\/2024\/12\/09\/automattic-welcomes-wpai\/\" target=\"_blank\" rel=\"noreferrer noopener\">Automattic bought the team behind CodeWP in late 2024<\/a> and built Telex: a tool that generates Gutenberg blocks based on a simple description. Elementor, Divi and Rank Math all have AI features built in. In addition, with WordPress 7.0 on the horizon, native AI links are coming into the core.    <\/p>\n<p>For us as a full-service agency, this raises a question: how do we relate to this shift? Do we go along with the promise of faster, cheaper and easier? Or do we bet on what AI cannot (yet) do?  <\/p>\n<p>The answer is: both. But with a clear distinction. <\/p>\n<h2 class=\"wp-block-heading\">Where AI makes our work better<\/h2>\n<p>At 2manydots, we use AI on a daily basis. Not as a replacement for our developers, but as an accelerator of their work. Think about:  <\/p>\n<ul class=\"wp-block-list\">\n<li><strong>Prototyping and boilerplate.<\/strong>  A simple plugin structure or a first draft for a custom block? What used to take half a day, now stands in half an hour. The AI provides the skeleton, our developers take care of the quality.  <\/li>\n<li><strong>Code review and debugging.<\/strong>  AI tools are excellent at detecting patterns and suggesting solutions. For example, every pull request with us is checked by Claude. Especially with complex WooCommerce integrations or migrated themes and plug-ins, this saves search time.  <\/li>\n<li><strong>Content and copywriting.<\/strong>  For first drafts of SEO texts, meta-descriptions or email campaigns, AI is a good sparring partner. The end result always passes through our own fingers. <\/li>\n<li><strong>Data analysis and reporting.<\/strong>  Interpreting GA4 data, inventing Looker Studio dashboards and recognizing patterns in large data sets: AI helps us arrive at insights faster.<\/li>\n<\/ul>\n<p>In the aggregate, then, this means: AI as assistant, not author. As first concept, not final product. <\/p>\n<h2 class=\"wp-block-heading\">Where it goes wrong: the rise of &#8220;vibe coding&#8221;<\/h2>\n<p>There&#8217;s a term you hear more and more often: <em>vibe coding<\/em>. The idea is simple: you describe what you want in plain language, the AI builds it, and you adjust with new prompts instead of code. It sounds magical, and for a quick landing page or a simple pricing table, it works just fine.  <\/p>\n<p>But once it becomes more serious, larger and more business-critical, the risks quickly mount.<\/p>\n<p>WebDevStudios, another agency, recently shared a telling case. They reviewed a plug-in that a client had entirely generated by an AI model. At first glance, everything worked. An in-depth audit revealed more than a hundred security issues, including critical vulnerabilities.   <\/p>\n<p>This is no accident. The <a href=\"https:\/\/savvy.co.il\/en\/blog\/wordpress-development\/vibe-coding-wordpress\/\" target=\"_blank\" rel=\"noreferrer noopener\">2026 Patchstack Security Report<\/a> shows that over 11,000 new WordPress vulnerabilities were recorded in 2025, a 42% increase over the previous year. In fact, the number of severely exploitable vulnerabilities increased by 113%. AI-generated code that is not reviewed by an experienced developer most likely contributes to that problem.   <\/p>\n<p>Joost de Valk, founder of Yoast and one of the most influential voices in the WordPress community, recently <a href=\"https:\/\/joost.blog\/vibe-coding-trap-design-system\/\" target=\"_blank\" rel=\"noreferrer noopener\">warned<\/a> that vibe-coded blocks are &#8220;disposable code&#8221;: isolated islands of logic and styling with no cohesion. When an AI generates twenty different blocks based on twenty separate prompts, you haven&#8217;t built a website. You&#8217;ve stuck a few pretty band-aids that fall apart at the first major change.  <\/p>\n<h2 class=\"wp-block-heading\">What AI can&#8217;t do (and probably won&#8217;t be able to do for now)<\/h2>\n<p>The core of our work is not about code knocking. It&#8217;s about solving the right problem. And that requires things where AI is structurally deficient:  <\/p>\n<ul class=\"wp-block-list\">\n<li><strong>Strategic thinking.<\/strong>  An AI can build a checkout flow, but cannot determine whether that flow fits your target audience&#8217;s purchasing behavior.<\/li>\n<li><strong>Understanding context.<\/strong>  Each client has its own tech stack, its own integrations, its own business logic and pain points in the business. AI doesn&#8217;t know that context and makes assumptions that an experienced agency would be more likely to predict. Ask an AI to build a WooCommerce integration and you&#8217;ll get something that makes technical sense, but makes no sense commercially. Like asking a chef to make a dish without telling you that the guest is allergic to nuts.   <\/li>\n<li><strong>Taking responsibility.<\/strong>  If something goes wrong after an update, who fixes it? AI-generated code without human ownership is a risk you pass on to the future. <\/li>\n<li><strong>Long-term quality.<\/strong>  WordPress releases new updates several times a year. Plug-ins update weekly. PHP versions change. Code that works today may quietly break after the next update. Maintenance requires understanding, not just output. Someone with knowledge must take ownership of this.     <\/li>\n<\/ul>\n<p>Brad Vincent, CEO of FooPlugins, articulated:<\/p>\n<blockquote class=\"wp-block-quote is-layout-flow wp-block-quote-is-layout-flow\">\n<blockquote class=\"wp-block-quote is-layout-flow wp-block-quote-is-layout-flow\">\n<p><em>&#8220;Some people have the opinion that you can just vibe code a plugin from scratch. And this might be true for a lot of simple plugins. But there are 2 things you do not get from vibe coded plugins: <strong>support when things go wrong<\/strong> and an <strong>author who cares<\/strong> about the things you have not even considered (standards, WP core updates, security, etc).&#8221;  <\/em><\/p>\n<p><cite>Brad Vincent (CEO of FooPlugins) &#8211; Source: Blocksy<\/cite><\/p><\/blockquote>\n<\/blockquote>\n<h2 class=\"wp-block-heading\">Our approach: AI as a tool, people as the foundation<\/h2>\n<p>At 2manydots, we deliberately take a hybrid approach:<\/p>\n<ul class=\"wp-block-list\">\n<li><strong>Automate low-risk tasks.<\/strong>  Prototypes, boilerplate, initial concepts, data analysis. Wherever the cost of error is low and the time savings are high. <\/li>\n<li><strong>Protecting high-risk tasks.<\/strong>  Checkout flows, customer data, payment integrations, security configurations. Here, human expertise is not optional, but essential. Not for nothing are we ISO 27001 and ISO 9001 certified: information security and quality assurance are in every process with us.  <\/li>\n<li><strong>Always review.<\/strong>  No line of AI-generated code goes live without review by a developer who knows WordPress inside out. This is not a distrust toward the technology. It&#8217;s the best thing to do.  <\/li>\n<\/ul>\n<p>AI makes it easier to produce something working quickly. But the difference is in knowing <em>why<\/em> something works and when it will break. You build that knowledge with experience, not prompts.  <\/p>\n<h2 class=\"wp-block-heading\">What does this mean for you as a customer?<\/h2>\n<p>If you are considering using AI for your WordPress website or webshop, these are the questions you should ask yourself:<\/p>\n<p><strong>How great is the risk if things go wrong?<\/strong>  A generated FAQ page? Fine. A generated payment module? Think twice.   <\/p>\n<p><strong>Who takes responsibility?<\/strong>  If an AI-generated plug-in contains a security vulnerability, who fixes it? And who monitors the security? <\/p>\n<p><strong>Are you thinking in cost or in value?<\/strong>  AI makes it cheaper to produce code. But the value of a well-built Web site is not in the code alone. It&#8217;s in the strategy, the reliability, the follow-through and the assurance that it&#8217;s right.  <\/p>\n<h2 class=\"wp-block-heading\">Hours are our revenue model<\/h2>\n<p>We also want to be honest here about something you don&#8217;t often read in agency blog posts: AI is exciting for us, too. And we don&#8217;t mean &#8220;exciting&#8221; as in enthusiastic, but as in uncomfortable. <\/p>\n<p>Our revenue model, like most agencies, is based on hours. We sell time from smart people. And if an AI tool allows a developer to do something in two hours that previously took eight hours, that&#8217;s great for the client. But it also means that as a company we have to think about what we are actually selling then.   <\/p>\n<p>That tension is real, and we think it&#8217;s important to be open about it. It forces us to continually ask ourselves the question: where is our value really? <\/p>\n<p>The answer we find again and again: not in typing lines of code. The value is in knowing what lines of code are needed. In understanding a customer&#8217;s context, in foreseeing problems before they arise, and in taking responsibility for the end result. Those are things that don&#8217;t get faster through AI. Those get better through experience.    <\/p>\n<p>At the same time, we also see it as an opportunity. If we can deliver faster, we can provide more value within the same budget. We can dive deeper into strategy, pay more attention to quality control and focus on the kind of work that will benefit a client the most. But it requires that we dare to adjust our model and remain honest about what an hour of ours is worth and why.   <\/p>\n<h2 class=\"wp-block-heading\">Don&#8217;t get me wrong<\/h2>\n<p>This is not a <em>trash post<\/em> about AI. Far from it. <\/p>\n<p>AI is fantastic. I still marvel at it every day. The speed at which you go from idea to working prototype, the way it helps you think, the possibilities that were impossible just a year ago. It&#8217;s truly amazing and I wouldn&#8217;t want to be without it.   <\/p>\n<p>But enthusiasm should not be a reason to turn off your common sense. You don&#8217;t just install an open AI tool<a href=\"https:\/\/tweakers.net\/geek\/245068\/ai-topvrouw-meta-wist-per-ongeluk-honderden-e-mails-met-openclaw.html\" target=\"_blank\" rel=\"noopener\">(OpenClaw<\/a>) and give it access to everything. You don&#8217;t let an AI write unchecked code that runs on an online store where customers leave their credit card information. You don&#8217;t blindly trust output that looks good but no one has really looked at.   <\/p>\n<p>Because AI can also start working on its own if you don&#8217;t shield it properly. It does not distinguish between a smart solution and a dangerous one. Making that distinction, that is and always will be human work.  <\/p>\n<p>The agencies that are going to make a difference are not the ones shouting the loudest about AI. Nor the ones who ignore it. They are the agencies that know when to &#8220;step on the gas&#8221; and when to apply the brakes for a moment.  <\/p>\n<p>At 2manydots we do both, of course. \ud83d\ude09 <\/p>\n","protected":false},"author":3,"featured_media":7216,"template":"","tags":[],"type_news_pt":[],"theme_news_pt":[],"class_list":["post-7214","news_pt","type-news_pt","status-publish","has-post-thumbnail","hentry"],"acf":[],"_links":{"self":[{"href":"https:\/\/www.2manydots.nl\/en\/wp-json\/wp\/v2\/news_pt\/7214","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.2manydots.nl\/en\/wp-json\/wp\/v2\/news_pt"}],"about":[{"href":"https:\/\/www.2manydots.nl\/en\/wp-json\/wp\/v2\/types\/news_pt"}],"author":[{"embeddable":true,"href":"https:\/\/www.2manydots.nl\/en\/wp-json\/wp\/v2\/users\/3"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.2manydots.nl\/en\/wp-json\/wp\/v2\/media\/7216"}],"wp:attachment":[{"href":"https:\/\/www.2manydots.nl\/en\/wp-json\/wp\/v2\/media?parent=7214"}],"wp:term":[{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.2manydots.nl\/en\/wp-json\/wp\/v2\/tags?post=7214"},{"taxonomy":"type_news_pt","embeddable":true,"href":"https:\/\/www.2manydots.nl\/en\/wp-json\/wp\/v2\/type_news_pt?post=7214"},{"taxonomy":"theme_news_pt","embeddable":true,"href":"https:\/\/www.2manydots.nl\/en\/wp-json\/wp\/v2\/theme_news_pt?post=7214"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}