Framer Publishing Troubleshooting

When a Framer publish fails, the status and error are recorded in Publish History. Use the sections below to fix the cause. For setup, see Publish to Framer CMS.

Token or authentication errors

• Confirm the Personal Access Token is active and belongs to the same Framer account that owns the project.
• Ensure the token has read and write access to CMS items.
• After rotating a token in Framer, reconnect the integration in PrismSEO — the old token stops working immediately.

Project or collection errors

• Double-check the Project ID and Collection ID. A token that's valid but points at the wrong project or collection fails validation.
• Confirm the target collection still exists and wasn't renamed or deleted.

A field didn't get populated

PrismSEO matches your collection fields by name, so an unmatched name is silently skipped.

• Make sure the collection has a clearly named field for each part of the article: Title, Slug, Content (rich text / HTML), and optionally Excerpt, SEO Title, SEO Description, Cover Image.
• Rename any ambiguous field to a recognized name so PrismSEO can map it.
• The body must be a rich text / HTML field — a plain short-text field can't hold a full article.

Duplicate or failed slug updates

• PrismSEO updates the existing item when a slug matches, so re-publishing shouldn't duplicate. If it does, confirm you're writing to the field that's actually your collection's slug field.
• If your collection enforces unique slugs and the update fails, verify the item isn't locked or in a conflicting state in Framer.

Slow or partial publishes

• Retry the failed item individually and watch Publish History.
• Repeated upstream Framer API errors (5xx) are transient — retry; if they persist, reconnect the credentials.

Still stuck?

Reconnect Framer from Integrations, verify the collection's field names against the field mapping, and do one draft publish to read the exact failing step.