Build a WordPress Site With ChatGPT or Claude  🔗 **Source:** [Build a WordPress Site With ChatGPT or Claude](https://jetpack.com/resources/build-a-wordpress-site-with-chatgpt-or-claude/) > [!note]+ Document Notes > tags: > - wordpress > - ai-assistants > - mcp > - jetpack > - site-management > - developer-tooling > author: Adam Pickering > source: https://jetpack.com/resources/build-a-wordpress-site-with-chatgpt-or-claude/ > reference: https://jetpack.com/resources/build-a-wordpress-site-with-chatgpt-or-claude/ > date created: 2026-09-17 > > > [!info] Generated analysis — not the author's words. Sections below are machine-written > > from the captured source. Only text inside `> [!quote]` blocks is verbatim from the author. > > Do not quote or attribute any other line to the named author. > > <!-- deep-read: light-touch --> > Light-touch because this is a ~550-word vendor feature page — marketing copy plus an activation checklist — with no argument, data, or methodology to work through. > <!-- deep-read:sections start --> ## 🏷️ Title **Build a WordPress Site with ChatGPT or Claude** — Adam Pickering, Jetpack (Automattic). Announces that Jetpack AI exposes an MCP endpoint so external LLM clients can act on a self-hosted WordPress site. The title oversells. Nothing here builds a site from zero: the workflow presupposes an existing self-hosted install, a working Jetpack connection, Jetpack 15.8+, and a **paid** Jetpack AI plan. The real subject is agentic site *management*. ## 🧭 Table of Contents 1. Intro — availability preconditions 2. Build and change your site 3. Put your daily work on autopilot 4. Manage all your sites from one chat 5. Schedule recurring tasks 6. Connect your site (4-step activation) 7. Availability / closing CTA ## 🔗 References (in-page) - Two `video.wordpress.com` embeds (Automattic-hosted; both failed to import, so the demo evidence is missing from the capture) - OpenAI help article on ChatGPT scheduled tasks — third-party, neutral - Anthropic support article on Claude Cowork recurring tasks — third-party, neutral The two scheduling docs are the only outbound non-Automattic links. Everything load-bearing — plan, plugin, connector — is the publisher's own paid stack. ## 📝 Summary Jetpack AI 15.8+ adds an **MCP and Connectors** panel in WP Admin. Enabling MCP access and connecting an external agent lets ChatGPT, Claude, or Cursor drive the site in natural language: edit pages, change designs, update plugins, run site-health checks, surface stale content, improve SEO metadata, report analytics. One connection reaches every site the account manages. A paid plan is required. ## 📖 Main Content Four capability blocks, each with example prompts, then an activation checklist and a CTA. The prompt lists are the most useful part: they implicitly document the tool surface exposed over MCP — content CRUD, design mutation, plugin lifecycle, site health, media inspection, stats reads. The activation path is short and accurate: WP Admin → Jetpack → Jetpack AI → MCP and Connectors → enable → connect agent. A real, checkable sequence, which is more than most AI-feature announcements offer. ### 🗒️ Notes - **Does it produce a working site?** For maintaining an *existing* site, plausibly yes. For "build a site," no — no domain, hosting, install, theme, or content-architecture step appears anywhere. - **Copy defect:** "Your ChatGPT of Claude can keep an eye on your site" — an unedited typo on a page selling AI-assisted quality. - **No evidence:** both demo videos are Automattic embeds that did not import. The captured text carries zero visual proof. - **Multi-site is the least examined claim.** Account-wide reach is a real capability and a real blast radius; no scoping, per-site opt-in, or least privilege is mentioned. - **"Make sure nothing broke"** does enormous unexamined work: verifying an update needs a snapshot, a check against known-good output, and a rollback path. None is described. ## 📚 References No external evidence beyond the two scheduling help docs — no benchmarks, case studies, named customers, or error rates. A feature announcement, not a claim-supported article. ## 🗣️ Paraphrase If you already pay for Jetpack AI and run Jetpack 15.8+ self-hosted, you can flip a switch in WP Admin and hand ChatGPT or Claude a live connection to your site. You then talk to your assistant instead of clicking through the admin: redesign a homepage, update plugins, find stale posts, fix thin SEO titles — across every site you manage. ## 📰 Newsletter **Your CMS just got an API for vibes.** Jetpack shipped an MCP endpoint, so ChatGPT and Claude can reach into a self-hosted WordPress site and actually do things — publish, restyle, update plugins, sweep a portfolio from one prompt. The headline says "build a site," which is marketing for "manage a site you already built." The move underneath is real: the WordPress admin is now an agent tool surface. Stare at the switch labeled **Enable MCP access**. It hands a remote model the capability set of whoever connected it, across every site on the connection. The post's own example — "Update my outdated plugins and make sure nothing broke" — is exactly the operation that wants a staging site, a backup, and a diff. It mentions none of the three. Try it on a throwaway site, read the tool scopes, keep a human on the merge button. Links: [the post](https://jetpack.com/resources/build-a-wordpress-site-with-chatgpt-or-claude/) · [ChatGPT scheduled tasks](https://help.openai.com/en/articles/10291617-scheduled-tasks-in-chatgpt) · [Claude Cowork recurring tasks](https://support.claude.com/en/articles/13854387-schedule-recurring-tasks-in-claude-cowork) ## ✅ Action Items ### DevRel - Run the four-step connect flow on a disposable site; document where reality diverges from the steps. - Enumerate the MCP tool surface and compare it to other WordPress MCP implementations. ### OSPO - Track whether the Jetpack MCP tool definitions are public or only visible through the connector. - Flag the licensing question: generated markup, patterns, and CSS land in a user's site with no stated provenance or license terms. ### Community - Expect "my AI updated my plugins and my site broke" threads. Pre-write the triage path. ### WordPress subteams - **Core AI** — should a WordPress MCP surface be a Core concern with a shared capability model, rather than per-vendor endpoints with per-vendor scopes? - **Core** — a connection should express `edit_posts` / `update_plugins` / `edit_theme_options` distinctly, not as one bearer of the connecting user's full role. - **Core Performance** — confirm whether "find large images that could be optimized" regenerates or merely reports. - **Playground** — the obvious sandbox for evaluating agentic edits before production. - **Accessibility** — nothing suggests AI-generated layouts are checked for contrast, heading order, landmarks, or alt text. Highest-value review hook. - **Hosting** — hosts absorb the support cost of agent-initiated updates; backup and rollback guidance should precede adoption. - **Themes / Plugins** — "10x your site design" implies theme.json and template mutation; directories may need a stance on agent-authored artifacts. ### The WPOCC - Worth a session on agent write access to community-run sites, and what consent and audit look like there. ### FAIR - If agents update plugins automatically, provenance and integrity of the update source matter more, not less. ## 🧪 Hypotheses 1. The MCP tools inherit the connecting user's capabilities wholesale. *Test: connect as an Editor, attempt a plugin update.* 2. "Make sure nothing broke" is a site-health check, not a functional regression test. *Test: break a template, see if it still reports success.* 3. Multi-site fan-out is opt-out rather than opt-in per site. *Test: connect, then list reachable sites.* 4. Generated designs will often fail WCAG contrast checks, because nothing in the loop tests for it. ## 📊 Methodology Not applicable to this source — a promotional page with no study, dataset, or stated evaluation behind its claims. ## ❓ Questions - What exactly can the agent do, and can that be narrowed per connection? - Is there an audit log of agent-initiated changes, and are they revertible? - Are prompts and site content sent to the model provider, under what retention terms? - Who owns and licenses the markup, copy, and styles the agent produces? - Does this require a WordPress.com-side connection, and what does that mean for data residency? ## 🔮 Future Research - Compare Jetpack AI's MCP surface against community WordPress MCP plugins and any Core AI direction. - Test agent-generated pages with automated accessibility tooling and publish the pass rate. - Measure whether agent-initiated updates raise or lower the rate of broken sites versus auto-updates. ## 💡 Implications The WordPress admin is becoming a tool surface as much as a UI, and whoever defines that surface shapes who can build on it. A vendor-owned, paid MCP endpoint is a reasonable commercial move — but the canonical "talk to your WordPress site" experience may end up behind a subscription rather than defined in Core. The useful work is ensuring an open, capability-scoped equivalent exists. ## 🧠 Learning Styles Assessment - **Visual** — Two demo videos are the intended payload but did not import; as captured, visual support is zero. - **Aural** — Same videos; no audio alternative or transcript. - **Verbal** — Strong. Short declarative sentences, concrete prompts, low jargon. - **Kinesthetic** — Good. The four-step checklist is directly actionable. - **Logical** — Weak. Capability is asserted, never demonstrated or bounded. - **Social** — Absent. No community, forum, or support channel named. - **Solitary** — Well suited; actionable alone in about five minutes. - **Naturalistic** — Not applicable; no environmental or systems framing. - **Reading level** — roughly grade 7–8. Plain marketing prose, short paragraphs, heavy imperative mood. ## 📊 Accessibility Assessment (WCAG 2.2 AA) 1. **Text alternatives (1.1.1)** — Two video embeds with no transcript; fallback is a generic "content could not be imported" line. Fails as captured. 2. **Time-based media (1.2.2 / 1.2.3)** — No captions or audio description indicated for either demo. 3. **Info and relationships (1.3.1)** — Clean heading hierarchy and genuine lists; passes. 4. **Distinguishable (1.4.3, 1.4.11)** — Contrast not verifiable from the capture. 5. **Navigable (2.4.6, 2.4.10)** — Descriptive headings, but the title misdescribes the content — a findability and expectation problem. 6. **Predictable / consistent help (3.2.6)** — No visible support or help affordance in the captured text. 7. **Input assistance & focus (3.3.x, 2.4.11)** — N/A for static prose, but the feature has no stated review or confirmation step before an agent mutates a live site: AI-generated layouts reach production untested. ## 🌍 DEIB Assessment - **Cultural breadth** — Narrow. US small-business framing ("my landscaping business"); no localization, RTL, or multilingual consideration despite Polyglots' size in this ecosystem. - **Inclusive language** — Generally fine; "your assistant" and singular "they" used naturally. One unedited typo ("ChatGPT of Claude"). - **Neurodiversity support** — Good. Short chunks, bulleted prompts, numbered steps, no wall of text. - **Representation** — No people depicted or named; neutral by absence rather than by design. - **Psychological safety** — Mixed. Confident "make sure nothing broke" framing could leave a less experienced owner unprepared for a failure they cannot roll back. ## ✅ Logical Validity Internally consistent but evidentially thin. The structure is: *here are things you could ask for* → *therefore the assistant can do them*. Capability asserted by example prompt is not evidence of capability. - **Title/content equivocation** — "Build a WordPress Site" stands in for "manage an existing WordPress site." Every prerequisite presupposes a site that already exists. - **Suppressed evidence** — The risk of granting a remote model write access to production, across a whole portfolio, is never mentioned. Backups, staging, capability scoping, audit logs, and rollback are all absent. - **Appeal to ease** — "Skip the hunt through WordPress. Just ask for what you need." frames judgment and review as friction to eliminate. None of this is dishonest; it is ordinary vendor copy. But read the prompt lists as a roadmap, not a guarantee. ## 🛡️ DARVO Analysis No DARVO pattern present. The piece makes no accusation, mounts no defense, and attacks no party — it never acknowledges a criticism at all, which is why there is nothing to deny, invert, or reverse. Not applicable to this source. ## 🎯 Conclusion A competent product page describing a genuinely significant capability: WordPress site operations exposed to external LLM clients over MCP. The activation steps are accurate, the example prompts are the clearest documentation of the tool surface, and multi-site management is a real differentiator. It is also mistitled, unevidenced as captured, and silent on everything a professional would want before enabling it — scope, audit, rollback, licensing, accessibility, and what leaves the site. Useful signal about where the ecosystem is heading, gated behind a paid plan, with the safety work left to the reader. ## 🧱 Refactor Appendix ### Literature Split Pad ### The paywall gate > [!quote] Jetpack AI connects supported AI assistants to your self-hosted WordPress site. You'll need a paid Jetpack AI plan to connect. The capability is subscription-gated; the value proposition routes to the publisher's own paid product. `#atom/literature/h1` ### Fleet-wide reach from one connection > [!quote] A unique feature of Jetpack is the management of all your sites from a single prompt. A single connection gives your AI assistant access to all the WordPress sites you manage. The strongest feature and the largest unexamined blast radius in the piece. `#atom/literature/h2` ### Friction framed as the enemy > [!quote] Skip the hunt through WordPress. Just ask for what you need. The admin UI is positioned as pure overhead; review goes with it. `#atom/literature/h3` ### Atomic Split Pad #### Z1 — Agent write access should be capability-scoped, not role-inherited An MCP connection should express a narrowed capability set per connection, with per-site opt-in, rather than handing a remote model the full role of whoever clicked connect. Fleet-wide access from one toggle is a design choice, not a necessity. `#atom/zettel/z1` ### Fleeting Queue #### F1 — Test the connect flow on Playground or a throwaway install and record what the agent can actually reach Also check whether "make sure nothing broke" does anything beyond a site-health ping, and whether any agent-initiated change is revertible. `#atom/fleeting/f1` <!-- deep-read:sections end --> 📄 **Full text:** [[Full Document Contents/Articles/Build a WordPress Site With ChatGPT or Claude.md|Build a WordPress Site With ChatGPT or Claude by Adam Pickering]] ## Highlights - With Jetpack AI, your assistant can work directly on your site to create pages, change your design, keep plugins up to date, and manage WordPress with natural language. ([View Highlight](https://read.readwise.io/read/01m2zdv8gr5zensgy0m1cpf43t)) - Update my outdated plugins and make sure nothing broke. ([View Highlight](https://read.readwise.io/read/01m2pfc19r4xk58b6bbh3srn98)) - Note: Asserts verification without naming a backup, staging site, diff, or rollback — the omitted half of the operation. - Tags: atom/fleeting/f1, fallacy/suppressed-evidence - Skip the hunt through WordPress. Just ask for what you need. ([View Highlight](https://read.readwise.io/read/01m2pfbzc4v9nr5dknm90dm124)) - Note: Frames admin navigation as pure friction, which quietly removes the review step along with it. - Tags: atom/literature/h3, fallacy/appeal-to-ease - A unique feature of Jetpack is the management of all your sites from a single prompt. A single connection gives your AI assistant access to all the WordPress sites you manage. ([View Highlight](https://read.readwise.io/read/01m2pfbxpbdfhdke7rzvrs7ezr)) - Note: Real differentiator and the largest unexamined blast radius: no per-site opt-in or capability scoping is described. - Tags: atom/zettel/z1, atom/literature/h2 - Jetpack AI connects supported AI assistants to your self-hosted WordPress site. You’ll need a paid Jetpack AI plan to connect. ([View Highlight](https://read.readwise.io/read/01m2pfbs5s2bstv2wfeqngztmn)) - Note: The whole capability is subscription-gated — the page routes to the publisher's own paid product. - Tags: atom/literature/h1, action/h1 - Build a page, update your plugins, publish a post, or ask what needs your attention, all from the AI assistant you already use. ([View Highlight](https://read.readwise.io/read/01m2pfc37792d1m95y2wxe6fxt)) - Note: "Build a WordPress Site" in the title means managing a site that already exists — every step presupposes an install, Jetpack 15.8+, and a paid plan. - Tags: fallacy/equivocation, action/h2 ## New Highlights added 2026-09-21 at 5:45 PM - With Jetpack AI, your assistant can work directly on your site to create pages, change your design, keep plugins up to date, and manage WordPress with natural language. ([View Highlight](https://read.readwise.io/read/01m2zdv8gr5zensgy0m1cpf43t)) - Update my outdated plugins and make sure nothing broke. ([View Highlight](https://read.readwise.io/read/01m2pfc19r4xk58b6bbh3srn98)) - Note: Asserts verification without naming a backup, staging site, diff, or rollback — the omitted half of the operation. - Tags: atom/fleeting/f1, fallacy/suppressed-evidence - Skip the hunt through WordPress. Just ask for what you need. ([View Highlight](https://read.readwise.io/read/01m2pfbzc4v9nr5dknm90dm124)) - Note: Frames admin navigation as pure friction, which quietly removes the review step along with it. - Tags: atom/literature/h3, fallacy/appeal-to-ease - A unique feature of Jetpack is the management of all your sites from a single prompt. A single connection gives your AI assistant access to all the WordPress sites you manage. ([View Highlight](https://read.readwise.io/read/01m2pfbxpbdfhdke7rzvrs7ezr)) - Note: Real differentiator and the largest unexamined blast radius: no per-site opt-in or capability scoping is described. - Tags: atom/zettel/z1, atom/literature/h2 - Jetpack AI connects supported AI assistants to your self-hosted WordPress site. You’ll need a paid Jetpack AI plan to connect. ([View Highlight](https://read.readwise.io/read/01m2pfbs5s2bstv2wfeqngztmn)) - Note: The whole capability is subscription-gated — the page routes to the publisher's own paid product. - Tags: atom/literature/h1, action/h1 - Build a page, update your plugins, publish a post, or ask what needs your attention, all from the AI assistant you already use. ([View Highlight](https://read.readwise.io/read/01m2pfc37792d1m95y2wxe6fxt)) - Note: "Build a WordPress Site" in the title means managing a site that already exists — every step presupposes an install, Jetpack 15.8+, and a paid plan. - Tags: fallacy/equivocation, action/h2 ## New Highlights added 2026-09-21 at 6:45 PM - With Jetpack AI, your assistant can work directly on your site to create pages, change your design, keep plugins up to date, and manage WordPress with natural language. ([View Highlight](https://read.readwise.io/read/01m2zdv8gr5zensgy0m1cpf43t)) - Update my outdated plugins and make sure nothing broke. ([View Highlight](https://read.readwise.io/read/01m2pfc19r4xk58b6bbh3srn98)) - Note: Asserts verification without naming a backup, staging site, diff, or rollback — the omitted half of the operation. - Tags: atom/fleeting/f1, fallacy/suppressed-evidence - Skip the hunt through WordPress. Just ask for what you need. ([View Highlight](https://read.readwise.io/read/01m2pfbzc4v9nr5dknm90dm124)) - Note: Frames admin navigation as pure friction, which quietly removes the review step along with it. - Tags: atom/literature/h3, fallacy/appeal-to-ease - A unique feature of Jetpack is the management of all your sites from a single prompt. A single connection gives your AI assistant access to all the WordPress sites you manage. ([View Highlight](https://read.readwise.io/read/01m2pfbxpbdfhdke7rzvrs7ezr)) - Note: Real differentiator and the largest unexamined blast radius: no per-site opt-in or capability scoping is described. - Tags: atom/zettel/z1, atom/literature/h2 - Jetpack AI connects supported AI assistants to your self-hosted WordPress site. You’ll need a paid Jetpack AI plan to connect. ([View Highlight](https://read.readwise.io/read/01m2pfbs5s2bstv2wfeqngztmn)) - Note: The whole capability is subscription-gated — the page routes to the publisher's own paid product. - Tags: atom/literature/h1, action/h1 - Build a page, update your plugins, publish a post, or ask what needs your attention, all from the AI assistant you already use. ([View Highlight](https://read.readwise.io/read/01m2pfc37792d1m95y2wxe6fxt)) - Note: "Build a WordPress Site" in the title means managing a site that already exists — every step presupposes an install, Jetpack 15.8+, and a paid plan. - Tags: fallacy/equivocation, action/h2 ## New Highlights added 2026-09-22 at 8:52 PM - With Jetpack AI, your assistant can work directly on your site to create pages, change your design, keep plugins up to date, and manage WordPress with natural language. ([View Highlight](https://read.readwise.io/read/01m2zdv8gr5zensgy0m1cpf43t)) - Update my outdated plugins and make sure nothing broke. ([View Highlight](https://read.readwise.io/read/01m2pfc19r4xk58b6bbh3srn98)) - Note: Asserts verification without naming a backup, staging site, diff, or rollback — the omitted half of the operation. - Tags: atom/fleeting/f1, fallacy/suppressed-evidence - Skip the hunt through WordPress. Just ask for what you need. ([View Highlight](https://read.readwise.io/read/01m2pfbzc4v9nr5dknm90dm124)) - Note: Frames admin navigation as pure friction, which quietly removes the review step along with it. - Tags: atom/literature/h3, fallacy/appeal-to-ease - A unique feature of Jetpack is the management of all your sites from a single prompt. A single connection gives your AI assistant access to all the WordPress sites you manage. ([View Highlight](https://read.readwise.io/read/01m2pfbxpbdfhdke7rzvrs7ezr)) - Note: Real differentiator and the largest unexamined blast radius: no per-site opt-in or capability scoping is described. - Tags: atom/zettel/z1, atom/literature/h2 - Jetpack AI connects supported AI assistants to your self-hosted WordPress site. You’ll need a paid Jetpack AI plan to connect. ([View Highlight](https://read.readwise.io/read/01m2pfbs5s2bstv2wfeqngztmn)) - Note: The whole capability is subscription-gated — the page routes to the publisher's own paid product. - Tags: atom/literature/h1, action/h1 - Build a page, update your plugins, publish a post, or ask what needs your attention, all from the AI assistant you already use. ([View Highlight](https://read.readwise.io/read/01m2pfc37792d1m95y2wxe6fxt)) - Note: "Build a WordPress Site" in the title means managing a site that already exists — every step presupposes an install, Jetpack 15.8+, and a paid plan. - Tags: fallacy/equivocation, action/h2 ## New Highlights added 2026-09-25 at 1:01 PM - With Jetpack AI, your assistant can work directly on your site to create pages, change your design, keep plugins up to date, and manage WordPress with natural language. ([View Highlight](https://read.readwise.io/read/01m2zdv8gr5zensgy0m1cpf43t)) - Update my outdated plugins and make sure nothing broke. ([View Highlight](https://read.readwise.io/read/01m2pfc19r4xk58b6bbh3srn98)) - Note: Asserts verification without naming a backup, staging site, diff, or rollback — the omitted half of the operation. - Tags: atom/fleeting/f1, fallacy/suppressed-evidence - Skip the hunt through WordPress. Just ask for what you need. ([View Highlight](https://read.readwise.io/read/01m2pfbzc4v9nr5dknm90dm124)) - Note: Frames admin navigation as pure friction, which quietly removes the review step along with it. - Tags: atom/literature/h3, fallacy/appeal-to-ease - A unique feature of Jetpack is the management of all your sites from a single prompt. A single connection gives your AI assistant access to all the WordPress sites you manage. ([View Highlight](https://read.readwise.io/read/01m2pfbxpbdfhdke7rzvrs7ezr)) - Note: Real differentiator and the largest unexamined blast radius: no per-site opt-in or capability scoping is described. - Tags: atom/zettel/z1, atom/literature/h2 - Jetpack AI connects supported AI assistants to your self-hosted WordPress site. You’ll need a paid Jetpack AI plan to connect. ([View Highlight](https://read.readwise.io/read/01m2pfbs5s2bstv2wfeqngztmn)) - Note: The whole capability is subscription-gated — the page routes to the publisher's own paid product. - Tags: atom/literature/h1, action/h1 - Build a page, update your plugins, publish a post, or ask what needs your attention, all from the AI assistant you already use. ([View Highlight](https://read.readwise.io/read/01m2pfc37792d1m95y2wxe6fxt)) - Note: "Build a WordPress Site" in the title means managing a site that already exists — every step presupposes an install, Jetpack 15.8+, and a paid plan. - Tags: fallacy/equivocation, action/h2 ## New Highlights added 2026-09-25 at 1:46 PM - With Jetpack AI, your assistant can work directly on your site to create pages, change your design, keep plugins up to date, and manage WordPress with natural language. ([View Highlight](https://read.readwise.io/read/01m2zdv8gr5zensgy0m1cpf43t)) - Update my outdated plugins and make sure nothing broke. ([View Highlight](https://read.readwise.io/read/01m2pfc19r4xk58b6bbh3srn98)) - Note: Asserts verification without naming a backup, staging site, diff, or rollback — the omitted half of the operation. - Tags: atom/fleeting/f1, fallacy/suppressed-evidence - Skip the hunt through WordPress. Just ask for what you need. ([View Highlight](https://read.readwise.io/read/01m2pfbzc4v9nr5dknm90dm124)) - Note: Frames admin navigation as pure friction, which quietly removes the review step along with it. - Tags: atom/literature/h3, fallacy/appeal-to-ease - A unique feature of Jetpack is the management of all your sites from a single prompt. A single connection gives your AI assistant access to all the WordPress sites you manage. ([View Highlight](https://read.readwise.io/read/01m2pfbxpbdfhdke7rzvrs7ezr)) - Note: Real differentiator and the largest unexamined blast radius: no per-site opt-in or capability scoping is described. - Tags: atom/zettel/z1, atom/literature/h2 - Jetpack AI connects supported AI assistants to your self-hosted WordPress site. You’ll need a paid Jetpack AI plan to connect. ([View Highlight](https://read.readwise.io/read/01m2pfbs5s2bstv2wfeqngztmn)) - Note: The whole capability is subscription-gated — the page routes to the publisher's own paid product. - Tags: atom/literature/h1, action/h1 - Build a page, update your plugins, publish a post, or ask what needs your attention, all from the AI assistant you already use. ([View Highlight](https://read.readwise.io/read/01m2pfc37792d1m95y2wxe6fxt)) - Note: "Build a WordPress Site" in the title means managing a site that already exists — every step presupposes an install, Jetpack 15.8+, and a paid plan. - Tags: fallacy/equivocation, action/h2 ## New Highlights added 2026-09-25 at 2:46 PM - With Jetpack AI, your assistant can work directly on your site to create pages, change your design, keep plugins up to date, and manage WordPress with natural language. ([View Highlight](https://read.readwise.io/read/01m2zdv8gr5zensgy0m1cpf43t)) - Update my outdated plugins and make sure nothing broke. ([View Highlight](https://read.readwise.io/read/01m2pfc19r4xk58b6bbh3srn98)) - Note: Asserts verification without naming a backup, staging site, diff, or rollback — the omitted half of the operation. - Tags: atom/fleeting/f1, fallacy/suppressed-evidence - Skip the hunt through WordPress. Just ask for what you need. ([View Highlight](https://read.readwise.io/read/01m2pfbzc4v9nr5dknm90dm124)) - Note: Frames admin navigation as pure friction, which quietly removes the review step along with it. - Tags: atom/literature/h3, fallacy/appeal-to-ease - A unique feature of Jetpack is the management of all your sites from a single prompt. A single connection gives your AI assistant access to all the WordPress sites you manage. ([View Highlight](https://read.readwise.io/read/01m2pfbxpbdfhdke7rzvrs7ezr)) - Note: Real differentiator and the largest unexamined blast radius: no per-site opt-in or capability scoping is described. - Tags: atom/zettel/z1, atom/literature/h2 - Jetpack AI connects supported AI assistants to your self-hosted WordPress site. You’ll need a paid Jetpack AI plan to connect. ([View Highlight](https://read.readwise.io/read/01m2pfbs5s2bstv2wfeqngztmn)) - Note: The whole capability is subscription-gated — the page routes to the publisher's own paid product. - Tags: atom/literature/h1, action/h1 - Build a page, update your plugins, publish a post, or ask what needs your attention, all from the AI assistant you already use. ([View Highlight](https://read.readwise.io/read/01m2pfc37792d1m95y2wxe6fxt)) - Note: "Build a WordPress Site" in the title means managing a site that already exists — every step presupposes an install, Jetpack 15.8+, and a paid plan. - Tags: fallacy/equivocation, action/h2 ## New Highlights added 2026-09-25 at 4:30 PM - With Jetpack AI, your assistant can work directly on your site to create pages, change your design, keep plugins up to date, and manage WordPress with natural language. ([View Highlight](https://read.readwise.io/read/01m2zdv8gr5zensgy0m1cpf43t)) - Update my outdated plugins and make sure nothing broke. ([View Highlight](https://read.readwise.io/read/01m2pfc19r4xk58b6bbh3srn98)) - Note: Asserts verification without naming a backup, staging site, diff, or rollback — the omitted half of the operation. - Tags: atom/fleeting/f1, fallacy/suppressed-evidence - Skip the hunt through WordPress. Just ask for what you need. ([View Highlight](https://read.readwise.io/read/01m2pfbzc4v9nr5dknm90dm124)) - Note: Frames admin navigation as pure friction, which quietly removes the review step along with it. - Tags: atom/literature/h3, fallacy/appeal-to-ease - A unique feature of Jetpack is the management of all your sites from a single prompt. A single connection gives your AI assistant access to all the WordPress sites you manage. ([View Highlight](https://read.readwise.io/read/01m2pfbxpbdfhdke7rzvrs7ezr)) - Note: Real differentiator and the largest unexamined blast radius: no per-site opt-in or capability scoping is described. - Tags: atom/zettel/z1, atom/literature/h2 - Jetpack AI connects supported AI assistants to your self-hosted WordPress site. You’ll need a paid Jetpack AI plan to connect. ([View Highlight](https://read.readwise.io/read/01m2pfbs5s2bstv2wfeqngztmn)) - Note: The whole capability is subscription-gated — the page routes to the publisher's own paid product. - Tags: atom/literature/h1, action/h1 - Build a page, update your plugins, publish a post, or ask what needs your attention, all from the AI assistant you already use. ([View Highlight](https://read.readwise.io/read/01m2pfc37792d1m95y2wxe6fxt)) - Note: "Build a WordPress Site" in the title means managing a site that already exists — every step presupposes an install, Jetpack 15.8+, and a paid plan. - Tags: fallacy/equivocation, action/h2 ## New Highlights added 2026-09-26 at 5:49 PM - With Jetpack AI, your assistant can work directly on your site to create pages, change your design, keep plugins up to date, and manage WordPress with natural language. ([View Highlight](https://read.readwise.io/read/01m2zdv8gr5zensgy0m1cpf43t)) - Update my outdated plugins and make sure nothing broke. ([View Highlight](https://read.readwise.io/read/01m2pfc19r4xk58b6bbh3srn98)) - Note: Asserts verification without naming a backup, staging site, diff, or rollback — the omitted half of the operation. - Tags: atom/fleeting/f1, fallacy/suppressed-evidence - Skip the hunt through WordPress. Just ask for what you need. ([View Highlight](https://read.readwise.io/read/01m2pfbzc4v9nr5dknm90dm124)) - Note: Frames admin navigation as pure friction, which quietly removes the review step along with it. - Tags: atom/literature/h3, fallacy/appeal-to-ease - A unique feature of Jetpack is the management of all your sites from a single prompt. A single connection gives your AI assistant access to all the WordPress sites you manage. ([View Highlight](https://read.readwise.io/read/01m2pfbxpbdfhdke7rzvrs7ezr)) - Note: Real differentiator and the largest unexamined blast radius: no per-site opt-in or capability scoping is described. - Tags: atom/zettel/z1, atom/literature/h2 - Jetpack AI connects supported AI assistants to your self-hosted WordPress site. You’ll need a paid Jetpack AI plan to connect. ([View Highlight](https://read.readwise.io/read/01m2pfbs5s2bstv2wfeqngztmn)) - Note: The whole capability is subscription-gated — the page routes to the publisher's own paid product. - Tags: atom/literature/h1, action/h1 - Build a page, update your plugins, publish a post, or ask what needs your attention, all from the AI assistant you already use. ([View Highlight](https://read.readwise.io/read/01m2pfc37792d1m95y2wxe6fxt)) - Note: "Build a WordPress Site" in the title means managing a site that already exists — every step presupposes an install, Jetpack 15.8+, and a paid plan. - Tags: fallacy/equivocation, action/h2