Most AI website tools work the same way. You describe what you want in a chat window, get back some code or a template, and then figure out what to do with it. The AI and the website live in separate worlds.
WordPress.com just collapsed that gap. The new WordPress AI Assistant, announced on February 17, works within the editor and Media Library—not alongside them. It understands your site’s content, layout, and structure, and takes action where you’re already building. No copy-pasting. No prompt engineering. No generated code, you need to place yourself.
That matters because WordPress powers roughly 43% of all websites on the internet. When AI becomes native to the platform that powers nearly half the web, it stops being a feature and becomes infrastructure.
What the Assistant Actually Does
The WordPress AI Assistant shows up in three places once enabled.
In the editor, it handles structure and content. Tell it to add a testimonials section, create a Contact page, change site colors, or swap fonts — and watch changes appear in real time. For content, it rewrites copy to match the tone, translates sections, and generates alternative headlines. The instructions are conversational. “Make this section feel more modern and spacious” works fine.
In the Media Library, the assistant generates and edits images using Google Gemini’s Nano Banana models. You can specify aspect ratios and styles — no separate subscription or external tool required.
In block notes — the collaborative annotation feature from WordPress 6.9 — tag the assistant with @ai to ask questions with your content as context. It can fact-check a paragraph, suggest examples, or propose headlines within the editor’s collaboration workflow. Responses include relevant links and citations.
Why Context Changes Everything
The distinction between “AI tool that generates website content” and “AI assistant that understands your website” is more significant than it sounds.
Standalone AI tools produce output in a vacuum. They don’t know your color palette, navigation structure, brand voice, or content organization. Every interaction starts from zero. You’re the integration layer.
The WordPress AI Assistant skips that step. Because it operates within the block editor and has access to your site’s structure, it makes changes that respect your existing design system. When it adds a section, it follows your current patterns. When it rewrites copy, it takes the surrounding content into account.
This is the same shift we’ve seen in developer tools—from AI that generates code in a chat window to AI that operates within the codebase with full project context. WordPress is applying that principle to web publishing.
“WordPress embedding AI into the editor rather than alongside it reflects where platform vendors are headed: AI as a native capability, not a bolt-on tool. At 43% of the web, that design choice carries weight even if the feature set is incremental,” according to Mitch Ashley, VP and practice lead, software lifecycle engineering, The Futurum Group.
“For web publishers, the shift is straightforward. Site-aware context that respects existing design and content structure reduces the integration work users currently absorb themselves in. That’s a workflow change, not a product revolution, but it’s the kind of friction removal that compounds over time.”
The Competitive Picture
WordPress isn’t the first web platform to add AI. Wix launched an AI Site Generator. Squarespace added AI copy tools. Shopify expanded its Magic features. But most treat AI as a creation tool — helpful at the starting line, then absent from ongoing work.
WordPress.com’s approach differs: the assistant continues after the site is built. It stays available for ongoing content updates, design adjustments, and structural changes. For the millions of WordPress sites that publish regularly, that ongoing presence matters more than one-time generation.
The opt-in model is worth noting. The assistant is available at no extra cost on Business and Commerce plans but requires manual activation. WordPress is clearly aware that not every user wants AI in their workflow.
What This Signals
The block notes integration is quietly the most interesting piece. By extending WordPress 6.9’s AI collaboration feature, WordPress transformed the assistant into a team member rather than a standalone tool. Content teams can ask the AI to fact-check, brainstorm, or suggest edits in the same space where they leave comments for each other. That blurs the line between human collaboration and AI assistance in a way that feels natural.
For the broader AI landscape, the signal is clear: the platforms where people build things are absorbing AI rather than outsourcing it. WordPress joining that trend — at 43% of the web — accelerates the shift from “AI as separate tool” to “AI as embedded capability.”
The assistant works best with block themes. Classic theme users can access AI image generation in the Media Library, but won’t see the assistant in the editor.
