Web60 Features
ChatGPT WordPress Fixes: Five Myths That Break Business Websites

Everyone says ChatGPT can now fix anything on a WordPress website: describe the problem, copy what it hands back, paste it in, job done. It is a lovely idea. Unfortunately it is also a familiar backstory for broken sites that reach hosting support desks, and the chatbot is rarely the real villain. The myth is.
Before anyone reads this as an anti-AI rant, know where I stand. I built a platform on the premise that AI has removed the skills barrier between business owners and a proper website, and I think AI-powered WordPress is the most useful thing to happen to small business websites in years. Building a site from your own description of your business is one job. Guessing at a fix for a site the chatbot has never seen is a different job entirely. The trouble lives in the gap between the two.
Five beliefs need taking apart.
Myth 1: The Chatbot Knows Your Website
It does not. The chatbot has never seen your site.
Ask a general-purpose AI assistant how to change something on your WordPress website and it answers for the average WordPress site in its training data. It has no idea which theme you run, which plugins are active, which version of WordPress you are on, or what a previous developer customised three years ago. Unless you tell it, it fills every gap with the most common answer. And because WordPress runs somewhere around 38 to 39% of all websites, according to W3Techs' figures this week, there is an enormous amount of WordPress advice for it to draw on, a lot of it written for versions that are long gone.
The classic example is the Customizer. Ask most chatbots how to change your colours or your footer and they will send you to Appearance, then Customize. Since WordPress 5.9, as the WordPress core team spelled out in its notes on the Customizer and block themes, WordPress removes that menu item when a block theme is active unless a plugin needs it. Block themes do the same work in the Site Editor.
So what does that cost you? An evening. You hunt for a menu that does not exist, conclude something is broken, then ask the chatbot how to get the Customizer back. The next answer usually involves installing a plugin or pasting code. One wrong assumption has now become three changes to your production site, and none of them were needed.
The fix is dull and it works. Tell the chatbot what you actually have: your WordPress version (Dashboard, then Updates), your theme name (Appearance, then Themes), and the exact wording of any error. A better question gets a better answer. It still does not get a verified one.
Myth 2: If the Code Looks Right, It Is Safe to Paste
This is the myth that costs money.
Even professional developers do not take AI code at face value. In the Stack Overflow 2025 Developer Survey, roughly two in three respondents named "AI solutions that are almost right, but not quite" as their biggest frustration with these tools, and more of them said they distrust the accuracy of AI output (a little under half) than trust it (about a third). Bear in mind that is a survey of people who write code for a living and can read what the tool produced. A bakery owner cannot, and that is not a criticism. It is the whole reason they asked.
Almost right is the dangerous zone. Completely wrong code tends to fail loudly. Nearly right code runs.
Take a composite example, the kind of request that surfaces every winter in one form or another. A Louth bakery takes Christmas cake orders through its WordPress shop and wants orders to close after the last baking date. The owner asks ChatGPT, gets a tidy snippet for the theme's functions.php file, and pastes it in on a Sunday evening. Two things can happen next. The snippet has a small syntax slip and the whole site falls over. Or it works slightly too well, closing the checkout for every product rather than just the cakes. The second outcome is worse, because nothing looks broken. Orders simply stop arriving, and by the time anyone notices, the busiest weekend of the year has gone to the shop across the road.
The Safety Net WordPress Already Has
WordPress does give you some cover here. Since version 4.9, according to the core team's announcement of its code editing improvements, saving a PHP change in the built-in theme or plugin file editor triggers a test request in the background. If that request hits a fatal error, the original file is restored and you are shown the error instead.
That catches the crash. It does not catch code that runs perfectly and does the wrong thing, like the checkout that quietly closed. Code added any other way gets no check from this feature at all. Nor does it help with the next problem.
The Fix That Disappears on Update
Chatbots love telling people to add code to functions.php. WordPress's own theme handbook is blunt about where that leads when the file belongs to a parent theme: "the next time your theme is updated, your function will disappear!" The handbook's answer is a child theme, which most owners have never heard of and the chatbot rarely mentions.
So the order cut-off works in November, the theme updates in December, and the fix silently evaporates. Nobody connects the two events, because they happened weeks apart.
Myth 3: The Plugin It Recommended Is Real
Ask a chatbot for a plugin that does a particular job and it will usually give you a confident name. Sometimes that plugin exists and is well maintained. Others exist but have not been touched in years. And now and then, nobody ever wrote it at all.
That last one is documented behaviour, not a quirk. Researchers presenting at USENIX Security 2025 generated 576,000 code samples from 16 code-generating models and found that at least one in twenty of the software packages suggested by commercial models, and more than one in five from open-source models, did not exist. Across the study that came to more than 200,000 unique invented names. Their work covered Python and JavaScript packages rather than WordPress plugins, so do not carry the percentages across directly. The mechanism carries across perfectly well: the model produces a name that sounds right. And the researchers' central warning applies to anyone installing software on a business website. When a model keeps inventing the same name, an attacker can publish something under it and wait.

