I build WordPress websites for a living, mostly with Elementor, and ChatGPT has become part of my workflow in a way I did not expect. It does not build the sites for me. It does something more useful: it removes the slow parts. The blank page, the boilerplate code, the client email I have been avoiding, the CSS I know is possible but cannot remember the syntax for. This is my real setup — the exact ways I use ChatGPT across a WordPress project, from the first client call to launch day.
I am not going to pretend it is magic. There are hard limits, and I will name them. But if you build WordPress sites and you are still only using ChatGPT to write the occasional paragraph, you are leaving the best parts on the table.
The setup: a Project that knows my stack
Everything starts with a ChatGPT Project I call "WordPress Work." A Project is a folder with its own instructions and uploaded files, and mine has three things in it: my coding standards (PHP 8, WordPress coding standards, no jQuery where vanilla JS will do), my Elementor habits (Astra theme, Elementor Pro, Theme Builder for header and footer, widgets over custom HTML wherever possible), and a short note on how I like code delivered — complete working blocks, with a one-line comment saying where each block goes.
That last part matters more than it sounds. When I ask for a snippet, I do not want a lecture and three fragments. I want the full functions.php block, or the full CSS block, with a note like "paste this in the Customizer, Additional CSS." The Project instructions make that the default, so I stopped repeating myself in every chat.
I also keep one chat per project, not one chat per question. When a client site starts, I open a chat, paste the brief, the sitemap, and the design notes, and that chat becomes the working memory for the whole build. Two weeks later, when I ask "what was the plan for the testimonials section?", it remembers — because the context is all in one place.
Writing code that actually fits WordPress
The most common mistake I see is asking ChatGPT for WordPress code the way you would ask for generic PHP. WordPress has its own way of doing things — hooks, filters, the right function for the right job — and generic code usually ignores all of it. So I always name the context: the WordPress version, the theme, the plugins involved, and what I am trying to hook into.
Here is a real example. Instead of "write code to change the excerpt length," I write: "WordPress 7.1, Astra theme, Elementor Pro. I need the blog archive excerpt limited to 25 words, only on the category archive, using a filter in functions.php, no plugin." That gets me a clean add_filter block I can paste straight in. The vague version gets me something that might work, might break the theme, and will definitely need debugging.
I also make it explain before it writes when the task touches something I do not fully understand — a custom post type registration, a REST API endpoint, a WooCommerce hook. Two sentences of explanation first, then the code. That catches wrong assumptions early, and it teaches me the WordPress way of doing it instead of just handing me a block to paste blindly.
And I always test in a staging copy. ChatGPT code is a first draft, not a finished product. I have never once pasted AI-generated PHP directly onto a live client site, and I never will. Staging first, check the error log, then deploy. That rule has saved me more than once.
CSS and Elementor: the fastest wins
Honestly, the fastest everyday win is CSS. Elementor covers most styling visually, but every real project hits the edge — a hover effect Elementor does not offer, a custom layout for one section, a mobile fix for one breakpoint. I describe what I want in plain words, paste the section's existing classes if I have them, and get back a CSS block I can drop into the Customizer or an Elementor HTML widget.
The trick is to be specific about the breakpoint. "Make this look good on mobile" is useless. "On screens under 767px, stack these two columns, reduce the heading to 28px, and hide the decorative image" gets you something usable first try. I also ask it to keep the CSS scoped to a class rather than styling elements globally, because a global rule that fixes one section and breaks three others is not a fix.
One thing I do not do: I do not ask ChatGPT to design the site. It is bad at taste. It will give you a generic hero section with a gradient and three feature cards, and every AI-designed page looks the same. Design decisions stay with me. ChatGPT executes the fiddly bits.
Content: drafts, not finished copy
ChatGPT writes a lot of the first drafts on my client sites — service pages, about pages, FAQ sections — and I want to be honest about how that works. The first draft is never the final copy. It is a structured starting point: the headings are right, the flow makes sense, and the facts are roughly correct. Then I rewrite it in the client's voice, fix the facts, and cut the generic filler. An AI first draft plus a human rewrite is faster than a blank page, and the result reads like a person wrote it — because a person did, in the end.
The rule I give clients is simple: AI can draft, but a human signs off. That matters most for anything factual — prices, dates, credentials, service details. I have seen ChatGPT invent a certification a client does not have and a service they do not offer, delivered with total confidence. If it goes on a live site, I check it. Every time.
For SEO, I use it to draft meta descriptions and to sanity-check heading structure, but I do not let it stuff keywords. Google is very good at spotting AI-written filler now, and a page that reads like it was written to please an algorithm will not please a visitor either.
Client emails and proposals
The unglamorous win: client communication. I hate writing the "here is the quote, here is what is included, here is the timeline" email, so I stopped writing it from scratch. I give ChatGPT the bullet points — scope, price, timeline, what is not included — and it drafts the email. Then I edit it into my voice and send it. What used to take twenty minutes of staring at a blank email takes five.
It is also good at the awkward emails. The "your content is two weeks late and I cannot launch without it" email. The "this is out of scope and here is what it would cost to add it" email. I tell it the situation and the tone I want — firm but friendly, no burning bridges — and it gives me a draft I can adjust. I never send an AI email without reading it first, but I almost never write one from zero anymore.
Where I draw the line
There are things I will not hand to ChatGPT, and they matter. I do not paste client passwords, API keys, or database credentials into it — ever. If a debugging task needs a credential, I redact it first. I do not ask it to write security-critical code unsupervised, like authentication or payment handling; that code gets written by me, reviewed carefully, and tested properly.
I also do not let it make decisions for me. It can compare hosting plans, list plugin options, and explain the trade-offs — but the choice is mine, because I am the one who has to maintain the site for the next two years. And I never publish anything it wrote without reading it. Not the code, not the copy, not the email. The day I start publishing unchecked AI output is the day my work stops being mine.
Conclusion
ChatGPT did not replace any part of building WordPress sites for me. It removed the slow parts: the blank page, the boilerplate, the syntax I cannot remember, the email I keep avoiding. My setup is simple — one Project that knows my stack, one chat per client project, specific requests with real context, and a hard rule that nothing goes live without my eyes on it.
If you build with WordPress and Elementor, start with the Project. Put your stack, your standards, and your delivery preferences in it once, and every chat after that gets better. Then use it for the CSS you keep Googling, the code you keep rewriting, and the first drafts you keep dreading. Keep the design, the decisions, and the final check for yourself. That is the workflow, and it has made me faster without making my work worse — which is the only trade worth making.
FAQ
Can ChatGPT build a whole WordPress site for me?
Not well. It can draft content, write snippets, and explain how to do things, but it cannot design, cannot judge taste, and cannot test anything. Use it as an assistant across the build, not as the builder.
What is the best way to ask ChatGPT for WordPress code?
Name the context every time: WordPress version, theme, plugins involved, and the exact outcome. Ask for complete working blocks with a note on where they go, and ask it to explain the approach first when the task is new to you.
Is it safe to paste my site's code into ChatGPT?
Your own theme and plugin code is generally fine, but never paste passwords, API keys, database credentials, or client private data. Redact secrets first, and remember that free and Plus chats may be used for training unless you turn that off in Data Controls.
Can ChatGPT write Elementor custom code?
Yes, for the fiddly bits — custom CSS, small JavaScript, and PHP snippets for functions.php. It is best at scoped, specific tasks. For layout and design, Elementor's visual builder is still faster and better than describing a design in words.
Should I let ChatGPT write my client's website copy?
Let it draft, then rewrite in the client's voice and check every fact. AI first drafts save time, but unchecked AI copy invents details — prices, credentials, services — with total confidence. A human must sign off before anything goes live.
Do I need the paid plan for WordPress work?
Plus at $20 a month is worth it if you use it daily — the stronger models, Projects, and higher limits matter for code and long chats. For occasional use, the free plan covers the basics. The Project feature alone is the reason I pay.
