WordPress security maintenance with AI: A safer routine for small business sites

A digital graphic illustrating AI-powered WordPress security and maintenance against a blue gradient background. On the right, a smiling man in an olive green sweater works on a laptop. In the background, a dark WordPress dashboard features a green badge reading "Website secured" with a shield check icon. In the foreground, a floating translucent UI card displays the user prompt "Review my plugins and users..." next to his avatar, followed by an AI status reading "Reviewing..." alongside a SiteGround logo, with a white sparkle symbol floating nearby.

WordPress security maintenance is the recurring work of keeping your site’s exposure small: updating WordPress itself along with your plugins and themes, checking what’s installed, reviewing who has access to the dashboard, removing what you no longer use, and confirming your backups ran. It’s basic housekeeping, and it’s separate from the tools that guard your site, but it’s just as important.

And for small business owners who manage their own WordPress websites, it’s another nuisance to think about. Our 2026 report on AI in WordPress for small businesses found that 67% of small business owners run their site entirely themselves, with no agency or freelancer behind them, and 28.9% named security and updates among the things they find hardest. What many don’t know is that an AI assistant can now help with WordPress security maintenance by connecting to their site and carrying out recurring tasks through a simple chat.

Key takeaways:

  • Protection and WordPress security maintenance are two different jobs. Protection is your firewall, malware scanner, and host, running around the clock. Maintenance is updates, audits, and access reviews, and it basically depends on you.
  • Most small business owners handle WordPress security maintenance alone. 67% of small business owners manage their site entirely themselves, and 28.9% find security and updates among the hardest parts, as per SiteGround’s report.
  • A specialized AI assistant like SiteGround’s AI Agent for WordPress can help you complete WordPress security maintenance faster and more consistently. It can do things like update plugins and themes, check what’s installed, and review users and roles.
  • You shouldn’t postpone your WordPress security maintenance work for too long. It takes five hours between a flaw being made public and the first attack on it.

What WordPress security maintenance actually covers

Most writing on this subject blurs two things that need to stay apart: the tools that watch your site continuously, and the housekeeping that keeps its exposure minimal. They work at different levels (and can fail in different ways):

LayerWhat it coversWho or what does it
Security protectionFirewall, malware scanning, watching for newly announced weaknesses, login protection, server hardening, cleanup after a break-in, and the backup system itselfDedicated security plugins, your host, or a managed service.
Security maintenanceUpdates to WordPress, plugins, and themes; checking what is installed; reviewing who has access; removing what you do not use; checking settings; and doing it again next monthYou. An AI Agent can help you complete much of this faster and more consistently.
The overlapBackups. The system that takes them is protection, but confirming they ran and knowing how to restore is maintenanceYour host or backup tool provides it. You confirm it, with or without AI help.

Security protection: what your tools and host do

Protection runs whether or not you are paying attention:

  • A firewall sits in front of your site and checks incoming visitors before they reach it, turning away requests that match known attack patterns. You may see it called a WAF, short for web application firewall.
  • A malware scanner reads through your site’s files looking for malicious code, which is code an attacker has added to make your site do something you did not intend, such as redirecting your visitors to another site.
  • Vulnerability monitoring watches for public announcements that something you have installed has a newly discovered weakness. A vulnerability is a flaw in a piece of software that someone can misuse to get in.
  • Login protection blocks repeated password guessing, known as a brute-force attack, where software tries thousands of passwords until one works.
  • Server hardening is your hosting company tightening the settings on the machine your site runs on, so that even a successful attack has less room to move.

None of this is a daily task for you. It runs continuously and automatically, which is why it belongs to dedicated security plugins and your hosting provider.

Security maintenance: what stays your job

While security protection runs automatically, security maintenance is something that gets done, over and over, and it involves judgments about your particular site: which plugins you actually still need, who should be able to log in, what is safe to remove. That is why it stays with you even when you have good security tools running.

Four things can help explain why these tasks matter more than they look:

  • An update is a fix you have to install. When a plugin developer finds a security flaw, they fix it and release a new version. Until you install that version, your site is still running the flawed code, and by then the flaw is public knowledge. The fix existing does nothing for you. Installing it does.
  • Access only ever accumulates. Everyone who has ever needed to log in still can, unless somebody removes them. Most people get given the administrator role, the highest level of access in WordPress, because it is the fastest way to unblock someone. A WordPress user access audit is going through that list and asking who still needs to be on it.
  • An abandoned plugin looks exactly like a maintained one. Nothing in your dashboard turns red when a developer stops working on a plugin. It stops receiving updates and carries on running as before. The only way to find out is to look.
  • A backup you have never restored is unproven. Backups fail without announcing it. A setting changes, a disk fills up, a plugin interrupts the process, and the report still says the job completed. You find out whether the backup is any good at the moment you need it most.

None of these tasks is difficult, which is what makes them easy to put off. There’s no deadline, nothing visibly breaks, and skipping them appears to cost nothing. Except when it does.

Why postponing WordPress security maintenance is riskier than it used to be

Two things changed recently, and neither is about WordPress itself getting worse. The first is volume: Patchstack’s annual security report recorded 11,334 new weaknesses across WordPress plugins, themes, and WordPress itself in 2025, 42% more than the year before and roughly 200 a week. The second matters more: the dangerous share grew faster than the total. Highly exploitable flaws rose 113% in a single year, and more high-severity ones were found in 2025 than in the previous two years combined. The same monthly check now covers more ground, and more of what it covers is worth attacking.

Where those weaknesses live has not changed. 91% were in plugins, and siix were in WordPress itself, all low priority. This basically means WordPress plugin security is a big part of the problem.

About half of high-impact weaknesses are attacked within 24 hours of becoming public, and weighted by how heavily each one was targeted, the median gap between a flaw being announced and the first attack on it was five hours.

No maintenance routine closes a five-hour gap. Nobody checks their site every five hours, and 46% of flaws had no fix available from the developer when they were disclosed, so updating sooner would not have helped in almost half of cases either. That’s the argument for dedicated protection running underneath your routine.

What a routine does fix is the backlog. Every skipped week adds unpatched plugins, unreviewed accounts, and code you have forgotten is still there. Plugins are sometimes pulled from the WordPress directory over security problems that never get fixed, and if one of yours has been pulled, updating will never help.

The recurring WordPress security maintenance checklist

Six tasks make up a WordPress security checklist within any broader WordPress maintenance checklist. None is complicated on its own. The value comes from doing them regularly instead of when something goes wrong.

TaskWhat it preventsHow often
Update WordPress, plugins, and themesPublished weaknesses being used against you when a fix already existsWeekly, and straight away for anything under active attack
Check what is installedAbandoned or withdrawn plugins sitting on your site unnoticedMonthly
Run a WordPress user access auditOld accounts and contractors who still have full administrator accessMonthly
Delete plugins and themes you don’t useInactive code that can still be attacked and still needs patchingQuarterly
Confirm backups ranFinding out during an emergency that the backup you counted on was never being takenWeekly
Check your settingsOptions that were changed for a one-off reason and never changed backQuarterly

Deleting unused WordPress plugins and themes is the task many people skip, because switching a plugin off feels like enough. However, deactivated code still sits on your server, can still be reachable, and still needs patches that nobody is applying because you stopped thinking about it. Switching off is a pause, while deleting is the fix.

Where an AI Agent helps with WordPress security maintenance

A specialized AI assistant like SiteGround’s AI Agent for WordPress is connected directly to your site, so that instead of only answering questions, it can make actual changes in your dashboard when you ask. For instance, if you ask a chatbot like ChatGPT in another browser tab how to update your plugins, it will explain the steps. But if you ask an AI connected agent, it can actually update them for you.

What an AI Agent can help you complete

Every task in the checklist above is something you would otherwise do by clicking through the dashboard, which means it is something the AI Agent for WordPress can do on request:

  • Updating WordPress core, plugins, and themes, individually or in bulk, with approval for higher-risk changes.
  • Managing plugins and themes across their lifecycle: listing what is installed, explaining what each item appears to do, activating, deactivating, updating, or removing unwanted items after approval.
  • Pointing out plugins or themes that look inactive, redundant, outdated, abandoned, or suspicious, so the quarterly clear-out becomes a short list to review rather than a full investigation.
  • Reviewing and managing users and roles, from listing administrator accounts to creating users, updating profiles, changing roles, downgrading access, or removing accounts after approval and content reassignment.
  • Helping configure WordPress-level or compatible plugin-level security settings, such as login protection or hardening options, when those controls are available inside the site.
  • Repeating the same routine across multiple connected sites, instead of opening one dashboard after another.

Here’s an example prompt you can give to the AI Agent for WordPress:

“Run a WordPress security maintenance review: core, plugins, themes, users, roles, comments, and supported security settings; identify updates, risky or inactive items, admin accounts, and cleanup tasks; group everything by risk; then ask for approval before making changes.”

The AI Agent sorts what it finds into high, medium, and low risk, lists the plugins, themes, users, and settings it checked, then proposes a specific plan: deactivate this, delete those two, switch on these three settings, leave the rest alone.

A screenshot of the AI Agent by SiteGround interface displaying a Recommended cleanup plan for a WordPress website. The outlined plan categorizes tasks including deactivating the WordPress Beta Tester plugin, deleting inactive themes (Twenty Twenty-Four and Twenty Twenty-Three) while retaining Twenty Twenty-Five, enabling security settings like two-factor authentication, and noting an optional decision for inactive Akismet. At the bottom sits a text input box with the placeholder "Ask me anything WordPress related and I'll help."

Approve the plan and it works through it, then reports back on what it changed. Anything it was not sure about it leaves alone and asks about separately, so any genuine judgment calls come back to you.

A screenshot of the AI Agent by SiteGround chat interface following up on site cleanup tasks. At the top right, a user prompt reads "Proceed with the recommended changes." In response, the "WordPress Expert" assistant confirms that the approved recommendations have been completed—listing the deactivation of the WordPress Beta Tester plugin, deletion of Twenty Twenty-Four and Twenty Twenty-Three themes, enablement of two-factor authentication and readme file removal, and disabling of default pingbacks. The assistant then asks whether to delete Akismet or keep it installed for future anti-spam configuration. At the bottom, an input box sits with the placeholder "Ask me anything WordPress related and I'll help."

For more prompts you can reuse and adapt, read our guide on how to turn WordPress admin work into simple conversations.

What an AI Agent cannot do for WordPress security

An AI Agent doesn’t run a firewall, and it doesn’t scan your files for malware. It doesn’t watch vulnerability announcements overnight and wake up when something you have installed comes under attack. It doesn’t itself block password-guessing attempts in real time, although it may help configure a security tool that does. It doesn’t harden the server itself, although it may help adjust WordPress-level hardening settings.

The reason is structural rather than a gap somebody will close in the next version. An agent acts when you ask it to, working through the same WordPress controls you would use yourself.

A firewall works somewhere else entirely: it inspects every request arriving at your site, thousands of times a day, before WordPress even starts loading. A malware scanner reads every file on a fixed schedule. Vulnerability monitoring watches disclosure feeds around the clock and does not wait to be asked. Those jobs are continuous, automatic, and positioned underneath or in front of the layer an assistant works in.

How to run AI-assisted WordPress security updates without breaking your site

Applying WordPress security updates quickly matters, especially when an update fixes a security issue. But updating carelessly creates its own problems. An AI Agent can reduce the manual work, organize the process, and add approval steps before high-impact changes, but it cannot make live updates risk-free. A plugin, theme, or WordPress core update can still introduce a bug, conflict with another extension, break checkout, alter layouts, or trigger a compatibility issue.

The safest way to use AI is not to let it push every update blindly. It’s to use it as an operator with guardrails: inventory first, plan the work, update in controlled batches, and keep a rollback path ready.

  • Back up before you update, and know how to restore. A backup you have never tested is a hope rather than a plan. The AI Agent can help coordinate the update routine, but it is not the backup or restore system, so the restore point needs to exist before changes begin.
  • Test complicated or business-critical updates on a staging copy first. WooCommerce, payment plugins, page builders, membership plugins, booking systems, multilingual plugins, caching tools, and major theme updates can break important parts of a site. The AI Agent can help identify which updates belong in the staging-first group before anything touches the live site.
  • Use AI to plan and batch the work, not to remove judgment. Instead of updating everything at once, ask the agent to list available updates, group them by risk, and run smaller batches. If something breaks after one giant update batch, it is much harder to know what caused it.
  • Keep approval over anything with a large blast radius. Deleting plugins, removing themes, changing user roles, modifying security settings, and running bulk operations should pause for confirmation. A good AI-assisted workflow keeps the agent as an operator, not an unchecked autopilot.
  • Check the site after meaningful update batches. Visit key pages, test forms, confirm the dashboard is not showing new errors, and run through checkout if you sell online. The AI Agent can report which updates completed successfully, but it cannot replace checking the real user journeys your site depends on.
  • Know how to undo an update before you need to. For posts and pages, WordPress revisions may help. For plugin, theme, core, or database-impacting changes, your real rollback plan is usually a backup, restore point, staging copy, or dedicated rollback tool.

A recurring WordPress security routine you can actually keep

For a busy small business owner, the difference is not just how long each WordPress security maintenance task takes, but how much of the security maintenance routine can be organized, explained, and safely prepared before you have to make a decision.

CadenceWhat you doRoughly how long manuallyRoughly how long with AI
WeeklyReview WordPress core, plugin, and theme updates. Apply low-risk updates, test complicated or business-critical plugins on staging first, confirm your latest backup exists, and check key pages or flows after updating.30 to 60 minutes5 to 15 minutes, plus any staging or manual checks
MonthlyCheck installed plugins and themes against what you actually use. Review users and roles, especially administrator accounts, and remove or downgrade access that is no longer needed.45 to 90 minutes10 to 20 minutes, depending on how many items need approval
QuarterlyIdentify inactive, redundant, abandoned, or confirmed-unused plugins and themes, then delete what you no longer need. Review WordPress security settings, backup settings, and connected services. Restore a backup somewhere safe to prove it works.2 to 4 hours30 to 60 minutes, plus the time needed to test the backup restore
Continuously, not by youFirewall, malware scanning, vulnerability monitoring, login protection, and automated backups run underneath all of the above.Handled by your tools and hostStill handled by your tools and host


These estimates assume someone who doesn’t already know every plugin, setting, and maintenance screen by heart. The AI Agent shortens the dashboard work by inventorying, explaining, grouping, and carrying out approved changes, but it doesn’t remove the time needed for staging, backup restores, or checking the parts of the site your visitors actually use.

Close the follow-through gap

WordPress security maintenance rarely fails because someone decides it doesn’t matter. It fails because it’s never the most urgent thing on any given day, and because a neglected site can look perfectly fine for months. That is the follow-through gap: the space between knowing what should be done and actually doing it regularly.

AI does not replace the security layers that run all the time. Your firewall, malware scanner, vulnerability monitoring, backups, and host still handle the continuous work. But an AI Agent can make the recurring WordPress-side work much easier to keep: checking updates, reviewing plugins and themes, auditing users, spotting old admin accounts, cleaning up clutter, and preparing changes for approval.

FAQs

Can AI keep a WordPress site secure?

No. AI cannot keep a WordPress site secure on its own. It can help with WordPress security maintenance that reduces risk, such as updates, audits, and access reviews, but firewall, malware scanning, vulnerability monitoring, and login protection still require dedicated security tools and your host.

What is included in WordPress security maintenance?

WordPress security maintenance includes updating WordPress, plugins, and themes, checking which extensions are installed, completing a WordPress user access audit, deleting unused plugins and themes, confirming backups ran, and checking your settings on a recurring schedule.

Does an AI Agent replace a firewall or WordPress security plugin?

No. An AI Agent does not replace a firewall or security plugin. They do different jobs. A firewall and scanner watch your site continuously, while an AI Agent helps you complete the maintenance work that would otherwise be postponed.

Why should unused WordPress plugins and themes be removed?

Unused WordPress plugins and themes should be removed because inactive code can still be attacked and still needs patching. Plugins accounted for 91% of WordPress vulnerabilities recorded in 2025, and switching a plugin off does not remove its code from your server.

How often should WordPress plugins and themes be updated?

WordPress plugins and themes should be updated at least weekly, and WordPress security updates for anything under active attack should be applied as soon as you can safely test them. Patchstack measured a weighted median of five hours between a flaw becoming public and the first attack on it.

Can an AI Agent update WordPress plugins safely?

Yes, with conditions. An AI Agent can update WordPress plugins safely when you back up first, test complicated plugins such as WooCommerce or page builders on a staging copy, and keep approval over high-impact changes rather than letting anything run unattended.

What is a safe recurring WordPress security routine?

A safe recurring WordPress security routine follows a WordPress security checklist: check updates and backups weekly, review users and installed extensions monthly, and check settings and remove unused plugins and themes quarterly, with dedicated security tools running continuously underneath.

How much does it cost to build a website or web app for your business in 2026?

A digital graphic illustrating website building and development costs against a dark green grid background. In the center, a website editor preview showcases a culinary site featuring a steaming bowl of risotto garnished with herbs, where a selected white button reading "GET STARTED" sits beneath a floating text-formatting toolbar. Floating on the right are three translucent price badges with indicator arrows displaying "$6,173" with a red upward arrow, "$2,646" with a green downward arrow, and "$1,376" with a green downward arrow, anchored by a white price tag icon badge in the bottom right corner.

Search for what a website costs, and you’ll get answers ranging from nothing to $250,000, which can hardly help you. The number is that wide because the question should really be what your project costs based on the path you take to build it.

The cost to build a website in 2026 is about $200 a year on a DIY builder, $1,500 to $8,000 with a freelancer, and $6,000 to $35,000 or more at an agency. Web apps and MVPs start higher, from a few hundred dollars on no-code tools to $18,000 and up for custom development.

Key takeaways:

  • Most small businesses spend under $10,000. 61% of small business buyers spent less than $10,000 on their most recent website and 84% spent under $20,000. Professional small business website costs cluster between $3,000 and $15,000.
  • The cost to build a website or web app is set by the path, not just the project. The same brochure site can cost $200 a year on a builder or $12,000 at an agency. What changes is who does the work.
  • A web app costs more than a website because it does something. Custom web app development starts around $18,000 for an MVP, against $3,000 to $15,000 for a typical small business site.
  • AI and no-code builders are the cheapest entry. AI app builders start free, and no-code platforms now run roughly $36 to $69 per month at entry level.
  • Ongoing costs are the line most quotes leave out. Budget roughly $600 to $6,000 a year for a small business site, and 15% to 25% of the build cost annually for a web app.

What determines website and web app development cost

Many cost guides start with features: how many pages, whether you need e-commerce, how complex the design is. Those are important details, but they’re actually second-order. The variable that moves the number most is who builds it and on what.

A five-page brochure site is a five-page brochure site whether you assemble it on a template, hand it to a freelancer, or commission an agency. The work is broadly the same. But that site is about $200 a year built yourself, around $4,000 from a freelancer, and $12,000 or more from an agency. You are not buying more website at the top of that range. You are buying more of three things.

  • Time is the one people underestimate. What you don’t pay in money you pay in hours: learning the tool, writing the copy, resizing images, fixing what breaks. A DIY site isn’t free, it’s unpaid. If your hours are worth anything to the business, price them before calling the builder path cheap.
  • Judgment is knowing which decisions matter and where projects like yours usually go wrong. Someone who has built dozens of these will skip the arguments you would have had. On the DIY path, that judgment is yours to supply, which is fine when the stakes are low and expensive when they aren’t.
  • Accountability is the least visible line on any quote. It answers who fixes it when the contact form stops sending on a Tuesday. On a builder, that’s you. With a freelancer, it depends what you agreed and whether they’re free that week. With an agency on a retainer, it’s contractual.

That’s also why quotes from different paths aren’t directly comparable. A $3,000 freelancer and a $12,000 agency are often quoting different work, because content, photography, revisions, and post-launch support may be inside one number and billed separately in the other. Write down what you need first, then check each quote against the same list.

So the useful question isn’t what a website costs. It’s which path fits what your site or app has to do, and what that path costs in 2026.

How much does it cost to build a website in 2026?

It costs between roughly $16 per month and $35,000 or more to build a website in 2026, depending on the path. Most professional small business website costs land between $3,000 and $15,000. In the Clutch 2026 survey, 61% of small businesses spent under $10,000 on their most recent website. GoodFirms’ 2026 software development cost survey found 51.6% of web development agencies quoting $3,000 to $15,000 for small-scale sites.