The WordPress hardening guide puts the defence in a single line: "Do not get plugins/themes from untrusted sources." For a business owner, that translates into three habits:
- Search for the plugin by name from your own dashboard (Plugins, then Add New), which searches the official WordPress directory.
- Verify when it was last updated, how many active installations it has, and whether it has been tested with your version of WordPress.
- Treat a plugin that only exists as a download link on an unfamiliar site as a no, however convincing the chatbot made it sound.
If it is not in the directory and not sold by a developer you can identify, it does not go on your site.
Myth 4: If It Breaks, You Can Just Undo It
There is no undo button for a code change. That genuinely surprises people. WordPress keeps revisions of your pages and posts, so owners reasonably assume the same safety net covers everything. It does not cover code, settings or plugins.
What happens when pasted code takes a site down is well documented. WordPress's Recovery Mode documentation explains that, since version 5.2, a fatal error shows visitors a message reading "There has been a critical error on this website," and an email goes to the site's administrator address with a special link to log in and investigate.
Three details in that documentation matter more than the rest.
- Your customers keep seeing the error. Recovery Mode pauses the faulty plugin or theme for your own logged-in session only. The public site stays broken until the cause is fixed.
- The email may never arrive. The documentation warns that the recovery message can be filtered to spam or blocked entirely, depending on how the server sends mail. If the administrator address is a former employee's inbox, it goes nowhere useful at all.
- You still have to find the faulty code. Recovery Mode gets you back into the dashboard. It does not tell you which line the chatbot got wrong.
Anyone who has worked a hosting support desk knows how this evening goes. A five-minute tweak turns into three hours, nearly all of it spent trying to get back to where things stood at six o'clock. The tweak was never the expensive part. Getting back was.
What a Proper Rollback Actually Means
A rollback is not a feeling of having been careful. It is a restore point taken before the change, plus a way to put it back in minutes without a developer. That is the standard to judge any setup against. Could you, today, return your website to exactly how it was an hour ago, on your own, before your next customer arrives?
If the honest answer is no, the problem is not the chatbot.
Myth 5: The Answer Is to Keep AI Away From Your Website
After four sections on what goes wrong, this is the myth I most want to kill.
AI is genuinely good at a large share of website work. Drafting an About page from your rough notes. Explaining a Site Health warning in plain English. Rewording a service page so it answers the question customers actually ask. Pointing you towards the settings screen that probably holds the thing you are looking for. Building the site in the first place from a description of your business, which is exactly how Web60's AI builder produces a complete WordPress site in under a minute. None of that involves pasting server code into production.
The line is not AI versus no AI. It is advice versus deployment. A chatbot's answer is advice from a confident stranger who has never seen your site, and that is still useful. Anything that changes code, settings or plugins goes through a process that assumes the advice might be wrong. The same distinction explains why an AI code generator can leave you with a site nobody can edit six weeks later, while AI that builds on WordPress leaves you with a site you can keep changing yourself.
How to Try an AI Fix Without Betting Your Production Site
When a chatbot does hand you code or a plugin name, this order keeps your customers out of the experiment.
- Describe. Give the chatbot your WordPress version, theme name and the exact error wording, and ask it to explain the change in plain English before it writes anything.
- Verify. Look up any plugin it names in the official directory, and ask whether a built-in setting or a well-established plugin already does the job without custom code.
- Snapshot. Take a manual backup immediately before you touch anything, so your restore point is minutes old rather than last night's.
- Clone to staging. Make the change on a staging copy first and click through the pages that earn money, especially checkout, booking and contact forms.
- Deploy, verify or roll back. Apply it to production only once staging behaves, check those same pages again within the hour, and restore the snapshot the moment anything looks off.

