How to enable the WordPress AI Assistant 🔗 **Source:** [How to enable the WordPress AI Assistant](https://wordpress.com/blog/2026/02/17/wordpress-ai-assistant/) > [!note]+ Document Notes > tags: [WordPress, AI, site-building] > author: Ronnie Burt > source: WordPress.com > reference: [https://wordpress.com/blog/2026/02/17/wordpress-ai-assistant/] > date created: 2026-02-17 00:00 > > # 🏷️ Title: How to enable the WordPress AI Assistant > <!-- deep-read:sections start --> ## 🧭 Table of Contents - [📝 Summary](#-summary) - [📖 Main Content](#-main-content) - [🗒️ Notes](#️-notes) - [📚 References](#-references) - [🗣️ Paraphrase](#️-paraphrase) - [📰 Newsletter](#-newsletter) - [✅ Action Items](#-action-items) - [🧪 Hypotheses](#-hypotheses) - [📊 Methodology](#-methodology) - [❓ Questions](#-questions) - [🔮 Future Research](#-future-research) - [💡 Implications](#-implications) - [🧠 Learning Styles Assessment](#-learning-styles-assessment) - [📊 Accessibility Assessment](#-accessibility-assessment) - [🌍 DEIB Assessment](#-deib-assessment) - [✅ Logical Validity](#-logical-validity) - [🛡️ DARVO Analysis](#-darvo-analysis) - [🎯 Conclusion](#-conclusion) ### 🔗 References - Include links cited in or relevant to the article. ## 📝 Summary - What happened: WordPress.com introduced an on-site AI Assistant for Business/Commerce plans (and AI-built sites) that lives in the editor, Media Library, and block notes. - Why it matters: Brings “ask-and-apply” AI directly into WordPress, removing copy-paste and prompt-engineering friction. - Key stakeholders: WordPress.com site owners, content creators, designers, devs, and teams collaborating in the editor. - Risks and tradeoffs: Works best with block themes; classic-theme users get only image generation/editing. Reliance on AI quality and accuracy. - Bottom line: A native, opt‑in AI layer for design, content, and media, tightly integrated into the WordPress.com editing experience. ## 📖 Main Content - The article announces that the WordPress AI Assistant is now available inside WordPress.com sites, especially for Business and Commerce plans, at no extra cost. If you used the AI website builder, the same intelligence now remains available while you edit. - Unlike standalone tools, the assistant runs inside your dashboard and understands your layout and content so it can directly modify blocks, patterns, and media without extra code or copy‑pasting. - In the editor, you can ask natural-language requests such as “Make this section feel more modern and spacious” or “Add a Contact page,” and it will adjust layouts, styles, colors, fonts, and even generate images or translations right where you’re working. - In the Media Library, you can generate and edit images (for example, “Generate an image of a calico cat reading a book” or “Update this image to be black and white”). The feature uses “Nano Banana” models and lets you control style and aspect ratio. - Block notes, introduced in WordPress 6.9, allow in-editor collaboration. The AI Assistant plugs into that via `@ai` mentions, letting you request fact-checks, headline ideas, or examples with the current content as context plus relevant external info. - Enabling the assistant is done via site settings: log in, open your site’s settings, find the “AI tools” section, and toggle the assistant on. If your site was created with the AI website builder, the assistant is enabled automatically. - The tool works best with block themes; in classic themes, it won’t appear in the editor but image generation/editing in the Media Library remains available. - The article frames this as “WordPress with intelligence built in,” positioning the assistant as an ongoing helper for creating, designing, and growing sites faster than traditional workflows. ### 🗒️ Notes - AI Assistant is embedded in WordPress.com, not a separate app. - Available at no extra cost for Business/Commerce plans; automatically on for sites created with the AI website builder. - Primary capabilities: - Editor: - Adjust sections and layouts by description. - Change site colors and font choices. - Insert sections like testimonials or new pages (e.g., Contact). - Rewrite content for different tones. - Translate sections (e.g., into Spanish). - Generate contextual images (e.g., croissant image for a blog post). - Media Library: - Generate new images using prompts. - Edit existing images (style, color, elements swapped out). - Uses Nano Banana models; no separate subscription. - Block Notes: - `@ai` mention to: - Fact-check content. - Propose headlines. - Suggest examples to strengthen a paragraph. - Uses current block content and external sources as context. - Enabling steps: - Log in → Sites list → select site → Settings → “AI tools” → toggle on. - For AI-built sites, already on regardless of plan. - Theme compatibility: - Best with block themes: full editor integration. - Classic themes: no assistant in editor, but Media Library AI images still work. - Positioning: - Contrast with one-off site generators or isolated chat boxes. - Emphasis on integrated, continuous assistance for design, content, and media. ## 📚 References - WordPress.com announcement: “How to enable the WordPress AI Assistant” (primary source). - WordPress.com: AI website builder product page. - WordPress 6.9 release notes (for context on block notes and editor features). - WordPress.com documentation on block themes vs classic themes. - WordPress.com support docs on Media Library and image editing. ## 🗣️ Paraphrase - Paragraph A: WordPress.com now embeds an AI Assistant directly into your dashboard so it can understand and act on your site’s content and layout, especially for customers on higher-tier plans, keeping the same conversational AI you may have used to generate your site in the first place. - Paragraph B: Once enabled, the assistant helps you shape layouts, tweak design systems, write and refine copy, translate text, and generate or edit images from within the editor or Media Library, and it hooks into collaborative block notes so you can request fact-checks or ideas inline as you and your team work. ## 📰 Newsletter WordPress.com just leveled up your editing toolbox. The new WordPress AI Assistant now lives right inside your editor, Media Library, and block notes—no more bouncing between tools or wrangling prompts. Ask it to redesign a section, translate a page, or generate on-brand images, and see changes applied instantly. If you’re on a Business or Commerce plan (or used the AI website builder), you can enable it today from your site settings and start shipping faster with an AI co‑pilot baked into WordPress. ## ✅ Action Items #### DevRel - Document end-to-end demos showing AI Assistant workflows (editor + Media Library + block notes). - Produce sample prompts and “prompt patterns” for common WordPress use cases (landing pages, blogs, portfolios). - Add AI Assistant sections to existing WordPress.com tutorials and workshop curricula. - Gather developer feedback on block-theme requirements and integration surface for future extensibility. - Track adoption metrics and identify friction in enabling the assistant from site settings. #### OSPO - Clarify upstream relationships and licensing for Nano Banana models and any third‑party AI. - Establish internal guidance on AI‑generated asset licensing and attribution for site owners. - Coordinate security and privacy reviews around AI data handling within WordPress.com. - Maintain an inventory of AI-related components, dependencies, and model versions. #### Community - Encourage meetups and WordCamps to host live sessions on using the AI Assistant responsibly. - Curate community prompt libraries and example sites showcasing AI-designed layouts. - Collect feedback from classic theme users on Media Library-only AI workflows and needs. #### WordPress - Core: monitor how AI-driven editing patterns influence block editor UX and future feature priorities. - Core Performance: study performance impact of AI tools in the editor/Media Library and optimize. - Core AI: define evaluation sets for content quality, factual accuracy, and style control. - **Core Program Team:** sync roadmaps so editor, themes, and AI features evolve coherently. - Mobile: explore how similar assistant capabilities could surface in the apps. - Playground: create browser-based labs to safely try the AI Assistant with sample content. - Community: update meetup kits with AI Assistant demo scripts and guidance. - Training: publish lesson plans focusing on responsible AI usage in WordPress.com. - Marketing: run campaigns highlighting the integrated, no-extra-cost Assistant for eligible plans. - Support: extend knowledge base coverage for AI troubleshooting, limits, and best practices. - Documentation: clearly document theme requirements, enabling steps, and prompt examples. - Accessibility: ensure AI-generated layouts and images align with accessibility best practices. - Meta: consider .org/.com boundaries and messaging around where the Assistant is available. #### The WPOCC - Programs: pilot fellowships focused on AI-in-WordPress education and governance. - Projects: sponsor documentation sprints to cover AI features and responsible-use guidelines. - Funding experiments: support contributors building open, auditable AI evaluation tools for WordPress sites. ### FAIR - Technical independence: document model sources and allow exports of AI-related content metadata. - Policies and covenants: publish transparent policies on AI funding, partnerships, and vendor lock‑in mitigation. - Productized governance artifacts: provide templates for AI feature charters and evaluation scorecards for WordPress projects. ## 🧪 Hypotheses - H1: Embedding the AI Assistant directly in the editor will reduce time to publish new pages compared to using external AI tools. - H2: Sites using block themes will see higher adoption and satisfaction with the assistant than classic-theme sites. - H3: Integrating AI into block notes will increase collaborative editing frequency and depth. - H4: Native AI image generation in the Media Library will reduce reliance on third‑party stock image services. ### 📊 Methodology - Compare publishing timelines and edit counts for users before/after enabling the assistant. - Segment user feedback and usage metrics by theme type (block vs classic). - Instrument block notes usage, tracking `@ai` mentions and resulting content changes. - Survey media usage patterns and external image-source referrals pre- and post-launch. ### ❓ Questions - How does WordPress.com handle privacy and training data for content passed through the assistant? - What safeguards exist for factual accuracy, especially when using `@ai` for fact-checking? - Will similar AI features become available to self-hosted WordPress.org users? - How customizable will the assistant be for different brands or editorial standards? ### 🔮 Future Research - Evaluate long-term impact of AI-assisted editing on content quality and accessibility. - Study how AI-generated layouts affect user engagement and conversion. - Explore personalization (per-site or per-user AI behavior) within WordPress. - Investigate best practices for teams co-editing with AI in block notes. ### 💡 Implications - Practice: Site owners can offload routine design and content tasks to AI, focusing more on strategy. - Policy: Platforms need clear AI-use and disclosure policies, including for generated images. - Security: AI services integrated into dashboards must be audited for data handling risks. - Education: Training materials should teach both capabilities and limits of the assistant. - Funding: Investment may shift from standalone AI tools to platform-embedded assistants. ### 🧠 Learning Styles Assessment - Reading level estimate: Around grade 8–10 (Flesch-Kincaid style) based on short sentences, marketing tone, and limited jargon. #### 👀 Visual learners - Present: Product screenshots (editor, Media Library, block notes) illustrating the assistant. - Improve: Add labeled before/after layout and image comparisons, plus a simple architecture sketch of where AI lives in the workflow. #### 🔊 Aural learners - Present: No explicit audio or narration mentioned. - Improve: Provide a short narrated video or audio walkthrough of enabling and using the assistant. #### 🗣️ Verbal learners - Present: Clear examples of prompts and use cases in plain language. - Improve: Add a glossary for key terms (block themes, block notes, Media Library, etc.). #### 🧩 Kinesthetic learners - Present: Step-by-step enabling instructions and concrete prompts to try. - Improve: Include a mini “lab” checklist (e.g., “enable assistant, redesign a section, generate one image, use `@ai` in block notes”). #### 🧠 Logical learners - Present: Implicit comparisons to other tools, and structured feature breakdowns. - Improve: Provide decision trees (e.g., “If using classic theme, then…”), and feature matrices vs external tools. #### 🧑‍🤝‍🧑 Social learners - Present: Emphasis on block notes collaboration. - Improve: Offer discussion prompts and links to community forums for sharing prompt ideas. #### 🧘‍♀️ Solitary learners - Present: Article format allows quiet, self‑paced exploration. - Improve: Add self-check questions or short reflective prompts about when to delegate work to AI. #### 🌿 Naturalistic learners - Present: No explicit environmental framing. - Improve: Discuss sustainability considerations of AI workloads or “digital ecosystem” analogies. ### 📊 Accessibility Assessment #### Screen reader semantics - Present: Blog layout typically uses headings and landmarks; screenshots may have some alt text. - Improve: Ensure all AI-related screenshots have descriptive alt text and that AI UI labels are semantic. #### Keyboard navigation - Present: Standard WordPress.com UI usually supports keyboard navigation. - Improve: Confirm all new AI controls (toggles, buttons, block notes mentions) are reachable and operable via keyboard. #### Contrast and readability - Present: WordPress.com generally respects minimum contrast. - Improve: Validate AI-related badges, highlights, and tooltips meet 4.5:1 contrast and have sufficient line-height. #### Text resizing and reflow - Present: Responsive design likely supports zoom and reflow. - Improve: Confirm AI panels and sidebars reflow gracefully at 200%+ zoom and with reduced-motion preferences. #### Media and captions - Present: Static screenshots only; no mention of video or captions. - Improve: Provide captioned video demos and downloadable transcripts for AI Assistant walk-throughs. #### Forms and interactions - Present: Basic toggle in settings; prompt input fields. - Improve: Ensure clear labels, error messages, and accessible notifications for AI failures or rate limits. #### Standards reference - Map identified improvements to WCAG 2.2 AA criteria, especially 1.4.x (contrast), 2.1.x (keyboard), 1.2.x (media), and 3.3.x (input assistance). ### 🌍 DEIB Assessment #### Cultural breadth - Present: Examples like croissants, Parisian cafés, cats reading—largely Western-centric but non-exclusive. - Improve: Show multilingual use cases and examples relevant to diverse regions and industries. #### Inclusive language - Present: Neutral, user-focused language with minimal jargon. - Improve: Add a short plain-language summary and clarify any WordPress-specific terminology. #### Neurodiversity support - Present: Clear headings, bullet lists, and concrete examples. - Improve: Further chunk content, use consistent icon+text patterns, and avoid dense paragraphs in future docs. #### Representation - Present: Visuals not fully described; diversity not clearly addressed. - Improve: Use imagery that reflects varied identities and roles, and describe that diversity in alt text where appropriate. #### Psychological safety - Present: Friendly, encouraging tone; no threatening or shaming language. - Improve: Link to community guidelines and provide channels for feedback/concerns about AI behavior. ### ✅ Logical Validity #### Strong reasoning - The article makes a clear comparative claim: external AI tools create friction (copy-paste, code handling), whereas an integrated assistant reduces that by acting directly on the site. This is a straightforward causal argument grounded in workflow differences. - It logically links block theme support to richer assistant capabilities, which follows from how block-based editing exposes structure the AI can manipulate. #### Fallacies - No obvious formal fallacies; the piece is mostly descriptive marketing rather than heavy argumentation. - Potential soft spot: it implies “faster than ever” without quantitative evidence; this could be strengthened with specific metrics or case studies. #### Tone of voice - Tone: optimistic, promotional, and user-centric. - Uses inviting language (“ready to help you create, design, and grow faster than ever”) and concrete prompts to make the assistant feel approachable. ### 🛡️ DARVO Analysis - Deny: No denial or minimization of harms; risks or limitations (e.g., classic theme constraints) are mentioned briefly but not spun. - Attack: No attacks on users or competitors, though there is light comparison to “most tools” and “others,” framed neutrally. - Reverse victim/offender: Not present; the article does not position WordPress.com as a victim or reframe criticism. ## 🎯 Conclusion - Bottom line: WordPress.com’s AI Assistant brings conversational, action-oriented AI into the editor, Media Library, and block notes, especially for Business/Commerce and AI-built sites. It emphasizes convenience—no copy‑paste or code—and works best with block themes. Next steps for readers are to enable the assistant in site settings, experiment with prompts for layout, content, and media, and evaluate how it fits into their publishing workflow. ## 🧱 Refactor Appendix ### 📚 Literature Split Pad - Purpose: Stage Konik CEE units that become per-source Literature notes. - Split level: **H3**. - Include verbatim quotes under 25 words and a [view highlight] link. ### [H1] WordPress embeds AI inside editor > [!quote] [How to enable the WordPress AI Assistant](https://wordpress.com/blog/2026/02/17/wordpress-ai-assistant/) by [[Ronnie Burt]] via [[WordPress.com]]. Published 2026-02-17. Accessed 2026-02-17. > “The WordPress AI Assistant works inside your actual site, helping adjust blocks, shape layouts, write content, and guide decisions.” Two lines: context and use. Cite data if relevant. [view highlight](https://wordpress.com/blog/2026/02/17/wordpress-ai-assistant/#H1) #xref #articleseed ID:rw_[MISSING] ### [H2] Assistant enhances Media Library images > [!quote] [How to enable the WordPress AI Assistant](https://wordpress.com/blog/2026/02/17/wordpress-ai-assistant/) > “Create and edit images directly in your Media Library.” Two lines: context and use. [view highlight](https://wordpress.com/blog/2026/02/17/wordpress-ai-assistant/#H2) #xref ID:rw_[MISSING] --- ### 🔖 Atomic Split Pad (Zettel Candidates) - Purpose: Promote reusable claims into Atomic notes. - Split level: **H4**. - Each item: one idea, present tense, specific, testable. #### [Z1] Embedded AI reduces WordPress editing friction - Condition: Users work in block themes with the AI Assistant enabled. - Pointer: AI Assistant announcement article. - Links: [[WordPress-AI]] [[Editor-Workflows]] #### [Z2] Native AI image tools lower third-party dependence - Condition: Users adopt Media Library AI generation and editing. - Pointer: AI Assistant announcement article. - Links: [[WordPress-Media-Library]] [[AI-Images]] --- ### ✏️ Fleeting Queue (Extract by Selection) - Purpose: Capture quick actions or sparks for Fleeting notes. - Extraction: **Select one line** → “Refactor: Extract selection to new note (content only).” - Keep each line short and self-contained. - [F1] Test AI Assistant prompts for layout and style changes—https://wordpress.com/blog/2026/02/17/wordpress-ai-assistant/ #fleeting #inbox - [F2] Compare Media Library AI images vs third-party stock workflows—https://wordpress.com/blog/2026/02/17/wordpress-ai-assistant/ #fleeting #inbox - [F3] Document best practices for `@ai` block notes collaboration—https://wordpress.com/blog/2026/02/17/wordpress-ai-assistant/ #fleeting #inbox --- <!-- deep-read:sections end -->