Build pathTypical 2026 costBest forWatch for
DIY website builder (Wix, Squarespace)$16 to $50 per monthSimple brochure sites, tight budgets, fast launchLimited customization, and you build and maintain it yourself
AI website builderFree to about $50 per monthNon-technical owners who want a fast first versionOutput quality varies, and publishing or a custom domain usually needs a paid plan
Self-hosted WordPress (DIY)$100 to $500 per yearOwners comfortable with a small learning curveMore technical than a hosted builder
Freelancer$1,500 to $8,000 one-timeCustom branding without agency overheadTurnaround times and limited post-launch support
Boutique or full agency$6,000 to $35,000 and upStrategy, custom design, and ongoing supportHighest upfront cost, and scope creep adds to it

The builder prices are entry plans billed annually: Wix starts at $17 per month and Squarespace at $16 to $19, but the plan most small businesses actually need sits closer to $29 to $39 once you add selling or remove transaction fees. And the agency range is wide because it covers everything from a boutique studio’s $6,000 template build to a $35,000 custom project with strategy and content included.

AI website builders sit alongside the DIY tier rather than replacing it, and the sticker price is rarely the whole bill. Our guide to AI website builder pricing covers plans, renewals, limits, and the fees that appear when you try to publish.

How much does it cost to build a web app or MVP in 2026?

Web app development cost starts where website cost tops out. An MVP built with no-code tools can cost a few hundred dollars a year, while custom development for the same idea starts around $18,000. The cost to build a web app depends on the same build path question, with an extra tier at the top that websites do not have.

Build pathTypical 2026 costBest forWatch for
AI app builderFree to about $300 per year to startValidating an idea fast, cheapest entryA complexity ceiling you may eventually outgrow
No-code platform (Bubble, Adalo, FlutterFlow)About $430 to $2,400 per yearFounders needing more logic than a builder allowsYou rent it, expect 100 to 300 hours to learn it, and per-seat costs climb
Hybrid no-code plus custom work$1,000 to $5,000MVPs expected to scale to real usersNeeds some technical help at the edges
Agency-built MVP$5,000 to $25,000 with a productized or offshore teamFunded teams wanting a polished first versionUS agencies commonly quote $25,000 and up for the same scope
Custom development (agency or team)$18,000 to $60,000 for an MVP; $45,000 to $150,000+ for a full appGenuinely complex or large-scale softwareMost expensive by far, and typically three to six months

No-code platforms are the tier most often misquoted in older guides. Entry plans currently run roughly $36 to $69 a month, with Adalo at the lower end and Bubble at the upper, and FlutterFlow’s Basic plan at $39. FlutterFlow raised that from $30 during 2026, so check current pricing rather than trusting a figure from last year’s roundup.

Note also how wide the agency MVP band is. Productized offers and offshore teams genuinely deliver at $5,000 to $25,000, while US agency quotes for a lean MVP commonly start at $25,000 and run past $100,000. If you are scoping an MVP, our guide to building an MVP with vibe coding covers what to include and what to cut.

“MVP” has no agreed meaning, which is why the quotes vary so much. One agency’s MVP is a landing page with a signup form. Another’s is a working product with accounts, payments, and an admin panel. When quotes for the same idea come back at $8,000 and $60,000, they are usually pricing different products, not the same product at different rates. Write the feature list yourself first, in plain language, and send the identical list to everyone. The spread shrinks immediately.

Why a web app costs more than a website

A web app costs more than a website because it does something, while a website mostly shows something. That single distinction explains most of the gap between the two tables.

A website presents information: pages, images, a contact form, maybe a shop. The work is largely design and content, and once built it mostly sits there. A web app has users who log in, data belonging to each of them, rules about who can see and change what, and logic that has to be right every time. All of that needs designing, building, and testing, and testing is where the hours go. Custom web app costs also carry a longer tail than custom website costs, because logic touching real customer data has to keep working as payment providers and integrations change around it.

What increases the cost

Within any path, five things move you from the bottom of the range to the top.

  • Design originality. A template build and a custom design are different products. This is the single biggest gap between a $3,500 site and a $14,000 one.
  • Page count and feature complexity. Bookings, e-commerce, and third-party integrations push toward the top of every range, because each one is a system that has to be configured and tested.
  • Who writes the content. Writing it yourself is free and slow. Done-for-you copy and photography are often quoted separately, and they are a common reason a quote comes in higher than expected.
  • User roles, data, and logic. This is the dividing line between website pricing and web app pricing. The moment people log in and the site remembers things about them, you have crossed into the second table.
  • Ongoing costs. Hosting, security, backups, maintenance, and tool subscriptions are rarely in the headline quote, and they run for as long as the site does.

On the AI and DIY paths there is a sixth cost that does not appear on any invoice, which is your own time. AI builders produce a first version quickly, then you iterate, and the number of rounds is where the hours accumulate. Describing what you want precisely cuts that down, and our guide to writing better prompts for building is the practical version of that skill.

Which path is right for your budget

One question routes you faster than any feature checklist: how much of your revenue depends on this site or app? Not how much you like it, or how much you want it to impress people. How much money moves through it or because of it.

If the site is a low-cost small business site or an early test

Stay in the DIY and AI builder tier, free to about $50 per month. This covers a local service business that needs to be findable and credible, a portfolio, a landing page for something you are still validating, or a first version of an app idea. Paying $8,000 for a site that supports a business but does not drive it is a poor trade.

This is also where an all-in-one AI builder earns its keep on cost. For instance, SiteGround’s Coderick AI sits on this line: you describe what you want, and building, hosting, SSL, version control, and publishing come in the same plan rather than as five separate subscriptions you assemble and pay for individually.

If the site is one of several lead sources

Look at freelancers and small agencies, roughly $1,500 to $10,000. This is the tier where custom design starts paying for itself, because the site is doing real work in a real sales process and looking like everyone else’s template costs you something measurable. A freelancer at $1,500 to $8,000 gets you custom branding without agency overhead. A boutique agency from around $6,000 adds strategy and a process, which matters more as the site gets more complicated.

If the site or app is revenue-critical

Budget for an agency or custom website or web app development: $6,000 to $35,000 and up for websites, $18,000 and up for web apps. If the site is the storefront, if downtime costs money by the hour, or if the app is the product itself, the cost of getting it wrong is larger than the cost of building it properly. This is also the tier where the ongoing budget stops being optional, because software that carries revenue needs someone responsible for it.

Pro tip: Count the weeks, not just the money. A site built with an AI builder can be live in a few days. An agency project commonly runs eight to sixteen weeks, and a custom web app three to six months. If the site or app brings in customers, every month of delay is revenue you didn’t earn, and that rarely appears in any comparison. It can flip the maths entirely: a cheaper build that starts working in March may beat a better one that starts in July.

Ongoing website and web app costs to budget for

Ongoing website costs, including website maintenance costs, are the line most quotes leave out, and they are why a build that looked affordable becomes a problem in year two. Website maintenance cost covers:

  • Hosting. The largest recurring line for most sites, and the one that scales as traffic grows.
  • Domain renewal. Small and annual, and easy to forget until the site goes down.
  • SSL certificate. Usually included with hosting now, but worth confirming rather than assuming.
  • Software and plugin updates. Free if you do them yourself, billed if somebody else does.
  • Security and backups. Sometimes bundled with hosting, sometimes a separate subscription.
  • Content edits. The line that grows fastest if you cannot make changes yourself.

For a small business site, expect roughly $600 to $6,000 a year in total, with full-service maintenance plans commonly landing at $95 to $195 per month. If the site is simple and you handle updates yourself, you can run it for well under $100 a year in domain and hosting alone, but you are paying in hours instead.

Ongoing web app costs work differently and are higher. Web app maintenance costs are usually estimated as a percentage of the build rather than a flat fee, at roughly 15% to 25% of the original cost every year, because the code has to keep working as the services around it change. On a $40,000 MVP that is $6,000 to $10,000 a year, indefinitely. Add hosting, monitoring, and any AI or third-party services the app depends on. If you want to see how those separate subscriptions add up in practice, our breakdown of AI coding and hosting costs prices a full stack line by line.

Match the path to the job, not to the lowest price

The cost to build a website or web app in 2026 spans four orders of magnitude, and every number in that range is correct for somebody. What makes it useful is the question underneath it, which is what this thing has to do for your business. A site that has to be findable and credible does not need the budget of a site that has to sell. An idea you are testing does not need the budget of a product people will pay for.

Pick the cheapest path that can genuinely do the job, then add the ongoing costs before you compare quotes. The expensive mistake is rarely overspending at the start. It’s choosing a path that cannot do what you needed, and paying to build the thing twice.

If you are not sure which tier you are in, the cheapest way to find out is to build the simple version and see where it runs out. A month with a real site teaches you more about what you need than another week of comparing quotes, and it makes the next quote a better one.

[96]

FAQs

How much does it cost to build a website in 2026?

It costs anywhere from about $16 per month on a DIY builder to $35,000 or more at a full agency to build a website in 2026. Most professional small business sites land between $3,000 and $15,000, and 61% of small businesses spent under $10,000 on their last site.

Why does a web app cost more than a website?

Web app development cost is usually higher than website development cost because a web app does something rather than just shows something. Websites mostly present information, while web apps handle users, data, logic, and roles, which means more design, engineering, and testing. Custom web app MVPs typically start around $18,000.

What is the cheapest way to build a business website?

The cheapest way to build a business website is a DIY or AI builder, starting free to around $50 per month. You trade customization and hands-off support for a low price, which suits simple brochure sites and early-stage testing.

Should I use an AI builder, freelancer, agency, or developer?

You should choose based on how much of your revenue depends on the site, how much customization you need, and your website development cost ceiling. An AI or DIY builder fits simple needs and tight budgets, a freelancer suits custom branding at $1,500 to $8,000, and an agency fits complex, revenue-critical projects starting around $6,000.

How much does it cost to build an MVP before hiring developers?

MVP development cost can range from nothing to a few thousand dollars before hiring developers, depending on the build path. AI app builder costs start free to about $300 per year, no-code app builder costs run roughly $430 to $2,400 per year, and hybrid builds land around $1,000 to $5,000.

How much does custom website or web app development cost?

Custom website cost is usually lower than custom web app cost, because a web app requires more logic, data handling, user interaction, and testing. Custom websites run from around $6,000 to $35,000 and up, while custom web apps start near $18,000 for an MVP and reach $150,000 or more for a full product.

What are the ongoing costs after building a website or web app?

Ongoing website costs and ongoing web app costs include hosting, domain renewal, security, backups, updates, subscriptions, and support. Budget roughly $600 to $6,000 a year for a small business site, and 15% to 25% of the build cost annually for a web app.

Can Coderick AI reduce the cost of building a website or web app?

Yes. Coderick AI can reduce the cost of building a website or web app by combining AI building, hosting, SSL, version control, and publishing in one plan, which removes several separate setup and subscription costs that a pieced-together stack would carry.

7 AI mistakes small businesses make with WordPress AI tools and how to avoid them

A digital graphic depicting AI tool management and cost tracking around a website, set against a light blue gradient background. In the center, a browser mockup displays a waterfront luxury real estate website titled "THE ATELIER." Floating UI cards surround the website, detailing various software costs and system statuses: a "Generic AI Writer" card at "$8/mo," an "Enterprise Bot" card noting "Idle for 14 days • $120 spent," an active "WP Core" card showing "$15 spent," an inactive "Image Optimizer" card showing "$45 spent," a "Cohesive Agent" card at "$78," and a "Legacy Translator" card at "$12" displaying a "Memory limit exceeded" error.

Small business owners managing their WordPress sites are increasingly relying on AI, as our 2026 report on AI in WordPress for small businesses found by surveying more than 7,000 of them. However, we also saw the same handful of issues come up again and again.

The most common AI mistakes small businesses make on WordPress usually happen around the tools they choose and how they’re set up: generic chatbots that can’t reach their site, AI plugins that reach too far into it, API keys left exposed, token bills nobody capped, and changes published without review. Luckily, each one is easily avoidable, and the fix is usually smaller than the problem.

Key takeaways:

  • The AI mistakes small businesses make on WordPress start with the tool, not the task. Two-thirds use ChatGPT as their main AI tool, but that usage clusters in research (66.5%) and content (65.7%), not the site admin that eats the most time.
  • Plugin sprawl is the fastest-growing risk. WordPress AI plugins are growing about three times faster than the wider plugin economy, and most reported WordPress vulnerabilities come from plugins.
  • Your AI API key is a billing credential. Keys saved through the WordPress Connectors screen sit in your database as readable text, and WordPress sets no spending limit by default.
  • Unreviewed output costs more than it saves. 41% of small business owners say usable results take multiple attempts, and 22% don’t trust AI accuracy.
  • Some AI setups create more admin than they remove. Getting AI running in WordPress by hand means a provider account, an API key, two plugins, and a separate billing dashboard to watch.

Mistake 1. Relying on a generic chatbot for WordPress work

Two-thirds of small business owners use ChatGPT as their primary AI tool for WordPress work, but our 2026 report on AI in WordPress also found that usage concentrated in research and content creation. Site management, which is where most of the hours actually go, barely registers.

There’s a simple reason for that gap. A chatbot in a browser tab has no connection to your WordPress installation. It can write you a product description for your WooCommerce store, explain where a setting lives, and draft a policy page. But you’re still the one who publishes the page, updates 40 product descriptions, and clicks through to the setting three menus deep. The time you saved with the chatbot comes back as implementation time, which is why you’re still spending hours in the WordPress admin.

The fix: Go beyond generic chatbots to an AI agent that can reach your site. For example, a site-connected AI assistant like SiteGround’s AI Agent for WordPress can not only draft your product descriptions, but it can update them in bulk, use your store data to create and update the products themselves, adjust pricing, generate discount coupons, manage customer orders, and even pull a sales report for you. Our guide to using AI in WordPress beyond content creation covers what that looks like.

SiteGround AI Agent for WordPress chat interface with a prompt to update sale prices for all products in the Tennis category, with a WooCommerce product grid showing discounted tennis equipment in the background

Mistake 2. Installing AI plugins reactively, one problem at a time

WordPress AI plugins are growing roughly three times faster than the wider plugin economy, and installing them on impulse is one of the most common WordPress AI mistakes. It happens because of how these plugins are built: most do one job. For example, a translation plugin turns your pages into other languages, and an SEO plugin writes your page titles and meta descriptions.

Each is good at its own job, so when you need three of those things, you install three plugins, each with its own settings screen, its own subscription, and often its own AI account to create. Also, many AI plugins don’t include the AI itself: they connect to a service like ChatGPT or Gemini through an account you set up and pay for separately. Each install makes sense on the day you make it. Six months later, you’re paying for four tools and maintaining four interfaces, when one chosen with all four tasks in mind might have done.

The fix: Start from the job, not the plugin. Write down the two or three tasks that actually take up your week, then look at what you already have installed, because something on your site may already do part of it. Overlap is the check most people skip, and two plugins doing the same job compete rather than add up. If your list spans several different jobs, one tool that covers all of them costs you less time than four that each cover one. Our comparison of AI plugins and AI agents covers that choice.

Mistake 3. Stacking narrow plugins until the site is a patchwork

While we’re on the plugins topic, most WordPress security problems actually come from them. That isn’t because plugin developers are careless. It’s arithmetic: every plugin is code written by someone else, running inside your site, with permission to read and change what’s there. The more you install, the more chances one of them has a flaw.

WordPress AI plugins raise the stakes because of what they hold. Many store a key that lets them use an outside AI service and bills you for the usage, which makes them worth stealing in a way an ordinary plugin isn’t. Once a flaw becomes public, attackers typically start using it within five hours. And if you’re using WordPress 7.0 or above, your AI plugins share one set of AI credentials, which means a single compromised plugin can reach all of them, not just its own.

The fix: Fewer plugins is the fix for AI plugin fragmentation, and an audit is the fastest way there. Hand it to an AI assistant like SiteGround’s AI Agent for WordPress: it can list what’s installed, say what each one actually does rather than what its name suggests, flag anything that overlaps or hasn’t been updated in a long time, and remove the ones you agree to drop. Deleting a plugin you no longer use does more for your security than installing another that promises to protect you. Our guide to choosing AI plugins for WordPress covers what to look at.

Mistake 4. Leaving your AI API keys unprotected in WordPress

An API key is how one piece of software proves to another that it’s allowed to be there. Think of it as a password with your credit card attached: it identifies you to the AI service, and everything done with it gets billed to your account.

WordPress 7.0 added a Connectors screen where you paste that key in once, so any AI plugin on your site can use it. What isn’t obvious is where it goes: into your site’s database, as ordinary readable text. The screen hides it behind dots so nobody reads it over your shoulder, but that’s a curtain rather than a lock: the stored value is unchanged, and anything that can read your database can read the key. WordPress documented this when the feature shipped. It has since tightened how the key is displayed, but the encryption work is still open, so what’s in the database hasn’t changed.

Your database gets copied more often than you’d think: every backup, every staging copy, every time someone pulls the site down to work on it. The key travels with all of them. And unlike a stolen password, a stolen AI key locks nobody out and changes nothing you can see. Someone else simply starts spending on your account until the bill tells you.

The fix: Choose a setup where your host makes the connection for you, because a key you never paste in is a key nobody can copy out. If you do paste one in, treat it like a house key you’ve lent out: replace it whenever a copy of your site goes somewhere new, and delete any connection you’ve stopped using. And if you have someone technical to hand, ask them to keep the key in your site’s configuration file rather than the database, which is the route WordPress itself recommends. Our explainer on how AI works in WordPress 7.0 shows where these settings live.

Mistake 5. Not setting a limit on what AI can spend

AI billing costs in WordPress aren’t always a flat monthly fee. They bill by the amount of text going in and out, counted in units called tokens, where one token is roughly three-quarters of a word. So the cost moves with how much you ask for, and there’s no fixed number you can put in a budget.

If you’ve connected to an AI provider on WordPress 7.0 or above, WordPress itself doesn’t cap that for you. There’s no spending limit built in and no usage tracking either, so unless you set a limit yourself in your AI account, nothing stops the meter and nothing shows you it running. Two things push it up: a busy month of content can double or triple the bill, and some plugins send AI requests in the background while you work, checking your text or generating suggestions you never asked for.

The fix: Set the limit before you paste the key, and check it’s a limit that actually stops something. Providers differ here: OpenAI and Anthropic let you set a hard monthly cap that refuses requests once you reach it, while Google’s billing runs through Google Cloud, where the default budget is an alert that emails you and lets the spending carry on. Our comparison of ChatGPT, Claude, and Gemini covers how else the three differ.

Mistake 6. Publishing AI output on WordPress without review

Most people already know AI output on WordPress needs human review. In our 2026 report on AI in WordPress for small businesses, 41% of small business owners said they need several attempts before AI gives them something usable, and 22% said they don’t trust its accuracy. So the mistake isn’t that anyone believes AI is always right. It’s that knowing output is unreliable and actually checking it are two different things, and a page that looks finished tends to get published.

That’s what makes AI output hard to check: it rarely looks wrong. A made-up statistic reads exactly like a real one, and a product description can be fluent while describing a feature your product doesn’t have. There’s no equivalent of a spelling mistake to catch your eye, so anything published without a proper read has gone out on trust.

The fix: Make the AI check its own work. Paste the text back into the chat and ask it to separate what it knows from what it filled in, with a prompt like this one: “List every factual claim in the text above: numbers, dates, prices, product features, and names. For each one, tell me whether you are certain, unsure, or made it up. Do not rewrite anything.” What comes back is a short list to verify rather than a whole page to reread, and invented details tend to surface in the unsure column. It isn’t a guarantee, since a model can be wrong about its own confidence, so use it to narrow what you check rather than to replace checking. Our guide to writing ChatGPT prompts covers more habits that cut rework.

Mistake 7. Adding AI that creates more admin, not less

Some AI tools for WordPress take more admin to run than they save, and the setup is usually where that happens. For example, here’s what it currently takes to get AI working if you’re on WordPress 7.0 or above: open the Connectors screen, pick an AI provider, install that provider’s plugin, create an account on the provider’s website, find your way into its developer dashboard, generate an API key, come back to WordPress and paste it into the right field, then install a second plugin before you see any AI features you can actually use.

After that, you track spending in the provider’s billing dashboard, a third place to keep an eye on. That’s one job spread across WordPress, an AI company’s developer platform, and a separate billing system, creating more admin instead of removing it. And what many people get at the end of that setup is AI that writes text inside the editor, which is the part they were already doing in a chatbot.

The fix: Before setting anything up, count the accounts, screens, and bills involved. If a tool needs three systems to do one job, that’s admin you’ve taken on, not admin you’ve removed. The alternative is a tool that arrives already connected. For example, SiteGround’s AI Agent for WordPress is active on SiteGround-hosted sites from the start, with no provider account to create, no key to generate, and no separate bill to follow.

