Connection troubleshooting

When publishing, importing or Google data stops working, Blog AI shows a message that says what went wrong: on the post's page under Last publish attempt failed, on Home and the Actions page, on the Sites page, or in an email for scheduled posts. This page lists those messages, starting with the ones every connection shares, and links to the full list for your platform.

Whatever the problem, fixing it never costs you posts, ideas or Google data: use Fix connection rather than deleting and re-adding the site. See Fix a broken connection.

Find your platform

Each guide ends with a "Common problems and fixes" section that quotes every message that platform can show:

• WordPress: WordPress problems and fixes, and the Blog AI Connector plugin for Yoast SEO and Rank Math.
• Strapi: Strapi problems and fixes.
• Webhook (Zapier, Make, n8n or your own server): Webhook problems and fixes.
• Google Search Console and Google Analytics: Google problems and fixes, and When Google needs reconnecting.

Platforms in early access have their own guide, linked from their option under Add site once they're open for your account.

Problems every connection shares

"… rejected the credentials while trying to …" (HTTP 401 or 403)

Your site no longer accepts Blog AI's password, token or key: it was revoked, expired or lost a permission. Create a new one in your CMS and paste it under Fix connection. Then click Retry publish on the failed post.

"… redirected the request to …, so nothing was saved"

Your site moved, for example to https:// or to or from www.. Blog AI never sends a post to a redirecting address. Enter the new address under Fix connection.

"… failed to … (HTTP 429)" or "… rate limit was reached"

Your CMS or host is limiting how fast apps can write, usually after many posts at once. Wait a minute or two and click Retry publish. Retrying never creates a duplicate: Blog AI updates the post it already created.

"… failed to … (HTTP 500)" or a timeout

Your site or CMS had a problem or was down. Try again later. If it keeps happening, the text after the colon is what your site said; your host can explain it.

Titles show "&", "’" or similar

Older versions of Blog AI could send a title with HTML codes in it. Blog AI now sends titles, Google titles, descriptions, excerpts, categories and tags as plain text everywhere. For a post that still shows the codes, edit its title in Blog AI and click Update live post. If Blog AI says "There are no changes to push: the live post already has this version", correct the title in your CMS.

The featured image doesn't show

1. Check the post in your CMS. If the image is set there, your theme or website doesn't display it: turn on featured images in the theme, or ask your developer to render the field.
2. Check the field is mapped. On platforms where you map fields, the featured image only goes to the field you mapped. Map one under Fix connection.
3. Check for a publish message such as "Featured image is larger than 15 MB" or "Featured image has an unsupported type". Choose another image.
4. Changed the image after publishing? Update live post now sends a newly chosen featured image. See Update a post that is already live.

The FAQ isn't on my site

Blog AI sends a post's FAQ as its "Frequently asked questions" section at the end of the post, and its key takeaways after the introduction. Posts published before this was added get them the next time you use Update live post or apply a refresh: open the post, check the Key takeaways and FAQ card, and click Update live post. If the card is empty, the post has no FAQ; add questions there.

Headings show as ## or the body looks like code

Your website shows the body in a different format from the one Blog AI sent. WordPress gets HTML; Strapi gets Markdown; a webhook gets both; and where you map fields, a rich text field gets your CMS's own format and a long text field gets Markdown. Make sure your website renders the field as Markdown or rich text, or map the body to a field of the right type.

Videos, forms or iframes disappeared

Blog AI never writes embeds into a post. If someone adds them on your site, Update live post and refreshes refuse with "The live post contains content Blog AI can't rewrite without losing it", so they're safe. Edit those posts on your site.

"The live post was edited on your site since Blog AI last published it"

Someone changed the post in your CMS. Sending Blog AI's version would undo their edits, so it stops. Make the change on your site, or re-import the post first.

"The URL (slug) was not changed on your site"

Just a note: you changed the slug in Blog AI, but Blog AI never changes a live post's address, because that breaks every link to it.

Internal links go to the wrong address

Blog AI links to your other posts using the addresses Google Search Console reports, or the address it published them at. If your addresses changed, let Google sync and run Import posts and pages on the Sites page.

Posts have no Search Console data

Blog AI matches each post by its live address. If your site's post address pattern is wrong, or the Search Console property doesn't cover the blog's address, numbers stay empty. Open the post's live link from Blog AI: if it doesn't load the post, the address is wrong. See Google problems and fixes.

A scheduled post went out at the wrong time

You pick the time in your own computer's time zone. Your CMS may show it in the site's time zone, so it can look shifted there. Platforms without their own scheduler get the post within about five minutes of the time. If publishing fails, you get an email with the reason. See Publish or schedule a post.

Still stuck?

Open the post and copy the full message under Last publish attempt failed, then contact us with the site name and that text.