[{"data":1,"prerenderedAt":75},["ShallowReactive",2],{"help-article-pushing-to-your-cms":3},{"data":4},{"title":5,"excerpt":6,"content":7,"help_category":8,"seo":11},"Pushing to Your CMS","m18t writes and optimizes content, then pushes the finished piece to your headless CMS. Learn how to push to Strapi, what gets sent, and how environments work.","\u003Cp>\u003Cstrong>What you'll learn\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Why m18t feeds your headless CMS instead of being one.\u003C\u002Fli>\n\u003Cli>How to push a content piece to Strapi, and what gets sent.\u003C\u002Fli>\n\u003Cli>How environments and localized siblings are handled.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Chr>\n\u003Ch2>The concept: m18t writes, your CMS serves\u003C\u002Fh2>\n\u003Cp>A CMS like Strapi serves data to your website's front end. m18t is where you \u003Cem>write, review, and optimize\u003C\u002Fem> — then it pushes the finished piece across to your CMS. You keep one writing surface across every \u003Ca href=\"\u002Fhelp\u002Fbrand-vs-business\">brand\u003C\u002Fa> and a clean separation: drafting and \u003Ca href=\"\u002Fhelp\u002Fthe-seo-philosophy\">SEO\u003C\u002Fa> live in m18t; delivery to your site lives in your CMS.\u003C\u002Fp>\n\u003Cp>Native CMS support today is \u003Cstrong>Strapi v5\u003C\u002Fstrong>. Other vendors (WordPress, Sanity, Contentful, Payload) are roadmap — the adapter architecture exists, but only Strapi is wired right now. If your stack is Strapi, this is a first-class path; if it isn't, this article is a preview of where it's headed.\u003C\u002Fp>\n\u003Cp>When you push, m18t converts the \u003Ca href=\"\u002Fhelp\u002Fthe-unified-content-table\">rich-text\u003C\u002Fa> body to Markdown, assembles the SEO metadata, and sends it to your brand's connected Strapi instance for the chosen environment.\u003C\u002Fp>\n\u003Ch2>How to push content to Strapi\u003C\u002Fh2>\n\u003Col>\n\u003Cli>Set up the \u003Ca href=\"\u002Fhelp\u002Fconnect-strapi\">Strapi connection\u003C\u002Fa> for the brand first — instance URL, API token, environment. Tokens live in the \u003Ca href=\"\u002Fhelp\u002Fthe-secret-vault\">vault\u003C\u002Fa>.\u003C\u002Fli>\n\u003Cli>Open the content piece and go to the \u003Cstrong>Publishing\u003C\u002Fstrong> tab (it appears after the first save).\u003C\u002Fli>\n\u003Cli>In the \u003Cstrong>Push to CMS\u003C\u002Fstrong> section, pick the environment: \u003Cstrong>Production\u003C\u002Fstrong>, \u003Cstrong>Development\u003C\u002Fstrong>, or \u003Cstrong>Local\u003C\u002Fstrong>.\u003C\u002Fli>\n\u003Cli>Click \u003Cstrong>Push to CMS\u003C\u002Fstrong>. If this piece has already been synced, the button reads \u003Cstrong>Update in CMS\u003C\u002Fstrong> instead, and the section shows the existing document ID.\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Cp>The section tells you whether the piece is synced yet and, once it is, shows its Strapi document ID so you can confirm the link.\u003C\u002Fp>\n\u003Ch2>Localized content\u003C\u002Fh2>\n\u003Cp>If the piece belongs to a \u003Ca href=\"\u002Fhelp\u002Flocale-groups\">locale group\u003C\u002Fa>, the Push to CMS section shows a \u003Cstrong>Localization Sync Status\u003C\u002Fstrong> panel listing the current piece and each sibling, with whether each has been pushed. Tick \u003Cstrong>Sync current and all unsynced sibling locales\u003C\u002Fstrong> to push the current piece plus any unsynced siblings and link them through Strapi's localization API in one operation. See \u003Ca href=\"\u002Fhelp\u002Flocale-groups\">Locale Groups & Translation\u003C\u002Fa> for the full picture.\u003C\u002Fp>\n\u003Ch2>Common variations\u003C\u002Fh2>\n\u003Cp>\u003Cstrong>Multiple environments per brand.\u003C\u002Fstrong> A brand can hold separate Strapi connections for production, development, and local. The environment select on the push controls which one you're targeting, so you can push to a staging instance before production.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Checking the result.\u003C\u002Fstrong> The Publishing tab has a \u003Cstrong>Recent Activity\u003C\u002Fstrong> log, and \u003Cstrong>View All Logs\u003C\u002Fstrong> opens the full record. If a push fails, the error is recorded there.\u003C\u002Fp>\n\u003Ch2>FAQ\u003C\u002Fh2>\n\u003Cp>\u003Cstrong>Can I push to WordPress \u002F Sanity \u002F Contentful \u002F Payload?\u003C\u002Fstrong>\nNot natively today — Strapi v5 is the only wired CMS. Other vendors are roadmap. Don't plan around them being live yet.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Where does the content type matter?\u003C\u002Fstrong>\nYour m18t \u003Ca href=\"\u002Fhelp\u002Fregistering-a-custom-content-type\">content type\u003C\u002Fa> maps to the target collection in Strapi. Make sure your Strapi collection exists and (for translations) has i18n localization enabled, or Strapi will reject the payload.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>What's the difference between "Push to CMS" and "Update in CMS"?\u003C\u002Fstrong>\nFirst push creates the entry and the button says \u003Cstrong>Push to CMS\u003C\u002Fstrong>. After that, m18t knows the document ID, so the button becomes \u003Cstrong>Update in CMS\u003C\u002Fstrong> and subsequent pushes update the same entry.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Does pushing to my CMS also post to social?\u003C\u002Fstrong>\nNo. CMS push and \u003Ca href=\"\u002Fhelp\u002Fpublishing-to-facebook-and-instagram\">social publishing\u003C\u002Fa> are separate actions on the Publishing tab. Each destination is triggered on its own.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Will it push automatically when I schedule a date?\u003C\u002Fstrong>\nNo. There's no auto-publish — pushing to your CMS is a manual click. See \u003Ca href=\"\u002Fhelp\u002Fscheduling-vs-publishing\">Scheduling vs. Publishing\u003C\u002Fa>.\u003C\u002Fp>\n\u003Ch2>What's next\u003C\u002Fh2>\n\u003Cul>\n\u003Cli>\u003Ca href=\"\u002Fhelp\u002Fconnect-strapi\">Connect Strapi (CMS)\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"\u002Fhelp\u002Flocale-groups\">Locale Groups & Translation\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"\u002Fhelp\u002Fscheduling-vs-publishing\">Scheduling vs. Publishing\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"\u002Fhelp\u002Fregistering-a-custom-content-type\">Registering a Custom Content Type\u003C\u002Fa>\u003C\u002Fli>\n\u003C\u002Ful>\n",{"slug":9,"title":10},"content-and-publishing","Content & Publishing",{"meta_title":12,"meta_description":6,"keywords":13,"canonical_url":14,"og_title":5,"og_description":15,"og_image":16,"robots":17,"json_ld":18},"Pushing to Your CMS | m18t Help","push to CMS, headless CMS, strapi, content sync, environments, document id, cms publishing","https:\u002F\u002Fm18t.com\u002Fhelp\u002Fpushing-to-your-cms","m18t writes; your CMS serves. Push a finished piece to your brand's connected Strapi instance for the chosen environment.","https:\u002F\u002Fm18t.com\u002Fog-default.png","index, follow",{"@context":19,"@graph":20},"https:\u002F\u002Fschema.org",[21,34,59],{"@type":22,"headline":5,"description":6,"articleSection":10,"inLanguage":23,"datePublished":24,"dateModified":24,"image":16,"author":25,"publisher":29,"mainEntityOfPage":32},"Article","en","2026-06-25",{"@type":26,"name":27,"url":28},"Organization","m18t","https:\u002F\u002Fm18t.com",{"@type":26,"name":27,"url":28,"logo":30},{"@type":31,"url":16},"ImageObject",{"@type":33,"@id":14},"WebPage",{"@type":35,"mainEntity":36},"FAQPage",[37,43,47,51,55],{"@type":38,"name":39,"acceptedAnswer":40},"Question","Can I push to WordPress \u002F Sanity \u002F Contentful \u002F Payload?",{"@type":41,"text":42},"Answer","Not natively today — Strapi v5 is the only wired CMS. Other vendors are roadmap. Don't plan around them being live yet.",{"@type":38,"name":44,"acceptedAnswer":45},"Where does the content type matter?",{"@type":41,"text":46},"Your m18t content type maps to the target collection in Strapi. Make sure your Strapi collection exists and (for translations) has i18n localization enabled, or Strapi will reject the payload.",{"@type":38,"name":48,"acceptedAnswer":49},"What's the difference between \"Push to CMS\" and \"Update in CMS\"?",{"@type":41,"text":50},"First push creates the entry and the button says Push to CMS. After that, m18t knows the document ID, so the button becomes Update in CMS and subsequent pushes update the same entry.",{"@type":38,"name":52,"acceptedAnswer":53},"Does pushing to my CMS also post to social?",{"@type":41,"text":54},"No. CMS push and social publishing are separate actions on the Publishing tab. Each destination is triggered on its own.",{"@type":38,"name":56,"acceptedAnswer":57},"Will it push automatically when I schedule a date?",{"@type":41,"text":58},"No. There's no auto-publish — pushing to your CMS is a manual click.",{"@type":60,"itemListElement":61},"BreadcrumbList",[62,66,70,73],{"@type":63,"position":64,"name":65,"item":28},"ListItem",1,"Home",{"@type":63,"position":67,"name":68,"item":69},2,"Help","https:\u002F\u002Fm18t.com\u002Fhelp",{"@type":63,"position":71,"name":10,"item":72},3,"https:\u002F\u002Fm18t.com\u002Fhelp\u002Fcategories\u002Fcontent-and-publishing",{"@type":63,"position":74,"name":5,"item":14},4,1786312170024]