How WordPress Problems Show Up
Apex® talks to your site through the WordPress REST API, signed in with an application password. Problems show up in three places: as a message when you connect in Preferences → Connections → WordPress, as a red "WordPress didn't accept it." notice when you publish (with the reason underneath), and as a yellow notice after a publish that worked but had warnings. An article whose last publish failed also shows a red "WordPress: ..." box at the top of the editor.
Apex® never creates a duplicate post. Publishing an article again updates the same post, and an interrupted publish finds the post it already started instead of making a new one.
Connecting Your Site
| Problem | What to do |
|---|---|
| "Couldn't find WordPress at (site). Check the address, and that the REST API isn't blocked." | Enter your site's home address, like https://example.com (not the wp-admin link). If the address is right, a security plugin or your host may be blocking the REST API; ask them to allow it. |
| "Couldn't reach (site)... Check the site is online." | Open your site in a browser. If it loads, wait a minute and try again. |
| "WordPress didn't accept the username or application password..." | Create a new application password in WordPress (Users → Profile → Application Passwords) and paste it in. Use the application password, not your normal login password. |
| "Application passwords are turned off on this site (often by a security plugin)..." | Turn application passwords back on in your security plugin, or ask your host. They also need the site on https. |
| "This site isn't on https..." | WordPress only allows application passwords over https. Switch the site to https (your host can help) and connect again. |
| "This WordPress user can't write posts..." | Connect a user with the Author, Editor or Administrator role. |
| "WordPress sent back something unexpected. A security plugin or firewall may be blocking the REST API." | Ask your host or security plugin to allow requests to /wp-json/ on your site. |
An Article Won't Publish
| Problem | What to do |
|---|---|
| "Connect WordPress in Preferences → Connections first." | Connect your site, then come back. The editor offers Save And Connect so you don't lose changes. |
| "Your WordPress user can only save drafts. Send it as a draft, or use an Editor account." | Choose Save As WordPress Draft, or reconnect with an Editor or Administrator account to publish and schedule. |
| "Your WordPress user isn't allowed to do this..." | The connected user lacks a permission. Reconnect with an Editor or Administrator account. |
| "WordPress didn't accept the username or application password..." when publishing | The application password was revoked or the user changed. Create a new one and reconnect. |
| "Apex is working on this article right now. Try again in a moment." | Apex® AI is still writing or improving the article. Wait for it to finish. |
| "This article is already being sent to WordPress." | A publish is in progress. Wait for the result notice. |
| "Pick a time at least a few minutes from now." | Scheduled posts need a time a few minutes in the future. |
| "Publishing to WordPress was interrupted by a restart. Check WordPress, then publish again." | Look for the post in WordPress. Then publish again from Apex®; it updates the existing post rather than adding a second one. |
It Published, but With Warnings
| Warning | What to do |
|---|---|
| "Install the Apex SEO Bridge plugin so the SEO title, meta description and focus keyphrase reach (plugin)" | Most SEO plugins only accept these fields through the bridge. Install it (steps below) and publish again. |
| "All in One SEO needs the newer SEO Bridge (1.2)..." | Download the bridge again from Preferences → Connections → WordPress and upload it over the old one. |
| "(Plugin) didn't keep the ... as sent. Check the post in WordPress" | Another plugin may be changing those fields. Open the post in WordPress, check the SEO box, and run Test Mapping. |
| "FAQ schema wasn't added: install the Apex SEO Bridge plugin, or connect as an Administrator" | Install the bridge, or reconnect with an Administrator account. |
| "A file (...) wasn't moved to WordPress..., so it still loads from its old address" | The image still shows, but from its original address. Check your Media Library upload limits, then publish again to retry. |
| "The featured image wasn't uploaded (...)" | Check the upload limit and free space on your host, then publish again. |
| "Category ... wasn't added" or "Tag ... wasn't added" | The connected user can only use existing categories. Pick from your site's categories, or reconnect as an Editor. |
| "WordPress changed the slug to ... because another post already uses ..." | Another post (maybe in the trash) has that address. Change the slug in the editor or remove the old post. |
Install or Update the SEO Bridge
- Open Preferences → Connections → WordPress and find Apex SEO Bridge. Its status is Not Installed, Update Available or Up To Date.
- Click Download the plugin.
- In WordPress, go to Plugins → Add New → Upload Plugin, upload the file and activate it. When updating, choose Replace current with uploaded.
- Back in Apex®, click Check Again. The field mapping should show your SEO plugin's fields as ready.
- Click Test Mapping. Apex® sends every field to a private draft, checks where each one landed, then deletes the draft.
Still Stuck?
Email support@cyberdunes.com with your workspace name, your site address, the article title, what you did (connect, publish, schedule or draft), the exact message shown, and which SEO plugin you use. A screenshot of the Field Mapping table helps too.
Was this article helpful?