MistakeThe fix
Relying on a generic chatbot for WordPress workUse AI that connects to your site, so it makes the change instead of describing it
Installing AI plugins reactively, one problem at a timeWrite down the two or three tasks that eat your week, check what you already have, then pick one tool against the whole list
Stacking narrow plugins until the site is a patchworkAudit what’s installed and delete what you don’t use. A site-connected agent can list, flag overlaps, and remove
Leaving your AI API keys unprotectedAvoid handling a key at all where you can. Otherwise replace it whenever your site gets copied, and keep it in the config file rather than the database
Not setting a limit on what AI can spendSet a hard cap, or prepay credit so it can’t be exceeded. Use one key per plugin to see what each is spending
Publishing AI output without reviewHave the AI list its own factual claims, then check that short list instead of rereading the page
Adding AI that creates more admin, not lessCount the accounts, screens, and bills before you set anything up. Prefer tools that arrive connected

What these mistakes have in common

The AI mistakes small businesses make on WordPress look like seven unrelated problems, but they share a shape. In each one, the AI does exactly what it was built to do, and what’s missing sits around it: a tool that can reach the thing you want changed, a plan before the first plugin goes in, an audit before the fourth, a limit on the key, a ceiling on the bill, and a second look before anything reaches a customer. None of that arrives with the tools, so it lands on whoever adopted them, which on most small business sites is one person who already has a business to run.

That’s also why none of it takes technical skill to fix. Work out what you want AI to do before you go looking at WordPress AI tools, keep the stack small enough to hold in your head, and put a limit and a check on anything that can spend your money or change what your customers see. How much of that you’re left doing depends on what you choose. For instance, a tool that connects to your site on its own, with no key to guard and no separate bill to watch, means most of this list never becomes your problem.

FAQs

What are the most common AI mistakes small businesses make on WordPress?

The most common AI mistakes small businesses make on WordPress are treating a generic chatbot as a site management tool, installing AI plugins reactively, stacking too many, leaving API keys unprotected, skipping spend limits, publishing without review, and adding AI that creates more admin than it removes.

Why is relying on a generic chatbot a WordPress AI mistake?

Relying on a generic chatbot is a WordPress AI mistake when the tool isn’t connected to your site. It can draft and advise, but it can’t publish, update products, or change settings, so you still do the implementation by hand.

What are the risks of stacking WordPress AI plugins?

The risks of stacking WordPress AI plugins are a larger security surface, conflicting code, and multiple subscriptions and keys to manage. Most reported WordPress vulnerabilities come from plugins rather than from WordPress itself, and every AI plugin you add increases the exposure.

Why can AI billing surprise WordPress site owners?

AI billing costs in WordPress can surprise site owners because providers charge by the amount of text processed and WordPress sets no spending limit by default. A plugin making frequent background requests, or a busy content month, can double or triple the bill before anyone notices.

Why should you review AI output before publishing on WordPress?

You should review AI output before publishing on WordPress because AI rarely looks wrong when it is wrong. In our survey, 41% said usable results take multiple attempts and 22% don’t trust AI accuracy, so anything published without a proper read has gone out on trust.

How can a small business use AI safely on a WordPress site?

A small business can improve WordPress AI safely by mapping its real workflow before installing anything, keeping the plugin stack small, avoiding or protecting API keys, setting spend limits, checking output before it goes live, and preferring site-connected tools that ask for confirmation.

Vibe coding MVPs for startups: Build faster with a small team

A digital graphic depicting AI-driven website development against a purple-to-blue gradient grid background. On the right, a man works on a laptop while a floating glassmorphism UI panel displays a real estate website mockup titled "NEW HOME" with navigation links for "PROPERTIES", "ABOUT", and "BOOK". On the left, a white prompt box displays the user command "An MVP to test my booking idea..." accompanied by floating AI status badges reading "Thinking...", "Generating code...", and "Version 1 created".

If you’re part of a startup, there has never been a better time to get a first version of your product in front of real people. You no longer need a technical co-founder or a budget for developers. You can build a vibe coding MVP instead: a first working version of your product, created by describing it to an AI tool in plain language rather than writing the code by hand. It exists to test one business assumption with real customers, so you find out whether the idea works before you spend more time on it.

All-in-one tools like Coderick AI have made it fast enough to go from an idea to working software in days, so building is no longer the part that holds you up. This frees you up to focus on everything around it: deciding what your MVP should test, keeping the first version small, reading what early users actually do, and knowing when to bring in a developer.

Key takeaways:

  • A vibe coding MVP is a working first version of your product, built by describing it to AI, and it exists to answer one business question rather than to launch your company.
  • Name the assumption that would sink your idea if it turned out to be wrong, then build only what puts that assumption in front of real customers.
  • Building the MVP is one job out of several, and deciding what to test, onboarding your first users, and reading the results all matter just as much.
  • Unlike AI builders that hand you a finished project and leave hosting, databases, and deployment for you to work out, Coderick AI includes all three, so your MVP can go live and reach real users the same day you build it.

What a vibe coding MVP is, and what it’s not

A vibe coding minimum viable product (MVP) is the smallest working version of your product that real customers can actually use, built by describing it to an AI tool instead of writing code or hiring a developer. What you get is a web app you can preview privately and publish at its own address, which is why you need an AI web app builder that takes you from idea to something testable in days.

Say you had a cool idea to build a SaaS MVP with AI that solved a real problem for a specific industry. Until a couple of years ago, this meant finding a budget for software development, a technical co-founder, or a year of learning to code, all of which required committing before you had any evidence that people wanted it. Vibe coding removed that step: you can now build the first version yourself, in days, and let real customers tell you whether the idea holds before you spend anything you would miss.

Prototype, MVP, and production product are three different things

These three get used interchangeably, and the confusion can be expensive, because each one answers a different question and takes a different amount of work to build.

  • A prototype is something you show your team or a few friends. It can be screens with nothing behind them. It tells you whether the idea makes sense on paper, and nothing more. It’s usually disposable.
  • A production product has to work for real clients, keep running when something breaks, handle many people arriving at once, and protect other people’s data. It is built to last, and it costs accordingly.
  • An MVP sits between the two. It’s more than a prototype, because a stranger has to be able to use it without you there: someone works through it on their own, with their own data, to do something they genuinely needed to do, and that is how you test your idea. But unlike a prototype, it’s not disposable: if your idea holds up, this is what you keep building on to get to the production product.
What it isWho uses itWhat it gives you
PrototypeYou and your teamA sense of whether the idea hangs together. It can be clickable screens with nothing behind them.
MVPReal customers, doing real workEvidence. This is the only one of the three that can tell you whether people want the thing.
Production productEveryone, at scaleA business you can run, built to handle load, failure, and other people’s data.

What the MVP is for: answering one question, not launching a company

An MVP is a research instrument that happens to look like a product. The question it answers is about user behavior: will people switch from the way they do this now, will they trust software to do the job instead of doing it themselves, will they come back a second time without being reminded, will they pay anything at all.

What makes a question worth building for is that a “no” would change your plans. If you would carry on the same way whatever the answer, you are not really asking anything. And once you have the question, it settles the build: only the features a user has to touch on the way to answering it earn a place. Everything else, however obvious it seems, is a decision you are making before you have the information to make it.

Start with the risky assumption, not the feature list

Before you decide what to build, decide what has to be true for the business to work. Every startup rests on a handful of assumptions, and one of them is load-bearing: if it turns out to be false, nothing else you build matters. That is the one the MVP exists to test.

Naming the one assumption the MVP has to test

Write down everything that has to be true for your idea to work, then look for the one that is both unproven and fatal. Say you want to build a tool that automatically sorts bank transactions into expense categories for freelance bookkeepers. Your idea depends on at least three things:

  1. Bookkeepers find manual sorting tedious. Almost certainly true, and you can confirm it in a few conversations without building anything.
  2. They would pay a monthly fee for software that helps. Worth testing, but it only matters if the next one is true.
  3. They would trust automatic sorting enough to work from it, instead of redoing it by hand. This is the risky one. If bookkeepers check every line anyway, your tool saves nobody any time and the business does not work.

The third assumption decides whether you have a product, and you cannot settle it by asking people. Everyone says they would trust it, right up until they see their own client’s messy data come back with mistakes in it. Assumptions like that can only be tested by letting people use something real, which is exactly what an MVP is for.

Deciding in advance what user behavior counts as evidence

Once you know what you are testing, write down what result would convince you, and do it before anyone touches the product. For the bookkeeping example, that might be: “I will believe bookkeepers trust this if at least half of the people who try it upload a second bank statement within a week, without me asking them to.”

Early results are almost always mixed, and after two weeks of building you will be strongly inclined to read them as good news. A number you committed to in advance is much harder to argue with than a feeling you form afterwards.

How to scope a vibe coding MVP

Scope your MVP to the shortest path a user can take to reach the moment that tests your assumption. Anything sitting off that path can wait. The easiest way to hold that line is to keep two separate lists instead of one.

Build scope and launch scope are two different lists

Build scope is what tests your assumption. Launch scope is the minimum that has to exist before you can responsibly let real people in. They serve different purposes, and merging them into a single to-do list is one of the most common reasons a small MVP can turn into a three-month project. Here’s how to tell the difference between the two:

Build scope: the path to your answerLaunch scope: what every real user needs
The first step a user takes toward the thing they came forA way to sign in
The one thing your product promises to doA privacy notice saying what you do with their data
Whatever lets them judge whether it workedA way to reach a human when something breaks
The point where they get the result and use itA way to delete their data on request

The launch scope is short, but it is not optional. If you are handling other people’s financial records, a privacy notice and a way to delete data are not polish you add later. In most countries, they are a legal requirement the moment a real customer uses your product.

What to leave out on purpose

The list of things to skip is longer than the list of things to build, and every item on it is something a reasonable person would argue for:

  • Accounts for a second type of user. Team access, client logins, admin roles. Build for one person doing one job, and add the rest when you know the job is worth doing.
  • Settings and customization. Every option you offer is a guess about what people will want to change, made before you have watched anyone use the product.
  • Integrations with other software. Connecting to the accounting tool everyone uses sounds essential and typically takes weeks. It also tests nothing, because nobody refuses a product they like over a missing integration at this stage.
  • Billing systems. You can take payment with an invoice or a payment link long before you build subscriptions, and doing it by hand teaches you more about how people buy.

How small startup teams divide the vibe coding work

Building an MVP for non-technical founders roughly splits into six tasks that can be completed by a startup team of two or three people, and only one of these tasks involves the actual vibe coding. Someone has to stay close to customers, someone has to decide what the MVP is testing and what result would count, someone runs the build, the whole team has to try the thing, someone onboards the first users by hand, and someone brings in technical help when the risk calls for it.

ResponsibilityWho owns it in a small team
Problem and customer evidenceFounder or whoever talks to customers most
MVP scope and success signalFounder or product owner
The vibe coding buildFounder, operator, or the most product-minded generalist
Workflow and usability testingThe whole team, on the real product
Early-user onboardingFounder or growth lead, by hand
Technical escalationAn experienced reviewer or developer, when risk requires it

If you are on your own, you still own all six. The value of the split is that it stops the build from swallowing the rest, which is the standard failure: the founder disappears into the tool for two weeks, comes back with something impressive, and has not spoken to a customer since. Do the six jobs in sequence, not as one blur, and note that only one of them requires the AI at all.

How to build an MVP with AI using Coderick AI

The build is the most straightforward part of the vibe coding MVP process. You describe the product in plain language, look at what the AI produces, and refine it over a few rounds until it does what you need. (Our guide to the vibe coding workflow walks through that loop in more detail.)

What varies between one AI MVP builder and another is mostly what happens after the MVP gets built. Many tools generate a project and then leave you to work out hosting, databases, and deployment on your own (see our vibe coding glossary to learn all about these), which is where founders building an MVP without coding usually get stuck. With Coderick AI, those pieces are handled inside the platform:

  • Hosting is included and optimized: You build safely on a private preview domain, and there is no separate hosting account to set up or pay for.
  • The database and user accounts come with it: If your MVP needs to store information or let people sign in, it works without you configuring anything, though you also get full access to a database admin dashboard to manage your data directly if needed
  • Publishing is one step: When the product is ready on your private staging environment, you simply click Publish. This automatically copies the current state of your app to your live, public web address (and paid plans fully support custom domains).

Start with one prompt

Your first AI MVP prompt should describe your build scope and say explicitly what to leave out. That second part matters more than people expect: asked simply for “a tool for bookkeepers,” an AI builder will helpfully add an admin dashboard and a settings page you never wanted and now have to maintain. It’s highly recommended to provide clear business requirements and add functionalities step-by-step, rather than dumping 5-6 features into a single prompt. You can even upload an image of a layout you like and ask the AI to use it as design inspiration.

A simple prompt you can start with:

“Build a web app for [Target Audience] that allows them to [Core Functionality]. Do not build [Features to Exclude].”

Using this prompt for the bookkeeping example, here’s how it looks:

“Build a web app for freelance bookkeepers that allows them to upload a CSV bank statement and automatically sort transactions into expense categories. Do not build an admin panel or user settings.”

After submitting this prompt, Coderick AI will generate a functional web application tailored for freelance bookkeepers to upload and categorize CSV bank statements, excluding an admin dashboard or user settings as instructed. To support these file uploads and data sorting features, the platform will automatically provision a database under the hood. You will immediately see the results in a split-screen interface, which features a text summary of the AI’s implementation plan on the left and a live, interactive preview of your new application hosted on a private staging domain on the right:

A screenshot of the SiteGround Coderick AI web development interface showing a split view with an AI assistant on the left and a live app preview on the right. The left panel details design notes and features for a financial app, alongside a prompt history tab and a text input asking "What do we build next?" The right panel displays the preview of a web application titled "Ledgerly — Statement categorizer for freelance bookkeepers," featuring the main headline "Turn a raw bank statement into a sorted ledger" and a dashed upload box reading "Drop your bank statement here."

Then iterate

It’s possible that the first AI-built MVP version will get something wrong, and your job is to describe the difference between what you see and what you meant, then run it again. Two or three rounds are normal for a narrowly scoped MVP. For quick visual tweaks, you can use Coderick AI’s “Visual Edit” mode to click directly on an element and apply AI-powered changes in place, saving you from writing lengthy chat prompts.

Remember to treat the AI like a real developer: back-and-forth testing and debugging are natural parts of the software lifecycle. If you find yourself on the twelfth round, it usually means the scope grew while you were working, not that the tool is failing you.

For more prompts you can copy and adapt, see our guide to vibe coding prompts.

How to test an AI-built MVP with early users

Testing an MVP means picking a small group of people who have the problem, getting them to do a real task with it, and watching what happens. Before you start, decide what the finish line is. Every MVP has one moment where the user gets the thing they came for. In the case of the bookkeeping tool, it is not signing up or uploading a file, it is exporting a corrected list they then actually use with a client. Everything before that moment is setup, and everything you measure is measured against it.

Ten or 15 people is enough, as long as they are the right ten or 15. People who respond because they know you will be kind, and kindness is not data. Go to wherever your users already are and recruit individually.

With that group, three things are worth measuring, and each one answers a different question.

  • Do they get there at all? Count how many reach that finish line the first time. If eight of 15 sign up and only three export a file, the problem is in the middle, and you can go and find out exactly where they stopped.
  • Do they come back and do it again? For an MVP, coming back means repeating the core action, not logging in. A second bank statement uploaded a week later means the first one was worth their trouble. One to two weeks is a long enough window to tell, and this is usually the strongest signal you can get this early.
  • Will they hand over money? This is where most founders fool themselves. Asking “would you pay for this?” tests nothing, because saying yes is free. Testing it means asking for the payment itself, before the product is really ready: an early-access price for the next three months, a paid pilot, a deposit, or, for business customers, a written commitment to buy. The honest version of this bar is a handful of paying customers who are not friends of yours.

Which of the three matters most depends on what you decided to test. If your risky assumption is that people will trust the output, repeat use is your answer and payment can wait. If the assumption is that anyone will pay for this at all, then you need to ask for money in week one, even if the product is held together with tape.

What early behavior tells you, and what it does not

Some signals are worth acting on. Others feel good but mean nothing.

This is evidenceThis is not
They come back and use it again without a nudgeThey signed up
They pay, even a small amountThey said they would definitely pay
They complete the task without asking you for helpThey said it looks great
They ask you for the next thingTraffic, impressions, and waitlist numbers
They complain about something specificNobody complained

The most useful thing to watch is where people stop. If four of your first ten users upload a file and never look at the results, you have learned something precise and slightly painful, which is exactly the sort of thing an MVP exists to produce. An MVP that produces a clear “no” has done its job as well as one that produces a “yes,” and it has done it for a fraction of what finding out later would have cost.

When you spot these drop-offs or receive specific complaints, you don’t need to start over. You can simply jump back into the Coderick AI chat, describe the necessary workflow changes to the AI, and iterate on your existing app to quickly deploy a better version.

A realistic timeline. Deciding what you are testing and what would count as evidence takes an afternoon, not a week, and it is the step most worth not rushing. The build is usually two to five days, including the rounds where you fix what the AI got wrong. Recruiting your first 15 users often takes longer than building, so start on it while you build. Then give the test one to two weeks, which is long enough to see whether anyone comes back. From decision to answer, three to four weeks is normal.

When to bring in a developer for a vibe-coded MVP

Most of the advice you will find on this question is published by companies that sell development services. Their answer to “when do you need a developer” is structurally likely to be “now.” However, a vibe-coded MVP can carry real users for longer than most people admit. What it should not do is carry them past a specific set of lines:

  • Complex business and application logic: AI builders are excellent at standard features, but if your app needs to follow highly specific, multi-step rules or complicated math, the AI can get confused. If you find the AI constantly breaking one feature while trying to fix another, a developer can step in to write those specific rules.
  • Connecting to outside services (integrations): While many AI tools have built-in connections for popular services (for example, Coderick AI can automatically connect to Stripe to take payments), asking the AI to connect to something like a custom stock market feed is often restricted. A developer is needed to securely set up those custom bridges.
  • Outgrowing the built-in database: Some vibe coding tools automatically set up a simple storage system in the background to hold your MVP’s information, like user passwords or a list of items for sale. Coderick AI, for example, gives you a beginner-friendly database that requires zero manual setup. However, if your MVP evolves into a massively popular product and requires a highly customized, heavy-duty data system to handle millions of records, you will eventually need a developer to upgrade it.
  • Highly custom designs and animations: AI MVP builders are fantastic for generating clean, modern, and standard website layouts. But if your brand requires deeply interactive visual effects, complex 3D animations, or highly specific custom designs that break standard grid layouts, the AI will likely struggle to get it exactly right. Human developers and designers are still needed for intricate visual work.

Build the smallest vibe coding MVP that can teach you something

Vibe coding has not removed the discipline that startups have always needed. It has removed enough of the build friction that a small team can get to a real answer sooner, which is a different and better thing than shipping sooner. The founders who get value out of vibe coding are the ones who decided what they were testing before they decided what they were building.

So start from the question. Name the assumption that would sink you if it were wrong, work out what behavior would settle it, build only the path that gets someone to that moment, and put it in front of 15 real people. Whether the answer is yes or no, you will have it in weeks and will have spent almost nothing to get it. That is the case for a vibe coding MVP, and it holds whether you build a SaaS MVP with AI, an internal tool, or something nobody has a name for yet.

[96]

FAQs

What is a vibe coding MVP?

A vibe coding MVP is a first working version of a product built by describing it to an AI tool in natural language rather than writing the code by hand. Its job is to test one business assumption with real users, not to be the finished product.

What is the difference between a prototype and an MVP?

The difference between a prototype and an MVP is who it is for. A prototype demonstrates an idea to you and your team, and can be screens with nothing behind them. An MVP is used by real customers doing real tasks, which is the only way it can produce evidence.

Can a non-technical founder build an MVP with AI?

Yes. A non-technical founder can build an MVP with AI by describing the product in plain language and refining the result over several rounds. The hard parts stay human: choosing what to test, deciding what counts as evidence, and reading what the result means.

What should a startup MVP include?

A startup MVP should include only the path a user takes to reach the moment that tests your assumption, plus whatever is legally or practically required before real people use it, such as sign-in, a privacy notice, and a way to reach you. Features that do not affect the test belong in later versions, not launch scope.

How should I test an AI-built MVP?

You should test an AI-built MVP by deciding what user behavior would count as evidence before anyone touches it, then watching whether that behavior happens. Sign-ups are not evidence. Repeat use and payment usually are, and where people stop tells you more than where they finish.

When should a startup bring in a developer?

