How does "Publish to site" work?

Click Publish to site beside any draft or fix and it lands on the site you connected, as a draft you review in your own editor. SKYA never publishes anything live.

Two kinds of thing

• Content (an article, a page section, an FAQ block, an answer block, a product description) becomes an unpublished post or page. WordPress gets it through the SKYA Helper plugin (version 1.2.0 or later); Webflow gets it as a draft item in your blog collection through the SKYA Webflow app; Shopify gets it as an unpublished blog article or hidden page through the SKYA app; Framer, and in beta Ghost, Strapi, Directus, Payload, Sanity, Drupal and Adobe Experience Manager, get it as a draft through a key you create there.
• Fixes (schema, meta title and description, sitemap, robots, llms.txt, canonical, Open Graph) install through the platform's own API or the plugin, the same path the readiness page uses.

Where the button is

Beside every draft or fix that belongs on a site, and it works the same way everywhere: the readiness Fix now drawer (also opened from Where you stand and My Action Plan), the "Fix with content" writer on My Action Plan and on Competitors > Plan to beat competitors, Content Engine outputs that belong on a site, hallucination audit corrections, and reviewed blog and landing copy in Regulated Content. Social, video, ad and email copy has no place on the site, so it has no button.

No site connected

The button still shows. Click it and SKYA checks what your site runs on, then says one of three things right there: - WordPress, Shopify, Webflow, or a CMS that connects with a key: it offers to connect that platform on the spot. If this particular fix is one that platform cannot take, it says so and puts Copy first. - A custom-built site, or a builder SKYA has no connection for: it says SKYA cannot publish to it directly and gives you Copy, to add the fix or draft by hand or send it to whoever builds your site. If your pages do come from a CMS the page did not show, "My site does use a CMS" opens every way to connect. - A site it could not read: it opens the connect window with every way to connect.

Connect once; every draft and fix after that can go straight to it.

What each stack can take

• WordPress: everything, including drafts, with SEO title and description written into the fields Yoast and Rank Math read.
• Shopify: drafts, llms.txt, schema, meta description and Open Graph, published through the SKYA head block without touching your theme files. Shopify manages the sitemap itself, and robots.txt stays a change you make in your theme, because Shopify does not let apps edit it. Connect it from your project in SKYA: the Shopify App Store listing is still being prepared, so searching the App Store will not find it yet. Shopify bills a small yearly app charge on its own invoice.
• Webflow: drafts into a blog-like CMS collection, and page title, meta description and Open Graph written to the page after you approve them. Drafts and page fields wait for you to publish in Webflow. The SKYA Webflow app adds no code or files to your site, so schema, robots.txt and the sitemap stay in your own Webflow settings. For a Webflow store, AI Shopping also imports your products and saves a longer product description you approve as a staged change; SKYA never publishes your site and never reads orders or customer details. How to connect, and every permission the app asks for: Connecting Webflow to SKYA.
• Ghost, Strapi, Directus, Payload, Sanity, Drupal, Framer, Adobe Experience Manager: drafts only. All but Framer are in beta: the connection is built and you can connect it today, and we are still proving each one end to end on a live site, so review the first draft closely. Each connects with a key you create inside the CMS (the connect card says exactly where), SKYA checks the key against the platform before saving it, and every draft lands unpublished: a Ghost draft post, a Strapi draft entry, a Directus item with status draft, a Payload draft document, a Sanity document under drafts, an unpublished Drupal node, a draft Framer collection item, an unpublished AEM Content Fragment. Head tags, robots and sitemaps live in these stacks' templates or hosting, so those fixes stay copy-and-paste.

Headless formatting

Sanity and Payload store rich text as blocks, not HTML. SKYA converts headings, paragraphs, lists and quotes; bold, links and images inside a paragraph are flattened to text, so give those drafts a formatting pass in the editor. Ghost, Strapi, Directus, Drupal, Framer and AEM take the HTML as written.

A plugin older than 1.2.0 answers "update the plugin"; download the current one from the readiness page.