How to Build a WordPress Site with AI in 2026 (Claude & Codex)

For years, building a WordPress site meant juggling page builders, themes, plugins, and the occasional snippet of PHP you copied from a forum. In 2026 there is a faster path: you build a WordPress site with AI by describing what you want in plain English, and an assistant like Claude or Codex makes the changes on your real site.

This is not a chatbot that hands you code to paste. The AI reads your actual pages, edits the real Elementor structure, and shows you the result — all as drafts you review before publishing. This guide walks through exactly how it works and how to set it up in about 20 minutes.

What "building WordPress with AI" actually means

There are three common ways people use AI with WordPress today, and only one of them feels like magic:

1. Copy-paste from a chatbot — you ask ChatGPT for HTML, then paste it into WordPress. Tedious and error-prone.
2. AI plugins inside wp-admin — handy for generating a paragraph, but locked to one box on one screen.
3. An AI agent connected to your whole site — the assistant can list your pages, read them, create new ones, upload images, swap a hero, switch themes, and fix SEO — by chat. This is the workflow this guide covers.

The connection that makes option 3 possible is MCP (Model Context Protocol) — think of it as a USB-C port for AI tools. You plug your site into your assistant once, and the assistant gains a set of WordPress actions it can take on your behalf.

What you need

• A WordPress site on any host (the plugin method works on managed WordPress — no SSH required).
• A paid Claude or Codex plan so you have enough credits to build comfortably.
• A free XeoRank account — XeoRank is the bridge between your AI assistant and WordPress.
• Optional but recommended: Elementor Pro for the full design range.

Step 1: Connect your AI assistant to XeoRank

The MCP server URL is always https://mcp.xyle.app/mcp.

• Claude (Desktop or web): Settings → Connectors → Customize → + Add connector → paste the URL → sign in. No API key needed.
• Codex: add a custom MCP → choose Streamable HTTP → URL https://mcp.xyle.app/mcp → add a header Authorization: Bearer <your XeoRank API key>.

Then verify it worked by asking your assistant: "List my XeoRank sites." If it answers, you are connected.

Step 2: Connect WordPress

1. In WordPress, go to Plugins → Add New → Upload Plugin and install the Xyle Connector (a one-time download from your dashboard).
2. Create an Application Password under Users → Profile → Application Passwords.
3. Tell your assistant: "Connect my WordPress site example.com — username is my-wp-login@email.com, app password is xxxx xxxx xxxx xxxx. Then enable writes."

One gotcha that trips everyone up: the username is your wp-admin login (usually an email), not the Application Password's name. Writes are off by default — you enable them when you are ready for the AI to make changes.

Step 3: Build by chatting

Now the fun part. You describe outcomes; the assistant builds drafts. A few real prompts:

Build a draft landing page for our AI services: a hero with two buttons, a row of three feature cards, a testimonial, and a contact CTA.

Write a draft blog post titled "5 ways to cut AI serving costs" — intro, five sections, and a closing CTA.

Upload this image to my media library and use it as the hero on the services page: https://…/hero.jpg

Read my homepage, then change only the hero heading to "Ship faster with AI" and swap the hero image.

Everything lands as a draft in WordPress. You review it (in Elementor, like any other page), tweak if needed, and publish when you are happy.

Why this is safer than it sounds

People worry that letting AI touch a live site is risky. The workflow is built to prevent that:

• Writes are off by default — the assistant can read your site freely, but cannot change anything until you opt in per site.
• Draft-first — new pages and posts are drafts; nothing publishes without you.
• Reversible — edits go through WordPress's normal revision history, so you can roll back.
• Revocable — your Application Password and API key can be revoked in seconds.

A good habit before any big change: take a backup (a host snapshot or a plugin like UpdraftPlus). The connector avoids touching sensitive theme and core files, but a backup is cheap insurance.

How fast is it really?

In practice, a landing page that used to take three to four days drops to roughly one to two hours, because the AI handles the repetitive scaffolding — sections, copy, and basic structure — while you direct and refine. The biggest speed-ups come from:

• Brand guidelines fed in once. Point the assistant at a reference site or a brand doc and it matches your colors, fonts, and tone.
• Design by screenshot. Paste a screenshot of a layout you like and ask it to match.
• Building one section at a time rather than one giant prompt — easier to review and far more accurate.

Frequently asked questions

Can AI build a whole WordPress site, or just pages? Both. You can spin up individual pages and blog posts, or build out a multi-page site section by section. The recommended approach is one page (or one service) at a time so you can review each.

Does it work with Elementor? Yes — the assistant builds native Elementor pages, so you can still edit them visually afterward. For pixel-perfect custom components you can also have it drop in an HTML block.

What happens if I remove the connector plugin? Nothing to your content. Every page and post lives in your own WordPress; the plugin is just the bridge.

Is there a free plan? Yes. You can build and edit one site for free with a generous daily editing allowance. Running multiple brands, automation, and version history are part of paid plans.

Build your first AI-powered page today

The fastest way to understand this is to try it. Grab the full step-by-step walkthrough in the WordPress vibe-coding guide, read the MCP setup docs, or just sign up for XeoRank and ask your assistant to build a page. Twenty minutes from now, your AI assistant could be editing your WordPress site by chat.

For a deeper look at the connection layer, read our companion post on the WordPress MCP server.