A startup should bring in a developer when specific triggers appear: you are handling payments or personal data, a second paying cohort has arrived, a compliance obligation applies, the data model would be expensive to change, or something breaks that you cannot diagnose.

Can Coderick AI help a startup build an MVP?

Yes. Coderick AI can help a startup build an MVP by turning a written description of the product into a working first version that the team can refine, test with early users, and host without setting up infrastructure separately, since hosting is included in every paid plan.

Claude Opus 5 for small businesses: Costs, use cases, and whether it’s worth it for you

A digital graphic in warm terracotta tones featuring a smiling man working on a laptop at a desk. Floating translucent glassmorphism UI elements highlight AI model updates, including a mouse cursor selecting "Opus 5.0" from a dropdown list and a bar chart widget displaying performance progression across model versions labeled 4.0, 4.6, 4.8, and 5.0 next to an asterisk logo icon.

Claude Opus 5 is Anthropic’s most recent Opus-tier model for complex work: long documents, detailed research, multi-step projects, and coding. It costs $5 per million input tokens and $25 per million output tokens, exactly what Opus 4.8 cost. It can hold 1 million tokens in a single conversation, and it sits below Claude Fable 5, Anthropic’s most powerful model, at half of its price.

Anthropic released Claude Opus 5 on July 24, 2026, and most of the coverage since has been benchmark scores and per-token rates. But if you run a small business rather than an engineering team, is it worth it for your daily workflow, and is it going to cost you more? This guide will tackle these questions, including how you can compare Claude Opus 5 to other leading models like Google’s Gemini 3.1 Pro and OpenAI’s ChatGPT 5.6 in SiteGround AI Studio, all under a single subscription.

Key takeaways:

  • Claude Opus 5 costs exactly what the model it replaces did, $5 per million input tokens and $25 per million output, but it now thinks before it answers by default, and that thinking is billed as output, so the same job can still come out more expensive.
  • Opus 5 earns its place on long, layered work: reading a full report and telling you what matters, cleaning up messy source material, or running a project through several stages without you restating the goal.
  • Sonnet 5 still handles routine writing to the same standard for less, so the skill worth having is reaching for Opus 5 only on the long, layered jobs where you can see the difference.
  • You can compare Opus 5 with Google’s Gemini 3.1 Pro, OpenAI’s GPT 5.6, and other leading models directly within SiteGround AI Studio on a single subscription, which is the best way to find out which model actually suits your work.

Claude Opus 5 vs Opus 4.8: what actually changed

Three things changed in Claude Opus 5 vs Opus 4.8, and the price was not one of them.

  1. It thinks before it answers. Opus 5 now works through a problem before responding, instead of doing that only when you ask it to.
  2. It holds far more at once. In paid Claude chat, Opus 5 expands the context window from Opus 4.8’s 500,000 to 1 million tokens (the small chunks of text that AI use is measured and billed in, each one roughly three-quarters of a word), so it can work across a large set of documents without you breaking them up.
  3. It knows more recent things. Its knowledge runs to May 2026, the most recent of any Claude model. That date is the knowledge cutoff, the point where the information it was trained on stops.

The rates stayed exactly where Opus 4.8 left them, which is the actual story of this release. Anthropic held the price of its mid-tier model steady while closing most of the gap to its flagship, so work that was only worth running on a cheaper model last month may be worth running on this one now.

Claude Opus 5 pricing: the same rates, but different real-world costs

Before the numbers, it helps to know which of them apply to you, because there are three quite different ways to pay for Claude.

  • If you use the Claude chat app, you pay a flat monthly fee. Free gives you Sonnet 5 with daily limits. Pro is $20 a month (about $17 if you pay yearly) and gives you the full model menu including Opus 5, though Sonnet 5 stays the default until you change it. Max is $100 or $200 a month and makes Opus 5 the default. Choosing Opus 5 instead of Sonnet 5 on any of these plans costs you nothing extra. What it costs is headroom: usage limits run on rolling five-hour sessions with weekly caps on top, and a heavier model works through that allowance faster. Run out, and you can switch on usage credits, which bill at the per-token rates below.
  • If you use a bundled AI workspace, you pay a flat plan fee and your usage is measured as an allowance. For example, SiteGround AI Studio works this way, with a monthly token allowance rather than a per-message limit. Here your model choice does show up, because heavier work draws down the allowance faster.
  • If you use the API, you pay per token, the way you pay for electricity. You would only be here if you or someone you hired built something that talks to Claude directly, like a chatbot answering questions on your website or a tool that reads your emails. At the end of the month, you get a bill based on how much text went in and out.

The table below is that third route, the API rate card. You pay one rate for what you send the model, called the input, and a higher rate for what it sends back, the output, and as a rough guide 1,000 tokens is about 750 words. Even if you never touch the API, these rates are the way to see what different kinds of work weigh.

ModelInput (per million tokens)Output (per million tokens)
Claude Haiku 4.5$1$5
Claude Sonnet 5$2 (rising to $3 in September)$10 (rising to $15 in September)
Claude Opus 4.8$5$25
Claude Opus 5$5$25
Claude Fable 5$10$50

Opus 5 matches Opus 4.8 to the cent and undercuts Fable 5 by half. That is a real saving on paper, but it’s not a guarantee that your next invoice will look the same, for a reason most launch coverage files under specifications rather than costs.

Thinking is on by default now, and that is what moves your Claude Opus 5 bill

Opus 5 reasons through a request before it responds, and it now does this by default rather than only when you switch it on. That working out happens in the background, but it’s made of text like everything else, so it’s counted in tokens (these are usually called thinking tokens) and billed at the higher output rate. The same request that cost you a certain amount on Opus 4.8 can therefore cost more on Opus 5 at identical published prices, because the model is doing more work before it speaks.

This is not a hidden fee, it’s the reason the answers are better. It’s also the one thing to understand before you switch, because it explains an outcome that otherwise makes no sense: a model priced identically to its predecessor producing a larger bill.

What the Claude Opus 5 context window means in practice

A context window is how much text a model can hold in mind at one time, counting everything you have sent it and everything it has said back. The Claude Opus 5 context window is 1 million tokens, roughly 750,000 words, or a stack of documents a couple of thousand pages deep. It is both the default and the maximum, with no smaller version to choose from. You can hand it a whole contract set, a year of customer emails, or every page on your website and ask questions across all of it without breaking the material up.

The catch is that a big window is an option, not an instruction. Everything you put into it is input you pay for, so pasting your entire document library into every request is how a task that should cost pennies starts costing real money.

How much does Claude Opus 5 cost a small business?

Less than you would expect for ordinary writing work, and more than you would expect once you start feeding it long documents. The useful way to think about Claude Opus 5 cost is per month of real work, not per million tokens. The examples below are estimates at published API rates, worked out using the rule that 1,000 tokens is about 750 words, and assuming the model’s thinking roughly doubles the output you pay for.

Read them two ways. If you pay per token, this is roughly your bill. If you use Claude through a flat subscription, this is not your bill, since you already paid your $20, but it’s a fair picture of how much of your monthly allowance a given workload eats. Either way, the point is the same: it shows you which of your work is light and which is heavy.

Claude Opus 5 cost examples for content, products, and email

A month of…What that involvesEstimated cost
Blog contentFour posts of about 1,200 words, each written from a brief plus some reference material, with a few rounds of editsAbout $1
A product catalog rewriteTwo hundred product descriptions of about 150 words each, generated from your existing specificationsAbout $2.50
Social and email copyTwenty social posts and four email campaignsUnder $1

Run all three in the same month, and you are still under $5. But if you ask Opus 5 to read a 300-page report (about 200,000 tokens), that single request will cost a dollar in input before it writes a word. Do that twenty times in a month while you dig through a document set, and you have spent $20, which is more than everything in the table above combined, several times over.

So writing is cheap, and reading is what costs you. On a per-token bill, that’s money. On a subscription, it’s the reason you can spend all morning writing and hit no limits, then upload three long PDFs after lunch and find yourself capped. Either way, the number to watch is how much you are putting in, not how much comes back.

What changes the real cost of Claude Opus 5: caching, batching, and thinking tokens

Three things sit between the published rate and what you actually pay.

  • Thinking tokens push it up. As mentioned above, the model’s working out is billed at the output rate, so a request costs more than the visible answer suggests.
  • Prompt caching pulls it down, by up to 90%. This is a discount on material you send again and again, such as a style guide or a product list. On Opus 5, anything over 512 tokens qualifies, so even a short brief counts.
  • Batch processing halves both rates. The trade is speed: you send work off to be answered within about a day rather than straight away.

If you reach Claude through a subscription or a bundled workspace rather than the API, you will never touch these settings. They are still worth knowing about, because they are why a monthly token allowance stretches further than the raw arithmetic suggests.

Pro tip: The simplest way to keep your costs down has nothing to do with which model you pick. It is to stop re-sending the same background. If you paste your brand guidelines, product list, or tone-of-voice rules into every new chat, you are paying for those words every single time, in money if you are billed per token and in usage allowance if you are not. Keep them somewhere the model can refer back to, in a saved project or a document you attach once, and you stop buying the same context over and over.

What is Claude Opus 5 best for?

Claude Opus 5 is best for work that is long, layered, or expensive to get wrong. The Claude Opus 5 benchmarks worth paying attention to are the ones about sustained, multi-step tasks, because that is where the gap over Opus 4.8 is widest.

Benchmarks are standardized tests that model makers run to compare one model against another. On one of them, FrontierBench v0.1, which measures how well a model handles long jobs made of many steps, Opus 5 scored 43.3% against 18.7% for Opus 4.8. Those are Anthropic’s own evaluations on tasks it chose, so treat them as a direction rather than a promise, but the direction is this: the further a job runs, the more the difference shows.

Long documents and multi-step work

Translated into work you actually have, that means jobs like these:

  • Reading something long and telling you what matters. A research report, a set of contracts, a competitor’s whole website: hand over the lot and ask what you should take from it, and it can work across every page rather than the first few.
  • Making sense of a pile of feedback. Hand it a year of reviews, survey responses, or support emails and ask what customers keep complaining about, and it works across the whole set rather than a sample.
  • Cleaning up messy source material. Turning three inconsistent supplier spreadsheets into one usable catalog is the kind of long, fiddly job where cheaper models start well and drift.
  • Projects with several stages. Auditing your existing content, deciding what to keep, and building a plan from it, without you restating the goal at every step.
  • Anything involving code. Building, reviewing, or debugging something on your site or in a small internal tool. Debugging means finding and fixing the errors that stop code working, and it is a job where the model has to hold the whole picture to be any use.

We tested it with a long document: we uploaded SiteGround’s 2026 report on AI in WordPress for small businesses in SiteGround AI Studio (where you can pick the leading models from providers such as Anthropic, OpenAI and Google under one subscription), we picked Opus 5 from the model list, and asked this:

“This is SiteGround’s 2026 report on how small businesses use AI in WordPress. I run a small business with a WordPress site and about five hours a week to spend on it. Read the whole thing and tell me the three findings that matter most for someone in my position, what each one actually means in practice, and which one I should act on first.”

A screenshot of the SiteGround AI Studio interface centered around the prompt "How can I help you today?" Inside a main query box, an attached PDF document titled "ai-in-wordpress-2..." is accompanied by a prompt asking for an analysis of SiteGround's 2026 report on how small businesses use AI in WordPress. An open model selection dropdown highlights "Claude Opus 5" under an "ADVANCED THINKING" section, alongside additional options including "Gemini 3.1 Pro," "Gemini 2.5 Pro," and "GPT 5.6 Sol." The left sidebar displays navigation links for New Chat, Agents, Prompts, Projects, Files, and History.

Opus 5 pulled figures from across the whole document rather than the opening pages, and built them into a single argument, at one point quoting a line from one of SiteGround’s product managers buried in section four and calling it the most useful sentence in the report. Asked which finding to act on first, it picked one, laid out a two-week sequence, and explained why it had not chosen the more obvious alternative.

A screenshot of the SiteGround AI Studio web interface displaying an AI-generated advice response titled "What to act on first." The response details a four-step implementation plan based on a report finding: auditing workflows for 30 minutes in week one, connecting a single site-integrated AI tool rather than multiple plugins, targeting the largest backlog item first, and keeping approval oversight on customer-facing content. At the bottom sits a text input box with the placeholder "Ask anything, or use @ for Agents and Prompts" and a model selector set to "Claude Opus 5," framed by the left-hand navigation sidebar.

Where a cheaper model does the same job

Plenty of the work you do every day does not require Claude Opus 5. Short marketing copy, routine customer replies, summarizing a meeting note, tagging and sorting, first drafts of the kind of thing you write every week: Sonnet 5 finishes all of that to a standard you will not be able to fault. If you cannot tell which model wrote it, you spent more than you needed to, whether that was money on a per-token bill or the session allowance you have left for the rest of the day. Reserve Opus 5 for the jobs where you can tell.

Claude Opus 5 vs Sonnet 5 vs Fable 5: which one fits your business?

Claude is a family rather than a single product, and the practical skill is matching the tier to the task. Here is where each one earns its place.

If you need to…Use this model
Sort, tag, or classify things in bulkHaiku 4.5
Draft blog posts, emails, and social copySonnet 5
Write straightforward product descriptionsSonnet 5
Analyze long documents or a year of customer feedbackOpus 5
Run a project with several stages, or work with codeOpus 5
Hand over a large job and let it run start to finishFable 5

On Claude Opus 5 vs Sonnet 5, the answer for most small businesses is that Sonnet 5 stays your daily driver and Opus 5 is what you switch to when the work gets hard. Sonnet 5 costs $2 and $10 per million tokens right now, rising to $3 and $15 in September, against Opus 5’s $5 and $25. If you are on the chat app, that gap is not money, since both models are included in the same subscription, and it shows up instead as how quickly you burn through your usage limits. Either way, across everyday writing, you will not see a difference in the output that justifies reaching for the heavier model.

On Claude Opus 5 vs Fable 5, the picture is more interesting than the positioning suggests. Anthropic places Fable 5 above Opus 5 in maximum capability and charges twice as much for it, $10 and $50, yet on several of its own published tests, including FrontierBench, Opus 5 scored higher. For small business work, the price gap is easier to feel than the capability gap. Fable 5 makes sense when you want to hand over a genuinely large job and leave it running unsupervised; short of that, Opus 5 is the sensible ceiling.

And if the question you are really asking is which company’s AI to use rather than which Claude tier, our guide to ChatGPT vs Claude vs Gemini covers that comparison.

Should you upgrade to Claude Opus 5?

  • If you mostly write short marketing copy: Sonnet 5 handles this, and paying Opus rates for a social caption is spending with nothing to show for it.
  • If you work with long documents, research, or analysis: Yes, and this is the release that makes it affordable. Work you were breaking into chunks to keep costs down can now run in one pass.
  • If you build or look after a website or an app: Yes. Coding and debugging are where the gains over Opus 4.8 are clearest, and holding a whole project in context is the difference between help and noise.
  • If you are paying for several AI subscriptions: Then Opus 5 is not really your question. Consolidating what you already pay for is, and it will save you more than any model choice.

The bottom line: is Claude Opus 5 worth it for your business?

For most small businesses, the sensible setup after this release is the same shape as before, with better economics: a cheaper model for the daily grind, and Claude Opus 5 for work that is long, messy, or consequential. What changed is that reaching for the better model no longer costs a premium, so whether Claude Opus 5 is worth it depends less on the model than on what you point it at.

And don’t take anyone’s word for it, including ours. The most useful Claude Opus 5 review is the one you run yourself. Take one real job you already do, run it on the model you use now and on Opus 5, and compare the finished result and what each run cost. Two tasks in, you will know which of your work belongs on which model, which beats any benchmark chart.

Claude Opus 5 is available in SiteGround AI Studio, where you can compare it to other leading models like Google’s Gemini and OpenAI’s ChatGPT, all under a single subscription. Instead of juggling multiple paid accounts for different providers, AI Studio gives you access to all these major models in one intuitive workspace. When you open a new chat, you can easily switch to Claude Opus 5—or any other available model—using a simple dropdown menu right in the interface. This makes it incredibly easy to run your own real-world comparison: just type your prompt, test it on your usual model, and then select Opus 5 from the dropdown to instantly compare the results.

[97]

FAQs

How much does Claude Opus 5 cost?

What Claude Opus 5 costs depends on how you reach it. Through the Claude chat app it costs nothing beyond your subscription, which is $20 a month on Pro or $100 to $200 on Max, and Opus 5 is included on both. Through the API you pay per token, at $5 per million input tokens and $25 per million output, the same rates as Opus 4.8, which works out to a few dollars a month for typical small-business content work.

Is Claude Opus 5 better than Claude Fable 5?

Claude Opus 5 is the better-value choice for most small-business work, while Anthropic positions Claude Fable 5 as the higher-capability model for the largest autonomous jobs. Claude Opus 5 scored higher than Claude Fable 5 on several of Anthropic’s published tests, including FrontierBench, and costs half as much. Claude Fable 5 remains the stronger choice for very large projects that need to run unsupervised from start to finish.

What changed between Claude Opus 5 and Opus 4.8?

Pricing did not change between Claude Opus 5 and Opus 4.8. What changed is that Opus 5 thinks through a request before answering by default, it can hold 1 million tokens of text at once as both the default and the maximum, it can write up to 128,000 tokens in one reply (around 96,000 words), and its knowledge now runs to May 2026.

Do I need a paid Anthropic plan to use Claude Opus 5?

You do need a paid plan to reach Claude Opus 5 through Anthropic’s own app, since the free tier runs Sonnet 5, but a paid Anthropic subscription is not the only route. Opus 5 is included on Claude Pro and Max, and you can also reach Claude models through a bundled workspace such as SiteGround AI Studio, which carries Claude alongside ChatGPT and Gemini on one subscription.

What is the Claude Opus 5 context window?

The Claude Opus 5 context window is 1 million tokens, roughly 750,000 words, and it is both the default and the maximum with no smaller version available. Long requests are billed at the same per-token rate as short ones, so there is no surcharge for using it, but everything you put in it is input you pay for.

Is Claude Opus 5 worth it for a small business?

Claude Opus 5 is worth it for a small business doing long documents, research, analysis, or anything involving code, where it now costs no more than the model it replaced. For short marketing copy and routine replies, a cheaper model such as Sonnet 5 usually produces the same result for less.

Which Claude model should a small business use?

Most small businesses should use Claude Sonnet 5 as their everyday model and switch to Claude Opus 5 for long, complex, or multi-step work. Claude Haiku 4.5 is the better fit for high-volume sorting and tagging, while Claude Fable 5 is best reserved for large jobs that need to run on their own.

How to use AI in WordPress beyond content creation with site-connected AI

A digital graphic illustrating AI image management for WordPress against a deep blue gradient background. In the center, a translucent glassmorphism UI modal displays a media library grid with six photos—a dew-covered leaf, a spiral staircase, a golden retriever in a field, an alleyway, a coffee desk setup, and a sunset—with several selected via blue checkmarks. In the lower foreground, a white AI prompt box shows the user command "Add alt text to all images ..." alongside action buttons, surrounded by floating dark UI toolbars and a top badge labeled "WordPress Agent."

According to our 2026 report on AI in WordPress for small businesses, most small business owners now use AI every day. However, almost all of them use it the same way: a generic chatbot like ChatGPT for research and content creation. This leaves the vast majority of AI’s real potential standing at the front door, while you are left inside still doing all the heavy lifting of WordPress management.

Learning how to use AI in WordPress beyond content creation means using site-connected AI that can work with your WordPress data and complete real tasks, like publishing posts, updating products, and running maintenance, instead of only advising you or handing you text to paste. This guide shows what that looks like and how a specialized, site-connected assistant like the AI Agent for WordPress turns AI into something genuinely useful for your WordPress site and your business.

Key takeaways:

  • Most small business owners running their WordPress sites already use AI daily, but mainly through a general chatbot like ChatGPT, and mostly for research and content creation.
  • A general chatbot can advise and draft, but it cannot act on your site, so you are still left doing the hard WordPress work by hand.
  • Site-connected AI completes approved tasks inside WordPress, from publishing and SEO to WooCommerce, maintenance, and comments, on your instruction.
  • Learning how to use AI in WordPress beyond content creation is the shift from AI that suggests to AI that does, and it is where the real time savings live.

How do small businesses use AI in WordPress today?

Most small business owners use AI every day, but almost entirely through general-purpose tools like ChatGPT rather than specialized WordPress AI tools. Our AI in WordPress report, which included a survey of more than 7,000 small business owners conducted at the end of last year, found that 53.9% use AI daily and another 24.1% use it several times a week.

