WordPress 7.0 Lands With Built-In AI, While Agencies Tackle Bots and Rebuild Community

The WordPress ecosystem saw a busy stretch this month. WordPress 7.0 “Armstrong” shipped with native AI features and a redesigned admin interface. Kinsta published back-to-back guides on diagnosing and fixing bot traffic problems that drain server resources. Meanwhile, two WP Tavern podcast episodes tackled how agencies are actually using AI day-to-day and why local WordPress meetups are still struggling to recover post-pandemic.

Key Takeaways

• WordPress 7.0 “Armstrong” introduces a central AI hub, a new admin theme, and expanded developer tools.
• Scaling hosting infrastructure does not solve bot traffic problems — it just raises the bill.
• Sites can cut bandwidth waste from bots without accidentally blocking real visitors.
• WordPress agencies are connecting AI to internal documentation, QA workflows, and client tools via MCPs.
• Local WordPress meetups and community events are still fighting to regain pre-pandemic attendance.

WordPress 7.0 “Armstrong” Ships With Native AI and a Fresh Dashboard

WordPress 7.0, codenamed “Armstrong,” is now live. The headline feature is a central AI hub built directly into the dashboard. Site owners can access AI capabilities without third-party plugins for the first time. The release also includes a sleek new admin theme applied across the entire backend, new blocks, and additional design tools.

Developers get an expanded toolbox. WordPress.org says the update gives builders “more control than ever.” The naming follows the project’s tradition of honouring jazz musicians — this one tips its hat to Louis Armstrong.

More info: https://wordpress.org/news/2026/05/armstrong/

Upgrading Your Hosting Plan Won’t Fix a Bot Problem

Kinsta published a detailed breakdown of a common misdiagnosis. When a client site’s resource usage climbs but real traffic stays flat, the instinct is to upgrade the hosting plan. That’s the wrong move.

The actual culprit is almost always bot traffic. Bots hammer uncacheable endpoints — think wp-login.php, xmlrpc.php, and WooCommerce AJAX calls — and those requests bypass the cache layer entirely. Every hit consumes PHP workers and database queries. A bigger plan just gives bots more room to consume. The fix starts with identifying what’s actually hitting the server, not throwing more resources at it.

More info: https://kinsta.com/blog/bot-traffic-server-load-wordpress/

Cutting Bandwidth Waste Without Locking Out Real Users

Kinsta’s second post tackles the next step: reducing bandwidth drain from bots while keeping the door open for legitimate visitors. Blanket IP blocking or aggressive rate limiting can backfire. Real users on shared networks or VPNs get caught in the crossfire.

The recommended approach is more surgical:

• Identify which endpoints bots target most frequently.
• Apply targeted rules at the CDN or server level to throttle or challenge suspicious requests.
• Monitor results to ensure genuine traffic flows uninterrupted.

The guides are aimed squarely at agencies managing multiple WordPress client sites where wasted bandwidth quietly inflates costs each month.

More info: https://kinsta.com/blog/reduce-bandwidth-waste-bot-traffic/

Agencies Are Wiring AI Into Documentation, QA, and Internal Tools

On WP Tavern’s Jukebox podcast, Matt Schwartz spoke with Nathan Wrigley about practical AI use inside WordPress agencies. This isn’t theory. Schwartz described connecting AI models to agency documentation so team members can query internal knowledge bases instantly.

He also discussed implementing guardrails through MCPs (Model Context Protocols) — a way to keep AI outputs consistent and safe. Other use cases include automated QA checks and building lightweight internal tools. Schwartz noted the impact on agency staffing and workflows is real but still evolving.

More info: https://wptavern.com/podcast/216-matt-schwartz-on-exploring-ais-impact-in-wordpress-agencies-part-2

WordPress Meetups Still Struggling to Bounce Back After COVID

Simon Pollard joined WP Tavern to talk about the state of WordPress community events. Before the pandemic, local meetups were thriving. COVID wiped out in-person gatherings almost overnight. The recovery has been slow and uneven.

Pollard described an ongoing struggle to rebuild momentum. Attendance is down. Organisers are burnt out. The conversation explored what the “new normal” actually looks like for WordPress communities and whether hybrid or online-only formats can fill the gap left by fewer in-person events.

More info: https://wptavern.com/podcast/209-simon-pollard-on-navigating-the-new-normal-for-wordpress-community-and-events

WordPress 7.0 marks a clear signal that AI is now a core platform concern, not a plugin afterthought. At the same time, the nuts-and-bolts work of running WordPress sites — fighting bot traffic, managing costs, and keeping communities alive — remains just as pressing. Agencies that get both sides right will be in the strongest position heading into the second half of 2026.

Frequently Asked Questions

What is WordPress 7.0 “Armstrong” and what are its main new features?

WordPress 7.0 “Armstrong” is the latest major release, launched in May 2026. It introduces a built-in AI hub, a redesigned admin theme, new blocks, and an expanded set of developer tools.

Why does upgrading your hosting plan not fix bot traffic issues on WordPress?

Bots target uncacheable endpoints like wp-login.php and AJAX calls, consuming PHP workers regardless of plan size. A bigger plan simply gives bots more resources to burn through, raising costs without solving the root cause.

How do WordPress agencies use AI for internal workflows and QA?

Agencies are connecting AI to internal documentation so staff can query knowledge bases instantly. They also use AI for automated QA checks and build lightweight internal tools, with guardrails set via Model Context Protocols.

How can site owners reduce bot bandwidth waste without blocking real users?

The key is applying targeted rules at the CDN or server level to throttle or challenge requests on specific endpoints bots favour. Blanket IP blocking should be avoided because it risks catching legitimate visitors on shared networks or VPNs.

Why are WordPress meetups and community events still declining after the pandemic?

COVID halted in-person WordPress meetups almost entirely, and attendance has not recovered to pre-pandemic levels. Organiser burnout and uncertainty around hybrid formats continue to slow the rebuild.