WordPress’s official AI plugin, last updated in July with comment-reply drafting, has a new release out. Version 1.3.0 adds two editor experiments and a few changes worth knowing about if you use the plugin’s developer-facing features.
This is the free, official AI plugin distributed through WordPress.org, not a feature built into WordPress core. You need to install it separately, and the new tools below are opt-in experiments you turn on yourself.
Translate content without leaving the editor
The new Content Translation experiment lets you pick a target language and translate a post’s Paragraph and Heading blocks right inside the block editor. You can also translate the title. The translated text replaces the original in the editor so you can review and adjust it before publishing, it does not publish automatically.
Get a slug suggestion before you hit publish
Slug Generation suggests a short, search-friendly permalink based on your title and content. It shows up in the permalink controls and again in the pre-publish checklist, and you can edit, regenerate, or accept the suggestion. It also shows a preview of how your manual edits will be normalized into a valid slug, so you’re not guessing what characters get stripped out.
What changed for site admins and developers
Custom Abilities, which let outside integrations use specific WordPress capabilities through the plugin’s Abilities API, now sit behind their own opt-in setting. If your site has an integration built on this, you need to turn the new experiment on after upgrading or that integration will stop working.
Site admins can also export the plugin’s settings as a JSON file to move a configuration between sites. API keys and other credentials are deliberately left out of the export, so you’ll still need to re-enter those on the new site.
Update if you use it
The release also tightens up security, with stronger sanitization on AI-generated content and nonce checks on bulk actions, and improves keyboard navigation and screen reader support across the editor tools. If you built anything on top of the plugin’s custom meta keys, note that the prefix changed from ai_ to wpai_ in this release, check your integration after updating.
End of article