However, this usage is overwhelmingly confined to generic chatbots: you open a separate tab, type a prompt, and get text back. That format is incredibly easy to try, which explains why adoption skyrocketed so fast in a single year. Compared to 2024, ChatGPT usage rose over 21 points, and Google Gemini jumped nearly 25 points, with every major tool seeing double-digit growth.

AI toolShare of owners in 2025Change since 2024
ChatGPT67.1%+21.4 pts
Google Gemini36.9%+24.5 pts
Microsoft Copilot18.1%+9.3 pts
Claude16.7%+9.3 pts
Perplexity12.1%+10.9 pts

And because a standard chatbot works exclusively in words, the tasks it wins are the ones that begin and end in words: researching a topic, drafting a post, or rewriting a paragraph. You just paste the result somewhere or throw it away. As a result, these became the natural first jobs to hand over to AI, and they still dominate the workflow by a massive margin.

What small business owners use AI forShare of small business owners
Research and data gathering66.5%
Content creation and editing65.7%
Image creation and editing39.7%
Code writing35.1%
Data analysis34.2%
Automating repetitive tasks28.7%
Building or editing websites21.6%
Translation20.7%

The other tasks are lower not because small business owners tried them and stopped, but because most have never thought of AI as something that could do them in the first place.

Why using ChatGPT for WordPress still requires a site connection

To take full advantage of how AI can save you time in WordPress, you should definitely go beyond generic chatbots like ChatGPT. A generic chatbot can write a draft blog post or the copy for a landing page, and if you ask it how to do something in WordPress, it will walk you through the steps.

The problem is that the chatbot sits in a separate app with no connection to your WordPress site, so everything it produces is something you then have to carry out yourself. It writes the post, but you are the one who pastes it in, formats it, and publishes it. When it explains how to change a setting, you are still the one who goes and changes it, which can still take an hour of clicking through menus.

And because it cannot see your site, generic AI’s advice is often shaky. If you ask it to recommend a plugin, it will happily list the popular options from around the web, but it has no idea which version of WordPress you are on, what theme you use, or what else you have installed, so it cannot tell you whether its suggestion will actually work on your site or break something, and you usually only find that out after you have installed it.

That leaves you two ways to get a useful result: you can learn to prompt well, spelling out your setup in detail every time so the tool has enough context to give a sensible answer, or you can take whatever it gives you and check it all yourself. Either way, a good part of your time still goes back into managing WordPress, because a chatbot can advise and draft, but it cannot reach your site.

What is site-connected AI for WordPress?

Site-connected AI for WordPress is a major step up from normal chatbots you might be used to. Instead of just writing text for you to copy and paste, it’s a dedicated assistant that plugs directly into your WordPress website and actually does the work for you.

This direct connection changes everything about how AI helps you. A site-connected AI for WordPress can actually “see” your real setup. It knows exactly which version of WordPress you are running, what active theme your site uses, and which plugins are already installed. This means every action it takes is grounded in the reality of your specific website, completely eliminating the guesswork.

And because it can see your site and act on it, your daily WordPress workflow completely changes. You are no longer the one doing all the clicking, searching through complicated WordPress menus, or worrying about where a specific setting is hidden. When you need something made, you simply ask for it in plain English.

The AI Agent for WordPress, part of SiteGround’s AI Studio, is the perfect example of this new kind of tool. You chat with it just like any regular AI, but the conversation ends with the actual job done on your website.

What can AI do in WordPress beyond content creation?

Once AI is linked to your dashboard, it moves beyond content generation into AI for WordPress site management. The easiest way to see this difference is to look at the everyday jobs you might already use AI for, and follow each one past the initial drafting phase into the manual work you usually have to finish yourself.

For instance, the AI Agent for WordPress can take over each of those tedious steps:

Publishing and organizing content, not just drafting it

Instead of writing a draft that you have to copy, paste, format, and categorize manually, the AI Agent can publish the post or page and sort it into the right categories and tags as it goes. It can even handle mass edits, so refreshing or filing a stack of old posts becomes a single request rather than an afternoon of tedious clicking.

Applying SEO and media, not just suggesting it

A normal chatbot will happily suggest a title tag or some alt text (the short description that search engines and screen readers use for images). A site-connected AI like the AI Agent for WordPress actually writes that metadata and applies it directly to your live posts and images. It can also manage your media library, allowing you to seamlessly upload new files or clear out old ones you no longer need.

Running your store, not just describing products

For a WooCommerce shop, a standard AI can write a catchy product description. A connected assistant goes much further: it uses your real store data to actually create and update the products, adjust pricing, generate discount coupons, manage customer orders, and even pull a sales report for you to review.

Handling maintenance, not just reminding you about it

Generic AI can tell you that site updates are something you should do, while site-connected AI actually does the upkeep. You can ask it to install new themes, update your plugins, run WordPress core updates, clear your site’s cache, or change your general site settings.

Managing users and comments, not just answering them

Beyond just drafting a reply for you to paste, a connected assistant like the AI Agent for WordPress can actively manage your community. It can moderate your comments (approving the good ones, holding the doubtful, and clearing the spam), and it can even create or update user accounts and roles for your staff, without you having to dig through the WordPress settings.

Task areaGeneric AI gives youSite-connected AI completes
ContentA draft you copy, format, and publish yourself.Publishes posts and pages, edits in bulk, and files them under the correct categories and tags.
SEO and mediaSuggested titles and alt text to paste in.Applies metadata directly to posts and images, and actively manages the media library.
WooCommerceA product description you add by hand.Creates products, updates prices, generates discount coupons, manages orders, and pulls sales reports.
MaintenanceA reminder to update and back up.Installs plugins, updates themes, runs WordPress core updates, clears caches, and changes core settings
Users and commentsA reply you post yourself.Creates user accounts, updates roles, and moderates your comments.

How site-connected AI completes a WordPress task in practice

Say you haven’t been adding alt text for many of your images, and you just learn you have to do it so that search engines can properly understand and rank your content. (We know you are likely already on top of this from reading SiteGround’s Academy, but just imagine for the sake of the argument.)

Now you have to click through the media library, image by image, writing and pasting those descriptions by hand to catch up. A standard AI chatbot like ChatGPT will happily write a list of image descriptions for you to copy if you give it the images or describe them. You would then have to manually paste them for each individual image, which can take so much time.

However, a site-connected AI actually does the data entry for you. Because it is directly linked to your site, it can analyze your assets, formulate a strategy, and apply the text across your entire media library in seconds.

For example, you can just give the AI Agent for WordPress this prompt:

“Generate and apply SEO alt text for all the images in my media library.”

The AI Agent for WordPress then actively scans your live media library, finds the images, explains exactly how it plans to optimize them, and pauses to ask for your confirmation.

A screenshot of the AI Agent by SiteGround chat interface outlining a bulk alt text generation task. At the top, a user prompt reads "Generate and apply SEO alt text for all the images in my media library." Below, under "Plan," the assistant outlines a proposal titled "Media Library Images — 86 updates bulk," detailing how it will generate SEO-friendly alt text for 86 media items using existing titles, filenames, slugs, and context while refining or replacing blank and generic descriptions. At the bottom, the assistant asks for confirmation to proceed, situated above a prompt input box reading "Ask me anything WordPress related and I'll help."

Once you review the plan and give the green light, the AI Agent for WordPress executes the changes on your backend and reports back with a clear summary of the work it completed.

This perfectly highlights what makes a site-connected AI assistant so powerful. It acts as a responsible, hands-on partner that does the heavy lifting, saving you hours of clicking and pasting while keeping you in complete control of the final outcome.

Which WordPress tasks still need human review?

A site-connected AI is not designed to run your business, but to run your errands. Strategic decisions will always remain human. What products to sell, how to price your services, the overarching direction of your website, and the final review of anything your customers will actually see are your choices.

In the case of the AI Agent for WordPress, you also never have to worry about it making a major mistake behind your back. Because it acts as a responsible partner, it uses built-in safeguards like Power Mode to ensure you stay in complete control. It will always pause and require your explicit approval before executing any action with real consequences, like deleting data or altering core settings.

So, the most accurate way to picture this new era of WordPress management isn’t “AI runs my site,” but rather “I make the decisions, and the AI does the legwork.” That is the ultimate value of learning how to use AI in WordPress beyond content creation: you keep the creative control, and you hand over the tedious tasks.

FAQs


How do you use AI in WordPress beyond content creation?

You use AI in WordPress beyond content creation by connecting it to your site so it can complete tasks, not just draft them. Instead of pasting in AI-written text, a site-connected assistant can publish posts, apply SEO metadata, update WooCommerce products, run maintenance, and moderate comments, on your instruction and with your approval for anything major.

Can AI manage a WordPress site?

Yes, a site-connected AI can manage much of a WordPress site. Because it is connected to your real content and settings, it can publish and organize content, update products and prices, run plugin and core updates, and moderate comments. You keep the decisions and approvals; the AI carries out the work.

Why can’t ChatGPT manage WordPress without a site connection?

ChatGPT cannot manage WordPress on its own because it is not connected to your site. It has never seen your pages, products, or settings, so it can only suggest text and steps that you then carry out by hand. Managing a site needs AI that can read your real data and make approved changes directly.

What is site-connected AI for WordPress?

Site-connected AI for WordPress is AI plugged directly into your site, so it can read your real content and complete approved tasks rather than only producing drafts. It is the difference between an assistant that suggests a change and one that makes the change for you inside WordPress.

What can AI do in WordPress besides writing?

Besides writing, AI connected to your site can publish and organize content, apply SEO metadata across posts and images, manage WooCommerce products, prices, and orders, install and update plugins and themes, run core updates, and moderate comments and users, turning suggestions into completed work.

Can a WordPress AI agent complete tasks on the site?

Yes. A WordPress AI agent connected to your site can complete tasks directly, such as publishing a post, updating a batch of products, or running updates, rather than only advising you. It acts on your instruction and typically pauses for confirmation before anything high-impact.

How can a small business start managing WordPress with AI?

A small business can start to manage WordPress with AI by picking one repetitive task, such as publishing a backlog of posts or updating product prices, and handing it to a site-connected assistant like the AI Agent for WordPress. Starting with a single real task is the simplest way to see the difference between drafting and completing.

How to choose AI plugins for WordPress without overloading your site

A digital graphic illustrating WordPress AI plugin selection against a purple gradient background. On the right, a browser mockup displays a website hero section featuring a woman in a purple beanie alongside the tag "+ NEW COLLECTION", the headline "Where Comfort Meets Confidence", and a dark call-to-action button. On the left, floating plugin selection cards display active choices marked with blue checkmarks—including circular icons for support, email, and content editing—positioned underneath a black AI sparkle icon button.

As we found in our 2026 report on AI in WordPress for small businesses, the AI plugins market has been exploding. There is now an AI plugin for almost every WordPress task imaginable, and it’s tempting to install each shiny new tool that promises to make your life easier with a bit of AI magic. But that is how your site ends up overloaded, so the real question is: how do you choose AI plugins for WordPress well, and end up with only the ones you actually need?

Fortunately, you don’t need to test every option. Choosing AI plugins for WordPress means starting with the task you need to complete, narrowing your options to the right plugin category, and evaluating each candidate for compatibility, total cost, API requirements, security, overlap, and ongoing maintenance before installing it. That kind of WordPress AI plugin selection is what keeps your site fast and easy to manage rather than cluttered.

This article will walk you through the whole process and show you how a site-connected assistant like the AI Agent for WordPress can help you search for and install the AI plugins you actually need.

Key takeaways:

  • Choosing AI plugins for WordPress is a process, not a shopping trip: start from the task, narrow to the category, then run one candidate through nine checks before you install anything.
  • Judge every plugin on the same nine points, from whether it fits the job to how it handles your data and whether it overlaps something you already run.
  • The real cost is rarely the sticker price, because separate subscriptions, AI provider accounts, and API keys can add up across a stack of AI tools.
  • Overlap is the check most people skip, yet removing a plugin you no longer need is often a bigger speed and security win than adding a new one.
  • A site-connected assistant like the AI Agent for WordPress can run these checks against your live site, recommend or install a plugin, and in many cases handle the task so you need no new plugin at all.

How do you choose an AI plugin for WordPress?

The best way to choose an AI plugin for WordPress is to define the task first, then check a single candidate against the same short list of questions every time, so the decision is consistent instead of swayed by whichever tool has the best marketing that week.

AI has become the headline feature nearly every plugin leads with, from established names bolting an AI panel onto tools you already know to brand-new plugins built entirely around a single model. On the surface, many can look almost identical, which makes it genuinely hard to tell a tool that will still be maintained next year from one that was rushed out to catch the wave.

For a detailed analysis of the AI plugins market, download our 2026 report on AI in WordPress for small businesses.

The nine checks below cover the things that actually decide whether a plugin helps your site or slowly weighs it down.

1. Does it fit the specific task?

Among WordPress AI tools, task fit matters more than feature count. The question is not whether a plugin does a little or a lot, it’s whether what it does matches what you actually need. If you have one narrow job, a plugin built for exactly that will serve you better than a broad suite where your task is buried among features you will never open. If your need is genuinely bigger, like WordPress management as a whole, then a tool scoped to that makes sense. What you are avoiding is the mismatch: paying for and loading capabilities that have nothing to do with the job in front of you.

2. Is the AI plugin compatible with your WordPress setup?

AI plugin compatibility is whether the plugin works cleanly alongside the rest of your site: your WordPress version, your theme (the design template that controls how your site looks), and the plugins you already run. Plugin conflicts are one of the most common reasons a WordPress site suddenly looks broken or slows to a crawl, because two tools try to do overlapping things at the same time.

Check that the plugin lists support for a current WordPress version and was tested recently. AI plugin compatibility problems are far cheaper to avoid than to diagnose after the fact.

3. What does the subscription actually cost?

Note the plugin’s own price, monthly or yearly, and be honest about which tier you will really need. The free version is often a preview, and the feature you actually came for (bulk actions, higher limits, the model you want) tends to sit on a paid plan. AI plugin pricing is worth writing down rather than eyeballing, because a “cheap” plugin at the tier that does nothing useful is not cheap. And this is only half the cost picture, which brings us to the next check.

4. Does it need its own API keys or provider account?

This is the cost that catches people out. Many WordPress AI plugins don’t include the AI itself. Instead, they connect to AI models like ChatGPT, Claude or Gemini, and to do that you have to create your own account there and generate an API key, a long password that lets the plugin use that service and bills you for what it uses.

When this is the case, you’re paying twice: once for the plugin and again for the AI usage on a separate bill you have to set up and watch. Always check whether the AI is included or billed separately before you decide a plugin is affordable.

If you are on WordPress 7.0 or later, this check gets easier. WordPress 7 added a built-in way to connect an AI provider like OpenAI or Anthropic once, from a single Connectors screen, and plugins built for it share that connection instead of each asking for its own API key. You still set up one provider account and still pay for what the AI uses, but it is one connection and one bill to watch rather than a separate key buried in every plugin. Our guide to AI in WordPress 7.0 for business explains this in detail.

5. How does it handle your data and permissions?

An AI plugin often needs real access to your site to read your content, change your pages, or send your data to an outside service to process it. That is quite common, but it’s worth a moment’s thought. Look at what the plugin asks to do, and where your content goes when it uses AI. A well-made plugin is clear about both.

WordPress AI plugin security comes down to two simple questions: does it ask for more access than the job requires, where does it send site data, and is it still being looked after? An abandoned plugin with deep access is one of the riskier things you can leave installed, which leads us to the next check.

6. Is it actively maintained?

WordPress, PHP (the programming language WordPress runs on), and the AI services behind these plugins all change regularly. An AI plugin that is not kept up to date will eventually break against them, or stop being safe. Before installing, look at when it was last updated and how often new versions appear. A plugin updated last week is a good sign; one untouched for a year is a warning, however good it looked at launch.

7. Is there real support if something goes wrong?

It’s possible at some point an AI plugin will do something you didn’t expect, and what matters then is whether you can reach a human who can help. Check what support looks like before you commit: documentation only, a community forum, or actual responsive help from the people who built it. On a free plugin, the answer is often “you are on your own,” which can be fine for something minor and painful for something your business depends on.

8. Does it overlap with something you already have?

This is the check almost everyone skips, and it is the core of a simple WordPress plugin audit. Before adding a plugin, look at what is already installed, because there is a fair chance something on your site already does part of the job. Running two WordPress AI plugins that overlap is worse than wasteful: they compete, they both load code on every page, and they widen the surface where things can break. That overlap can add cost, maintenance work, and conflict risk even when both plugins are technically compatible. This is how sites end up slow and fragile without anyone deciding they should be.

9. How much work is it to set up and keep running?

Finally, be realistic about effort, both to get started and to live with. Some plugins are active in a click; others want accounts, keys, and a page of configuration before they do anything. And setup is only day onе: every plugin you keep is another interface to learn, another thing to update, another candidate when something goes wrong. A slightly less powerful tool that you will actually keep current often beats a stronger one that becomes a chore. Low ongoing effort is a feature, not an afterthought.

CheckWhat to verify
Task fitIt does the job you need, without sprawling into features you will never use.
Compatibility and performanceWorks with your WordPress version, theme, and existing plugins without causing conflicts or unnecessary load.
Subscription priceThe plugin’s own cost, at the tier that actually does the job.
API keys and accountsWhether the AI is included or billed separately through your own account.
Data and permissionsHow it handles your content and how much access it asks for.
Active maintenanceUpdated regularly and keeping pace with WordPress and PHP.
SupportReal help available when something goes wrong.
OverlapNothing you already run does the same job.
Setup, testing and upkeepCan be tested safely, reversed if needed, and maintained without excessive effort.

How an AI Agent for WordPress can run these checks for you

Running all these checks can be a fair amount of work. But here’s some good news: you don’t actually have to do this by yourself. It’s exactly the kind of job a specialized AI agent for WordPress can do for you, from choosing the AI plugin against these criteria to even installing it.

For example, you can ask SiteGround’s AI Agent for WordPress to act as your research assistant. And because it connects directly to your site, it doesn’t just give generic advice, but actually looks at what you have installed right now. In one exchange, it can handle the hardest check—overlap—by cross-referencing your actual setup, potentially saving you from adding a plugin you don’t even need.

If a new tool genuinely is the answer, the agent will search and generate a comparison table with pros, cons, and a suggested starting point. Once you’re satisfied, just give the agent the word, and it will install your chosen plugin for you.

Here’s an example prompt you can copy and adapt:

“Find me the best WordPress AI plugin for a [task] on my WordPress site. Compare options based on task fit, compatibility, performance impact, pricing, API key/provider costs, security, update history, support quality, overlap with my existing plugins, and setup/testing effort. Check my existing plugins first, then give me a shortlist and one final recommendation.”

Say you are about to add another AI tool for a visitor chatbot. Rather than reaching for a generic “best chatbots” list, the agent checks your WordPress version, your theme, and your active plugins, and tells you what it finds. It works through the same nine checks for you, weighing a handful of candidates on task fit, compatibility with your exact setup, pricing, whether each needs its own API keys, how it handles your visitors’ data, update history, support, and setup effort.

A screenshot of the AI Agent by SiteGround chat interface presenting a plugin suggestion titled "Recommendation." The panel highlights "Best final recommendation: Tidio – Live Chat & AI Chatbots" followed by key reasoning, including its design for visitor chat and AI handoff, compatibility tested up to WordPress version 7.0.2, over 80,000 active installs, a 4.7/5 rating, and direct support for both AI responses and human live chat. A floating blue down-arrow scroll button sits above a bottom prompt input bar reading "Ask me anything WordPress related and I'll help."

You can then just tell the AI Agent “install it.” And because the AI Agent is securely linked to your site, you don’t need to log into the dashboard, navigate through the Plugins menu, or search the repository yourself. It instantly downloads, installs, and activates the plugin directly on your live site.

When your site does not need another AI plugin at all

Knowing you can choose the right AI plugins so easily doesn’t change the big problem: stack up too many of them, and your dashboard fills with separate settings screens, each with its own login, its own way of working, and its own updates to keep track of. Your monthly costs can climb, because most of these tools are subscriptions, and several small ones add up to a bill you never sat down and agreed to. And your site gets heavier, because each plugin loads its own code, so the more you stack, the slower and more fragile the whole thing becomes.

This is once again where a site-connected WordPress assistant changes the math, because it doesn’t do one job. A specialized AI agent can often replace a whole shelf of single-purpose plugins at once and become the most useful WordPress AI tool for your business.

With the SiteGround AI Agent for WordPress, for example, the same tool can draft and publish a post, generate and apply SEO metadata, upload images to your media library, create products and discount coupons in your store, and moderate comments—all from one place, on your instruction. It can even clear your site’s cache, install and update themes, or run your core updates.

