WordPress.com switched its MCP server to OAuth 2.1 with PKCE, so AI agents no longer need long-lived tokens pasted into a config file. What the code verifier protects against, and what an authorized agent can do on your site.
Most WordPress sites keep their data as loose post meta rows. Healthcare got further by agreeing on shared ontologies before writing any code, and the same approach works in a WordPress codebase, from CPT design through JSON-LD output.
The WordPress Abilities API landed in 6.9 Beta 2, minus the JavaScript registration, which moved to a standalone NPM package in the Gutenberg repo. Notes on that split, the AI Experiments plugin, the WP AI Client 0.1.0 plan and the MCP Adapter refactor.
Site Editor changes live in the database, not in your theme files. This is the setup I use to pull those visual edits back into version control: WordPress Playground, the Create Block Theme plugin and a GitHub repo as the source of truth.
Low-tech logistics companies do not need AGI, they need to stop counting stock with a pen. Voice-driven inventory counts in n8n, damage reports generated from a photo, and a WordPress REST endpoint that takes the data in without breaking WooCommerce stock.
Google Trends hands you a 0-100 score, not search volume, and that score moves when the date window moves. Notes on the normalization and rounding problems, plus the overlapping-window stitching I use to rebuild a daily series a model can actually learn from.
Perplexity and BLEU tell you nothing about whether an automated customer journey actually goes anywhere. The CDP framework scores continuity, deepening and progression against a taxonomy of journey stages instead.
LLM-as-judge asks a model that hallucinates to catch hallucinations. Displacement Consistency scores the vector between a question and its answer against grounded neighbors instead, with no source document and no second model call at inference time.
WordPress 7.0 arrives in April 2026 and raises the PHP minimum to 7.4, dropping 7.2 and 7.3. What that changes for plugin authors, and what happens to sites that stay on the old versions.
WooCommerce 10.5 ships an experimental in-memory cache for product objects, so a single request stops rebuilding the same object over and over. The benchmarks, plus the stale data trap waiting for anyone who updates products with direct SQL.