📥 Hello, and greetings from the Central Office!
Each month we share what we actually shipped so you can see the work behind the scenes. May was a busy release month across both our PDA and PPWP product lines.
Releases this month: PDA Access Restriction, PDA Magic Link, PPWP Free v1.9.18, PPWP Password Suite, Password Statistics v1.3.7, and PPWP WooCommerce Integration.
Six releases in one month. Each one represents real work: code reviews, testing, compatibility checks, and coordination across the team. Next week we will share the security and code quality improvements that went into making these releases better.
🎥 Did you know we have a YouTube channel focused on WordPress security?
We share step-by-step tutorials on how to secure your site and protect your content.
⚡️ Watch our latest video:
Create a WordPress Membership Site with Passwords
👉 Explore the full channel:
youtube/@wpdefenselab
Don’t miss the next one 🚀
Welcome to WP Defense Lab — your weekly brief on the WordPress news that impacts your business.
This week, Amazon v. Perplexity reaches oral argument at the Ninth Circuit today, the CFAA case testing whether Terms of Service can block AI agents with federal enforcement power.
In WP Radar: Yoast tracks your brand in Claude, AI translation gets cheaper for WordPress sites, bot traffic hits 1 in 31 web visits, and publishers cut six-figure AI licensing deals.
The Case That Decides Who Controls AI Agent Access to Every Site
Amazon's CFAA theory reaches oral argument at the Ninth Circuit today. The case could set the precedent for whether Terms of Service can block AI agents with federal enforcement, and it applies to your WordPress site, not just Amazon’s.
The Amazon v. Perplexity CFAA case reaches oral argument at the Ninth Circuit Court of Appeals in Seattle today.
The legal question sounds narrow: can Amazon use the Computer Fraud and Abuse Act to block Perplexity's Comet browser from accessing logged-in Amazon pages?
The downstream implications reach every website with a logged-in user layer - subscriptions, memberships, account-based content.
The Anatomy of Amazon's Argument
Comet, Perplexity's AI-powered browser, logs into a user's Amazon account using stored credentials, browses products on behalf of the user, and completes purchases through Amazon's checkout.
Amazon's CFAA claim rests on three steps: its Terms of Service explicitly prohibit automated access; Comet - not the human - is the entity making requests to Amazon's servers; therefore Comet accesses Amazon "without authorization" regardless of what the user instructed.
The user's instruction to delegate access is, under Amazon's theory, legally irrelevant to whether Amazon authorized the agent.
Why The Ninth Circuit's Pause Matters
On March 10, 2026, U.S. District Judge Maxine Chesney granted Amazon a preliminary injunction blocking Comet from logged-in Amazon pages.
Roughly a week later, the Ninth Circuit paused that injunction pending appeal. Appellate stays of preliminary injunctions are rare.
The Ninth Circuit applies a four-factor test that includes likelihood of success on the merits - a panel granting a stay signals the moving party has a reasonable shot at winning.
Mozilla and the Electronic Frontier Foundation filed amicus briefs supporting Perplexity's principal-agent doctrine argument: that agent acts are legally imputed to the principal who instructed them.
What Each Outcome Sets in Motion
If Amazon prevails, ToS clauses prohibiting automated access become federally enforceable against AI agents.
Every site owner gains a legal mechanism for blocking AI agents from logged-in areas beyond robots.txt.
If Perplexity prevails, the CFAA gets pushed back toward its 1986 anti-hacking scope. Websites retain civil contract remedies and technical controls but lose the federal criminal-law lever.
A middle-ground ruling - distinguishing agents completing transactions from agents retrieving data only - would shape how sites structure access posture without resolving the full question.
The WordPress Site Owner's Audit
WordPress site owners already control both levers in this equation.
Robots.txt is directly editable or manageable through plugins. Terms of Service pages are standard site features.
What most sites lack is ToS language that explicitly addresses AI agents acting on behalf of users. Most WordPress ToS pages predate the agentic web - they may prohibit "automated access" or "scraping" in general terms.
Whether that language, updated to name AI agents explicitly, carries federal enforcement weight depends on what the Ninth Circuit decides.
The Practical Question
Review your current Terms of Service.
Does it define who - and what - counts as an authorized visitor? Does it address AI agents acting on behalf of users? Does it distinguish public content from logged-in account areas?
The sites positioned to benefit from an Amazon win are the ones with ToS that explicitly covers AI agent access before the court crystallizes the standard.
This week in WP Radar: Yoast adds Claude to its AI brand tracking dashboard, WordPress 7.0 ships AI management infrastructure, Kinsta's research shows AI bots now account for 1 in 31 web visits, and publishers start landing six-figure AI content licensing deals.
Yoast Adds Claude to AI Brand Visibility Tracking. Yoast AI Brand Insights now scans how your brand appears in Claude alongside ChatGPT, Perplexity, and Gemini - all in one dashboard. Each AI platform draws on different sources and applies different reasoning, so the same brand question produces different answers across platforms. With 64% of consumers planning to use AI to research purchases in 2026, tracking where your brand appears across every AI answer layer is no longer optional for WP site owners.
AI Translation Gets Cheaper for WordPress Sites. WordPress 7.0 'Armstrong' shipped in May, continues to build out the AI management layer around site operations. The more practical update for site owners may be Universally; an AI translation platform highlighted in WPBeginner’s May Spotlight. It translates WordPress sites into 110+ languages through cloud-based delivery, processed 250 million words in private beta, and starts at $7.50 per month. For publishers, ecommerce stores, and membership sites targeting multilingual audiences without database bloat, professional translation infrastructure is becoming much cheaper to deploy.
1 in 31 Web Visits Is Now an AI Bot. Kinsta's bot traffic research found that by end of 2025, roughly 1 in 31 web visits came from AI bots - up from about 1 in 200 at the start of that year. AI crawlers accounted for an average of 4.2% of HTML requests on Cloudflare's network, with the share fluctuating between 2.4% and 6.4%. Around 80% of AI crawling is tied to model training, not search or user queries. Traffic dashboards no longer reflect only real user demand.
Six-Figure AI Content Licensing Deals Land Now. Publishers are cutting six-figure AI content licensing deals via Snowflake's Cortex Knowledge Extensions. Washington Post, AP, People Inc., and USA Today Network are among 17 publishers now signed on. Enterprises pay publishers for access to paywalled content inside Snowflake's AI environment without exposing raw feeds or enabling model training. Revenue is incremental - not a traffic replacement - but it is the first meaningful recurring revenue stream from AI for publishers who own their content archives.
A compromised Scroll To Top plugin sat dormant inside 20,000 WordPress sites, connected to a hijacked update channel and waiting for the attacker to pull the trigger, before researcher Austin Ginder caught it using AI forensics.
Bad actors are buying legitimate WordPress plugins and redirecting auto-updates to rogue servers with no visible symptoms until the payload fires. The wordpress.org repo holds over 60,000 plugins; individual site owners have no way to audit ownership changes at scale. Ginder documented four separate supply chain attacks across different plugins in recent months, all using the same method: acquire, hijack the update channel, wait.
That’s all for this week!
Michael - Operator @WP Folio - now WP Defense Lab. Same Plugins. Different Name.