wordpress 7.1 is live, AI bot traffic now exceeds human visitors, and the gap between fixing WordPress sites and running them reliably is costing agencies real money. This week’s developments demand immediate action across site builds, hosting operations, and bot management. Here is what matters and what we are already implementing for our clients.

Key Takeaways

• WordPress 7.1 “Mary Lou” ships with responsive styling controls and deeper collaboration features that change how we build client sites.
• Automated bots now account for over 53% of all web traffic, with AI crawlers ignoring established crawling conventions.
• robots.txt, llms.txt, and bot protection tools each control different layers of AI access—and none of them work alone.
• Operational automation in WordPress is no longer optional; the cost of ad-hoc fixes compounds fast at scale.
• WordPress 7.1’s release at WordCamp US signals the platform’s continued investment in modern admin experiences and AI integration.

WordPress 7.1 Drops With Responsive Controls We Have Been Waiting For

The release is named after jazz pioneer Mary Lou Williams, and it carries her spirit of reinvention. WordPress 7.1 introduces responsive styling controls directly in the editor, a feature we have been requesting since the block editor’s early days. This means our designers can now adjust spacing, typography, and layout behaviour per breakpoint without writing custom CSS or relying on third-party Plugins, as detailed in the official WordPress 7.1 “Mary Lou” announcement.

We have been testing the beta on staging environments for the past week. The collaboration enhancements—real-time co-editing improvements and streamlined workflows—reduce friction when multiple team members work on the same page. For our retainer clients, this cuts revision turnaround times noticeably. A thorough breakdown of the new features and screenshots is available in WPBeginner’s hands-on preview of WordPress 7.1.

AI Crawlers Now Outpace Human Traffic—and They Are Not Playing by the Rules

Bots accounted for 53% of all web traffic in 2025. That was the first time automated traffic outpaced humans in a full calendar year. By mid-2026, the numbers have climbed further. The problem is not volume alone. AI crawlers from major LLM providers are routinely ignoring robots.txt directives, hammering servers with aggressive request rates, and scraping content without attribution, as documented in Kinsta’s analysis of why AI crawlers are breaking web-crawling rules.

For our clients running content-heavy WordPress sites, this creates two problems: inflated server costs from junk traffic, and unauthorised content harvesting. We are now auditing every client site’s bot exposure as a standard part of our maintenance workflow.

robots.txt vs llms.txt vs Bot Protection: Understanding What Actually Works

There is genuine confusion about which tool controls what. robots.txt is a suggestion, not an enforcement mechanism. llms.txt is a newer convention aimed at telling AI models what content to reference. Neither stops a determined crawler. Server-level bot protection—rate limiting, challenge pages, IP blocking—is the only layer with actual teeth.

We now deploy a layered approach for every WordPress site we manage: properly configured robots.txt, an llms.txt file where appropriate, and active bot mitigation at the hosting or CDN level. This multi-layer strategy aligns with the practical guidance outlined in Kinsta’s comparison of llms.txt, robots.txt, and bot protection for WordPress.

Ad-Hoc WordPress Fixes Are a Liability—Automation Is the Standard Now

Most WordPress teams can troubleshoot. Fewer can run operations reliably at scale. The difference is automation: scheduled updates, automated backups with tested restore procedures, deployment pipelines, and monitoring that triggers before clients notice downtime. The cost of manual, reactive maintenance compounds with every site added to a portfolio, a point made clearly in Kinsta’s case for automation in WordPress operations.

Our team moved to automated deployment and update pipelines in 2025. The result: fewer emergency calls, faster rollouts, and measurably better uptime across our managed portfolio. If your agency still relies on one-off fixes, the operational debt is growing whether you see it or not.

WordCamp US Timing Signals WordPress’s Continued Platform Ambition

Releasing 7.1 at WordCamp US is deliberate. It puts the new features in front of the largest concentration of WordPress developers and decision-makers simultaneously. With the 7.0 cycle having rebuilt the admin interface and introduced AI-assisted editing, 7.1 refines and extends those foundations. We expect adoption to accelerate quickly given the practical quality-of-life improvements this release delivers.

The message from this week is clear. WordPress is maturing fast, AI bots are an infrastructure concern that demands active management, and operational discipline separates agencies that scale from those that stall. We are updating client sites to 7.1 on a staged rollout, tightening bot controls across every property, and continuing to invest in the automation systems that keep our managed sites running without surprises.

Frequently Asked Questions

What is new in WordPress 7.1 “Mary Lou” for web designers?

WordPress 7.1 introduces native responsive styling controls in the block editor, letting designers adjust layouts per breakpoint without custom CSS. It also adds collaboration improvements that streamline multi-user editing workflows.

How do web designers protect WordPress sites from AI crawlers?

A layered approach works best: configure robots.txt and llms.txt to signal access preferences, then enforce limits with server-level bot protection such as rate limiting and challenge pages. No single tool is sufficient on its own because many AI crawlers ignore directive files entirely.

Why does automating WordPress maintenance matter for agencies?

Manual, reactive fixes become increasingly expensive as site portfolios grow, creating compounding operational debt. Automated pipelines for updates, backups, and monitoring deliver consistent uptime and free team capacity for higher-value work.

What is the difference between robots.txt and llms.txt on a WordPress site?

robots.txt tells traditional search engine crawlers which pages to avoid, while llms.txt is a newer convention that guides large language models on which content to reference. Both are advisory only—neither can technically block a non-compliant bot.

How do I update my WordPress site to version 7.1 safely?

Test the update on a staging environment first, verify plugin and theme compatibility, and ensure you have a recent, tested backup before applying it to your live site. A staged rollout approach reduces the risk of unexpected conflicts reaching your visitors.