How to Publish From Frase to WordPress, Webflow, Sanity, Wix, or FraseCMS

Georgina D'SouzaMarketing Manager
9 min read

Frase publishes to WordPress, Webflow, Sanity, Wix, and FraseCMS. Here's exactly what you connect and what happens when you hit publish, CMS by CMS.

#AI Visibility

How do you publish from Frase to WordPress, Webflow, Sanity, Wix, or FraseCMS?

You connect your CMS once in Frase's integration settings (a site URL and credentials for WordPress, an API token for Webflow or Sanity, an API key and site ID for Wix), then publish any piece straight from the content editor. Frase pushes the title, body, SEO meta, and featured image in as a draft or a live post, or you can skip the external CMS entirely and host on FraseCMS instead. Nothing goes live on its own — by default a person reviews and approves every publish. (Auto-publish, where a piece can ship without that review, is an opt-in setting on FraseCMS.)

The five destinations: WordPress, Webflow, Sanity, Wix, and FraseCMS. Here's what each one actually requires and does, plus how Frase's agent-native workflow fits publishing into the rest of your content pipeline.

What Frase pushes when you publish

Across every CMS, the same core payload goes out:

  • Title
  • Body content
  • URL slug
  • SEO title and meta description
  • Featured image
  • JSON-LD schema markup, on the CMS platforms that support it

What differs is the connection method, the draft-vs-live behavior, and a few platform-specific quirks worth knowing before you connect anything. Before you connect, have the right credential ready:

  • WordPress: site URL, username, and an Application Password
  • Webflow: an API token, plus the target site and collection
  • Sanity: an API token, project ID, and dataset name
  • Wix: an API key, account ID, and site ID
  • FraseCMS: nothing to gather, it's built into your Frase site already
