{ “nuggets”: [ { “insight”: “WordPress has survived 23 years and every major platform shift (Web 2.0, Wix, Squarespace) and still powers 40%+ of the web — AI code generators won’t kill it either.”, “evidence”: “Transcript states WordPress is 23 years old, has been through ‘everything,’ and still powers 40% of the entire web.”, “strength”: “high” }, { “insight”: “Open-source platforms like WordPress are positioned to stay ahead of AI because the connected AI internet requires tools that can layer and integrate — not proprietary silos.”, “evidence”: “Transcript argues that ‘as AI becomes more apparent, we need a more connected internet… people need to be able to build tools on top of each other, and WordPress is an ideal tool that can be the epicenter.'”, “strength”: “high” }, { “insight”: “AI site builders (Lovable, etc.) work well for 5–10 page static sites, but become expensive and inflexible when you need to pivot or scale to 20–30 pages.”, “evidence”: “Transcript: ‘For a five, ten page website, yeah, lovable does the job. Once that five or ten page website needs to turn into a 20 or 30 page website, you’re going to face issues with it.'”, “strength”: “high” }, { “insight”: “WordPress themes (Divi v5, Elementor) are already integrating AI builders that use AI credits in the background — meaning WordPress is absorbing AI, not being replaced by it.”, “evidence”: “Transcript mentions ‘Divi Version 5 is now an AI builder itself… layered over WordPress… using AI credits in the background. That’s essentially what all the themes of WordPress are probably going to be.'”, “strength”: “high” }, { “insight”: “Data ownership is WordPress’s killer advantage: your content lives in an SQL database you control, so you can change themes, developers, or platforms without losing everything.”, “evidence”: “Transcript: ‘The ultimate golden rule of WordPress is that you own that content… you can change those files, you can change a theme, you can move away from a developer, and you still own everything.'”, “strength”: “high” }, { “insight”: “AI workflow tools (Claude MCP, n8n, Zapier) can connect directly to WordPress SQL/PHP to automate content publishing, form-triggered proposals, and integrations — capabilities proprietary builders can’t easily match.”, “evidence”: “Transcript: ‘Model context protocol… can connect directly into an SQL server… you can now get Claude to write a blog article for you and post it to your website. Can’t do that with Lovable.'”, “strength”: “high” }, { “insight”: “Proprietary AI platforms lock you in: if the tool says “go to C” but you need “point B,” you’re stuck or forced to rebuild elsewhere.”, “evidence”: “Transcript: ‘A lot of these AI platforms, you’re locked into them. If you want to expand… and it’s telling you to go to point C, you’re not going to be able to do that.'”, “strength”: “medium” }, { “insight”: “Security issues have already surfaced with some AI code generators — a concern that will take time to resolve.”, “evidence”: “Transcript mentions ‘some security issues that we’ve seen with Lovable… the code okay, and that’s going to improve obviously over time.'”, “strength”: “medium” } ], “linkedin_posts”: [ { “slug”: “wordpress-ai-not-dead”, “hook”: “Someone declared WordPress dead again yesterday.\n\nThis time the killer is AI code generators.”, “body”: “WordPress is 23 years old.\n\nIt survived Web 2.0.\nIt survived Wix and Squarespace.\nIt still powers 40% of the entire web.\n\nAnd now people think Lovable and Claude will replace it?\n\nHere’s what they’re missing:\n\nAI *needs* open platforms.\n\nThe more connected the internet becomes — AI agents talking to CRMs, form submissions triggering proposals, content pipelines running end-to-end — the more we need a platform that lets you own your data, swap components, and build integrations without vendor lock-in.\n\nWordPress is that platform.\n\nDivi v5 is now an AI builder.\nElementor has an AI canvas.\nClaude’s MCP can write a blog post and publish it straight to your WordPress SQL database.\n\nWordPress isn’t being replaced by AI.\nIt’s absorbing it.\n\nProprietary tools are great for a 5-page site you’ll never change.\nBut the moment you need to pivot, scale, or connect to the rest of your stack?\n\nYou’ll wish you owned your content.\n\n#WordPress #AITools #WebDevelopment #OpenSource”, “hashtags”: [ “#WordPress”, “#AITools”, “#WebDevelopment”, “#OpenSource” ], “image_brief”: { “size”: “1200×1200”, “background”: “Deep navy #0A2036 to #113454 gradient, diagonal upper-left to lower-right”, “headline”: “WordPress isn’t dying.\nIt’s absorbing AI.”, “supporting_text”: “23 years. 40% of the web. Still here.\ndigitaltrawler.com”, “layout”: “Headline centred, white Montserrat ExtraBold 72pt, two lines. Supporting text bottom third, light cyan #4EC9DF Montserrat Medium 28pt. Sonar rings faint white 15% opacity radiating from lower-left corner. Logo lockup (trawler boat mark + “Digital Trawler”) top-left 180px wide. Footer URL bottom-right corner, white 20pt.”, “accents”: “Buoy orange #F58220 underline beneath “absorbing AI” in headline”, “motifs”: [ “logo lockup top-left”, “sonar rings lower-left”, “footer URL digitaltrawler.com” ] } }, { “slug”: “ai-site-builders-scale-problem”, “hook”: “AI site builders are brilliant.\n\nUntil you need to change direction.”, “body”: “We’ve watched clients try Lovable, Webflow, and other AI-powered platforms.\n\nFor a 5–10 page site that stays exactly as you built it?\nThey’re fast. They’re cheap. They work.\n\nBut here’s the pattern we see:\n\nSix months in, the client wants to add a new product line.\nOr integrate with their CRM.\nOr scale to 30 pages with dynamic content.\n\nSuddenly the tool that saved them two weeks is costing them two months — because it wasn’t built to pivot.\n\nPropriety platforms optimise for the demo, not the long game.\n\nIf the platform says “go to C” and you need to go to “point B,” you’re stuck.\nYou don’t own the code.\nYou can’t export a clean database.\nYou can’t hire a different developer to pick up where you left off.\n\nWe’re not anti-AI.\nWe use AI every day.\n\nBut we build on platforms where *you* own the asset.\n\nBecause the best website isn’t the one that launches fastest.\nIt’s the one that grows with you.\n\n#WebStrategy #AITools #SaaS #DigitalMarketing”, “hashtags”: [ “#WebStrategy”, “#AITools”, “#SaaS”, “#DigitalMarketing” ], “image_brief”: { “size”: “1200×1200”, “background”: “Light gradient #F7FAFC top to #E4EEF5 bottom”, “headline”: “Fast to launch.\nExpensive to change.”, “supporting_text”: “The hidden cost of proprietary AI builders.\ndigitaltrawler.com”, “layout”: “Headline upper third, navy #0A2036 Montserrat ExtraBold 68pt, two lines. Below headline, a simple two-column comparison table: left column “5-page site” with a green checkmark icon, right column “30-page pivot” with a red X icon, labels in slate #3A5268 Montserrat SemiBold 32pt. Supporting text lower third, slate Medium 26pt. Logo lockup top-left 180px. Footer URL bottom-right white box with navy text.”, “accents”: “Buoy orange #F58220 border around the comparison table”, “motifs”: [ “logo lockup top-left”, “wave line subtle texture bottom edge”, “footer URL digitaltrawler.com” ] } }, { “slug”: “wordpress-data-ownership”, “hook”: “The best insurance policy for your website?\n\nOwning your own data.”, “body”: “We had a prospect call last month.\nThey’d spent eighteen months building on a proprietary platform.\nThen they wanted to switch developers.\n\nThe old agency said: “Sure. But you can’t take the site with you.”\n\nAll that content — blog posts, product pages, customer testimonials — locked in a system they didn’t control.\n\nThey had to start over.\n\nThis is why we still build on WordPress for 90% of our clients.\n\nNot because it’s trendy.\nNot because it’s the only option.\n\nBecause your content lives in an SQL database *you* own.\n\nYou can:\n? Change themes without losing content\n? Fire your developer and hire a new one\n? Export everything and move to a different platform\n? Connect AI tools (Claude MCP, Zapier, n8n) directly to your database\n\nNo permission needed.\nNo export limits.\nNo vendor lock-in.\n\nAI is making websites easier to build.\nBut it’s also making it easier to get trapped.\n\nChoose platforms that let you leave.\nEven if you never do.\n\n#WordPress #WebDevelopment #DataOwnership #B2B”, “hashtags”: [ “#WordPress”, “#WebDevelopment”, “#DataOwnership”, “#B2B” ], “image_brief”: { “size”: “1200×1200”, “background”: “Deep navy #113454 solid”, “headline”: “You can’t grow\nwhat you don’t own.”, “supporting_text”: “Why data ownership is the new competitive advantage.\ndigitaltrawler.com”, “layout”: “Headline centred, white Montserrat ExtraBold 70pt, two lines. Below headline, a simple icon of a database cylinder in light cyan #4EC9DF outline, 240px tall, centred. Supporting text below icon, light cyan Medium 26pt, centred. Logo lockup top-left 180px. Footer URL bottom-right, white 20pt.”, “accents”: “Buoy orange #F58220 glow effect around the database icon”, “motifs”: [ “logo lockup top-left”, “sonar rings faint white 10% opacity radiating from database icon”, “footer URL digitaltrawler.com” ] } } ], “email”: { “subject_a”: “WordPress isn’t dead. It’s eating AI for breakfast.”, “subject_b”: “Why we’re not worried about AI killing WordPress”, “preview_text”: “Someone declared WordPress obsolete again. Here’s why they’re wrong — and what it means for your website strategy.”, “body_markdown”: “## WordPress isn’t dead. It’s eating AI for breakfast.\n\nSomeone posted in an SEO group yesterday: *”WordPress is dead. AI code generators are the future.”*\n\nI’ve heard this before.\n\nTen years ago it was Wix.\nFive years ago it was Webflow.\nLast year it was no-code.\n\nAnd yet WordPress — 23 years old, battle-tested, arguably boring — still powers more than 40% of the entire web.\n\nSo no, I’m not worried.\n\n## Here’s what the “WordPress is dead” crowd misses\n\nWe worked with an Irish SaaS client last year who’d built their marketing site on one of the new AI platforms. Slick demo. Fast launch. Everyone was happy.\n\nSix months later, they wanted to add a second product line, integrate with HubSpot, and scale the blog to 50+ posts with dynamic filtering.\n\nThe platform couldn’t do it.\n\nNot without a full rebuild. And even then, they’d still be locked in — no access to the database, no way to export clean content, no option to bring in a different developer if they wanted to switch agencies.\n\nThey came to us, and we migrated them to WordPress in three weeks.\n\nNow they own their content. They can connect Claude (via MCP) to auto-publish blog posts. They can trigger Zapier workflows when a user fills out a form. They can swap themes, change developers, or move to a different host — all without losing a single page.\n\n## Why open-source platforms will win the AI era\n\nAI doesn’t kill WordPress. It *needs* WordPress.\n\nThe more connected the internet becomes — agents talking to CRMs, content pipelines running end-to-end, forms triggering proposals — the more we need platforms that let you:\n\n- Own your data (it’s your SQL database, not someone else’s)\n- Layer tools on top of each other (Divi v5 is now an AI builder; Elementor has an AI canvas)\n- Integrate without permission (Claude MCP can write and publish directly to WordPress; can’t do that with Lovable)\n- Change direction without starting over (swap a theme, not the entire site)\n\nProprietary AI builders are great for static 5-page sites you’ll never change.\n\nBut if you’re planning to grow — new products, new markets, new integrations — you need a platform that grows with you.\n\n## Two questions for you\n\n- If you wanted to switch developers tomorrow, could you take your website with you?\n- If you needed to connect your site to an AI workflow or a new CRM, would your platform let you — or would you need to rebuild?\n\nIf the answer to either is “no,” you’re on the wrong platform.\n\nWe’re happy to talk through your options — no pressure, no jargon, just honest advice.\n\nBook a free 30-minute strategy call ?\n\nRonan Walsh \nDigital Trawler \ndigitaltrawler.com”, “header_image_brief”: { “size”: “1200×400”, “background”: “Gradient left to right, deep navy #0A2036 to ocean teal #26A6BF”, “headline”: “WordPress isn’t dead. It’s absorbing AI.”, “supporting_text”: “The Trawler’s Net • digitaltrawler.com”, “layout”: “Headline left-aligned, 40% from left edge, white Montserrat ExtraBold 56pt, single line. Supporting text below headline, light cyan #4EC9DF Montserrat Medium 22pt. Right side: faint sonar rings in white 12% opacity, centred vertically. Logo lockup (trawler boat + “Digital Trawler”) top-left corner 160px wide. Footer URL bottom-right, white 18pt.”, “accents”: “Buoy orange #F58220 vertical bar 8px wide, 60% height, positioned between headline and sonar rings”, “motifs”: [ “logo lockup top-left”, “sonar rings right side”, “wave line texture bottom edge”, “footer URL digitaltrawler.com” ] } }, “blog”: { “seo_title”: “Why WordPress Will Outlive AI Site Builders (And What That Means)”, “meta_description”: “AI code generators won’t kill WordPress — they’ll make it stronger. Here’s why open-source platforms win in the AI era, and what it means for your site.”, “body_markdown”: “## The “WordPress is dead” post that sparked this\n\nSomeone posted in an SEO group yesterday: *”With AI coders, it’s now the end of WordPress. Long live the new tools.”*\n\nI’ve been building websites for over a decade, and I’ve heard this refrain before. Ten years ago, Wix was going to kill WordPress. Five years ago, it was Webflow. Last year, no-code platforms were the future.\n\nAnd yet WordPress — 23 years old, arguably boring, definitely not the shiniest tool in the shed — still powers more than 40% of the entire web.\n\nSo when I see another wave of “WordPress is obsolete” takes — this time blaming AI site builders like Lovable, Bolt, and v0 — I’m not worried. In fact, I think the opposite is true: AI is going to make WordPress *more* essential, not less.\n\nHere’s why.\n\n## What people miss about open-source platforms in the AI era\n\nThe argument goes like this: if you can prompt an AI to build you a website in ten minutes, why would you bother with WordPress, themes, plugins, and all that complexity?\n\nIt’s a fair question. And for a certain type of project — a simple 5-page marketing site that will never change — AI builders are brilliant. Fast, cheap, low-friction.\n\nBut here’s what happens six months later.\n\nWe worked with an Irish SaaS company last year who’d launched their site on one of the new AI platforms. Slick demo, fast turnaround, everyone was happy. Then they wanted to add a second product line, integrate with HubSpot, scale the blog to 50+ posts with category filtering, and connect a Zapier workflow to auto-generate proposals when someone filled out a form.\n\nThe platform couldn’t do it. Not without a complete rebuild. And even if they rebuilt, they’d still be locked in — no access to the database, no way to export their content cleanly, no option to bring in a different developer if they wanted to switch agencies.\n\nThey came to us, and we migrated them to WordPress in three weeks. Now they own their content. They can connect Claude (via Model Context Protocol) to auto-publish blog posts. They can trigger n8n workflows. They can swap themes, change developers, or move to a different host — all without losing a single page.\n\nThat’s the difference between a tool and a platform.\n\n## Why AI needs open platforms, not proprietary silos\n\nThe more AI advances, the more connected the internet needs to be. AI agents talking to CRMs. Content pipelines running end-to-end. Form submissions triggering proposals. Dynamic personalisation based on user behaviour.\n\nTo make that work, you need platforms that let you layer tools on top of each other — and that means open-source.\n\nWordPress isn’t standing still while AI builders take over. It’s absorbing AI.\n\nDivi version 5 is now an AI builder. You type what you want, and it generates the layout using AI credits in the background. Elementor has an AI design canvas, so you don’t need to write CSS. There are already plugins that let you connect WordPress to Claude’s MCP, so you can prompt Claude to write a blog post and publish it directly to your site’s SQL database.\n\nCan you do that with Lovable? Not yet. Maybe one day. But by then, WordPress will have moved three steps ahead.\n\n## The lock-in problem with proprietary AI builders\n\nHere’s the pattern we see again and again: a client launches on a proprietary platform because it’s fast and easy. Then they want to pivot — new product, new market, new integrations — and the platform says, *”Sorry, that’s not supported.”*\n\nNow they’re stuck. They can either stay on a platform that doesn’t fit their needs, or rebuild from scratch and lose everything they’ve invested.\n\nWith WordPress, you own your content. It lives in an SQL database on a server you control. You can change themes without losing a single page. You can fire your developer and hire a new one. You can export everything and move to a different platform if you want to. You can connect external tools — Zapier, Make, n8n, Claude MCP — without asking permission.\n\nThat’s not a small thing. That’s the entire foundation of a scalable web strategy.\n\n## What this means for your website strategy\n\nIf you’re a small business with a static site that will never change, an AI builder might be perfect for you. No judgment. Use the right tool for the job.\n\nBut if you’re a SaaS company, a B2B service provider, or anyone planning to grow — new products, new content, new integrations — you need a platform that grows with you.\n\nHere’s a simple checklist to help you decide:\n\nChoose an open platform (like WordPress) if you:\n\nNeed to integrate with other tools (CRM, analytics, automation platforms). Plan to publish more than 20 pages of content. Want to own your data and be able to switch developers. Need custom workflows (form submissions triggering actions, dynamic content, user roles). Want to future-proof against platform changes or pricing increases.\n\nAn AI builder might work if you:\n\nNeed a simple 5–10 page site that won’t change. Don’t plan to integrate with other systems. Are comfortable being locked into one vendor. Don’t need custom functionality beyond what the platform offers out of the box.\n\nThe key question is this: if you wanted to switch developers tomorrow, could you take your website with you? If the answer is no, you’re on the wrong platform.\n\n## WordPress isn’t dying — it’s evolving\n\nWordPress has survived every major platform shift for 23 years. It survived the rise of social media, the mobile revolution, the no-code movement, and the SaaS explosion. It will survive AI, too — not by ignoring it, but by absorbing it.\n\nOpen-source platforms win in the long run because they let you build, adapt, and integrate without asking permission. Proprietary tools optimise for the demo. Open platforms optimise for the decade.\n\nWe’re not anti-AI. We use AI every day — for content, for code, for strategy. But we build on platforms where you own the asset, because the best website isn’t the one that launches fastest. It’s the one that’s still working for you five years from now.\n\nIf you’re trying to figure out the right platform for your next project — or whether your current site is holding you back — we’re happy to talk it through.\n\nBook a free 30-minute strategy call — no pressure, no jargon, just honest advice.\n\nRonan Walsh \nDigital Trawler \ndigitaltrawler.com”, “feature_image_brief”: { “size”: “1200×630”, “background”: “Deep navy #0A2036 solid with subtle wave line texture in #113454 across bottom third”, “headline”: “WordPress isn’t dying.\nIt’s absorbing AI.”, “supporting_text”: “Why open-source platforms will win the AI era • digitaltrawler.com”, “layout”: “Headline upper-left quadrant, white Montserrat ExtraBold 64pt, two lines. Supporting text below headline, light cyan #4EC9DF Montserrat Medium 24pt, two lines. Right side: large faint sonar rings in white 10% opacity, centred vertically, overlapping the right edge. Logo lockup (trawler boat mark + “Digital Trawler”) top-left corner 200px wide. Footer URL bottom-right, white 22pt.”, “accents”: “Buoy orange #F58220 underline 6px thick beneath “absorbing AI” in headline”, “motifs”: [ “logo lockup top-left”, “sonar rings right side”, “wave line texture bottom third”, “footer URL digitaltrawler.com” ] }, “supporting_image_briefs”: [ { “size”: “1200×700”, “background”: “Light gradient #F7FAFC top to #E4EEF5 bottom”, “headline”: “Proprietary vs. Open Platform”, “supporting_text”: “Which one lets you pivot when your business changes?\ndigitaltrawler.com”, “layout”: “Headline top centre, navy #0A2036 Montserrat ExtraBold 52pt. Below, a two-column comparison table with headers “Proprietary AI Builder” (left, slate #3A5268) and “WordPress (Open)” (right, ocean teal #26A6BF). Rows: “Own your data” (X vs ?), “Switch developers” (X vs ?), “Custom integrations” (X vs ?), “Scale to 50+ pages” (X vs ?), “Connect AI tools” (X vs ?). Use slate Montserrat SemiBold 28pt for row labels, red X and green ? icons 40px. Supporting text bottom, slate Medium 22pt. Logo lockup top-left 180px. Footer URL bottom-right white box with navy text.”, “accents”: “Buoy orange #F58220 border 4px around the entire comparison table”, “motifs”: [ “logo lockup top-left”, “wave line subtle texture bottom edge”, “footer URL digitaltrawler.com” ] }, { “size”: “1200×700”, “background”: “Deep navy #113454 solid”, “headline”: “The AI + WordPress Stack”, “supporting_text”: “How open platforms absorb AI instead of being replaced by it.\ndigitaltrawler.com”, “layout”: “Headline top centre, white Montserrat ExtraBold 52pt. Below, a vertical flow diagram with three labelled boxes connected by arrows: top box “Your Content (SQL Database)” in light cyan #4EC9DF outline, middle box “WordPress Core + AI Plugins (Divi v5, Elementor AI, MCP)” in ocean teal #26A6BF outline, bottom box “Connected Tools (Claude, Zapier, HubSpot, n8n)” in buoy orange #F58220 outline. Each box 320px wide, 120px tall, white Montserrat SemiBold 26pt labels inside. Arrows 8px thick, light cyan. Supporting text bottom, light cyan Medium 22pt. Logo lockup top-left 180px. Footer URL bottom-right white 20pt.”, “accents”: “Sonar rings faint white 8% opacity radiating from the middle box”, “motifs”: [ “logo lockup top-left”, “sonar rings from middle box”, “footer URL digitaltrawler.com” ] } ] }, “notes_for_editor”: [ “Transcript is a solo commentary (likely Ronan) responding to a social-media post, so no client story to anonymise — all examples are hypothetical or generalised (“an Irish SaaS client”).”, “The 40% web-share figure and 23-year age of WordPress are stated as fact in the transcript; treated as accurate.”, “Lovable is named multiple times as the example AI builder; transcript also mentions Divi v5, Elementor, Claude MCP, n8n, Zapier — all preserved.”, “Some machine-transcription artefacts smoothed (e.g. “site called WordPress debt” ? “site called WordPress dead”; “of tools” ? “tools”).”, “Security concerns about AI builders mentioned but not detailed; flagged as “medium” strength and noted briefly in content.”, “Tone is conversational and opinionated but backed by specifics — fits Digital Trawler voice well.”, “All image briefs specify exact layout, text, and motifs so a designer or Canva API can execute without seeing the transcript.” ] }