What Your Hosting Should Be Doing Underneath
That workflow only works if the platform underneath supports it. Strip away the marketing and a sensible setup for an owner who uses AI help comes down to four things:
- A staging copy you can create without a developer, so the first person to test a change is you rather than a customer with a card in hand.
- Restore points you can take yourself, plus automatic ones before updates, so you are never relying on last week's backup.
- A restore you can run in minutes, because a site showing a critical error on a Saturday morning is losing bookings by the quarter hour.
- A human who answers, for the night the recovery email never arrives.
Web60 was built to meet that standard. Every site gets one-click staging environments, so the Sunday-evening snippet breaks a copy rather than the shop. Manual on-demand backups sit alongside automatic nightly backups with one-click restore, and the platform takes pre-update and pre-restore safety snapshots automatically, so a plugin update or a restore you regret can itself be reversed. When something still goes sideways, the support team is Irish-based and made up of real people rather than an outsourced script. All of it is included in the €60 a year, with no add-on charge for the safety features you need most on the worst night.
One Limitation Worth Knowing Before You Restore
A restore is a time machine for the whole site, not just the bad code. Roll back to a snapshot taken at six o'clock and any orders, bookings or contact form entries that arrived after six are rolled back too. For a shop mid-campaign, note the newest order number before you restore, then reconcile anything later from your order confirmation emails or your payment provider. Staging has its own blind spot: it shows you the change working on a copy while orders keep arriving on production, so keep test windows short around busy periods.
Where a Closed Builder Genuinely Suits Better
One honest concession. If you know yourself well enough to admit you will paste whatever a chatbot gives you at midnight and never test it, a closed website builder that simply does not let you add server code will protect you from that habit better than any WordPress host can. You give up the plugin ecosystem, the flexibility and much of the ownership in exchange, and for most businesses that trade is a poor one. For that particular owner, it is a fair one.
Conclusion
AI has made website help available at any hour, for free, in plain English, and that is good for every business owner who runs their own site. What it has not done is see your website. Treat what a chatbot tells you as a well-read stranger's suggestion, verify any plugin it names, and put every code change through staging and a fresh snapshot before it reaches production. Do that, and AI becomes the cheapest website adviser you have ever had rather than the most expensive one. The next time a chatbot hands you a block of code, you will know which questions to ask of it, and of your hosting, before it goes anywhere near your customers.
Frequently Asked Questions
Is it safe to use ChatGPT to fix my WordPress website?
It is safe to use ChatGPT for advice, explanations and draft wording. It is not safe to paste code or install plugins it suggests straight onto your live site. The chatbot cannot see your theme, plugins or WordPress version, so its answer may be outdated or slightly wrong. Take a backup, try the change on a staging copy, and verify your key pages before applying it to production.
What does the critical error message on my WordPress website mean?
It means WordPress hit a fatal PHP error, usually caused by a plugin, a theme or custom code, and has switched into Recovery Mode. Visitors see the error message while an email with a special login link goes to the site administrator address. That link lets you log in with the faulty component paused so you can deactivate or fix it. If the email does not arrive, contact your hosting support or restore a backup taken before the change.
How do I know if a plugin ChatGPT recommended is real?
Search for it by name in your dashboard under Plugins, then Add New, which searches the official WordPress plugin directory. A genuine, well-supported plugin shows when it was last updated, how many active installations it has and which WordPress version it has been tested with. If you cannot find it there or on the website of a developer you can identify, do not install it. Chatbots sometimes invent plausible names for software that does not exist.
Where should I paste code that ChatGPT gives me?
Ideally, nowhere on your live site until it has been tested. First ask whether a built-in setting or an established plugin does the same job, because that avoids custom code entirely. If code really is needed, try it on a staging copy after taking a backup. Code added directly to a parent theme's functions.php file is lost when the theme updates, which is why WordPress recommends a child theme for that kind of change.
Will my changes survive a WordPress theme update?
Changes made inside the theme's own files will not. When a theme updates, its files are replaced with the new version, so anything you added to them disappears. Your pages, posts and settings are stored separately and survive. Code customisations belong in a child theme or a dedicated plugin so they are not overwritten.
Can AI build my website instead of fixing an old one?
Yes. AI website builders now create a complete site from a description of your business rather than patching an existing one line by line. Web60's AI builder produces a fully designed WordPress site in under a minute, and because it is full WordPress you can edit everything yourself afterwards. Hosting, SSL, backups, staging and security are included for 60 euro a year.
Sources
- AI section, Stack Overflow 2025 Developer Survey
- We Have a Package for You! A Comprehensive Analysis of Package Hallucinations by Code Generating LLMs, USENIX Security 2025
- Recovery Mode, WordPress.org Documentation
- Code Editing Improvements in WordPress 4.9, Make WordPress Core (22 October 2017)
- State of the Customizer with Block Themes in WordPress 5.9, Make WordPress Core (7 January 2022)
- Child Themes, WordPress Theme Handbook
- Hardening WordPress, WordPress Advanced Administration Handbook
- Usage statistics of WordPress, W3Techs
Graeme Conkie founded SmartHost in 2020 and has spent years building hosting infrastructure for Irish businesses. He created Web60 after seeing the same problem repeatedly — Irish SMEs paying too much for hosting that underdelivers. He writes about WordPress infrastructure, server security, developer workflows, managed hosting strategy, and the real cost of hosting decisions for Irish business owners.
More by Graeme Conkie →Ready to get your business online?
Describe your business. AI builds your website in 60 seconds.
Build My Website Free →More from the blog
Payment Test Mode Left On: The Staging Push That Took No Money
Payment test mode left on after a staging push leaves a shop that looks open but takes no money. Where the switch hides and what to verify after every change.
WordPress Default Settings Still Showing on Your Business Website, and How to Clear Them
Hello world posts, Sample Page, an old tagline and a draft privacy policy: the WordPress default settings that make a business website look unfinished.
