Quick answer: WordPress AI 1.4.0 adds Markdown versions of published content at /feed/markdown/ and by appending ?output_format=markdown to an individual post or page URL. Before upgrading, confirm the site runs WordPress 7.0.3 or newer, take a backup, and test on staging: the AI plugin is experimental, supports the Block Editor rather than Classic Editor, and some AI features require a separate provider connector and API key. [1] [2]
Try the new Markdown output in 60 seconds
After installing or updating the official AI plugin and enabling its Markdown Feeds experiment, replace example.com with your domain and test these URLs:
https://example.com/feed/markdown/
https://example.com/your-post-slug/?output_format=markdownFor a quick command-line check, use:
curl -L -I "https://example.com/feed/markdown/"
curl -L "https://example.com/your-post-slug/?output_format=markdown"- Expect an HTTP success response rather than a 404 or redirect loop.
- Confirm headings, links, images, lists, blockquotes and code remain understandable.
- Check that titles and excerpts do not contain raw HTML entities.
- Test a simple post and a complex block-heavy page.
- Purge page/CDN cache if the endpoint is missing immediately after activation.
WordPress says the conversion preserves common content structures and normalizes titles, excerpts and feed content. It is intended to give AI agents, language models and developer tools a cleaner representation than rendered HTML. [1]
Safe WordPress AI 1.4 upgrade checklist
- Check WordPress core: AI 1.4.0 raises the minimum supported version to WordPress 7.0.3. Update core first if the site is older.
- Confirm the editor: the plugin directory says the AI plugin requires the Block Editor and does not support Classic Editor or other non-block editing experiences.
- Back up files and database: create a restorable backup before updating an experimental plugin.
- Clone to staging: test the same theme, active plugins, cache and PHP configuration used in production.
- Review custom integrations: migrate renamed abilities and update any code calling
generate_embeddings. - Update the plugin: install AI 1.4.0 from WordPress.org or use the normal WordPress Updates screen.
- Review experiments individually: the old global “Enable AI” switch has been removed; features and experiments are now controlled separately.
- Test Markdown URLs: verify both the site feed and representative post/page output.
- Test editorial workflows: recheck translation, alt-text generation, Type Ahead, comment moderation and request logs if you use them.
- Monitor errors: inspect the AI request log and server/PHP logs after deployment, then roll back if production behavior differs from staging.
The WordPress AI team encourages prompt updating because 1.4.0 includes security hardening, but the plugin directory also recommends staging because the plugin remains experimental. [1] [2]
What changed in WordPress AI 1.4.0?
| Change | Who should care | Action |
|---|---|---|
| Markdown feed and per-URL Markdown output | Publishers, AI/search teams, developers | Enable the experiment and validate representative content |
| Comment value score from 0 to 1 | Sites with active comments | Use it as an extra moderation signal, not an automatic truth score |
wpai_embeddings storage plus vector math/ranking classes | Plugin developers | Review the new infrastructure; it is not a finished semantic-search feature |
| Translation workflow improvements | Multilingual editorial teams | Test retry behavior, added target languages and formatting preservation |
| Decorative-image awareness for alt text | Editors and accessibility teams | Mark decorative images correctly and verify they are handled as intended |
| More accurate provider error logging | Admins and support teams | Use logged 4xx/5xx details when diagnosing connector failures |
| Renamed/deprecated abilities | Developers and agent integrations | Move to the new names before aliases disappear |
| Security hardening | Every installation | Update after staging and regression checks |
The release announcement describes embeddings as developer infrastructure for possible future semantic search, retrieval and recommendation features—not as a new complete end-user search tool in 1.4.0. [1]
Developer migration: copy this mapping
| Previous ability | Use in 1.4.0 | Status |
|---|---|---|
core/read-content | core/content-query | Old name remains as a deprecated alias for now |
core/read-users | core/users-query | Old name remains as a deprecated alias for now |
core/read-settings | core/settings-get | Old name remains as a deprecated alias for now |
ai/get-post-details | Single-post mode of core/content-query | Deprecated |
The embeddings helper also has a breaking change: callers of generate_embeddings must specify an embedding model. The release says code may pass a model ID or a ModelInterface instance; when using a model ID, it must also identify the provider offering that model. [1] [3]
Provider and cost reality check
The core AI plugin does not include provider credentials or provider implementations. For provider-backed features, WordPress instructs users to install a compatible connector, configure it under Settings → Connectors, and then control experiments under Settings → AI. The AI plugin itself is free, but external API usage may cost money depending on the chosen provider and workload. [2]
For example, the official OpenAI connector dynamically discovers supported OpenAI models and requires the underlying PHP AI Client plus an OpenAI API key. Do not place a secret key in a public post, repository or screenshot. [4]
Troubleshooting Markdown feeds
The Markdown URL returns 404
Confirm AI 1.4.0 is active, the Markdown Feeds experiment is enabled, and WordPress core is at least 7.0.3. Resave Settings → Permalinks on staging, clear all caches, and test again. If the site uses a security or redirect plugin, check whether query parameters or custom feed routes are being blocked.
The AI feature is unavailable
Check that a compatible provider connector is installed, authenticated and supports the operation the feature needs. The plugin directory warns that features can appear unavailable until those conditions are met. [2]
A custom integration stopped working
Search the integration for the old ability names and for calls to generate_embeddings. Apply the migration table above, add the required model/provider arguments, and rerun integration tests before production deployment.
Provider requests look successful even when they fail
Update to 1.4.0 and inspect AI Request Logging again. The release corrects earlier behavior that could record provider HTTP 4xx and 5xx responses as successful requests; it now records the error status and message. [1]
Frequently asked questions
What is the WordPress AI 1.4 Markdown feed URL?
The site-wide route is /feed/markdown/. For a single published post or page, append ?output_format=markdown to its normal URL.
Does WordPress AI 1.4 work with Classic Editor?
No. The official plugin page says it supports the Block Editor and does not support Classic Editor or other non-block editing experiences.
What WordPress version does AI 1.4 require?
Version 1.4.0 requires WordPress 7.0.3 or newer.
Do I need an API key?
Provider-backed AI features currently need a configured connector and its credentials. The exact key and cost depend on the provider you select.
Should I install WordPress AI 1.4 on a live site?
Test it on staging first. WordPress describes the plugin as experimental, while also encouraging users to update because 1.4.0 includes security improvements.
Sources
- WordPress AI Team — What’s new in AI 1.4.0?
- WordPress.org Plugin Directory — AI
- GitHub — WordPress AI 1.4.0 release
- WordPress.org Plugin Directory — AI Provider for OpenAI
Last checked: October 11, 2026. The AI plugin is experimental, so interfaces, requirements and feature behavior can change in later releases.