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.
A slow WordPress site is not just annoying. It costs you rankings, conversions, and money. Google’s data shows that when load time goes from 1 to 3 seconds, bounce probability jumps 32 percent. 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. Fix Your Hosting First
Hosting is the biggest speed lever there is. No amount of caching plugins can fix a server that takes two seconds to respond. If your TTFB (time to first byte) is over 600ms on repeat tests, your host is the problem.
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. It is the fastest option because it talks directly to the server. 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 the number one cause of 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.
The Quick Wins Checklist
Baseline test with PageSpeed Insights
Upgrade hosting if TTFB is over 600ms
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.
AI website builders promise a finished site in 60 seconds. WordPress powers over 40 percent of the web. 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 ADI 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: speed, zero learning curve, hosting included, no maintenance. Where they fall short: the copy is generic until you rewrite it, design options hit a ceiling fast, SEO control is limited, and you can never move the site off their platform.
What WordPress Delivers
WordPress is not a builder, it is a foundation. You own the files, the database, and every ranking the site ever earns. Any feature you can imagine exists as a plugin. Any designer can work on it after me, or before me.
Where it shines: ownership, SEO control, unlimited customization, no monthly platform tax. 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 forever
$5 to $40 hosting
You own the site
No
Yes
SEO ceiling
Low to medium
As high as you want
Custom features
Limited
Unlimited
Best for
Testing an idea
Building an asset
The Decision in One Paragraph
If you are validating a brand-new business and might pivot in 3 months, use an AI builder and do not overthink it. If your business depends on Google traffic, local search, or you plan to be around in 5 years, build on WordPress. The businesses that regret their choice are almost always the ones that grew on a builder and then discovered they could not take anything with them.
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 for easy keywords, but you hit a ceiling. Limited schema control, slower pages, and thin content tools make competitive rankings harder.
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?
At $30 a month average, about $1,800, and you own nothing at the end. A $2,000 WordPress build plus cheap hosting costs about the same and you own everything.
Can I move my Wix site to WordPress later?
Your content can move, your design and SEO signals mostly cannot. It is a rebuild, not a transfer.
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.
Disclosure: This post contains affiliate links. If you buy through them I may earn a commission at no extra cost to you.
I have been building WordPress sites since 2007, and hosting is the number one thing my clients get wrong before they come to me. Slow, oversold hosting kills your Google rankings and your patience. These are the hosts I actually put client sites on in 2026, in order of who should use them.
SiteGround is my default recommendation for most small business sites. Speed is solid, their WordPress tools handle caching and updates for you, and support responds fast when something breaks.
Pros: fast managed WordPress setup, excellent support, free email hosting included Cons: renewal prices are higher than the intro rate Pricing: intro plans start around $3 to $8/month
If your budget is tight, Hostinger gets you online for a few dollars a month with decent speed. This very site runs on Hostinger. Just know you will likely upgrade within a couple of years as traffic grows.
Pros: cheapest way to start properly, decent performance for the price Cons: support is slower, renewal prices jump Pricing: starts under $5/month
WP Engine is what I use when a client has outgrown budget hosting. Built-in staging, daily backups, and their support team knows WordPress specifically, not just servers.
Pros: WordPress-specific support, great developer tools, includes premium themes Cons: overkill for a brand new site Pricing: starts around $20 to $30/month
Kinsta: best premium option when downtime is not acceptable
I recommend Kinsta when a business cannot afford downtime. Google Cloud infrastructure, free migrations, and support that actually answers.
Pros: fast out of the box, excellent dashboard, free staging Cons: no email hosting included, premium price Pricing: starts around $35/month
How I actually choose for clients
Under 5,000 visits/month and tight budget: Hostinger
A business site that produces revenue: SiteGround
Ecommerce or multiple sites: WP Engine or Kinsta
FAQ
Is cheap hosting really that bad? For a hobby site, no. For a business, yes. A one second delay in load time measurably drops conversions, and budget hosts get slow at exactly the moment your site gets popular.
Should I use hosting resold by my web designer? Only if they are transparent about which company is behind it. I set clients up on their own accounts so they always own their site.
Can you migrate my site for me? Yes. I do migrations and full site builds. Get in touch here.
Need help picking or migrating? I have done this hundreds of times. Contact me and I will point you the right way even if you do not hire me.
In the digital age, where having a visually appealing responsive web design is paramount, it's essential to master the latest CSS techniques to create captivating, user-friendly websites. One such innovation that has profoundly impacted web design in recent years is CSS Grid, a powerful layout system that enables developers to create dynamic and responsive grid-based designs with ease.
In this comprehensive guide, we will delve into the exciting world of CSS Grid, exploring its core concepts, benefits, and applications in WordPress web design. From understanding the versatile features of CSS Grid to implementing responsive and engaging layouts in your website, this article will help you harness the power of CSS Grid to create visually stunning, highly functional WordPress websites.
In addition to educating you on the intricacies of CSS Grid, this guide also offers practical examples, hands-on tutorials, and valuable resources to help you implement the techniques effectively and efficiently. We aim to empower you to create websites that cater to modern design preferences and provide exceptional user experiences.
Understanding the Core Concepts of CSS Grid
Before diving into the practical implementation of CSS Grid in WordPress web design, familiarize yourself with the essential concepts behind this innovative layout system.
Grid Container: The parent element that holds the entire grid layout and controls its properties, such as the number of columns, rows, and gaps.
Grid Items: The individual content elements placed within the grid container can be organized and manipulated using CSS Grid properties.
Grid Lines: The vertical and horizontal lines delineate the grid columns and rows, providing a flexible reference system for positioning grid items.
Grid Tracks: The spaces between adjacent grid lines form the columns and rows that make up the grid layout.
Unveiling the Benefits of CSS Grid in WordPress Web Design
CSS Grid offers several advantages over traditional layout techniques, making it a powerful tool for creating responsive and modern web layouts in WordPress.
Responsive Design: Easily create fluid and adaptable layouts that adjust seamlessly to different viewport sizes and screen resolutions.
Unprecedented Flexibility: Design complex, nested grid layouts easily, thanks to CSS Grid's versatile features and easy-to-use syntax.
Simplified Code Structure: Minimize using floats, clears, and other cumbersome CSS techniques, resulting in cleaner and more maintainable code.
Superior Browser Support: With most modern browsers supporting CSS Grid, you can confidently implement grid-based designs while maintaining cross-browser compatibility.
Applying CSS Grid Techniques in WordPress Web Design
Once you've grasped the essentials of CSS Grid, you can begin incorporating its powerful features into your WordPress website with these practical strategies.
Start with a Mobile-First Approach: Design your grid layouts with mobile devices in mind, using media queries to enhance your layout for larger screen sizes progressively.
Employ the `fr` Unit for Fluid Grids: Utilize the flexible `fr` unit for defining grid tracks, which automatically adjusts your layout to fill available space and create a fluid grid system.
Leverage Grid Template Areas for Clarity: Define named grid template areas in your grid container to simplify the positioning of grid items and improve the readability of your code.
Combine CSS Grid with Flexbox: Use CSS Grid for overall layout structure and Flexbox for grid item arrangement, capitalizing on each layout system's unique strengths.
Tapping into WordPress Themes and Plugins for CSS Grid Compatibility
Embrace CSS Grid in your WordPress workflow by exploring themes, plugins, and resources specifically designed to support grid-based layouts.
Choose CSS Grid-Ready Themes: Opt for WordPress themes built with CSS Grid in mind, such as Astra, GeneratePress, or Neve. These themes usually offer built-in support for grid-based layouts, making creating and customizing your website's design easier.
Integrate Page Builders with CSS Grid Support: Many popular WordPress page builders like Elementor, Beaver Builder, and Divi incorporate CSS Grid functionality, allowing you to design grid layouts within the page builder interface intuitively.
Explore CSS Grid-Based Plugins: Discover plugins like WP Grid Builder, Essential Grid, and GridKit that provide dedicated grid-building tools and options, further enhancing your web design process.
Conclusion
Mastering the power of CSS Grid in WordPress web design can transform how you create responsive, visually engaging websites that leave a lasting impression on your audience. By understanding the fundamental concepts, harnessing the numerous advantages, implementing practical strategies, and leveraging supportive themes and plugins, you can revolutionize your WordPress web design journey and easily create modern, captivating, and user-friendly websites.
Don't hesitate to experiment with various CSS Grid techniques, learn from your experiences, and stay informed about this groundbreaking layout system's latest updates and developments. Embracing the world of CSS Grid bolsters your web design skills and empowers you to create captivating websites that stand out from the competition and truly resonate with your target audience.
At Nick Throlson, our team of proficient web designers and developers is committed to amplifying your brand's web presence with meticulously crafted, modern, and engaging responsive WordPress websites tailored to your unique requirements. If you need WordPress development services, get in touch with us today!
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
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.
