The videos promise a full website from one prompt. What actually works is less magical and more useful: ChatGPT handles the parts of a build that are mostly writing and structure — the site map, the page copy, the section outlines, small CSS and JavaScript snippets, the SEO metadata — and you handle the parts that are decisions and taste. Build a WordPress website with ChatGPT this way and a five-page service site that used to take me a week of writing and assembly takes a day or two, and the result does not read like a template.
This is the workflow I use when a client wants a site fast, with the prompts that work and the checkpoints where a human has to look. It assumes WordPress with Elementor Pro; if you want the version where an AI agent works directly inside a local WordPress install, that is a separate guide on Claude and Local WP coming next in this series.
What ChatGPT is good at in a website build
- Structure: site maps, page outlines, section order, FAQ lists.
- Copy drafts: headlines, service descriptions, about text, CTAs — given real inputs.
- Small code: CSS tweaks, a JavaScript snippet for a form event, a schema block.
- SEO metadata: titles, descriptions, image alt text, in bulk.
- Explaining Elementor settings you cannot find.
What it is bad at: knowing anything about your business it was not told, design judgement, and checking its own work. Those are your jobs.
Step 1: Give it the facts (the brief document)
Before any prompt, write a plain document and paste it at the start of every conversation:
Business: Lakeside Dental, Leeds. Family and cosmetic dentistry, 3 dentists. Audience: families within 10 miles; adults 30–55 considering Invisalign or whitening. What makes us different: same-week appointments, 0% finance, 4.9 stars from 380 reviews. Goal of the site: booked consultations. Tone: warm, plain, no dental jargon. Services: [list]. Real proof: [3 quotes, numbers]. Words to avoid: “unlock”, “elevate”, “seamless”.
Every generic AI website I have been asked to fix was generic because this document did not exist. The model fills gaps with clichés; do not leave gaps.
Step 2: Site map and page outlines
Prompt: “Using the brief, propose a site map for a five-page website whose goal is booked consultations. For each page give the purpose, the sections in order, and the one call to action. Keep it to what a small practice needs — no pages we would not maintain.”
Edit the result. Delete pages you will not keep updated. Then, per page: “Outline the Home page section by section. For each section: heading, one-line purpose, what content goes in it, and which Elementor widget you would use (heading, text, icon list, image, testimonial, form).” This outline becomes your build plan.
Step 3: Copy, section by section
Do not ask for “the home page copy”. Ask for one section at a time with constraints:
“Write the hero for the Home page: a headline under 10 words that states the outcome for the visitor, a sub-headline under 25 words, and a button label. Use the proof from the brief. Three options for the headline, in the tone described.”
Pick, edit, move on. For the services section: “Six service blurbs, 35–45 words each, each ending with what the visitor should do next.” For FAQs: “Ten questions a patient asks before booking, with answers under 60 words, based only on the brief — flag any answer you had to guess.” That last clause matters; a good prompt makes the model tell you where it invented something.
Read every sentence before it goes on the site. Check numbers, claims, service names and anything legal. The model will confidently write “over 20 years of experience” for a practice that opened in 2019 if the brief did not say otherwise.
Step 4: Build the pages in Elementor
Set up the Elementor kit first — global colours, two fonts, button style — so every page inherits the brand. Then build each page from the outline with core Elementor Pro widgets; avoid addon packs (they are the first thing I remove in a speed rescue). Paste the copy section by section. Use the Theme Builder for the header and footer once, with conditions set to the whole site.
Where ChatGPT helps here: “I have an Elementor container with three icon boxes. On mobile I want them stacked with 16px gap and the icons left-aligned. Which container and widget settings do that?” It knows the settings panels well and saves hunting.
Step 5: Small code, checked
Custom CSS for a detail the builder cannot do, a snippet to push form submissions to the data layer for Tag Manager, a schema block — ChatGPT writes these well. Two rules: paste code into Elementor’s Custom CSS or a child theme, never into a random plugin you installed for the purpose; and test on a phone before publishing. If the code touches PHP, keep a backup and a way to roll back — a syntax error in functions.php takes the site down.
Step 6: Images
AI image generators can produce hero backgrounds and abstract graphics; they are poor at your actual team, premises and work. Use real photos where the visitor expects reality (people, place, results) and generated or stock imagery only for decoration. Whatever you use, resize and convert to WebP before upload; the speed checklist explains why this single step matters most.
Step 7: SEO metadata in bulk
Paste your page list with a one-line summary of each and ask: “For each page, write an SEO title under 60 characters including the main keyword and location, a meta description under 155 characters written to earn the click, and alt text for the hero image.” Review, then enter them in Rank Math or Yoast. Then ask for the FAQ schema questions if you used an FAQ section. This is thirty minutes of work that used to be three hours.
Step 8: The human pass
Before launch, read the whole site aloud. Anything that sounds like every other website — “we’re passionate about delivering exceptional solutions” — gets rewritten with a specific fact from the brief. Check every claim. Click every link. Submit every form and confirm it lands in the inbox or the CRM (see connecting forms to a CRM). Run PageSpeed Insights on mobile. Then publish.
A realistic timeline for a five-page site
| Stage | With ChatGPT | Without |
|---|---|---|
| Brief and site map | 1–2 hours | Half a day |
| Copy (all pages) | Half a day incl. editing | 2–3 days |
| Elementor build | 1 day | 1 day (unchanged) |
| Metadata, schema, checks | 1–2 hours | Half a day |
The build itself does not get faster from a chat interface — that needs an agent that can work in the install, which is the next article. The writing and structuring do, dramatically.
Where this goes wrong
- No brief document. Generic in, generic out.
- Accepting the first draft. The first draft is the average of the internet. The third, with your edits, is yours.
- Pasting code you do not understand into places you cannot undo. Child theme, backups, test on a phone.
- Letting the AI choose the design. It will suggest the same three-column, icon-box layout for everything. Design is a decision; make it.
- Publishing invented facts. Read every claim.
Further reading: Elementor Help Center · ChatGPT.
FAQ
Can ChatGPT build a WordPress website by itself?
No. It cannot log in, click, or see your site. It generates text and code that you place into WordPress and Elementor. Used that way, it removes most of the writing and structuring work from a build.
What should I ask ChatGPT for first?
A site map and a page outline based on your services, audience and goals. Getting the structure right first means every later prompt for copy and sections has a clear place to go.
Will Google penalise an AI-written website?
Google evaluates whether content is helpful and original, not how it was produced. Generic AI text that says nothing specific ranks poorly; AI-drafted text edited with real detail, real numbers and a real voice ranks like any good content.
Which is better for this, ChatGPT or Claude?
Both produce good drafts; the difference is small compared with the quality of your prompt and your editing. For code-heavy work, an agent that can work inside a local WordPress install — covered in a separate guide — goes further than either chat interface.
Built a site this way and want it checked, tightened and made fast before launch? Book a call — a finishing pass is a fraction of a full build, and it is where AI-assisted sites usually need help.