So instead of adding another tool to the pile, you are removing the reason the pile exists. And there are no separate logins to remember, no API keys to configure, and no subscriptions to keep track of. In fact, the AI Agent for WordPress is completely free for SiteGround customers, giving you 20,000 AI tokens a month as part of the free AI Studio Essential plan. You can also use it on sites hosted elsewhere (if you have a SiteGround account): it’s one lightweight plugin and about a minute to connect.

FAQs

How do you choose an AI plugin for WordPress?

You choose an AI plugin for WordPress by starting from the specific task you need done, narrowing to the right type of plugin, and then checking one candidate against a consistent set of questions, about task fit, compatibility, real cost, API keys, data and permissions, maintenance, support, overlap, and setup effort, before installing anything.

What should you check before installing an AI plugin for WordPress?

Before installing an AI plugin for WordPress, check that it fits your exact task, works with your WordPress version and existing plugins, and is priced clearly, including whether the AI is billed separately through your own account. Then look at how it handles your data, whether it is actively maintained and supported, and whether anything you already run does the same job.

Should I install multiple AI plugins on WordPress?

Not by default — each one adds its own settings, login, and code to every page load, and overlapping plugins compete rather than add value. Check for overlap with what you already run before adding another, and consider whether a site-connected assistant like the AI Agent for WordPress can cover several of those jobs at once instead of adding another single-purpose tool.

Which type of WordPress AI plugin does my business site need?

The type of WordPress AI plugin your business needs depends on the job you are trying to finish, such as writing content, generating SEO metadata, editing images, translating a store, or moderating comments. Define that task first, then look only at plugins in that category, rather than at broad tools that promise to do everything.

How much do WordPress AI plugins cost?

To compare the true cost of WordPress AI plugins, add the subscription price at the tier you actually need to any separate AI usage billed through your own provider account. Many plugins connect to an outside AI service, so the real cost is the plugin plus that usage, not just the advertised plan.

Do WordPress AI plugins require API keys?

Many WordPress AI plugins do require API keys, because they connect to an outside AI service rather than including the AI themselves, though WordPress 7.0 lets you connect a provider once for the whole site rather than per plugin. An API key is a private credential that lets the plugin use that service on your account, which usually means a second bill for AI usage on top of the plugin’s own price. Always check whether the AI is included or billed separately.

How can I tell whether two WordPress AI plugins overlap?

Two WordPress AI plugins overlap when they can perform the same job, such as two tools that both generate SEO metadata. Review what each installed plugin actually does, not just its name, and remove duplicates, since overlapping plugins compete, add weight to every page, and increase the chance of conflicts.

How do I audit the AI plugins on my WordPress site?

To audit the AI plugins on your WordPress site, list everything installed, note the single job each one does, and flag any that overlap, sit unused, or have not been updated in a long time. Removing those is often a faster performance and security win than adding a new plugin. A site-connected assistant can run this audit for you.

Can an AI Agent for WordPress recommend and install plugins?

Yes. An AI Agent for WordPress can recommend a plugin for a task, check it against what you already have installed to avoid overlap, and install it on your instruction. Because it is connected to your live site, its recommendations reflect your actual setup, and it can also remove plugins you no longer need, with your confirmation.

AI website builder pricing: how to compare plans without getting burned

A digital graphic featuring an open laptop displaying a website mockup for "Panto" with a dark interior scene and the headline "MINIMALISTIC & MODERN INTERIOR" against a green to deep purple gradient background. To the left of the laptop sits a three-by-three grid of square UI icon buttons. To the right, a highlighted glassmorphism card topped with a bright green "BEST VALUE" banner displays a "Pricing plan" priced at "5.49 €/mo" above feature line placeholders, with other blurred plan cards in the background. In the bottom-right foreground, a white callout button reads "SELECT PLAN" with an arrow cursor clicking on it.

An AI website builder can look cheap right up until you try to connect your domain or actually publish the site. That’s because AI website builder pricing is rarely just the monthly plan price you see on the pricing page. The real cost can include the builder itself, hosting, domain, SSL, storage, forms, ecommerce features, email, renewals, transaction fees, and upgrades. The safest comparison is a year-one cost check plus a list of features your business actually needs.

This article shows you how to choose the right AI website builder plan for your business, spot the limits that make a cheap plan expensive later, and understand how all-in-one AI website builders such as Coderick AI combine building, hosting, security, and publishing in one platform instead of leaving you assembling separate services.

Key takeaways:

  • Compare the cost of a working AI-built website, not the price of access to the builder. Hosting, a domain, email, forms, payments, and renewals can change the result.
  • Choose a plan by the job the website must do (generate inquiries, take bookings, or sell) not by the lowest price on the page.
  • Translate technical limits into business limits. A cap on form submissions, products, team members, or monthly AI credits can become a cap on leads, sales, and updates.
  • Calculate both year one and year two. Introductory discounts make the first bill look attractive; renewals reveal the recurring cost.
  • Use a free plan or trial to test your real workflow, including editing, mobile viewing, form delivery, publishing, and the plan required for your must-have features.
  • With an all-in-one platform such as Coderick AI, paid plans combine the builder with premium hosting and publishing support, reducing separate setup steps and bills.

What does AI website builder pricing actually include?

An AI website builder pricing page usually leads with the easiest number to advertise: the builder subscription. Your business, however, needs a live website that customers can visit, trust, and use. The practical question is therefore not “What does the builder cost?” but “What will it cost to get the result I need and keep it running?”

The AI builder subscription

This is the fee for creating, editing, and maintaining the website inside the AI builder. The important detail is not simply whether the plan says “AI included,” but how the AI is metered. Some services limit generations, edits, pages, projects, or monthly credits. A plan can be generous enough to create a first draft but restrictive once you start refining copy, adding pages, updating sections, or maintaining the site. If you’re comparing platforms, use the website-builder checklist.

Hosting

Hosting is the service that keeps your website available on the internet. It’s the online home where the site’s pages, images, and files live. Every website needs hosting, whether it appears as a separate bill or is included in the AI website builder plan.

When hosting is separate, you may need another account, another renewal date, and a connection between the builder and the host. When it is included, publishing is usually simpler because the tool that creates the site already knows where the site will run.

Domain name

A domain name is the address customers type, such as yourbusiness.com. A temporary builder address is fine while you test, but most businesses eventually need their own domain for credibility, branded email, and easier marketing.

Check three separate things:

  • whether a domain is included,
  • whether that offer applies only to the first year,
  • and what the renewal price will be.

“Free domain” often describes the first invoice rather than the long-term cost.

SSL certificate and HTTPS

SSL is the security technology that encrypts information moving between a visitor and your website. When it is working, the address starts with https:// and the browser shows a padlock or other security indicator. This matters even on a simple brochure site because contact forms, logins, and customer details should not travel across an unsecured connection.

Most modern platforms include SSL, but don’t rely on “secure hosting” as a vague promise. Confirm that HTTPS is enabled automatically for your own domain and that renewal is handled without a separate certificate purchase.

Business email

A professional inbox uses your domain (for example, hello@yourbusiness.com) instead of a personal address. It may be included, sold separately, or priced per mailbox. That last detail is important when several people need addresses such as sales@, bookings@, and accounts@.

Also check what “email included” means. A forwarding address that sends mail elsewhere is not the same as a full inbox you can send from, search, and access on your phone.

Business features

Forms, appointment booking, payments, ecommerce, customer accounts, and marketing integrations are often the real reason a business needs a website. These features are also where plans diverge. A low-cost tier may let you design the page but require an upgrade before visitors can complete the action the page was built for.

Work backwards from your revenue path. If customers must submit a quote request, reserve a time, or pay online, test and price that complete journey, not just the page that introduces it.

Support

Support becomes part of the price when your website affects inquiries or sales. Compare the channel, hours, and scope: documentation only, an AI assistant, live chat, email tickets, or hands-on help. A cheaper plan can cost more in practice when a small publishing problem takes an afternoon to solve.

Pro tip: Count accounts as well as money. A builder, host, domain registrar, email provider, booking tool, and payment add-on can create six logins, six renewal dates, and six places to troubleshoot. Fewer moving parts have a real operational value for a small team.

Cost itemPlain-English meaningQuestions to ask
AI builderThe tool used to create and edit the siteAre generations, edits, pages, projects, or credits limited?
HostingThe online service that keeps the site availableIs it included? Who handles publishing, speed, backups, and security?
DomainYour website addressIs the first year free? What does it renew at? Can you use an existing domain?
SSL/HTTPSThe encrypted connection that secures the siteIs it automatic for a custom domain, and does it renew automatically?
Business emailAn inbox using your domainIs it a full mailbox? How many inboxes are included?
Forms/bookingTools that collect leads or appointmentsWhich plan unlocks them? Are submissions or bookings capped?
EcommerceProducts, cart, checkout, and order toolsAre there product, sales, or platform transaction limits?
SupportHelp when setup or publishing goes wrongIs human support included, and when is it available?

How much does an AI website builder cost in year one?

Year one is the best time to compare AI website builder costs because it forces all required items onto the same page. It also prevents a common comparison mistake: putting an all-in-one plan next to a builder-only plan and treating the two headline prices as equivalent.

A simple example: Plan A costs $12 a month, but needs a $20 domain, $72 of business email, and a $120 booking add-on. Its first-year total is $356. Plan B costs $24 a month and includes those items, for a $288 total. These figures are illustrative, but the comparison method is the point: the lower monthly price was not the lower business cost.

Monthly subscription

Multiply the price by the number of months you will actually pay. If the page shows a low “per month” figure beside annual billing, check whether the full year is charged upfront. A monthly equivalent is not the same as a month-to-month commitment.

Monthly vs annual billing

Annual billing often reduces the monthly equivalent, but the saving is payment for commitment. Before prepaying, check the refund window, what happens if you cancel, whether unused credit carries over, and whether the plan can be downgraded at renewal.

For a new business idea, a slightly higher month-to-month price can be sensible while you prove demand. For an established business replacing an existing site, annual billing may be easier to justify once the trial has confirmed the platform fits.

Domain registration and renewal

Record the first-year domain charge and the standard renewal separately. If you already own a domain, check whether connecting it is included in the plan you are considering. Some entry tiers only allow a platform-branded web address.

Email and add-ons

Add every mailbox and every extension the live website requires. Don’t count optional ideas you may never use, but do count the tools your daily workflow depends on. For example, a salon should include booking and reminders; a consultant should include a reliable inquiry form; a retailer should include product and checkout features.

Ecommerce or booking costs

A selling plan can carry three separate costs: the website plan, the payment processor’s fee, and sometimes an additional platform transaction fee. A booking system may also charge for reminders, staff calendars, locations, or the number of appointments. Compare the cost at your expected volume, not only at launch.

Renewal pricing after discounts

The first-year total tells you whether you can launch. The year-two total tells you whether the setup is sustainable. Record the regular plan price, domain renewal, mailbox renewals, and any promotional add-ons that revert to full price.

Year-one cost formula: Plan + domain + email + required features + payment/transaction costs + setup or migration costs

A digital graphic featuring a translucent glassmorphism UI dashboard floating against a dark blue gradient background with faint flowchart wireframes. The central dashboard panel displays a hero banner with a woman wearing sunglasses beside the bold text "BUILD NEW TRACKER," a user profile card for "Victoria Louise," and bottom widgets showing a "$43,007" metric and a "4.72" star rating. In the bottom-right foreground, a solid white card highlights "Monthly visitors" with an upward-trending blue graph and a growth count of "+10.90k."

Which AI website builder plans do small businesses usually need?

Most pricing pages present a ladder: free, starter, business, store, and growth. The names are marketing labels. The useful way to choose an AI website builder plan is to identify the first tier that supports the customer action that makes the website valuable to your business.

Free plan

A free AI website builder plan is best used as a test environment. It can show whether you understand the editor and whether the AI produces a useful starting point. It’s rarely the final home for a business because free tiers commonly use platform branding, a temporary address, lower usage limits, or restricted publishing.

Starter site plan

A starter plan can suit a simple information site: a homepage, services, about, and contact details. The deciding question is whether it supports your own domain and a working form. A “brochure site” still needs a clear way for a potential customer to take the next step.

Business website plan

This is often the practical level for lead generation. Look for custom domains, forms, basic search settings, analytics, enough storage for real images, and a manageable way to update the site. If email, form routing, or additional pages are extra, add those costs before comparing.

Booking or service-business plan

Choose this level when your calendar is part of the sale. Test the full process from a customer choosing a time to you receiving the booking. Check staff calendars, locations, cancellation rules, reminders, deposits, and monthly appointment limits. A booking widget that only looks good in a demo is not enough.

Online store plan

A store needs product management, stock or availability, a cart, checkout, order notifications, taxes or shipping rules where relevant, and a clear refund process. The cheapest ecommerce tier may be suitable for a few products, but product caps and extra transaction fees matter quickly as sales grow.

Advanced or growth plan

A growth plan becomes relevant when the business needs more projects, storage, traffic capacity, team access, languages, advanced reporting, or integrations. Don’t buy it for vague “future growth.” Buy it when a specific limit on the lower plan would interrupt work or revenue.

Plan typeUsually fitsMust-have proof before buyingTypical upgrade trigger
FreeTesting the builderYou can create and edit the kind of site you needCustom domain, publishing, branding removal
StarterSimple information siteCustom domain, HTTPS, mobile layout, working contact pathMore pages, forms, storage, or analytics
BusinessLead-generation siteForms reach the right inbox and are not heavily cappedBooking, more submissions, team access
BookingAppointment-led businessCalendar, reminders, deposits, and cancellation flow workMore staff, locations, or monthly bookings
StoreSelling products or servicesProducts, checkout, payment, notifications, and policies workProduct count, sales volume, transaction fees
GrowthLarger or multiple sitesThe extra capacity solves a known operational needMore projects, storage, credits, or users

What hidden AI website builder fees should you check?

Most hidden AI website builder fees are not literally secret. They are simply separated from the headline price, described in a footnote, or triggered only after the site becomes useful. The best defense is to look for the event that creates each charge: renewal, adding a mailbox, receiving a payment, exceeding a limit, or leaving the platform.

Renewal price after the first term

Introductory rates can apply for a long first term and then renew at a higher standard rate. Record the renewal date and recurring price when you buy. A low first bill should be treated as a discount, not as the permanent cost of the website.

Domain renewal and domain privacy

The domain may be renewed separately from the website plan. Domain privacy, which prevents your personal contact details from being displayed in public registration records where applicable, may be included or charged separately. Check both items for every domain you manage.

Email inboxes

Email is commonly priced per user or mailbox. A single included address can be enough for a sole trader, but a small team may need several. Decide whether shared addresses can forward to one inbox or whether each person requires a full account.

Payment processing and transaction fees

Payment processors charge for handling card or online payments. Some website platforms add their own transaction fee on top. Even a small extra percentage becomes significant at higher sales volume, so calculate the fee using your expected monthly revenue rather than judging it in isolation.

Apps, plugins, and add-ons

A plan may depend on third-party extensions for bookings, reviews, pop-ups, multilingual content, or advanced forms. Check whether those tools have their own subscriptions and whether the integration is maintained by the builder or by an outside developer. An add-on that stops being updated creates a reliability cost as well as a financial one.

Storage, bandwidth, page, and AI-credit caps

Storage is the space used by your images and files. Bandwidth is the amount of data sent to visitors when they load the site. Page caps limit how much you can publish, while AI credits (the units some builders use to meter how much you can generate or edit) can limit how often you generate or revise content and functionality. These limits are not automatically bad; they become expensive when normal use pushes you into the next tier.

Premium support

Priority queues, phone help, migration assistance, or hands-on setup may sit behind a higher plan. Think about the cost of downtime and your confidence with troubleshooting. A business that takes orders all day has a different support requirement from a portfolio updated twice a year.

Migration, export, and switching costs

The cost of leaving is easy to ignore when joining. Check whether you can export your text, images, products, customer records, form submissions, and domain. Some sites cannot be moved as a complete design, which means switching platforms involves rebuilding. That future labor is part of the long-term price.

Pro tip: Save a PDF or screenshot of the pricing page and included features on the day you subscribe. Pricing and plan names change. A simple record makes renewal decisions and support conversations much easier a year later.

Which limits trigger upgrades later?

Cheap AI website builder plans become expensive when its limits are attached to the part of your website that is succeeding. The useful exercise is to translate every cap into a business event you understand. “100 form submissions” means roughly three per day; “five team seats” means the sixth colleague changes the plan; “10GB storage” means something different for a text-led consultant than for a photographer.

Here are the limits that most often force an upgrade, and what each one really means for your business:

  • Traffic and bandwidth. More visitors cause the site to transfer more data. Ask what happens at the limit: a warning, slower service, an overage charge, or an automatic upgrade.
  • Pages. A page cap can become restrictive when you add individual services, locations, case studies, or campaign landing pages.
  • Storage. High-resolution photos, videos, downloadable files, and product images use space quickly. Image optimization can delay an upgrade without hurting quality.
  • Form submissions. A monthly cap can turn into lost inquiries if the form stops accepting entries or older submissions become inaccessible.
  • Bookings. Check monthly appointment limits, staff calendars, locations, reminder messages, and whether cancelled appointments still count.
  • Products and orders. Stores may cap listed products, variants, orders, or sales value. Make sure the tier fits seasonal peaks, not only an average month.
  • Team seats. The person who writes copy, the person who handles orders, and an outside freelancer may each need access. Role and permission controls matter as much as seat count.
  • AI credits or generations. Building consumes credits, but so does maintaining the site. It’s a different metering logic than token-based coding tools, such as Claude Code. Reserve capacity for later edits, new pages, and campaign updates.
  • Advanced SEO or analytics. Basic page titles may be included while redirects, structured data, deeper reporting, or integrations require a higher level.
  • Custom domain and branding. Using your own address and removing platform branding are classic reasons a free plan becomes paid.

Reality check: Do not forecast only average usage. A holiday campaign, press mention, busy booking season, or successful social post can create a short spike. Check how the platform handles peaks before a good month becomes an emergency upgrade.

How does included hosting change AI website builder cost?

Included hosting changes both AI website builder cost and the amount of technical coordination required. A builder-only product gives you a design or code output and leaves you to arrange where it runs. An all-in-one product includes the environment needed to publish and keep it online.

Builder-only pricing versus all-in-one pricing

A builder-only plan can be attractive when you already have hosting and know how deployment works. For a complete beginner, however, separate services create extra decisions: choosing a host, connecting accounts, configuring the domain, enabling HTTPS, and working out which provider is responsible when publishing fails.

An all-in-one AI website builder plan can appear more expensive beside a design-only tool because it includes more of the finished result. Compare like with like: either add hosting and publishing costs to the builder-only plan or remove them from the all-in-one total before judging value.

Why hosting matters for total cost

Hosting affects whether the website is available, how quickly pages load, how backups and security are handled, and how easily the site can grow. Those might sound like abstract technical details, but a slow or unavailable site loses trust, inquiries, and sales.

Domain, SSL, and publishing setup

Connecting a domain tells the internet where your website lives. SSL then secures that connection so visitors reach the site over HTTPS. With separate services, you may have to copy settings between the domain provider, builder, and host. With an integrated platform, much of that work can be handled inside one account.

SiteGround Coderick AI homepage with a prompt input field and quick-start options for building sites, tools, and apps

How Coderick AI handles building and hosting

Because most AI builders stop at building and leave hosting, domains, and security for you to piece together afterward (which is why such AI design tools alone are not enough), Coderick AI is designed as an end-to-end build-and-publish platform. You describe the project, refine it in plain language or via visual editing (which is basically what vibe coding is), and publish it on SiteGround’s battle-tested infrastructure from the same environment. Paid Coderick AI plans include SiteGround hosting and custom-domain support, with security and the publishing workflow integrated rather than left as a separate deployment project.

For a small business owner, the practical benefit is that there are fewer hand-offs between the moment the website looks ready and the moment customers can actually use it.

Time is part of the price: If separate setup takes five hours of your own time (or requires paid help), add that to the comparison. The cheapest software is not the cheapest route when it turns the owner into an unpaid systems integrator.

A year-one AI website builder cost worksheet

Use one copy of this AI website builder cost worksheet for every platform you are considering. Enter zero only after confirming that an item is included, not because it is absent from the headline price. The year-two column is deliberately included so introductory discounts do not control the decision.

