The 0.7.0 release of the experimental plugin is the largest change to WordPress AI features so far. I have been following the AI integrations heading for core for a while, and this is not a routine version bump. It sketches out how WordPress 7.0 will probably handle metadata and editorial logic. Rough in places and still experimental, but worth your attention if you manage a large content library.
Content classification and SEO automation
Taxonomy management jams up most editorial workflows. I have seen sites carrying 5,000 tags where half are duplicates, “WP” and “WordPress” sitting side by side. Tagging is also the first thing a writer drops when a deadline is close. The new Content Classification experiment suggests categories and tags from the post content, title and excerpt.
Unlike earlier “magic” attempts at this, 0.7.0 only suggests terms that already exist on the site. That restraint is what makes it usable. A suggested tag that does not exist yet is mostly noise. Tying the model to the taxonomy you already maintain keeps the database from filling up with AI-slop tags.
Bulk alt text and the accessibility backlog
Then there is the media library. “Add alt text later” has been the going advice for years, which is why most sites carry hundreds of images with no accessibility metadata at all. Version 0.7.0 adds bulk alt text generation. Select a batch of images and the AI writes the descriptions, following the W3C Alt Text decision tree.
Do not leave it unattended, though. Description quality varies by provider. On an older host with tight resources, a bulk job can hit a transient timeout partway through. Check the background processing logs any time you queue more than 50 images at once.
Extensibility and the 0.7.0 developer API
For developers, the interesting part of this release is not the UI, it is the hooks. The team added ways to modify the system instructions and adjust results before they reach the database. If you are building a custom editorial dashboard, you can push brand voice guidelines straight into the AI’s context.
Earlier this year I wrote about future-proofing WordPress AI features, and 0.7.0 is close to what I was hoping for. Less black box generation, more infrastructure a developer can actually hook into.
<?php
/**
* Example: Customizing the AI Post Context
* Prefix: bbioon_
*/
add_filter( 'wp_ai_post_context', function( $context, $post_id ) {
// Inject specific brand tone guidelines into the prompt context
$brand_guidelines = get_option( 'bbioon_brand_voice_rules' );
if ( ! empty( $brand_guidelines ) ) {
$context['system_instructions'] .= "\nFollow these voice rules: " . $brand_guidelines;
}
return $context;
}, 10, 2 );
If this AI plugin work is eating your dev hours, I can take it on. I have been wrestling with WordPress since the 4.x days, and I can help you build an editorial workflow that scales without breaking the site.
What is queued for 0.8.0
The 0.8.0 roadmap already lists “Refine from Notes” and dashboard widgets, so this has stopped being a plugin you try on the side and is turning into part of the platform. If you have not put the v0.7.0 release on a staging site yet, do that now. Get your PHP environment to 8.1 or newer first, or the newer async providers can hit race conditions.
