WordPress 7.0 shipped on May 20, 2026, and I have now run it across enough client sites to tell you what actually matters and what is just release-note noise. Here is the short version: this update does not put AI on your website. It puts in the plumbing that lets other things put AI on your website. That distinction is the whole story, and it changes what you should be doing over the next few months.
If you have been quietly ignoring the update prompt in your dashboard, this one is worth ten minutes.
What actually shipped in WordPress 7.0
The release, codenamed Armstrong, was originally targeted for April to line up with WordCamp Asia. Leadership pushed it back roughly six weeks to stabilize the AI infrastructure and finish the admin redesign. What landed on May 20:
The AI Client, a provider-agnostic PHP interface built into core
The Abilities API, a central registry of named actions your site can expose
A Connectors hub in wp-admin where you authenticate outside AI providers
An optional official AI plugin for generating titles, excerpts, alt text, and images
The first real visual refresh of wp-admin in over a decade, including a Command Palette
PHP-only blocks, so developers can ship blocks without touching React
A minimum PHP bump to 7.4, dropping support for 7.2 and 7.3
Notice what is not on that list: a chatbot, an AI writer in your editor, or anything that starts generating content the moment you hit update. Core shipped the wiring, not the appliance.
The AI Client, explained without the jargon
Before 7.0, every AI plugin rolled its own connection to OpenAI or Claude or whoever else. Each one wanted its own API key, stored it in its own settings page, and broke in its own creative fashion when a provider changed an endpoint. Three AI plugins meant three integrations to maintain and three places for a key to leak.
The AI Client replaces that with one standardized interface in core. A plugin sends a prompt through it and gets a response back in a predictable format, regardless of which model is on the other end. You authenticate providers once in the Connectors hub, and plugins request access through core rather than hoarding credentials.
For you as a site owner, the wins are simple. Fewer places to store API keys, fewer plugins doing sketchy things with your credentials, and the ability to swap model providers without rebuilding every AI feature on the site. That last one matters more than people realize, because AI pricing keeps moving and vendor lock-in is how you end up overpaying.
The Abilities API is the part that actually matters
If the AI Client is the wire, the Abilities API is the outlet. It is a registry where plugins, themes, and core itself declare named actions along with input rules, output rules, and permission checks. Things like create_order, list_products, get_inventory, or schedule_post.
Here is why that beats the AI writing features everyone is talking about. Once your site publishes a structured list of what it can do and who is allowed to do it, an AI tool can operate your website instead of just writing text for it. A support assistant that genuinely looks up an order status. A tool that checks live inventory before answering.
WordPress.com has already expanded its AI agent from read-only access to actual write actions, and the guardrails they built are the model everyone should follow: changes need explicit approval, new posts default to drafts, deletions stay reversible where possible, activity shows in the site log, permissions follow existing WordPress user roles, and every operation can be switched on or off individually.
Take that list and treat it as your checklist. Any AI plugin that wants write access to your site and does not offer approval gates, role-based permissions, and an audit log has no business being installed on a site that makes you money.
The admin redesign you will notice on day one
The dashboard got its first serious visual overhaul in more than ten years. The static list tables you have stared at since WordPress 3.x are replaced by React-based DataViews. There is a proper font management page, visual revision scrubbing, and a Command Palette you open with Cmd+K.
The Command Palette is the sleeper feature. Instead of hunting through menus to reach a settings page or jump to a specific post, you hit Cmd+K and type. If you manage a lot of sites, it changes how fast you move.
Fair warning though. A redesigned admin means your staff and your clients open the dashboard and find things moved. If you hand off site access to anyone, plan a short walkthrough before you update, not after the panicked phone call.
What got pulled from the release
Real-time collaboration, the feature most people were actually waiting on, was cut twelve days before launch over performance and server load concerns, and postponed to a future version. If your plan this year involved multiple people editing the same post at once in WordPress, keep whatever workaround you have. I would rather they pull a feature than ship one that hammers shared hosting, but it does mean the update is less transformative on day one than the buildup suggested.
Check your PHP version before you do anything else
This is where I see small business sites break, every single release cycle. WordPress 7.0 requires PHP 7.4 minimum. Support for 7.2 and 7.3 is gone.
If you are on budget shared hosting that has not touched its PHP defaults in years, you may be sitting on an older version and not know it. Check under Tools then Site Health then Info in your dashboard. If you are below 7.4, do not update WordPress until your PHP is current. And honestly, 7.4 is the floor, not the target. Run PHP 8.2 or higher if your plugins support it, because the performance difference is significant and older versions stopped getting security patches a long time ago.
There is a second hosting consideration nobody put in the release notes. AI features mean outbound API calls, and the React-based admin is heavier than the old list tables. On cheap hosting, both show up as a sluggish dashboard. If your admin already felt slow, it will feel worse after this update, and that is a hosting problem rather than a WordPress problem. I broke down the usual culprits in my guide on how to speed up a slow WordPress site.
If your current host cannot give you a modern PHP version without an upsell call, that is your answer about whether to stay. I keep client sites on hosts that stay current without being asked. Hostinger is where I put budget-conscious sites that still need real performance, and SiteGround is my pick when a client needs stronger support and staging built in. I compared the options I actually use in my best WordPress hosting guide.
What I am telling clients to do right now
Five steps, in this order.
1. Confirm your PHP version first. Site Health tells you in about fifteen seconds. Fix it before updating core, not after.
2. Update on staging, not production. This is a major version with a redesigned admin and new APIs, and every plugin you run interacts with that. Test it somewhere that does not cost you customers if it breaks. If your host does not offer staging, that is another reason to move.
3. Audit your existing AI plugins. If you picked up AI tools over the last two years, several of them are now doing redundantly what core does natively. Every plugin you remove is one less security surface, one less update to babysit, and one less thing slowing your admin down. I keep a running list of the tools that survive my own audits in my post on the AI tools I actually use for small business clients.
4. Do not connect a provider until you know what it can touch. The Connectors hub makes authentication easy, which also makes it easy to hand broad access to something you have not vetted. Check what abilities a plugin registers and what permissions it wants before you authorize it.
5. Leave real-time collaboration out of your plans. It is not shipping in this version. Plan around the tools you have.
The part most small business owners are missing
The Abilities API is quietly the most important thing in this release, and it has almost nothing to do with writing blog posts.
What it sets up is a future where AI tools interact with your website as a system rather than as a page of text. That means the structure of your site, your product data, your inventory, your service descriptions, and your schema all start mattering in a new way. A site with clean, structured, well-labeled data becomes usable by AI agents. A site with everything crammed into unstructured page builder content does not.
That is the same lesson showing up in search right now, where clear structure and direct answers are what get a business quoted in AI results. I covered that side of it in my post on how small businesses get cited in Google AI Overviews. Different surface, same underlying requirement. Structure your content properly and machines can use it. Leave it messy and you get skipped.
So the real takeaway from WordPress 7.0 is not “install the AI plugin.” It is “get your site data and structure in order, because the tools that read it are about to get a lot more capable.”
Where this leaves you
WordPress 7.0 is a foundation release. It is not going to redesign your homepage or write your service pages. What it does is make WordPress a platform AI tools can plug into properly, with permissions and audit trails instead of a pile of competing plugins each holding their own API key.
The sites that benefit are the ones that are technically current: modern PHP, a host that keeps up, a lean plugin stack, and content that is actually structured. The sites that suffer are the ones on old PHP with fifteen overlapping plugins and everything locked inside a page builder. Getting from the second group to the first is most of the work, and it is the part people put off.
If you would rather not spend your weekend checking PHP versions and testing a major update on staging, that is what I do. I handle WordPress updates, hosting migrations, performance work, and site recovery for small businesses, and I have been doing it since long before anybody put AI in a release note. Head over to webguynick.com and tell me what your site is doing. I will tell you straight whether it needs work or whether you are fine to sit tight.
AI Overviews can change how people discover a small business website. The useful response is to make your pages clear, credible, and easy to use, then measure what happens. There is no setting that guarantees a citation.
What Google Requires
Google says a supporting page must be indexed and eligible to appear in Search with a snippet. Its usual search requirements apply; there is no special AI schema or separate optimization requirement. Start with Google's official guidance on AI features.
Start With Your Own Search Data
A traffic change can have several causes. In Search Console, compare the same pages and queries across equivalent periods, then check which pages lost clicks or impressions. Review important landing pages on your phone and test the next step a visitor should take. Write down the issue before choosing a fix.
A Practical Content Checklist
Answer the reader's actual question with clear, specific language.
Use headings that describe the page's sections.
Support claims with examples, sources, or evidence from real work.
Link to related pages that help the reader continue.
Keep your business details accurate and current.
These are useful editorial habits, not a formula for winning an AI citation. Here is how I approach them.
Lead With the Answer
The single biggest change I make on client sites is rewriting opening paragraphs. Readers should not have to search for the point. Answer the main question early, then use the rest of the page to explain, support, and add depth.
I also add what I call an answer capsule under each H2: two or three sentences that directly answer the question the heading asks, followed by supporting detail. That structure gives readers a clear answer and room to inspect the supporting detail. Add a specific example or source when it helps explain the claim.
Make Your Pages Easy to Read
Clear structure helps visitors find the information they need. My checklist:
One clear H1, descriptive H2s phrased as questions people actually search.
Paragraphs of two to four sentences. No walls of text.
Bullet lists for steps and comparisons, tables for pricing or specs.
Answers to real customer questions, written for the reader.
Accurate structured data that matches the visible page and the type of business.
If you are on WordPress, most of this is built into the block editor plus a good SEO plugin. Modern versions of Rank Math and Yoast will handle the schema and flag structure issues right in your dashboard.
Show Real Experience, Not Generic Advice
Show the work behind your advice: a specific problem, what you tried, what changed, and the limits of the result. Use original screenshots or project examples when you have permission to share them. Do not invent results or add first-person claims solely for search.
Keep Your Business Info Consistent Everywhere
Keep your name, address, phone number, hours, and services accurate across your website, Google Business Profile, and relevant directories. Old or contradictory details make it harder for customers to know how to reach you. Review these listings when your business changes, and respond to reviews thoughtfully.
If you want a structured way to audit all of this, my 10 point website checkup covers the same items I run for clients.
Do Not Skip the Technical Basics
Check that important pages can be crawled and indexed, and that their main content is available to visitors. Then investigate performance issues that make the site frustrating to use. Core Web Vitals still count, so start with my guide on how to speed up a slow WordPress site. If you are evaluating hosting such as Hostinger, compare caching, support, renewal costs, and measured response times before deciding to move. A different host alone does not guarantee better search results.
Diversify Before Google Makes You
Even if you do everything right, zero-click search means Google owns less of your future than it used to. The small businesses winning right now treat their website as home base and build traffic sources they control. Grow an email list from day one. Repurpose every blog post into short vertical videos for YouTube, Instagram, and TikTok, which is something a tool like AutoShorts can automate for you. And lean on AI to keep your output sustainable. I covered my full stack in the 9 AI tools I actually use for small business clients.
Where to Start This Week
Do not try to overhaul your whole site at once. Here is the order I follow:
Find your five pages with the most impressions in Search Console and rewrite their openings to answer the query in the first 100 words.
Answer the questions customers actually ask on your top service page, and link to supporting guides.
Fix your business info everywhere it appears, starting with your Google Business Profile.
Record the changes and review the affected pages in Search Console over time. Compare leads and useful visits as well as clicks.
If you would rather have someone handle it for you, this is exactly the kind of work I do every day at Web Guy Nick. Start with an AI Visibility Audit and I will show you exactly where your site stands, what is holding it back, and which fixes to make first.
Disclosure: some links in this article are affiliate links. If you buy through them, I may earn a commission at no extra cost to you.
A slow WordPress site makes it harder for visitors to read, browse, and contact you. Start by measuring the problem, then change one thing at a time so you can see what actually helps. I have been fixing slow WordPress sites since 2007, and the good news is that most of them share the same handful of problems. Here is exactly how I approach it in 2026.
1. Test Before You Touch Anything
Run your site through PageSpeed Insights and note your Core Web Vitals: LCP, INP, and CLS. Screenshot the results. You need a baseline so you know which changes actually helped. Test your homepage plus your most important landing page, since they often behave very differently.
2. Check Server Response Before Changing Hosts
A slow initial response is a reason to investigate, not proof that your host is at fault. Time to first byte includes redirects, connection setup, network latency, and server processing. Compare several tests, check whether page caching is working, and look for slow plugins or database queries before paying for a migration. Google's TTFB guide suggests 0.8 seconds or less as a rough target, while explaining why context matters.
Two hosts I put my own clients on:
SiteGround for business sites that need speed and solid support. Their caching stack is excellent out of the box.
Hostinger when budget matters. Their LiteSpeed servers punch way above their price point.
I compared these in more depth in my WordPress hosting guide if you want the full breakdown.
3. Set Up Caching Properly
If you are on a LiteSpeed server (Hostinger and many others), use the LiteSpeed Cache plugin. Its server-level page caching is designed for LiteSpeed, so check that the server and plugin are configured together. On other hosts, WP Rocket is worth the license. One caching plugin only. Running two at once is one of the most common causes of broken, slow sites I get called in to fix.
4. Optimize Your Images
Oversized images are a common contributor to slow LCP scores. Three rules: serve WebP or AVIF, resize images to the dimensions they actually display at, and lazy load everything below the fold. Plugins like ShortPixel or the built-in optimization in LiteSpeed Cache handle all three automatically.
5. Cut the Plugin Bloat
Every active plugin adds PHP execution time, and many load CSS and JavaScript on every single page. Audit your plugin list twice a year. If you have not used it in six months, delete it. Deactivated plugins are still a security risk, so remove them completely.
6. Put a CDN in Front of It
Cloudflare's base plan covers most sites and takes about 15 minutes to set up. Your static files get served from a location near each visitor instead of making every request travel to your origin server. If you are on SiteGround, their built-in CDN works well too.
7. Clean Up Your Database
Years of post revisions, spam comments, and expired transients add up. WP-Optimize or the database tools in LiteSpeed Cache can clear these safely. Always take a backup first. On older sites I regularly recover 30 to 50 percent of the database size.
How to Check Whether a Fix Worked
Repeat the same page tests on mobile and desktop, under similar conditions. Compare the numbers with your saved baseline and check that the menu, forms, images, and checkout still work. A faster score is not a successful fix if visitors can no longer use the page.
PageSpeed Insights separates recent real-user experience, when available, from a single lab test. Use the lab results to investigate a problem and watch the real-user trend over time. Keep a short log of the change, date, page tested, and result so the next improvement starts with evidence.
The Quick Wins Checklist
Baseline test with PageSpeed Insights
Investigate slow server responses before choosing a hosting upgrade
One caching plugin, configured correctly
WebP images, sized right, lazy loaded
Delete unused plugins entirely
Cloudflare or host CDN enabled
Database cleaned quarterly
Want It Handled For You?
Speed work is measurable, which is why I like it. Before and after numbers do not lie. If you would rather have someone who does this every week take care of it, I offer site speed optimization and ongoing care plans through my agency. Start with my website checkup checklist to see where your site stands, or head to webguynick.com and tell me about your site.
Disclosure: some links in this post are affiliate links. I only recommend hosts I actually put client sites on, and it never changes what you pay.
Get the host and setup notes
Short and honest: this is the host I use for client sites. Fast servers fix a lot of speed problems before you touch a plugin. Affiliate disclosure: if you buy through my link I may earn a commission at no extra cost to you.
AI website builders promise a finished site in 60 seconds. I build with both, and the honest answer is that each one wins in different situations. Here is how to pick without wasting six months finding out you chose wrong.
What AI Builders Actually Deliver
Type a description, get a site. Wix and Hostinger’s AI builder genuinely work for this. In my testing you get a clean single-page or 5-page site with stock images and placeholder-quality copy in under 10 minutes.
Where they shine: quick first drafts, included hosting, and platform updates handled by the provider. Where they fall short: the copy needs review, design and search controls vary, and export options may be limited. Check the platform and plan before committing.
What WordPress Delivers
WordPress is not a builder, it is a foundation. With self-hosted WordPress, you control your site files and database and can choose where to host them. Search rankings still depend on the site and its content. Its themes, plugins, and developer ecosystem offer many ways to extend a site. Compatibility, security, budget, and ongoing maintenance still matter.
Where it shines: hosting choice, flexible search controls, and extensive customization options. Where it falls short: it needs hosting, updates, and either your time or a pro to set up right. Good hosting like SiteGround handles most of that for you.
Head to Head
Factor
AI Builder
WordPress
Time to launch
Same day
1 to 4 weeks done right
Up front cost
$0 to $100
$500 to $5,000
Monthly cost
$15 to $50 per month
$5 to $40 hosting
Hosting portability
Check export options
Choose your host
SEO controls
Varies by platform and plan
Flexible, but requires setup
Custom features
Check integrations and plan limits
Plugins or custom development
Best for
Testing an idea
Building an asset
The table gives illustrative planning ranges, not quotes. Check current pricing, renewal terms, and what each proposal includes.
Five Questions to Ask Before You Commit
Can I edit page titles, descriptions, URLs, and redirects?
Can I export the content and move the domain if my needs change?
Who handles backups, software updates, and recovery?
Does the quoted price include renewal fees, email, forms, and the integrations I need?
Can I test the important mobile tasks before launch?
If you need to test a straightforward idea quickly, an AI builder can be a practical starting point. If you need more hosting choice, integrations, or custom development, self-hosted WordPress may fit better. Choose for your content, budget, maintenance capacity, and next few years of work. Neither choice guarantees search traffic.
The Hybrid Move Nobody Talks About
Start with the AI builder to nail down your content and structure cheap, then have a pro rebuild it on WordPress once revenue proves it. I have done this migration for clients and it works, just know the rebuild is a full project, not an export button.
WordPress vs AI Builder FAQ
Can AI builders rank on Google?
Yes. The platform alone does not set a site's ranking ceiling. Compare crawlability, useful content, page experience, redirects, and the controls you need before choosing a builder.
Is WordPress harder to use than an AI builder?
Day one, yes. Day 100, no. Editing pages and posts in WordPress is simple once the site is built. The hard part is the initial build, which is what you hire out.
What does an AI builder really cost over 5 years?
A plan that stays at $30 a month totals $1,800 over five years, before extras. A WordPress build quoted at $2,000 plus $10 a month for hosting totals $2,600 over the same period, before domains, maintenance, and paid tools. These are examples, not quotes: compare the full scope and renewal terms.
Can I move my Wix site to WordPress later?
Moving platforms usually requires rebuilding the design and checking what content can be exported. Preserve useful content and existing URLs where possible. Map changed URLs to their closest equivalents with permanent redirects, update internal links, and monitor the move in Search Console. Rankings can fluctuate during a migration.
Not Sure Which Side You Land On?
Email me your situation and I will tell you straight, even if the answer is an AI builder and not me. I reply within 24 hours.
Some links on this page are affiliate links. If you buy through them I may earn a commission at no extra cost to you. I only recommend tools I actually use.
Short answer: most small businesses spend between $500 and $5,000 to get a website launched in 2026, then $30 to $150 a month to keep it running. Where you land in that range depends on one decision: build it yourself, hire a freelancer, or hire an agency.
I have built WordPress sites for small businesses since 2007, so the numbers below come from real projects, not guesses.
The Three Ways to Get a Website (and What Each Really Costs)
1. DIY With a Website Builder: $0 to $500 Up Front
Tools like Wix or Hostinger’s AI builder can get a basic site live in a weekend. Expect $15 to $50 a month for the platform, plus a domain at about $15 a year.
Good fit if you just need an online business card and you have more time than money. The tradeoff is your time, template-looking design, and hitting a wall the first time you need something custom.
2. Freelance Web Designer: $1,500 to $5,000
This is the sweet spot for most small businesses. A freelancer builds you a custom WordPress site you own outright, usually in 2 to 4 weeks. My own projects typically land in this range depending on page count and features.
What drives the price up or down: number of pages, e-commerce, booking systems, copywriting, and how much SEO work is included.
3. Agency: $5,000 to $25,000+
Agencies bring teams: strategist, designer, developer, project manager. If you are a funded startup or an established company with complex needs, this is your lane. Most local small businesses do not need agency pricing to get agency-quality results.
Paying monthly for page builders they never use, buying premium plugins that duplicate free ones, paying for SEO packages with no reporting, and rebuilding from scratch every 3 years because the last site was built on a platform they could not export from. A WordPress site you own avoids that last one entirely.
Cost vs Value: The Math That Matters
A $2,000 website that brings you two $1,500 clients has paid for itself and then some. A free website that never ranks and loads slow costs you every customer who searched and found your competitor instead. Price the outcome, not the invoice.
Small Business Website Cost FAQ
Can I get a professional website for under $1,000?
Yes, if you keep it to 3 to 5 pages and provide your own text and photos. Ask for a fixed quote up front.
Is WordPress cheaper than Wix long term?
Usually. Wix costs more per month forever and you cannot take the site with you. WordPress hosting runs $5 to $15 a month and you own everything.
How much should I budget per month after launch?
$30 to $150 covering hosting, domain, and basic maintenance. E-commerce sites run higher.
Do I need to pay for SEO separately?
Basic on-page SEO should be included in any decent build. Ongoing SEO campaigns are a separate service, typically $300 or more a month.
Want a Real Number for Your Project?
I build WordPress sites for small businesses and give fixed quotes with no surprises. Email me here and I will reply within 24 hours with a straight answer.
Some links on this page are affiliate links. If you buy through them I may earn a commission at no extra cost to you. I only recommend tools I actually use.
We use cookies to improve your experience on our site. By using our site, you consent to cookies.
Cookie Preferences
Manage your cookie preferences below:
Essential cookies enable basic functions and are necessary for the proper function of the website.
Name
Description
Duration
Cookie Preferences
This cookie is used to store the user's cookie consent preferences.
30 days
These cookies are needed for adding comments on this website.
Name
Description
Duration
comment_author
Used to track the user across multiple sessions.
Session
comment_author_email
Used to track the user across multiple sessions.
Session
comment_author_url
Used to track the user across multiple sessions.
Session
Google reCAPTCHA helps protect websites from spam and abuse by verifying user interactions through challenges.
Name
Description
Duration
_GRECAPTCHA
Google reCAPTCHA sets a necessary cookie (_GRECAPTCHA) when executed for the purpose of providing its risk analysis.
179 days
Google Tag Manager simplifies the management of marketing tags on your website without code changes.
Name
Description
Duration
cookiePreferences
Registers cookie preferences of a user
2 years
td
Registers statistical data on users' behaviour on the website. Used for internal analytics by the website operator.
session
Statistics cookies collect information anonymously. This information helps us understand how visitors use our website.
Jetpack's built-in visitor analytics. It records page views, referring sites, search terms, and outbound link clicks, and also carries the shared visitor-tracking library used by Jetpack Instant Search and WooCommerce Analytics.
