Framer

WordPress Integration for Framer

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

How HaloSEO connects to Framer

HaloSEO connects to your Framer site through the Framer CMS API. You create an API key in your Framer account and give it to HaloSEO. The key lets HaloSEO read your CMS collections and write new items to them. It does not give HaloSEO access to your Framer account settings, your billing, or your other projects. You can revoke the key in Framer at any time, and publishing stops as soon as you do.

What a published post looks like on a Framer site

HaloSEO writes each post as an item in the CMS collection you choose. The post uses the fields your collection already has: title, slug, body, meta description, and image. Your Framer site renders it with the same layout, fonts, colours, and components as every other post on the site. Nothing is injected into your pages and no widget is added. If your collection has custom fields, HaloSEO fills the ones you map and leaves the rest alone.

What happens on Framer that does not happen elsewhere

Framer sites are built and published as static pages, so a new CMS item only appears on the live site after Framer rebuilds and you publish. HaloSEO writes the item and triggers the publish step where your plan allows it. If your plan does not allow API publishing, the item sits in the CMS as a draft and you publish it from the Framer editor. Internal links are written as relative paths so they resolve on your Framer domain. Sitemap and structured data come from Framer, not from HaloSEO.

What breaks, and what happens when it does

The common failures are an expired or revoked API key, a renamed CMS collection, a field that was deleted or changed type, and a Framer publish that fails on their side. When a write fails, HaloSEO retries, then marks the post as failed and shows the error in your dashboard. It does not publish a partial post. If the key is revoked, queued posts stay queued until you add a new key. Nothing is deleted from your CMS by HaloSEO.

Who this is not right for

This is not right for you if your Framer site has no CMS collection set up for posts, or if you are on a Framer plan that does not allow API access to the CMS. It is also not right for you if you want to hand edit every post in the Framer editor before it goes live, because HaloSEO is built to publish without that step. In those cases, use HaloSEO with a WordPress site instead, or wait until your Framer setup supports the connection.

Related

How it runs, once it is connected

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

  1. 01

    Connect your website

  2. 02

    HaloSEO researches keywords

  3. 03

    Writes blog posts

  4. 04

    Publishes automatically

  5. 05

    Creates internal links

  6. 06

    Builds backlinks

  7. 07

    Improves rankings on Google and AI search engines