safe-publish

Plan and confirm Webflow site publishes with pre-publish checks.

111|18|Updated Jan 7, 2026
One-click install
npx skills add https://github.com/webflow/webflow-skills --skill safe-publish
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: safe-publish
Source: https://github.com/webflow/webflow-skills/tree/main/plugins/webflow-skills/skills/safe-publish
Command: npx skills add https://github.com/webflow/webflow-skills --skill safe-publish

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a safe, plan-confirm publish workflow for Webflow sites, showing what will change and requiring explicit user confirmation before going live, reducing the risk of unintended releases.

Core Features & Use Cases

  • Preview and plan: generate a detailed publish preview that lists changed pages and CMS items.
  • Pre-publish validation: run checks for broken references, missing required fields, and SEO gaps.
  • Explicit confirmation: require the user to type "publish" before deploying to subdomains or custom domains.
  • MCP-driven publishing: execute publishes through Webflow MCP tools and verify results post-publish.
  • Post-publish verification: re-fetch site details and confirm accessibility and URLs.

Quick Start

Use the safe-publish skill to review your site changes, then type "publish" to deploy after you confirm the scope and targets.

Frequently Asked Questions about safe-publish

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I preview Webflow site changes before publishing to production?

To preview Webflow site changes before publishing, the safe-publish workflow generates a detailed plan listing modified pages and CMS items, then requires explicit confirmation before any deployment goes live. This prevents unintended releases by making the full scope visible upfront.

What pre-publish validation checks are available for Webflow CMS items and pages?

Pre-publish validation for Webflow CMS items and pages checks for broken references, missing required fields, and SEO gaps before deployment. These checks run automatically during the planning phase to catch errors before changes reach production domains.

Can I require manual confirmation before a Webflow MCP deployment goes live?

Yes, Webflow MCP deployment can require manual confirmation by prompting the user to type "publish" before executing. This confirmation gate applies to site-wide changes including pages and CMS items, ensuring explicit approval for subdomain and custom domain targets.

What is the best way to verify a Webflow publish succeeded across site URLs?

The best way to verify a Webflow publish succeeded is through post-publish verification, which re-fetches site details via MCP tooling and confirms URL accessibility. This validation step ensures all changed pages and CMS items deployed correctly to their targets.

Does the Webflow safe-publish workflow support both subdomains and custom domains?

The Webflow safe-publish workflow supports publishing to both subdomains and custom domains. During the scope selection phase, users review all modification targets and explicitly confirm which domains receive the deployed changes before execution begins.