Framer

Webflow Integration for Framer

HaloSEO connects to Framer through the Framer plugin and the CMS API. This page explains the connection, the permissions it needs, and what happens when something breaks.

How HaloSEO connects to Framer

You install the HaloSEO plugin from the Framer plugin marketplace and run it inside your project. The plugin asks for a project token, which you generate in HaloSEO. That token lets HaloSEO read your CMS collections and write new items to the collection you choose. It does not need access to your Framer account, your billing, or any other project. You can revoke the token in HaloSEO at any time, and the plugin stops writing immediately.

What a published post looks like on a Framer site

HaloSEO writes into a CMS collection you already have, so the post uses your existing collection page template. Headings, body text, links and images inherit the fonts, colours and spacing set in that template. There is no separate HaloSEO stylesheet and no iframe. If you change the template later, every published post picks up the change. Posts that need a layout your template does not have are held back rather than published in a broken state.

What happens on Framer that does not happen elsewhere

Framer stores content in CMS collections, and HaloSEO writes to those collections directly rather than through a page builder. That means a post can appear in more than one place on your site, such as a blog index and a related posts list, without extra setup. Framer also publishes the whole site on each deploy, so a new post goes live with your next publish rather than on its own schedule. HaloSEO queues the post and marks it ready, and it goes live when you publish.

What breaks, and what happens when it does

The most common failure is a changed collection schema. If you rename or remove a field HaloSEO writes to, the write fails and the post stays in the queue. HaloSEO flags the missing field in your dashboard and does not publish a partial item. A revoked or expired token stops all writes until you issue a new one. If Framer is down or slow, HaloSEO retries the write and reports the delay. Nothing is published twice, because each post carries an ID that Framer checks before it creates an item.

Who this is not right for

This is not right for you if your Framer site has no CMS collections, or if you publish pages by hand and want to keep it that way. It is also not right for you if you need posts to go live the moment they are written, because Framer publishes on your schedule, not ours. And it is not a fit if you want to review and rewrite every sentence before it goes out, since HaloSEO is built to publish without that step.

the platform

Framer

the feature

Webflow Integration

How it runs, once it is connected

You do the first step. HaloSEO does the other six, on its own, every week.