SEO by platform
SEO for Framer
Framer does not expose a public API that lets an outside service create CMS items on any site, so there is no direct connector to pretend with. What Framer does offer is two doors we already serve: it imports a CMS collection from an RSS feed, and its official Zapier and Make integrations create CMS items from a webhook.
How publishing works on Framer
Pick RSS when the Framer site just needs a blog that stays current: every project exposes a keyed RSS feed of its published articles, and Framer's RSS plugin maps each item's title, summary, date and full HTML body onto collection fields. Pick the webhook when you want each article to land the moment it publishes: a Zapier or Make trigger receives the article as JSON and a Framer action creates the CMS item. Either way the articles are rendered by Framer's own CMS templates, we deliver the content and the Framer designer decides how it looks.
A keyed RSS feed Framer can import
The feed carries the twenty most recent published articles by default, add a limit parameter for more, and each item's guid is our article id, which is what a feed importer reads to tell an update from a new item.
Help centre: FramerOr signed JSON the moment it publishes
The webhook delivers each article as JSON with title, slug, HTML, markdown, meta fields and a stable id, signed with an HMAC when a secret is set. Deliveries retry up to four times, and the id is the one value that stays the same across every attempt, so dedupe on it.
The universal fallback is documented too
RSS is the universal adapter: when a platform has no write API and no integration here, it very often has an RSS import, and the same keyed feed serves those.
Articles come off a planned calendar
Plan items on the content calendar and write them two ways: click Write on a card, or let Auto-write pick each one up at midnight on its calendar date. Both run the same researched pipeline, which drafts the article and then revises it against the content score across sweeps.
Every article is scored before you ship it
The content score runs 36 fixed checks in 6 categories, with no randomness anywhere: the same page always produces the same score. Each check comes back as a pass, a warn or a fail, and each failure names its specific fix.
What this connection will not do
Stated up front, because finding out after the first publish costs more. Each line is a fact about what we send Framer, not a guess about the platform.
Neither path can replace the body of an article that is already in the Framer CMS. A refresh publishes a new item, unless the automation matches on our id and updates in place. Documented: Framer
Publish verification cannot see inside Framer, so these paths show as delivered rather than verified. A new CMS item is also not on the live site until the Framer project is published again. Documented: Framer
Images stay hosted by us. Framer copies nothing into its asset store on import, so do not delete articles here while a Framer page still shows them. Documented: Framer
Connect it in three steps
The same fields the connect wizard asks for, in the order it asks.
Copy the keyed feed URL
The share key is the token in the project's share link: open Projects, then Copy share link, and take the part after /share/. The feed is /api/public/rss with that key, and anyone holding the full URL can read the feed, so treat it like a password.
Import it in Framer
In Framer, open the CMS and add a collection with Framer's RSS plugin as its source, then paste the feed URL. The plugin maps title, summary, date and body onto collection fields.
Design and re-sync
Design the collection's list and detail pages like any Framer CMS collection, and re-sync when you want new articles pulled in. Framer polls on its own schedule. Want articles the moment they publish instead? Set up the webhook path with Zapier or Make.
Questions people ask
The ones that decide whether this fits, answered with the verdict first.
- Why is there no direct Framer connector?
- Because Framer does not expose a public API that lets an outside service create CMS items on any site. Rather than fake one, the two doors Framer actually offers are documented and served: RSS import and the official Zapier and Make integrations.
- Framer says the feed is invalid. What now?
- Open the feed URL in a browser. If XML renders, the feed is fine and the import is being strict about something optional. Make sure the URL was pasted whole, key and all.
- Why did items import twice?
- The share key was rotated, so the feed URL changed and Framer treats it as a new source. Keep one feed URL per collection and rotate on purpose.
Other platforms
Same pipeline, different door. Every platform page states what its connector sends and what it will not.
Webflow
Articles land as items in the CMS collection you point the connection at, your Webflow templates render them like any other item, and new connections create draft items that wait in Webflow for your publish action.
Next.js
Two paths for a Next.js site. The blog package scaffolds list, article, tag and sitemap routes and fills them from the articles your project publishes, with nothing to host on your side. Or commit markdown into your existing content folder through the GitHub connection and leave your rendering alone.
Wix
Wix stores posts in Ricos, its own structured editor format, rather than HTML. So each article is converted, headings, lists, links and images, into that format before publishing, and posts open cleanly in the Wix editor as if written there.
SEO by platform
See it on your own site
A free audit grades your site A+ to F, then the calendar, the writer and the Framer connection do the week's work. No card required.