Publish into the CMS you already run
Opinly writes, schedules and publishes straight into WordPress, Webflow, Wix, Shopify, Framer and HubSpot — and imports what is already there, so the whole blog lives in one place. Running headless instead? The SDK renders Opinly content inside your own app.
- Posts, in the format your platform expects
- Sections and categories
- Images, uploaded to the platform that hosts them
- Posts you already published, with their images
- Authors and categories, where the platform owns them
Scheduling, drafts and revisions stay in Opinly. Unpublishing never deletes the live article.
Exactly what crosses each lane differs by platform — Framer and HubSpot, for two, never host your in-body images.
Two ways to get Opinly content onto your site
They are genuinely different products, not tiers of the same one. Pick based on who you want rendering the page.
Your CMS keeps hosting the pages
Connect WordPress, Webflow, Wix, Shopify, Framer or HubSpot. Opinly writes and schedules the post, then pushes it into the platform, which serves it on your existing blog with your existing design. Anything already published there is imported first, so you are not starting from an empty library.
Your app renders the pages
No CMS in the middle. The Opinly SDK fetches posts over a versioned REST API and hands your app the data and rendering primitives — you own the layout, the routes and the markup. There are packages for Next.js, Nuxt, SvelteKit, React, Vue and Svelte, and a webhook tells your site when to revalidate.
The six CMS integrations
Each one connects differently and each one hands a different set of entities back and forth. The platform page spells out what publishes and what does not. The label on each card below is the one Opinly shows on the card you click in the app, so where it still says beta, expect the constraints on that page to move as it hardens.
WordPress
BETAPublish HTML posts with their categories, excerpt and Rank Math or Yoast SEO meta, sync categories both ways and authors down, and let Opinly install the analytics plugin for you.
WordPress integration →Webflow
BETAMap Opinly onto your own CMS collection — body, image, category, author — then publish items straight into Webflow.
Webflow integration →Wix
BETAConnect with a site API key, pick a default author, and Opinly pushes posts to the Wix blog in Wix's own rich-content format.
Wix integration →Shopify
BETAPublish articles into any Shopify blog, import the articles and tags you already have, and attribute orders back to the post.
Shopify integration →Framer
STABLEMap Opinly onto a Framer CMS collection, publish posts as collection items, and let Opinly republish the site for you.
Framer integration →HubSpot
BETAPublish into any HubSpot blog with authors and tags, import the posts you already have, and keep your HubSpot modules intact.
HubSpot integration →What each platform actually does
The honest comparison, including the parts that constrain you. Tags exist on two of the six, and only HubSpot pushes them back; in-body images are uploaded into the platform on four and stay on Opinly's CDN on Framer and HubSpot; and the author is owned by the platform on WordPress, Webflow and Wix, is yours to create on Shopify and HubSpot, and on Framer is whatever you wrote into the field you mapped.
| Capability | WordPress BETA | Webflow BETA | Wix BETA | Shopify BETA | Framer STABLE | HubSpot BETA |
|---|---|---|---|---|---|---|
| How you connect | Application Password for an Editor or Administrator, from the WordPress authorize screen or created by hand | A Webflow Site API token. Connecting as a Webflow app is not open to customers yet | A Wix API key plus your site details. The one-click app install is not available yet | Shopify app install (OAuth). There is no API-key route | Your project URL plus a Framer API key. There is no OAuth route | Sign in to HubSpot and approve access to your content (OAuth). There is no API-key route |
| What Opinly pushes | HTML posts with categories, excerpt and Rank Math or Yoast SEO meta, through a queued worker on a fixed set of IPs | HTML into the CMS collection and fields you choose, as live items | Ricos, Wix's own rich-content format | HTML articles into a Shopify blog | HTML into the collection and fields you choose, then a Framer site publish | HTML posts with SEO meta, summary, author and tags into the HubSpot blog you choose |
| What Opinly imports | Posts, authors, categories and images | Published posts, authors and categories | Posts, authors and categories | Blogs, articles, article tags and the images in your Files library | Published collection items and their images. Framer drafts are skipped | Blogs, authors, tags and published posts. HubSpot drafts are skipped |
| Authors | Your WordPress users, synced down. Authors are not created in Opinly | Items in your author collection, synced down. Create them in Webflow first; ones you delete there are removed | Wix members, synced down. Publishing needs an author with a Wix member behind it | A plain name on the article, so authors can be created in Opinly | The name is written into the author field you mapped. An option field with no matching option is left unset | Imported from HubSpot. An author created in Opinly is created in HubSpot on first publish |
| Sections | WordPress categories, including hierarchy. Folders you create push up | Your category collection. A missing category is created at publish | Wix categories. Folders you create push up | Shopify blogs, read-only. Create the blog in Shopify — publishing needs one | Your Opinly folder name, written into the category field you mapped | HubSpot blogs, read-only. A post in no blog goes to your default blog |
| Tags | Not supported | Not supported | Not supported | Imported from Shopify. Tags are not pushed back | Not supported | Imported and pushed with each post. Missing tags are created in HubSpot |
| Images in the body | Uploaded to the WordPress media library | Uploaded to Webflow assets | Uploaded to Wix media | Copied into your Shopify Files library and served from there. An image not uploaded yet is left out | Served from Opinly's CDN, not uploaded to Framer | Served from Opinly's CDN, not uploaded to HubSpot |
| Analytics pixel | The Opinly plugin, installed for you when the connected user is an Administrator. Otherwise you upload it and paste a key | Not available on Webflow today | A snippet you paste into your Wix custom code | A custom pixel Opinly generates and you paste into your Shopify admin | Written into your Framer custom code for you when you connect | A snippet you paste into your site's head HTML |
True on every integration
- It runs in both directions
- Opinly pushes new posts up and imports what is already on the platform — and on the platforms that own your authors and sections, those come down too. The matrix above says which ones do.
- Opinly becomes the source of truth
- After a post is imported, editing its body in the CMS will not flow back. Re-sync tracks slug changes only, so edit in Opinly and publish out.
- Scheduling is always Opinly-side
- The publish time lives in Opinly for every integration, so it works the same way whether or not your platform has its own scheduler.
- Unpublishing never deletes
- Unpublishing archives the post inside Opinly. The live article stays on your platform until you delete it there.
- A failed push does not lose the post
- If the platform rejects the write, the version is marked as failed with the reason. Nothing is silently dropped and nothing is rolled back behind your back.
- Keyword rankings track what you publish
- Whatever you publish is the same content Opinly measures for keyword rankings, so the loop closes on one library. AI-search visibility — how you show up in AI answers — is a paid add-on on top of your plan, not part of the integration.
Frequently asked questions
- Webflow vs WordPress: which is easier to run SEO content on?
- For day-to-day content operations the difference is setup and ownership. WordPress connects with an Application Password and Opinly maps onto the blog it already has, so there is nothing to configure per field. Webflow is a blank slate: you map Opinly onto your own CMS collection field by field, authors have to exist in Webflow before a post can reference them, and Opinly trims any field past the maximum length Webflow sets. WordPress also has the more complete analytics setup — approve Opinly as an Administrator on the guided authorize route and the analytics plugin installs itself where the host allows it, while Webflow has no pixel install route today.
- Webflow vs Wix for a blog?
- Wix gives you a fixed blog structure, so the Opinly setup is short: paste an API key with your site details and choose a default author. Webflow gives you the collection design, so the setup is longer but the output is yours. The catch on Wix is that publishing requires an author backed by a Wix member, and a one-click app install is not available yet; the catch on Webflow is the field mapping and silent trimming. Both import posts, authors and categories on connect.
- Framer or the SDK for a Framer site?
- If your Framer site renders its blog from a Framer CMS collection, use the Framer integration: Opinly maps onto that collection, publishes posts as items and republishes the site, and no code goes into your project. Reach for the SDK only if the blog is not a Framer collection at all. The Framer trade-offs are worth knowing first — in-body images stay on the Opinly CDN rather than moving into Framer, and there is no revenue attribution on Framer.
- Do I have to install a plugin?
- Only on WordPress, and only for analytics — approve Opinly as an Administrator on the guided authorize route and it installs and activates the plugin for you where your host permits remote plugin installs; otherwise you upload the plugin and paste a key. Content publishing on WordPress uses the REST API and an Application Password, with no plugin at all. Webflow, Wix, Shopify, Framer and HubSpot use their own app and API surfaces.
- What if my CMS is not one of the six?
- Use the SDK. Opinly becomes the content API and your application renders the pages, which works with any stack rather than a fixed list. Start at the docs, or the Next.js guide if that is your framework.
- Does connecting my CMS also track traffic and revenue?
- Analytics is a separate connection from content publishing, and it differs by platform. On WordPress, approve Opinly as an Administrator on the guided authorize route and the analytics plugin installs itself, with WooCommerce revenue included. On Framer, Opinly writes the pixel into your site custom code when you connect and republishes the site. Wix and HubSpot take a one-line snippet you paste into your site code. Shopify never provisions off a content connect: Opinly generates a custom pixel and you paste it into Settings → Customer events, which is also where its order revenue comes from. Webflow has no pixel install route today. Framer and Wix report traffic and form conversions, not revenue.
- Can I move my content later?
- Every post lives in Opinly as well as on your platform, including the ones imported from it. You can switch the connected platform, and anything already published stays live where it is. Two things to know before you do: switching to a different platform clears the link between each Opinly post and the article it created, so the old articles stay live but Opinly stops updating them; and disconnecting then reconnecting the same platform re-imports those articles as new posts rather than matching them back up.
Connect your CMS and start publishing
Research, draft, schedule and publish in one place — and let your existing site do what it already does well.