Troubleshooting

An application password is not your login password. In WordPress go to Users → Profile → Application Passwords, create a new one, and paste it whole — spaces and all, we strip them. Also check the username is the WordPress username rather than the email address.

Keys are per site and only the most recent one works. Open Citeca in your WordPress sidebar, generate a new key, and paste that into Manage on the WordPress card.

The request reached WordPress without a key, which usually means a security plugin or proxy is stripping custom headers. Ask your host whether X-API-Key or Authorization headers survive to PHP.

The plugin rate-limits after repeated failures to stop key guessing. It clears in fifteen minutes. Make sure you are pasting the current key before trying again.

The token has been revoked, regenerated, or lacks permissions. It needs CMS: read and write plus Sites: read only. Generate a fresh one and paste it into Manage.

Three causes, in order of likelihood: the plugin is not activated; the site address is wrong (check https and whether the site lives under a subdirectory); or a security plugin has disabled the WordPress REST API. Loading /wp-json/ in a browser tells you which — it should return JSON, not a 404 or a firewall page.

Same root cause without the plugin involved. Confirm /wp-json/wp/v2/ responds. Disable REST-blocking options in security plugins such as Wordfence or iThemes, and check your host is not filtering it.

Something is serving that path that is not us — a caching layer, a holding page, or a different site on that domain. Check the address points at the WordPress install you meant.

Your server errored rather than refusing us. Check your PHP error log around that timestamp; a plugin conflict or a memory limit during image import is the usual explanation.

We send semantic HTML and your theme styles it. If your theme has no styles for post content, or the CMS template renders a plain field, that is what you see. Compare against a post you wrote by hand: if that looks the same, it is the template.

Content is converted to HTML before sending, so this indicates an older publish. Open the article and press Republish — it is corrected in place, on the same URL.

A known Webflow issue with CMS rich-text fields in their Editor, not a problem with the article. Check the published page on your live domain, where it renders correctly.

With the Citeca plugin, images are uploaded into your media library — a failure here is usually a file-permissions or upload-limit problem on the host. Check Media in WP admin to see whether they arrived.

WordPress removes unfiltered HTML unless the publishing author has the unfiltered_html capability. Publish as an author who does, or accept the sanitised version.

Articles are matched on slug, so this happens when the slug changed between publishes — usually because the title was edited after the first publish. Delete the copy you do not want and keep the URL that has been indexed longest.

Webflow appends a suffix when a slug collides. We now look the item up first and patch it, so republishing updates in place. If you have historic duplicates, remove the extras by hand once.

Long titles produce long slugs, and platforms cap them. It is cosmetic and does not affect indexing, but if you want a shorter URL, shorten the title before the first publish.

The others were still taken down, and Unpublish stays available so you can retry just the one that failed. Fix the underlying cause first — usually an expired token or a collection that no longer exists.

Programmatic unpublishing is supported for WordPress, Webflow and Joomla. For other platforms, unpublish the post in that platform directly — the message names which one.

It should not, and it will not: unpublishing marks the article as deliberately taken down and the scheduler skips it. If you pressed Publish afterwards, that is what opted it back in.

The article has no record of reaching a connected site — usually it was published before you connected the destination, or it was removed by hand. Remove it in your CMS directly.