Cost itemWhat to enterYear 1Year 2
Website builder planFull amount charged, not only the monthly equivalent$$
HostingSeparate hosting plan or $0 when included$$
Domain nameRegistration, connection, and renewal$$
SSL/HTTPSCertificate or setup fee, usually $0 when included$$
Business emailNumber of paid mailboxes × annual price$$
Forms/bookingRequired plan upgrade or add-on$$
EcommerceStore plan, apps, and expected platform fees$$
Payment processingEstimated fees based on expected sales$$
Templates/appsOnly the paid additions you truly need$$
Migration/setupYour time, freelancer help, or provider service$$
SupportPremium support or maintenance help$$
ContingencyA small buffer for realistic changes$$
TOTALAdd every line above$$

Decision rule: When two totals are close, prefer the option with fewer critical add-ons and a clearer upgrade path. Predictability is valuable when the website is part of day-to-day operations.

What should a free trial prove before you pay?

An AI website builder trial is not a design competition. Its job is to remove uncertainty about the website you actually intend to run. Use real business details, test the feature that creates value, and follow the publishing path far enough to expose any plan upgrade or technical hand-off. For what a real first session looks like, use the 60-minute build walkthrough.

Can you build the site type you need?

Create a small but realistic version: a service business with a quote form, a studio with bookings, or a store with a few real products. A generic demo can hide the exact limitation that matters to you.

Can you edit content without fighting the tool?

Change the headline, replace an image, reorder a section, add a page, and update the main button. Building happens once; editing happens for the life of the site. The best platform is one you will actually keep current.

Can you add forms, booking, or store features?

Add the one feature the business depends on and complete it from a customer’s point of view. Submit the form and confirm where it arrives. Make a test booking and check the confirmation. Place a test order and inspect the notification. Note the plan required for each step.

Can you preview and use the mobile layout?

Preview is useful, but also open the test site on a real phone. Check text size, button spacing, forms, menus, images, booking, and checkout. A site can look tidy on a desktop preview and still be awkward to use with a thumb.

Can you understand publishing, domain, and HTTPS steps?

Find the publish button, the temporary address, the custom-domain instructions, and the point where HTTPS becomes active. You don’t need to memorize the technology. You do need confidence that the path is clear and that support can explain it in ordinary language.

Can you estimate the real paid plan you will need?

Before the trial ends, write down the lowest plan that supports every must-have feature, the annual amount charged, the renewal rate, and the main usage limits. If you cannot identify the real plan after testing, the pricing model is not yet clear enough to buy.

Pro tip: Don’t spend the trial polishing colors and stock photos. A plain site with a working inquiry, booking, or checkout flow tells you far more than a beautiful homepage that cannot run the business.

How to compare AI website builder pricing without getting burned

Use this sequence to compare AI website builder pricing across providers. It keeps the business requirement in front of the pricing language and makes unlike plans easier to compare.

  1. Define the website’s main job. Choose leads, bookings, sales, or another measurable outcome.
  2. List the must-have features. Separate launch requirements from ideas that can wait.
  3. Find the first plan that supports them. Ignore the cheapest tier if it cannot complete the customer journey.
  4. Add the missing services. Include hosting, domain, HTTPS, email, forms, booking, payments, apps, and support.
  5. Translate every limit. Convert credits, submissions, products, seats, storage, and traffic into ordinary monthly use.
  6. Calculate year one and year two. Separate promotional pricing from the recurring total.
  7. Test the real workflow. Build, edit, submit, book, buy, preview on mobile, and inspect publishing.
  8. Check the exit route. Confirm domain ownership and what content or data can be exported.
  9. Choose for total value and predictability. The right plan supports the website you need without surprise upgrades or unnecessary complexity.

Ready to build?

[96]

FAQs

What is included in AI website builder pricing?

AI website builder pricing usually includes access to the builder, but the complete package varies by platform and plan. Check hosting, a custom domain, HTTPS/SSL, business email, storage, forms, booking, ecommerce, support, AI usage, and publishing. The plan price is only comparable after every required item is counted.

How much does an AI website builder cost?

The cost of an AI website builder depends on the site’s job, billing term, included hosting, and required features. A simple information site normally needs less than a booking site or online store. Calculate the full first year and the standard renewal year rather than relying on an advertised monthly equivalent.

What hidden AI website builder fees should I watch for?

Common extra costs include renewal increases, domain renewal, email mailboxes, paid apps, booking tools, ecommerce upgrades, payment processing, platform transaction fees, extra storage, higher AI usage, premium support, and migration or rebuilding costs if you leave.

Are free AI website builder plans really free?

They can be free for testing, but they often limit publishing, custom domains, branding removal, pages, storage, forms, ecommerce, or support. A free plan is useful when it helps you prove the editor fits; it is rarely the final plan for a customer-facing business website.

Which AI website builder plan does a small business need?

Choose the lowest plan that supports the website’s main customer action. A lead-generation site needs a custom domain and reliable forms. A service business may need booking and reminders. A store needs products, checkout, payments, and order management. The plan label matters less than the complete workflow.

What do SSL and HTTPS mean?

SSL is the technology that encrypts information between a visitor and your website. HTTPS is the secure version of the web address that shows the protection is active. Most modern platforms include it, but confirm that it works automatically with your custom domain.

Why does hosting matter in AI website builder pricing?

Every website needs hosting to stay online. If it is not included, you need a separate service and may have to connect, configure, and troubleshoot it. All-in-one platforms, such as Coderick AI, include hosting and publishing, so their headline price covers more of the finished website.

Does Coderick AI have separate hosting fees?

Coderick AI is an end-to-end platform, and SiteGround hosting is included in paid plans. You can build, refine, and publish in the same environment instead of setting up a separate hosting account. Check the current plan page for the latest allowances and terms.

Is annual billing cheaper than monthly billing?

Annual billing often lowers the monthly equivalent, but it requires a larger upfront commitment. Compare the full amount charged, refund terms, renewal price, included features, and your confidence in the platform after testing.

What should I test during an AI website builder trial?

Build a small version of the real site, edit key content, test the main form, booking, or checkout flow, open it on a phone, follow the publishing and domain steps, and record which paid plan unlocks every required feature.

OpenAI GPT-5.6 Sol, Terra, Luna, and GPT-Live: what small business owners need to know

A digital graphic depicting an AI model tier comparison arranged like a solar system against a dark blue space-themed background. On the left, an open laptop displaying the white OpenAI logo rests on a bed of dark blue, jagged crystals. Above the laptop, a large golden yellow sphere represents "Sol 5.6" with the sublabel "Capability." Concentric orbital lines curve toward the right, highlighting a blue sphere for "Terra 5.6" sublabeled "Balanced production" and a smaller grey sphere further out for "Luna 5.6" sublabeled "Speed and cost."

OpenAI just released two AI updates at once: the latest OpenAI models in the GPT-5.6 family, which come in three versions named Sol, Terra, and Luna, and a new voice model called GPT-Live. But what does that all mean, and are all those models useful for you? This guide explains what each one is, where you actually run into it, and whether any of it matters for your business.

Key takeaways:

  • OpenAI’s latest launch has two parts: the GPT-5.6 text models (Sol, Terra, and Luna) and GPT-Live, a new voice model for ChatGPT.
  • In the ChatGPT app you don’t pick a version: paid plans use Sol, while free and Go plans stay on the previous model in regular chat. Choosing between Sol, Terra, and Luna only happens on OpenAI’s developer and business tools.
  • GPT-Live is the change you’ll most likely notice: ChatGPT’s voice can now hold a natural, back-and-forth conversation.
  • If you build with OpenAI’s developer tools, the three tiers are mostly about cost: Sol is the priciest and most capable, Terra is the balanced middle, and Luna is the cheapest.

Is GPT-5.6 available in ChatGPT, and how do you use it?

Whether you can use GPT-5.6, and how, comes down to two things: which plan you’re on, and where in ChatGPT you are. There are two places these models show up, and they follow different rules.

If you use the regular ChatGPT chat


If you use ChatGPT for things like marketing, you usually use the app. When you open it on your phone, computer, or the web, you don’t pick Sol, Terra, or Luna by name.

  • On a paid plan (Plus and up), you get GPT-5.6 Sol. It’s the flagship, and it sits behind the reasoning settings (the Medium, High, and Extra High options). So when you open the app, you can choose GPT-5.6 Sol and then choose how hard you want it to think.
  • On the Free or Go plan, you don’t get GPT-5.6 in regular chat. You stay on the previous model, GPT-5.5.

One thing that’s true on every plan: for quick, everyday questions, ChatGPT uses a fast default (GPT-5.5 Instant) unless you turn up the reasoning. So even on Plus, you’re only using GPT-5.6 when a task calls for it or you ask for it.

If you use the API, Codex, or ChatGPT Work

These are separate spaces inside ChatGPT: Work is a business workspace, and Codex is OpenAI’s coding tool. Here the picture flips, because this is where free users can reach GPT-5.6:

  • Free and Go plans get GPT-5.6 Terra here, at no cost, even though their regular chat stays on the old model.
  • Paid plans can pick between Sol, Terra, and Luna.

This is also the world developers work in through the API (the connection that wires a model straight into their own software, billed by how much they use). If you run a website chatbot or an automation, this is where the Sol, Terra, or Luna choice actually gets made, usually by your provider, not by you.

In short: the names Sol, Terra, and Luna matter most to developers. As an app user, all you really need to know is that GPT-5.6 starts at Plus in regular chat, and free plans get Terra inside Work and Codex.

What are OpenAI’s GPT-5.6 Sol, Terra, and Luna models?

OpenAI GPT-5.6 Sol, Terra, and Luna are three versions of the same new model family. The number 5.6 is the generation, and the names are the tiers, from most powerful to cheapest. Here’s what each one is and where you’d come across it.

GPT-5.6 Sol, the flagship (and the one in your app)

Sol is the most capable of the three, built for the hardest work like complex coding, deep research, and careful reasoning. It’s also the model you’re already using when you use GPT-5.6 in the ChatGPT app, so for most people Sol isn’t a decision, it’s just what you get. On the developer side, Sol is the most expensive by a wide margin, which is why developers save it for genuinely hard jobs instead of everyday ones.

GPT-5.6 Terra, the balanced middle (developer side only)

Terra is the sensible middle option: close to the previous flagship, GPT-5.5, in quality, at roughly half the cost. You can’t select Terra in the standard ChatGPT app. It lives on the developer side, where it’s the practical default for most business tools, chatbots, and automations that need good quality without paying top rates.

GPT-5.6 Luna, the fast and cheap one (developer side only)

Luna is the cheapest and fastest, meant for simple, high-volume jobs like sorting messages, tagging content, or first-draft summaries. Like Terra, it isn’t something you pick in the ChatGPT app. It’s a tool for developers keeping costs down when they run the same task thousands of times.

What’s genuinely new in this generation

Compared with the last version, GPT-5.6 is mainly better at coding, reasoning, and multi-step tasks. That’s a real gain if you build software or complex automations, and barely noticeable for everyday writing or questions. If you’d rather compare whole assistants than tiers, which is a more useful question for most owners, read our guide on ChatGPT vs Claude vs Gemini.

ModelWhere you’ll meet itWhat it’s best for
SolThe GPT-5.6 you use in the ChatGPT app (for Plus and up), and the developer sideHard reasoning, coding, research
TerraAPI, Codex, ChatGPT WorkMost everyday business tools, at lower cost
LunaAPI, Codex, ChatGPT WorkSimple, high-volume tasks, the cheapest option

How much does GPT-5.6 cost?

It depends entirely on which of the two worlds you’re in.

If you use the ChatGPT app

You pay your normal subscription and nothing per token (roughly a word or a part of a word). The free plan costs nothing, Plus is about $20 a month, and higher tiers cost more and raise the usage limits. GPT-5.6 (as Sol) is included in Plus and up, so using the newer model doesn’t cost you anything extra. The newest models do tend to reach paid plans first as the rollout continues.

If you build on the developer side

Here you pay per use, measured per roughly a million tokens of input and output. Input is everything you send the model (your question plus any background text or documents), and output is everything it writes back; you’re billed for both, and output usually costs more. These are API rates (what developers pay to plug a model into their own software, billed by how much they use rather than a flat monthly fee). Most small business owners never see these directly, since you meet them folded into the price of the AI tools you already pay for.

ModelCost per ~1M tokens inputCost per ~1M tokens output
Sol$5.00$30.00
Terra$2.50$15.00
Luna$1.00$6.00

What is GPT-Live?

GPT-Live is OpenAI’s new real-time voice model for ChatGPT, and it became the default voice experience on July 8, 2026, replacing Advanced Voice Mode. Unlike the text tiers, there’s nothing to choose and no developer side, it just shows up in the ChatGPT app. The difference is that it can listen and speak at the same time, so talking to it feels less like trading voice memos and more like a phone call.

A voice that talks more like a person

GPT-Live can be interrupted mid-sentence, pause while you think, and drop in a quick “mhmm” or “got it” the way a person does. This back-and-forth style, listening and speaking at once, is the main upgrade over the old take-turns voice.

Two versions, free and paid

GPT-Live-1 is the default voice on Go, Plus, and Pro plans, and GPT-Live-1 mini is the default on the free tier. Both are rolling out now on iOS, Android, and the web.

Smart when it needs to be

For harder questions, GPT-Live hands off to a more powerful model in the background, GPT-5.5 at launch, and keeps talking to you while it works. You can set how much it thinks before answering, and it can show visual cards for things like weather, stocks, and sports.

What it means for your business

GPT-Live suits the moments when typing gets in the way. The practical uses for a small business owner include:

  • Hands-free help while you’re doing something else
  • Dictating notes or emails
  • Practicing a sales pitch out loud
  • Getting quick answers without stopping to type

Good to know: If you already used ChatGPT’s voice feature, you don’t have to switch anything on. GPT-Live is now the default, so the upgrade arrives on its own. The older Advanced Voice Mode is still there if you need video or screen sharing.

Why GPT-5.6 launched in stages

GPT-5.6 didn’t go public the day it was announced. OpenAI previewed the models on June 26, 2026, then, at the US government’s request, limited access to about 20 vetted organizations for roughly two weeks before opening it to everyone on July 9. The reason given was the flagship’s strong cybersecurity capabilities.

OpenAI also shipped these models with its strongest safety controls yet, and reviewers rated the family high-risk for cybersecurity and biology. For normal business use, none of this changes anything you’ll notice.

This is becoming a pattern for the most capable AI. Anthropic’s Claude Fable 5 went through a similar restriction earlier in 2026 before its access was restored. For a small business owner, the practical takeaway is small: the most powerful new tools may now arrive a little later than the headlines, and that’s about it.

A sign of that pattern came a month later. On August 10, 2026, OpenAI expanded a program called Daybreak, which gives vetted security professionals access to its models with fewer restrictions, and released GPT-5.6-Cyber, a version built on Sol and trained specifically for security work. The difference is large: on OpenAI’s own test of advanced cybersecurity requests, the gated model answers 95% of them against 1.5% for standard Sol. Access requires identity checks, monitoring, legal attestations, and from September 2026 a hardware security key. The reassuring part for everyone else is what that implies about the app. The Sol you use in ChatGPT is the same underlying model with its guardrails left on, and the capabilities that needed gating now sit behind a separate door.

The bottom line

So if your plan is Plus or above, the GPT-5.6 model you use in the ChatGPT app is Sol. You can pick it yourself in the model picker (the Medium, High, and Extra High options are all Sol, at increasing levels of effort), and on paid plans the app can also switch to Sol automatically when a question looks complex, leaving quicker messages on the faster GPT-5.5. So you feel the upgrade on harder tasks, whether you select Sol yourself or let the app decide.

With that in mind, the gains show up in three specific places:

  • Research that digs through the web. Ask ChatGPT to look something up and pull it together (compare three suppliers’ pricing, summarize what changed in your industry this quarter, or check what competitors are claiming), and Sol is noticeably better than the old model at going out, reading several sources, and turning them into one clear answer. This is probably the improvement a ChatGPT app user is most likely to feel.
  • Making things, not just describing them. The generation’s biggest leap is building, and you get that through Sol in the app. A spreadsheet formula you can paste straight in, a working script to rename a folder of files, a simple web page, a fix for an automation that broke, these are far more likely to just work on the first try. If you’ve ever asked ChatGPT for a formula and then spent twenty minutes debugging it, that’s the gap that closed.
  • Long, multi-step jobs. Ask it to take a messy list, clean it, sort it into categories, and draft a follow-up for each, and Sol holds the thread where the previous model tended to lose it partway through. The more steps a task has, the more the upgrade shows.

The test: To see whether GPT-5.6’s research is actually a step up, we gave the same task to Sol and to GPT-5.5: “Compare the fees for taking online card payments with Stripe, PayPal, and Square. For each, give the per-transaction rate, any fixed per-transaction fee, monthly cost, and standard payout timing, and link your sources.” Both models got the rates right, but GPT-5.5 left us to line them up and total them ourselves. Sol fixed a scope first (each provider’s standard pay-as-you-go online checkout), put the three side by side, and worked a real example on a $100 sale. It also caught the part that actually costs you money: that Square’s cheaper online rate needs a paid plan. That level of detail is the research upgrade a ChatGPT app user is most likely to feel.

Everything else like drafting emails, replies, social posts, quick facts, or brainstorming, is essentially unchanged, and often still handled by the faster GPT-5.5 anyway. That work was already strong, so if it’s most of your day, you won’t notice the new generation much, and that’s fine.

GPT-Live is the one to actually try. The obvious part is that it sounds natural. The less obvious part is what makes it useful:

  • It can look things up mid-conversation, searching the web or thinking harder in the background and coming back with the answer, so it handles real questions, not just small talk.
  • It does live translation, a genuine sleeper feature if you ever deal with customers, suppliers, or staff who speak another language.
  • It copes with interruptions and background noise, so it actually works on the move, in the car, on the shop floor, mid-task, instead of only in a quiet room.

It’s free to try, so it’s worth ten minutes even if the text models change nothing for you.

Task What actually changedWorth acting on?
Everyday writing, emails, repliesLittle; GPT-5.5 Instant still strongNo
Quick facts and brainstormingLittleNo
Research that digs through the webSol reads deeper and synthesizes betterYes, if you do this often
Formulas, code, simple toolsSol’s biggest jump; more likely to just workYes, if you make things
Long, multi-step tasksSol holds the thread where the old model driftedYes, for complex jobs
Voice and hands-freeGPT-Live: natural, looks things up, live translationYes, try it (free)

The rule that holds up: match the tool to the job, and change your routine only when there’s a real reason to. For most owners, that means trying GPT-Live, reaching for GPT-5.6 when you research or build something, and otherwise carrying on exactly as you are, without chasing every release for its own sake.

SiteGround AI Studio chat window where you can select which LLM model to use

The simplest way to use models like these is inside a workspace that keeps the leading AI tools in one place. SiteGround AI Studio gives you access to top models by OpenAI, Anthropic, and Google (including ChatGPT, Claude, and Gemini) without requiring separate subscriptions for each provider.

[97]

The article was updated on 8/11/2026.

FAQs

What are OpenAI GPT-5.6 Sol, Terra, Luna, and GPT-Live?

OpenAI GPT-5.6 Sol, Terra, and Luna are three versions of OpenAI’s newest text models, and GPT-Live is its new voice model for ChatGPT. Sol is the most powerful, Terra is the balanced middle, and Luna is the fastest and cheapest. All became publicly available in early July 2026.

Which GPT-5.6 model am I using in the ChatGPT app?

On a paid plan like Plus, the GPT-5.6 model in the ChatGPT app is Sol, the most capable one. You don’t pick it by name, it sits behind the reasoning options, and ChatGPT uses a faster model for quick questions unless you choose otherwise.

Can I choose GPT-5.6 Terra or Luna?

Not in the standard ChatGPT app. GPT-5.6 Terra and Luna are only available on the developer side, through the API, Codex, or ChatGPT Work. If you use a tool or app built on OpenAI, its makers may have chosen Terra or Luna for you behind the scenes.

What’s the difference between Sol, Terra, and Luna?

They differ by power and price. Sol is the most capable and most expensive, Terra is a balanced middle option at about half Sol’s cost, and Luna is the fastest and cheapest. For developers, most everyday work runs fine on Terra or Luna.

What is GPT-Live, and how is it different from the old voice mode?

GPT-Live is OpenAI’s new voice model for ChatGPT, and it became the default voice experience on July 8, 2026, replacing Advanced Voice Mode. Unlike the old take-turns voice, it can listen and speak at the same time, so you can interrupt it and it responds more naturally.

Is GPT-Live free, and how do I use it?

Yes, a version is free. GPT-Live-1 mini is the default voice on the free ChatGPT plan, and GPT-Live-1 is the default on paid plans. You use it through ChatGPT’s voice feature on iOS, Android, or the web, with nothing new to install.

How much does GPT-5.6 cost?

