How to Build a WordPress Website With Claude (Local WP + Elementor) in Under an Hour

The claim in the title needs a boundary before it is useful. I do not type “make me a website” and go for a coffee. What I do is run Claude Desktop’s Code tab inside a Local WordPress install, give it a proper brief, and let it do the part of a build that is typing: installing and configuring, creating pages, generating Elementor layouts, drafting copy, writing the child-theme CSS, running checks. I do the part that is deciding. Build a WordPress website with Claude this way and, for a five-to-seven-page service site with the brief ready, it is honestly under an hour — and it used to be a day and a half.

This is the workflow in detail. If you would rather work in a chat window and paste things in, the ChatGPT and Elementor guide covers that slower, more manual version. This one is for people comfortable with a terminal and a local dev tool.

The stack

Nothing exotic. The difference from a normal build is that the AI has hands — it can run wp plugin install, write a file, import a template, and read the result — instead of only producing text for you to copy.

Before the clock starts: the brief

The hour depends entirely on this. A brief file (brief.md in the site folder) with:

• Business name, what it does, where, for whom, and the one thing that makes it different.
• Pages: Home, Services (with the three to six services listed), About, Contact, plus any specifics (Pricing, Areas, FAQ).
• Tone: two or three adjectives and a sentence you like the sound of.
• Brand: colours (hex), fonts, logo file path.
• Calls to action: phone, email, booking link, WhatsApp — and which one is primary.
• Rules for the assistant: child theme only, no plugins beyond the agreed list, never edit WordPress core or plugin files, ask before anything destructive.

Ten minutes writing this saves an hour of back-and-forth. A vague brief does not produce a bad site; it produces a generic one, which is worse because it looks finished.

The hour, minute by minute

1. 0–5 min: create the site and open the Code tab in it.

   New site in Local (blank WordPress, latest PHP). Open Claude Desktop’s Code tab in the site’s app/public folder so Claude can see the files and run WP-CLI. First prompt: read brief.md, confirm the plan, do nothing yet. I read the plan. It takes a minute and catches misunderstandings before they become pages.

2. 5–15 min: setup.

   Claude runs the setup through WP-CLI: install and activate Hello Elementor, Elementor and Elementor Pro (from a local zip), create a child theme, set permalinks to post name, timezone, site title and tagline, disable comments, create the pages from the brief, set the front page, build the primary menu, delete the sample content. Output is a checklist I can scan. This step is almost fully automatic and is the first place the hour comes from.

3. 15–35 min: build the layouts.

   Claude generates each page as an Elementor template JSON — containers, headings, text, buttons, icon boxes, image placeholders — from the brief, and imports it with wp elementor library import (or writes the page’s Elementor data directly). Header and footer go in as Theme Builder templates with display conditions. Global colours and fonts go into the Site Settings kit. Then wp elementor flush-css so the styles regenerate.

   Honest note: the first render is never perfect. I open each page in the editor, fix spacing, swap a section order, tighten a heading. Two or three rounds of “the services grid needs to be three columns on desktop, one on mobile, cards with a 12px radius” and it is right. This is the step where a developer’s eye matters most.

4. 35–45 min: copy and forms.

   Claude drafts page copy from the brief — headline, sub-headline, service descriptions, about story, FAQ — straight into the widgets. I edit for facts and voice; AI will happily invent “over 500 happy customers” if you let it, so every number and claim gets checked against the brief. The contact form (Elementor Pro Form) is wired to email and, if the client has a CRM, to a webhook — the form-to-CRM setup is the same as on any site.

5. 45–55 min: checks.

   This is the step that separates a demo from a deliverable, and Claude is good at it because it is tedious: every page has a unique title and meta description (Rank Math or equivalent); every image has alt text and is WebP; the menu has no dead links; phone and email are clickable everywhere; the 404 page exists; PHP files lint clean; mobile layouts are checked in the editor’s responsive mode and then on a real phone. The speed checklist basics — caching plugin, image sizes, font loading — are applied before anything ships.

6. 55–60 min: deploy.

   Local can push to some hosts directly; otherwise a migration plugin export, or — my preference — Claude connects to the host over SSH and deploys the theme, database and uploads with WP-CLI, then does a search-replace for the domain. Cache purge, a final crawl, done.

Prompts that work

Three from a real build, lightly cleaned up.

Read brief.md. Set up this Local site for it: install Hello Elementor, Elementor and Elementor Pro (zip in ~/plugins), create a child theme named after the business, set permalinks to /%postname%/, timezone Europe/London, disable comments, create the pages listed under “Pages” as published empty Elementor pages, set Home as the front page, build the primary menu in the listed order. Do not install anything else. Print a checklist of what you did.

Build the Home page in Elementor from the brief: hero (H1, sub-headline, primary CTA button to the booking link, secondary to Contact), a three-column services grid with icon boxes linking to the Services page, a “why us” section with the three differentiators, a testimonials placeholder, and a final CTA band. Use the global colours and fonts. Import it as the page’s layout and flush the Elementor CSS. Tell me anything you had to guess.

Run the pre-launch checks: unique title and meta description on every page, alt text on every image, no broken internal links, phone and email clickable, 404 page present, WebP images only, no PHP notices with WP_DEBUG on. Fix what you can inside the child theme and list what needs me.

Notice the shape: a clear scope, the rules restated, and “tell me what you guessed” at the end. That last line is where most of the quality comes from.

Where it goes wrong

• A thin brief. The site fills up with plausible generic copy and stock-looking sections. Fix the brief, not the output.
• “Just one more plugin.” An assistant with a terminal will solve every problem with a plugin unless you forbid it. My rule is a fixed list, and anything else is a question first.
• Skipping the editor pass. Programmatically generated layouts are structurally right and visually 80% there. The last 20% is you, in the Elementor editor.
• Trusting the copy. Check every claim, number, place name and service description against the brief.
• Not flushing CSS. Templates imported outside the editor look unstyled until wp elementor flush-css runs or the page is re-saved.
• Elementor and Hello updates. Never let the assistant edit plugin or core files to “fix” something — the fix lasts until the next update. Child theme only.
• Deploying without a backup on the host. Same rule as every deployment, AI or not.

How long it really takes

The hour is real for the first row. Everything below it is still dramatically faster than it was, but the time goes into decisions and testing rather than typing — which is where it should go. Slow builds were never slow because of typing; the tool just removed the excuse.

What changes for agencies

This is the workflow behind my white-label work. An agency sends a brief and a design direction; the first draft of the site exists the same day; the rounds that follow are about their client’s business, not about wrangling a page builder. The agency keeps the relationship and the margin; I keep the tooling sharp. The site the client receives is ordinary, well-built WordPress with Elementor — nothing they cannot maintain later — and it passes the same speed and quality checks as a hand-built one, because those checks are part of the hour.

Further reading: Claude Code · Local (LocalWP) · WP-CLI commands.

FAQ

Running an agency and want builds delivered this way under your brand? See how the white-label partnership works — brief in, reviewed first draft out, your name on it.