📥 Hello, and greetings from the Central Office!
Each month we like to share a quick look at what happens behind the scenes. Transparency matters to us, so we regularly show the work our team is doing to support customers, improve our plugins, and maintain the systems that power them.
Here is another update from the past month.
February included two important plugin releases along with continued development work across the platform.
Recent releases:
• PDA S3 extension
• PDA IP Block version 1.3.7
These releases focused on improving protection workflows and giving site owners more control over how their protected content is delivered and secured.
In addition to the releases, the team also tested several advanced features including protected video delivery, encrypted PDF handling, and password protection workflows connected to form submissions.
Continuous updates like these help ensure our plugins remain reliable across different WordPress environments.
The Traffic Shift Nobody's Questioning
Google Discover now accounts for 68% of traffic to global news sites, compared to just 32% from traditional search, according to Press Gazette analysis of 2,000 media websites.
Publishers are treating this as a diversification win. It's not.
You've moved from optimizing for user intent to optimizing for an algorithm that, in Google's own words from John Mueller at Search Central Live Zurich, "can be zero tomorrow."
Why This Matters for WordPress Creators
Clara Soteras, head of innovation at AMIC, frames Discover as reaching "people that don't know they need you." That's the problem disguised as opportunity.
Traditional search traffic arrives with intent: someone typed a query, your content matched, and transaction potential exists.
Discover traffic is algorithmic distribution to passive scrollers. Different ranking factors (location, images, headlines over relevance), different user behavior, different monetization math.
Political content rarely appears in Discover feeds. Entertainment and lifestyle dominate. If your WordPress site's revenue model depends on engaged readers who convert, you're chasing the wrong metric.
The Infrastructure Question
When 68% of your traffic comes from a single algorithmic feed you don't control, you don't have a traffic strategy, you have a dependency.
Google explicitly warns that this traffic "is for free, and someday it can be zero."
Compare that to owned infrastructure: an email list, a membership site on your WordPress install, a direct relationship where you control delivery. Discover optimization means adapting content categories, image selection, and headline formulas to match what an opaque algorithm surfaces to users who didn't search for you.
That's not audience building. That's renting attention with an eviction notice already posted.
What the Numbers Actually Mean
Press Gazette's data shows traditional search shrinking to 32% of Google-referred traffic for publishers. AI overviews are eating search intent. Discover is filling the gap with passive distribution. But passive distribution converts differently than intent-driven traffic.
Your analytics might show traffic growth while revenue per visitor drops. The economic model breaks when you optimize for volume from users who arrived by accident rather than choice.
WordPress creators building sustainable businesses need to ask: What's the lifetime value of a Discover visitor versus an email subscriber you own?
The Contrarian Play
If Discover is becoming the primary channel and Google warns it's unstable, the strategic move isn't optimization, it's conversion infrastructure. Use whatever Discover traffic arrives to build owned channels.
Every Discover visitor should see an email capture, a membership offer, a reason to establish a direct relationship. Treat Discover like paid traffic: measure cost per owned subscriber, not cost per pageview.
Because when that 68% goes to zero, and Mueller's warning suggests it will for many, the only traffic that matters is what you own.
Are you building for algorithmic visibility or business durability?
GEO vendor market emerges as publishers chase AI search visibility without proven ROI. New cottage industry of "Generative Engine Optimization" vendors promises AI search placement, mirroring early SEO gold rush dynamics. WordPress publishers face same pattern: pay consultants to optimize for algorithms they don't control, on platforms that don't share revenue.
Enterprise CMS platforms built for page rankings fail AI content interpretation. Marketing leaders discover legacy CMS architecture can't communicate structured meaning to AI systems. WordPress's native structured data capabilities and flexible architecture position it ahead of enterprise platforms requiring expensive audits to achieve AI readiness.
WordPress.org ships native Markdown output for AI agent consumption. Lead developer Dion Hulse confirms Markdown support across WordPress.org sites via Accept header or .md URL parameter. Platform-level AI readiness ships as core feature while competitors sell it as premium service.
Luma's creative AI agents coordinate multiple models for end-to-end production workflows. Unified Intelligence models handle text, image, video, audio generation with self-critique loops. Content creators face new competition: AI agents that plan, execute, and refine creative work without human iteration costs.
Verified Source Packs emerge as agent-readable truth layer beyond structured data. Agents need "official truth" with provenance and versioning, not just schema markup. WordPress sites that ship machine-consumable fact packs - products, pricing rules, policies - gain agent recommendation advantage over brands relying on crawlable pages alone.
WordPress sites using modern JavaScript frameworks no longer face the crawling penalties they did years ago. But here's the catch: Google's documentation updates lag reality by years. If you're still avoiding JS because of 2019 SEO advice, you're optimizing for problems Google already solved.
That’s all for this week!
Michael - Operator @WP Folio - now WP Defense Lab. Same Plugins. Different Name.