CMSDraft supportScheduled publishJSON-LD schemaCredential type
WordPressYesYesYesSite URL + username + Application Password
WebflowYesNoNoAPI token
SanityYesNo (requires Sanity's own Scheduling plugin)YesAPI token + project ID + dataset
WixYesNoYesAPI key + account ID + site ID
FraseCMSYesYesYesNothing external — built in

Swipe to see more →

WordPress

What you connect for WordPress

Your site URL, a WordPress username, and an Application Password generated from your WordPress dashboard (Users → Profile → Application Passwords). Frase talks to your site through the standard WordPress REST API, so there's no plugin required to publish. If your site runs an SEO plugin like Yoast or RankMath, Frase detects it and writes the SEO fields it understands. Credentials are encrypted at rest.

What happens when you publish to WordPress

Frase creates the post as a draft, a scheduled post, or a live publish, your call. It also detects whether you're running Yoast or RankMath and writes SEO title and meta description into the fields those plugins expect, so your existing SEO setup doesn't get bypassed. Full JSON-LD schema markup is supported.

Common WordPress publish issues

If a security plugin, firewall, or CDN sits in front of /wp-json, WordPress may return a non-JSON response and the publish will fail with a clear error telling you to allow REST API access. A rejected Application Password shows up as an authentication error naming the likely cause, an expired or mistyped password, or a host stripping the auth header, rather than a generic failure.

Webflow

What you connect for Webflow

A Webflow API token. Frase lists the sites your token can access, and you pick the target site and the CMS collection you want to publish into, then map Frase's fields (title, body, slug, image) to your collection's fields.

What happens when you publish to Webflow

Frase creates or updates a CMS item in that collection as a draft or a published item. Webflow doesn't have native scheduled publishing, so scheduling isn't available on this destination, publish now or leave as a draft and publish from Webflow's side later. Webflow also doesn't support JSON-LD schema markup injection through its CMS API, so structured data isn't pushed on this path.

Common Webflow publish issues

The field mapping step matters. If your collection's body field expects rich text and you've mapped it to a plain-text field, formatting won't carry over cleanly, so it's worth checking the mapping once when you first connect a collection.

Sanity

What you connect for Sanity

A Sanity API token, your project ID, and the dataset name (usually production). Frase discovers your document schema and lets you pick which document type to publish into.

What happens when you publish to Sanity

Frase converts the article body into Portable Text, the block-based content format Sanity expects, rather than pushing raw HTML, so headings, lists, bold and italic text, and links carry over as native Sanity blocks instead of an embedded HTML string. That matters if your Sanity-powered frontend renders Portable Text directly (most do). JSON-LD schema markup is supported and pushed alongside the document; scheduled publishing isn't, since that requires Sanity's own Scheduling plugin, so a Sanity publish from Frase is draft or live, not scheduled.

Common Sanity publish issues

If your Sanity schema requires custom fields Frase doesn't know about, the publish can fail validation on Sanity's side, worth a quick check of your document type's required fields before your first publish.

Wix

What you connect for Wix

A Wix API key, your Wix account ID, and the site ID (Wix calls this the meta-site ID) for the site you're publishing to, used against the Wix Blog API.

What happens when you publish to Wix

Frase converts the article into RICOS, Wix's own rich content format, and publishes through the Wix Blog API as a draft or a live post. Wix does support JSON-LD schema markup injection (with a conservative size cap to avoid bloating the page), so structured data does carry over here, unlike Webflow.

Common Wix publish issues

Wix's API doesn't always return a clean public URL right after publish, so Frase falls back to a URL template you can configure once (something like yoursite.com/post/{slug}) rather than guessing.

FraseCMS: publish without an external CMS at all

What FraseCMS is

FraseCMS is Frase's own headless content layer. Instead of pushing content out to a third-party platform, you publish directly into Frase, and Frase serves the page. There's no external credential to manage, no field mapping, no API token; you write, you optimize, you publish, done.

What's different about publishing to FraseCMS

Publishing to FraseCMS does one thing the other four destinations don't. The moment a post goes live (or is edited), Frase re-indexes it for Frase Answers, the conversational front door that answers visitor questions from your own content. On WordPress, Webflow, Sanity, or Wix, keeping your Answers index current means your site content and Frase's record of it need to stay in sync through your own publishing cadence. On FraseCMS, publish and index are the same event, so a piece goes live and immediately becomes something Frase Answers can cite and quote back to a visitor, or hand to Content Guard for decay monitoring, without a separate sync step.

A FraseCMS page also keeps the research it was built from: the sources, the questions people were asking, the brief it was written against. That record stays attached to the post after it publishes. So when a ranking slips or an AI engine stops citing the page, re-optimization starts from the original evidence, not a fresh guess at what the page was supposed to prove.

Draft, scheduled, or live on FraseCMS

FraseCMS supports all three: draft, scheduled, and live publish, the same range WordPress offers. Nothing ships automatically unless you've opted into auto-publish.

Which one should you use?

If you already run your site on WordPress, Webflow, Sanity, or Wix, connect that CMS and keep publishing where your site already lives, there's no migration required. If you're starting fresh, evaluating a rebuild, or want the tightest loop between publishing and your on-site answer engine, FraseCMS is the option built for that: hosted, headless, and wired directly into Frase Answers by default. Both paths run the same research → write → optimize → publish → monitor → fix loop underneath; the CMS choice only changes where the page actually lives.

FraseCMS is the one destination where all four of these show up together: native scheduled publishing, structured data regenerated on every render, instant Frase Answers indexing, and pages that keep the research they were built from. The other four remain full, honest publishing destinations; FraseCMS is just where all four of those capabilities show up together without you wiring them yourself.

Publishing is one step in a longer loop

Getting content onto your CMS is rarely the last step that matters. Once a piece is live, Frase's AI Visibility tracking (read what AI visibility means if the term is new) watches whether AI engines like ChatGPT, Perplexity, Gemini, and Google AI actually cite it, and Content Guard watches for ranking and traffic decay in Google Search Console, proposing a fix for your approval when a page starts slipping. Publishing isn't the finish line; it's the point where monitoring starts. You can check your current AI visibility across engines free before you publish your next piece, to see where the gaps already are.

If you want to see how this looks end to end, from research through publish through monitoring, start a free trial and connect your CMS in the integrations settings. Whether you publish from Frase to WordPress, Webflow, Sanity, Wix, or FraseCMS, the setup takes minutes and the loop keeps running after that first publish. Or if you're deciding between CMS options first, explore what FraseCMS does differently and see how Frase's agent-native workflow fits your stack.

Frequently Asked Questions

Which CMS platforms does Frase publish to?

Frase publishes to WordPress, Webflow, Sanity, Wix, and FraseCMS, Frase's own headless content layer. You can also connect multiple CMS platforms to a single Frase site and choose the destination per publish.

Do I need the WordPress plugin to publish from Frase?

No. Frase connects to WordPress through the standard WordPress REST API using a site URL, username, and an Application Password you generate from your WordPress dashboard. No plugin install is required to publish. There is no separate Frase plugin to install or maintain; if your site runs an SEO plugin like Yoast or RankMath, Frase detects it and writes the SEO fields it understands.

Does Frase publish as a draft or does it go live automatically?

You choose, and every connection supports at least draft and live publish. By default a person reviews and approves before anything ships. Fully automatic publishing is an opt-in setting available on FraseCMS.

Does publishing through Frase carry over my SEO meta and schema markup?

SEO title and meta description are pushed on every connection. JSON-LD schema markup is supported on WordPress, Sanity, Wix, and FraseCMS. Webflow's CMS API doesn't support structured data injection, so schema markup isn't pushed on that destination.

What's different about publishing to FraseCMS instead of an external CMS?

FraseCMS is hosted and headless inside Frase, so there's no external credential or field mapping to manage. The key difference: publishing to FraseCMS immediately re-indexes the post for Frase Answers, the on-site answer engine, so a page becomes citable the moment it goes live. On external CMS platforms, staying current with Answers depends on your own publish and sync cadence.

Can I move my existing WordPress, Webflow, Sanity, or Wix content into Frase later?

Frase's publishing connections are built to work with the CMS you already have; you don't need to migrate content to start publishing through Frase. If you later decide to move to FraseCMS, that's a separate step from day-to-day publishing and worth planning with your team first.

Why did my WordPress publish fail with an authentication error?

The most common cause is a rejected Application Password, either mistyped, expired, or stripped by a security plugin or host before it reaches WordPress. Frase surfaces the specific error WordPress returns so you can tell which of those it is rather than a generic failure message.

Does Frase support scheduled publishing on every CMS?

No. WordPress and FraseCMS support scheduled publishing today. Webflow and Wix don't expose scheduled publishing through their APIs, and Sanity's scheduling lives in a separate plugin Frase doesn't currently drive, so on those three you publish immediately or leave the item as a draft to publish manually later.

For most teams, that means you can publish from Frase to WordPress today with full scheduling, and add Webflow, Sanity, Wix, or FraseCMS to the same site whenever you need them, without any extra setup work.


About the author

GD

Georgina D'Souza

Marketing Manager

Georgina D'Souza is a Marketing Manager at Frase and Copysmith AI, the company behind Frase.io and Describely.ai. She brings ten years of marketing experience — spanning early-stage startups to multinational enterprise — specializing in content marketing, SEO, and generative engine optimization, helping SaaS brands adapt their content strategies for AI-powered search. Georgina writes about generative engine optimization, AI search visibility, and content marketing for the AI era.


See Frase run on your own content.

Research your market, draft in your voice, and track where you show up across Google and AI search. Start free.

Start free trial

7-day free trial. No credit card.

Start free for 7 days
No credit card required
Try Frase Free →