Publish into your Framer CMS

Connecting Framer

Three steps, because Framer lets you design the collection and Opinly refuses to guess which field is which. You only do it once, and the mapping can be changed afterwards.

What actually publishes

Including the parts that constrain you. Framer behaves like Webflow in shape and like HubSpot on images, and both of those are worth knowing before you connect.

Posts become items in your collection

Opinly renders the post to HTML and writes it into the collection and fields you mapped, so your existing Framer design renders it. There is no Opinly-shaped layout imposed on the site.

Publishing publishes your site

After the item is written, Opinly runs a Framer publish so the post is actually live rather than sitting in an unpublished change. That is a real publish of the project, so run it when you are happy for the current state of the site to go out.

Opinly does not upload your images into Framer

Like HubSpot, and unlike WordPress, Shopify, Webflow and Wix, Opinly does not upload images into Framer's own media. The post body points at Opinly-hosted image URLs, and the cover image is written into the image field you mapped as an Opinly URL too. Images in posts imported from Framer keep their original Framer URLs.

The author is a value, not a reference

Opinly writes the author name into the field you mapped. A text field takes the name as-is; an option field needs an option whose name matches, and if none does the field is left unset rather than failing the publish. Author collections referenced from your posts are not wired up.

Categories come from your Opinly folder

The folder a post sits in is written into the category field you mapped, by name. As with the author, an option field needs a matching option. Framer categories are not synced down into Opinly as folders.

Tags are not supported

The tag surface is hidden for Framer sites rather than shown and quietly dropped at publish.

The live URL is read from your sitemap

Rather than guessing the blog path, Opinly reads the published sitemap after the site publish to find the post and store its real URL. If the sitemap has not caught up yet, the route prefix it learned last time is used instead.

Unpublishing leaves the live post alone

Unpublishing archives the post in Opinly. The item stays live on your Framer site until you delete it there.

Traffic tracking

Analytics is a separate connection from publishing. On Framer, Opinly installs it off the back of a content connect, and it reports traffic and form conversions rather than revenue.

There is nothing to paste

When you connect Framer for content, Opinly writes the one-line pixel script into your site's custom code and publishes the site so it goes live. Web Analytics setup does the same for a Framer site that does not have it yet. Like any Opinly publish on Framer, that is a real publish of the whole project.

Page views, not revenue

On Framer the pixel reports traffic and form submissions, so your conversion goal is a form fill or plain analytics. Framer does not give the pixel your order totals, so a sale cannot be tied back to a post — pick Framer for traffic reporting, not for revenue attribution.

It fails safe

If the automatic install cannot reach your project it is reported as partial and an existing working connection is left alone. Opinly does not disable analytics that are already reporting, and you can still paste the snippet by hand.

Frequently asked questions

Is the Framer integration finished?

Framer is the one CMS Opinly publishes into that the app labels Stable rather than Beta — that is the label on the card you click. Publishing, importing, field remapping, scheduling and the automatic pixel install all work today; what is still moving is the edges, in particular how much of your Framer structure Opinly mirrors. Everything on this page describes what the integration does now, not what is planned.

Do I need to add code to my Framer site to publish?

No. Publishing goes through the Framer API with the key you pasted, so there is no component to add or maintain. The only code involved is the one-line analytics script, and Opinly writes that into your Framer custom code for you when you connect.

What happens to the posts already in my Framer collection?

The published ones are imported, with their images pulled into Opinly. Items still in draft in Framer are skipped. After import Opinly is the source of truth for the body — editing an item in Framer will not flow back, though a slug change will.

Framer vs Webflow through Opinly?

They are the same shape of integration — you own the collection, so you map Opinly onto your fields rather than accepting a fixed blog. Two differences matter. Webflow uploads your images, in the body and the cover, into Webflow assets and Framer does not, so on Framer they stay on the Opinly CDN. And Webflow resolves authors and categories as real references into your other collections, including creating a missing category, while Framer writes both as plain values into the fields you mapped. Both connect with a key or token you paste.

Can I schedule posts?

Yes, and the schedule lives in Opinly rather than in Framer, so it behaves the same way across every site you run.

Can I attribute a sale to a blog post on Framer?

No. Framer does not give the pixel your order totals, so Opinly reports traffic and form conversions but cannot tie an order back to the post. If revenue attribution is the point of the exercise, WordPress with WooCommerce or Shopify are the integrations that do it.

Do my post slugs have to be unique?

Keep them unique, yes. After creating an item Opinly finds it again by slug to record its Framer id, so two items sharing a slug in the same collection can leave the wrong one linked. Opinly keeps slugs unique on its side; the risk is duplicates that already exist in Framer.