In the ChatGPT app, nothing beyond your normal subscription, the newer model is included in your plan’s limits. On the developer side you pay per use: roughly $5 to $30 per million tokens on Sol, $2.50 to $15 on Terra, and $1 to $6 on Luna.

Do I need to do anything about this for my business?

If you use the ChatGPT app, the main change worth trying is GPT-Live, the new voice. The GPT-5.6 tiers matter mostly to developers and the tools you already use. Upgrade or switch only when you hit a real need, not because of the launch.

How to choose the right WordPress management approach: AI Agent, plugins, manual admin, or a virtual assistant

When you’re a small business owner actively running your own WordPress site, routine management tasks can quickly eat up hours you’d rather spend growing your business. Content updates, WooCommerce product changes, plugin maintenance, SEO metadata, user tasks, troubleshooting… The list never really ends, and it’s not always obvious how to get through it faster.

Here’s the thing: you can stay on top of it all if you choose the right WordPress management approach for each task. For example, some WordPress tasks are best handled by an AI Agent for WordPress, some by specialized plugins, some by manual WordPress admin, and some by a human virtual assistant (VA) or developer. This guide walks you through when to use each one, so you can match every WordPress task to the approach that handles it best and spend less time in the dashboard.

Key takeaways:

  • The best WordPress management approach depends on the task type, task volume, and level of human judgment required, not the tool name.
  • An AI Agent for WordPress is strongest for structured, repeatable, multi-step site management work.
  • WordPress plugins are best for focused features, manual WordPress admin is best for visual control, and a VA is best for judgment, communication, and coordination.
  • The strongest WordPress management setup often combines an AI Agent, specialized plugins, manual review, VA support, and developer help instead of relying on only one approach.

The business question: which WordPress management approach fits the task?

Over the years, a handful of different kinds of help have grown up around WordPress, and each is good at a different type of work. Here’s what each one is:

  • An AI Agent for WordPress is a newer kind of AI assistant that connects to your site and carries out WordPress management tasks through natural language prompts. Best for repetitive, multi-step admin work.
  • WordPress plugins are small add-on programs you install to give your site one focused feature. Best when you need a single focused capability, like an SEO tool or a chatbot.
  • A virtual assistant (VA) is a real person you hire remotely to run tasks for you. Best for anything that needs human judgment or a personal touch.
  • Manual WordPress admin simply means doing the job yourself inside the dashboard. Best for quick and one-off changes.

The right choice depends on task type, volume, and judgment

When you have something to do in WordPress, ask yourself these three quick questions:

  • What kind of task is it? Creative and visual, or structured and rule-based? Design work wants human eyes; repetitive, predictable WordPress admin work suits AI.
  • How much of it is there? Changing one WooCommerce product price is a 20-second manual job. Changing 200 is one you’ll want to hand to an AI agent for WordPress.
  • How much judgment does it need? If a wrong move would upset a customer or dent your brand, keep a person involved. If it’s mechanical and low-risk, a tool can run with it.
A digital graphic featuring five floating, translucent glassmorphism panels arranged in a staggered horizontal wave against a dark blue gradient background. From left to right, the cards display a gold circle with the WordPress logo, a white square with a coding symbol (<>), a green circle with a power plug icon, a circular portrait of a smiling man with glasses and a beard, and a white square with adjustment slider controls.

Why no single tool should handle every WordPress task

No method is good at everything. Hand a thousand repetitive product edits to a person, and you’re paying premium human time for work an AI agent could clear in minutes. Lean on AI for a delicate brand decision, and you save time but risk losing the human read that keeps customers on-side. Reach for a plugin when the job actually spans your whole site, and you’ve solved one slice while the rest stays manual.

The cost is rarely a broken result: it’s rather wasted time, wasted money, or an outcome that’s technically done but not quite what your site needed. Matching the task to the method is how you avoid paying that tax over and over.

How to think about AI Agents, plugins, manual admin, and VAs together

Picture them as a team with different specialties, not rivals competing for the same job. If you’re not sure where to start, don’t start with the tools at all, start with your own week. Look at where your time actually disappears: for example, updating WooCommerce products, improving SEO metadata, publishing posts, chasing maintenance, checking plugins, managing users, or troubleshooting errors.

Hand off the biggest, most repetitive drain first. That single move usually frees the most time, and the time you get back is time you can put into the work that actually grows your business.

In short: The best WordPress management approach depends on the work involved. Use an AI Agent for WordPress for structured and repeatable site-management tasks, plugins for focused features, manual WordPress admin for visual or technical control, and a VA for judgment-heavy work such as communication, review, coordination, and brand-sensitive decisions.

When should you use an AI Agent for WordPress?

The use of AI in the form of an AI Agent for WordPress is one of the newest and most exciting developments in the WordPress world, and it’s genuinely different from the AI chatbots or AI plugins most people have already tried. This kind of WordPress AI assistant connects directly to your site and can actually carry out tasks, such as creating a post, preparing SEO metadata, managing WooCommerce products, checking plugins, and adjusting settings, all through plain-language conversation, instead of just telling you how to do it yourself.

This means you can now trade a big pile of tedious WordPress work for a simple chat with AI. Instead of clicking through menu after menu, you type what you want in plain English, and it gets done. For a broader overview, see what SiteGround’s AI Agent for WordPress can do across content, WooCommerce, plugins, users, settings, and maintenance.

Use it for structured, repeatable WordPress tasks

An AI agent for WordPress is at its strongest on the routine work that eats your week: publishing a batch of posts, writing SEO details across dozens of pages, refreshing an outdated services page, updating prices on a long product list. These jobs are tedious precisely because they repeat, which is exactly why handing them off pays off. There’s also no learning curve to clear: you don’t get instructions to follow or code to paste, so you never have to hunt through menus to find the right setting.

A digital graphic featuring an open laptop screen displaying a WordPress administrative dashboard against a dark blue gradient background. Overlaid on the left is a floating, translucent glassmorphism chat panel showing a user prompt, "Add the new Spring Blend product..." followed by an AI status message reading "Adding..." above an empty input bar with a blue arrow button. On the right, another translucent panel displays a checklist with one completed green checkmark and two generic line placeholders. In the lower right foreground, a small badge confirms "Changes applied" next to a circular green checkmark icon, while a faint white sparkle graphic accents the left side.

Use it when one task crosses content, SEO, WooCommerce, or maintenance

Some jobs touch several parts of WordPress at once, and that’s usually where the dashboard fights you hardest, because you’re jumping between the editor, the SEO panel, the WooCommerce store, and the plugins page. An AI Agent works across your whole site in one conversation, so it can write a post, set its SEO details, add it to your menu, and check nothing conflicts, all without screen-hopping. It handles bulk work at this scale too: you can add alt text to 200 product images, translate 50 products, or restructure a set of categories from a single prompt.

Running more than one site? Advanced AI Agents like SiteGround’s AI Agent for WordPress can manage multiple WordPress sites at once, from one chat. You can connect any number of WordPress sites (on SiteGround or on other hosts) into a single workspace, then run one instruction across all of them: push a plugin or theme update to 30 sites, standardize a setting across your whole portfolio, or roll out the same content change everywhere, without logging into each one separately. For anyone running more than one site, or an agency looking after dozens of client sites, that turns a repetitive site-by-site chore into a single request.

Use it when speed matters but human review still matters

An AI agent can be fast, but it works best with you reviewing the output, not rubber-stamping it. Use it to prepare and implement the heavy lifting, then keep final approval over anything that affects customers and pricing.

Task typeWhy an AI Agent fits
Content updatesIt can help create, edit, organize, save, and publish WordPress content with review steps.
WooCommerce product tasksIt can help manage products, pricing, and store operations, including bulk changes.
MaintenanceIt can support plugin, theme, performance, and troubleshooting tasks.
SEO metadataIt can help with titles, descriptions, headings, content refresh suggestions, and internal links.
Users and settingsIt can help manage users and WordPress settings where permissions and Power Mode allow.
Multi-step workflowsIt can combine several WordPress admin steps in one conversation.

What the time savings actually look like: In our own testing across real projects, mundane WordPress tasks saw 80–95% time savings with SiteGround’s AI Agent for WordPress. One example: writing SEO metadata for 200+ product images dropped from roughly 58 hours of manual work to about 4.5 hours with AI assistance. Tellingly, half the people in the test were AI beginners. To learn more, take a look at our new AI in WordPress white paper.

When are WordPress AI plugins the better choice?

An AI plugin is a small add-on you install to give WordPress one specific feature it doesn’t have out of the box. While an AI agent ranges across your whole site, an AI plugin does a one job. You can reach for a plugin when you want a specialist that owns a single, well-defined area, and you’re happy to set it up and manage it as its own thing.

Use AI writing plugins for focused content generation

When you want AI help built into the writing experience itself, an AI writing plugin works inside the block editor, drafting, rewriting, or expanding text as you go, plus related pieces like excerpts, summaries, and alt text. A good example is the official WordPress AI plugin (from the WordPress team), which adds this kind of in-editor content generation if you’ve upgraded to WordPress 7.0.

Use SEO plugins for technical SEO controls

SEO plugins are the control panel for how search engines understand your site. They own the technical dials, page titles, meta descriptions (the short summaries shown under your link in search results), sitemaps, schema markup, redirects, and readability checks, and the best-known ones, Rank Math and Yoast, now add AI to help fill those fields.

Use chatbot plugins for visitor-facing support

A chatbot plugin is the only tool in this guide that talks to your visitors rather than helping you run the site behind the scenes. It answers common questions in real time, day and night, so buyers get a reply at 2 a.m. and you wake up to fewer repetitive emails.

Use page-builder AI for visual design support

If you design your pages in a page builder, its built-in AI can generate text, images, and whole layout sections right on the canvas, where you can see the result as you go. Builders like Elementor and Divi include this, so you can rough out a design by describing it, then fine-tune it by eye.

Pro tip: You can actually manage your plugins with an AI Agent. For example, you can ask SiteGround’s AI Agent for WordPress to find and install a plugin (just describe what you need and it locates a good option, installs it, and activates it), update one plugin or many at once (and even back up your site first, for peace of mind), and clean house by identifying and removing old, deactivated plugins you no longer use. Not sure what’s even running on your site? Ask for a list of every installed plugin and its status, and you get an audit that makes outdated or unnecessary ones easy to spot.

A digital graphic showcasing automated backend processes over a blurred WordPress plugin administration page. In the upper left, a dark translucent box captures a user request to "Update all plugins" alongside an AI status indicator reading "Updating...". Overlaid in the foreground is a large glassmorphism panel displaying a live log of sequential actions marked by sparkle icons. The log text includes "Checking updates...", "Checking up database...", "Updating Plugin “Rank Math SEO”", and "Updating plugin “WooCo”", concluding with several faint horizontal placeholder lines and a small decorative sparkle at the bottom.

When is manual WordPress admin still the best option?

AI can be pretty amazing, but sometimes the fastest, safest path is to just do it yourself. Manual admin, working directly in the WordPress dashboard, still wins whenever the task is visual, tiny, or highly technical.

Use manual admin for visual design and layout work

If you’re making aesthetic calls (like how much space sits between sections, whether an image feels balanced, where the eye lands first), those are judgments you make best by looking and adjusting in real time.

Use manual admin for one-off changes that take less than a minute

Plenty of changes are tiny and self-contained: fixing a typo, flipping a toggle, swapping out a link. When you already know exactly what needs changing and where it lives, going straight to that spot in the dashboard and doing it is the most direct path there is.

Use manual admin for custom code, CSS, or highly technical settings

When you’re editing CSS (the code that controls how things look) or touching precise technical settings, hands-on control is important. If you have the skill, doing it directly is more exact than describing the result.

Use manual admin when you need precise visual confirmation

Some changes you simply need to see before they go out. For final, public-facing review, looking at the real page with your own eyes is the point.

TaskWhy manual admin works better
Page layout designVisual judgment matters.
Gutenberg block editingDrag-and-drop control matters. (Gutenberg is WordPress’s built-in block editor.)
Page-builder changesSeeing the design preview matters.
Custom CSS or codeTechnical precision matters.
One quick setting changeFaster than explaining the task.
Final publishing reviewHuman eyes should approve public-facing changes.

When should you use a WordPress virtual assistant instead of AI?

If your budget allows it, hiring a WordPress virtual assistant is the right call whenever you need help from a real human, someone to make a judgment call, talk to another person, or protect how your business comes across. Despite the name, a virtual assistant isn’t software. “Virtual” just means they work remotely rather than from your office. A VA is a real person, usually a freelancer or contract worker, who logs into your website and handles tasks for you.

Use a VA for decisions that need judgment

Some tasks come down to a call only a person should make: which of today’s ten jobs actually matters, whether a risky change is worth it, whether something just looks wrong. A VA can help you weigh the specifics of your business and make some decisions for you.

Use a VA when real people need to talk to real people

When a customer has a major complaint, a question, or a delicate request, they can usually tell when they’re being handled by a bot, and it rarely makes them feel valued. A VA can reply as a genuine human: reading the mood, showing they understand, and handling the conversation with the care a real relationship deserves.

Use a VA to keep your brand sounding authentically human

AI chatbots can draft competent copy, but it can often read a little generic, and customers are increasingly good at spotting it. A VA who knows your business can make your content sound like a real person with a point of view, catch anything that feels off-brand, and add the small human touches that make people trust you.

Use a VA when someone needs to own a task end-to-end

A lot of real work isn’t one action but a thread that unfolds over days: a client conversation, an approval that waits on a reply, a project with moving parts. A VA can own that from start to finish, follow up, adapt as things change, and make sure nothing falls through the cracks.

Use an AI Agent to reduce the VA’s admin workload

If you hire a VA, you can still let an AI Agent for WordPress take the repetitive clicks off their plate (the bulk updates, the metadata, the routine maintenance), so your VA can spend their time on the conversations, the judgment, and the brand-sensitive work that genuinely needs a human.

How to find a good WordPress VA: Look for someone who has actually worked in WordPress, not just general “admin support.” Before hiring, check they can name the tasks you care about, ask for a reference or an example of a site they’ve managed, and start with a small paid trial task before handing over anything big. Give them their own login with only the access they need, never your main admin password, and agree how they’ll use AI: a VA who pairs an AI Agent with their own judgment will clear your work faster and cheaper than one doing it all by hand.

TaskWhy a VA fits
Client communicationRequires tone, judgment, and relationship context.
Editorial reviewRequires brand and audience understanding.
Project coordinationRequires prioritization and follow-up.
Inbox or support triageRequires human judgment.
Content polishingRequires nuance and taste.
QA after AI-assisted changesRequires accountable human review.

When are other WordPress AI management tools a better fit?

The four options so far cover the vast majority of what a small business needs. However, there are a few specific jobs that can call for something else.

Use developer AI tools when you need something custom-built

Say you want a feature that doesn’t exist yet, like a booking system wired into software you already use, or a special connection between your site and another business tool. That’s custom development, essentially, building something new rather than using something ready-made. There are AI tools that help with this, but they’re made for people who write code. In practice, this is the point where you’d hand the job to a developer (who might use those AI tools to work faster), rather than something you’d tackle yourself.

Use automation platforms when you want tasks to happen automatically

Imagine that every time you get a new order, you want the details added to a spreadsheet, and the customer added to your mailing list, without you lifting a finger. That’s what automation platforms do: they connect your different apps and pass information between them automatically, following simple “when this happens, do that” rules you set up once. The best-known ones are Zapier and Make. You don’t need to code, but you do need to spend a little time setting up each connection.

Use hosting-integrated AI when you want the least possible setup

If the idea of installing and connecting anything already feels like too much, the easiest starting point is AI that’s built right into your hosting (the service that stores your website and keeps it online). Because it’s part of the platform, there’s little or nothing to set up. SiteGround’s AI Agent for WordPress is an example: on sites hosted with SiteGround, it’s already connected and ready, with nothing to install. It also works with sites hosted elsewhere.

Use standalone tools when you want to choose your own AI provider

Most people are happy to let a tool decide which AI does the work behind the scenes. But some prefer to pick the specific AI service themselves, for example, choosing exactly which company’s AI writes their content. Tools that allow this ask you to bring your own “API key,” which is just a password-like code that links the tool to the AI service you signed up for. It gives you more control, but also more to set up and keep track of, so it mainly suits people who enjoy tinkering with the technical side. If that’s not you, you’re not missing out.

Decision matrix: AI Agent, plugins, manual admin, VA, or developer?

Run your WordPress task through the questions below. Start at the top, stop at the first line that matches what you’re trying to do, and you’ll land on the approach that usually fits best.

WordPress taskAI AgentAI pluginManual adminVADeveloper
Bulk content updatesBestLimitedTediousGoodNot needed
Long-form writingGoodBestSlowGoodNot needed
SEO titles and meta descriptions at scaleBestGoodTediousGoodNot needed
Technical SEO settingsLimitedBestGoodLimitedSometimes
Visual page designNot bestSometimesBestGoodSometimes
WooCommerce product updatesBestLimitedTediousGoodNot needed
Plugin and theme updatesBestN/AGoodGoodSometimes
Routine maintenanceBestLimitedManualGoodSometimes
Client communicationN/AN/AN/ABestNot needed
Brand strategyNot bestNot bestN/ABestSometimes
Custom codeNot suitableNot suitableIf skilledNot suitableBest
Server configurationNot suitableNot suitableHosting panelNot suitableBest
TroubleshootingGoodLimitedGoodGoodBest (complex)

Conclusion

Choosing the right WordPress management approach is not about finding one perfect tool. Once the task points toward an AI Agent, check who the AI Agent for WordPress is best for based on the site type, team, and recurring workload. It’s about recognizing what each task needs, then using the right mix. Sort a job by its type, its volume, and the judgment it takes, and the answer usually becomes clear.

If the task is…Choose
Structured, repeatable, or multi-stepAn AI Agent for WordPress
A focused AI feature, such as writing, SEO scoring, a chatbot, or designA WordPress plugin
Visual layout, a quick one-off edit, or a direct setting changeManual WordPress admin
Client communication, creative review, coordination, or brand-sensitive workA virtual assistant
Custom code, database work, integrations, or server configurationA developer
A high-impact live-site changeUse staging (a safe test copy of your site), backups, Power Mode safeguards, and human review

Ready to see how AI can help with routine WordPress management? Put SiteGround’s AI Agent for WordPress to work on your next batch of repeatable WordPress tasks.

[97]

FAQs

What is the best WordPress management approach for a small business?

The best WordPress management approach for a small business depends on the work. Use an AI Agent for WordPress for structured and repeatable site-management tasks, plugins for focused features, manual admin for visual or one-off changes, and a VA for communication, coordination, and judgment-heavy work. Most small businesses end up using a mix.

When should I use an AI Agent for WordPress instead of manual admin?

Use an AI Agent for WordPress for repetitive work, multi-step AI Agent workflows, or tasks spread across several areas of WordPress. Manual admin is still better for visual design, quick one-off changes, custom code, and the final review before publishing.

Is an AI Agent for WordPress better than WordPress AI plugins?

They solve different problems. An AI Agent for WordPress is better for site-management tasks across your whole site, while WordPress AI plugins are better for focused features such as writing, SEO scoring, chatbots, or design assistance. The full comparison of AI plugins vs AI agents for WordPress explains where each category fits.

Should I hire a WordPress virtual assistant or use an AI Agent for WordPress?

Use an AI Agent for WordPress for structured admin work like content updates, WooCommerce product changes, plugin checks, SEO metadata, and routine maintenance. Hire a VA for human judgment, brand-sensitive review, client communication, coordination, and ongoing quality control. Many businesses use both.

Can an AI Agent for WordPress and a virtual assistant work together?

Yes, and it’s a strong setup. A VA can use the AI Agent for WordPress to finish routine admin work faster, then focus on review, communication, prioritization, and brand-sensitive decisions. The agent handles the repetitive clicks; the VA handles the judgment.

When is manual WordPress admin better than AI?

Manual admin is better for visual page design, page-builder edits, drag-and-drop layout work, custom settings, direct code edits, and quick one-off changes that are faster to make than to explain through a prompt.

Is SiteGround’s AI Agent for WordPress easy to set up compared with other AI tools?

It’s designed to be. SiteGround’s AI Agent for WordPress works through SiteGround AI Studio and can manage connected WordPress sites through chat. SiteGround-hosted sites are connected automatically. Externally hosted WordPress sites can connect through the AI Agent by SiteGround plugin, while many standalone AI plugins require you to create AI provider accounts and manage your own API keys.

Can an AI Agent for WordPress replace a WordPress developer?

No. An AI Agent for WordPress can help with site-management tasks, but a developer is still needed for custom code, advanced integrations, theme development, database work, and server-level architecture, and complex troubleshooting.