Building a Full WordPress Site With AI Agents End to End

Four months ago I was skeptical WordPress and AI agents would mix. Now I build full WordPress sites with Claude Code driving most of the work. Clients get something they can maintain. I get my time back. Here is the workflow.

The Orchestration Mindset

I do not prompt Claude to 'build me a website.' That is a recipe for disappointment. I orchestrate it through a sequence of focused steps: scaffold the theme, build the blocks, configure the plugins, import the content, harden the site.

Each step has clear acceptance criteria I can verify. Each step produces a reviewable diff. This is agentic development: I direct, the agent executes, and I verify before moving on.

The Actual Sequence

First, I scaffold a block-based theme with Claude Code in a fresh directory. The theme has a theme.json, a few templates, and a style.css. This is five minutes of work.

Second, I build the site-specific blocks the client needs: a services block, a testimonial block, a pricing block. These are React components registered with WordPress. Claude handles the boilerplate while I define the behavior.

Third, I install and configure plugins. Yoast for SEO, WP Rocket for caching, Gravity Forms for contact. Each plugin gets its settings committed as configuration code so I can reproduce the setup.

# My WP deployment flow
wp theme activate custom-theme          # activate
wp plugin install yoast-seo --activate  # install
wp post create --post_type=page ...     # scaffold pages
wp import content.xml                   # import content
wp cache flush                          # clear

The Handoff Moment

The site gets handed to the client with full admin access. They can edit every page through the WordPress block editor. They can add new services, change prices, update images. No developer needed.

This is the whole point. I use AI agents to build the foundation, but the client owns the maintenance. That combination is the real unlock of agentic development applied to WordPress.

For the technical foundation see the WordPress block editor handbook. The workflow above stacks on top of standard WordPress, not around it. That is what makes it sustainable.