Get your Enterprise Workspace, team access, and core site settings in place before the build begins.
Create a new site from scratch, a template, or Webflow AI, or transfer an existing site into your Enterprise Workspace. Once your site has been added, coordinate with your Webflow account team or Webflow Support to confirm it's provisioned with the appropriate Enterprise Site plan and features before beginning development.
Where: Webflow Dashboard; Site settings > Plans
↳ Resources
Give your site a descriptive name that team members can easily identify in the Webflow Dashboard.
Where: Site settings > General
Identify who is responsible for designing, developing, managing content, reviewing changes, and publishing your site. Establish clear review and approval workflows, then invite collaborators to your Workspace or individual sites and assign roles and permissions based on their responsibilities. Use custom roles and granular access controls where applicable to your Enterprise setup.
Where: Workspace settings > Members; Site settings > Members
↳ Resources
Configure the staging domain your team will use to preview, test, and review changes before publishing to production. Enterprise teams may also use a custom staging domain to align with their existing review workflows.
Where: Site settings > Publishing > Staging
↳ Resources
If your Enterprise team requires restricted access to staging, enable private staging so only authenticated Workspace members and authorized guests can view the site. Publish the change for the setting to take effect.
Where: Site settings > Publishing > Staging
↳ Resources
Prevent search engines from indexing the Webflow staging subdomain so visitors are directed toward your intended production URLs.
Where: Site settings > SEO > Indexing
↳ Resources
Add branded icons for browser tabs, bookmarks, and mobile home screens. Upload an appropriate square image and use Webflow's icon settings to generate the required sizes. Consider a separate dark-mode favicon if needed.
Where: Site settings > General > Icons
↳ Resources
Choose the time zone used for scheduled CMS publishing. Make sure collaborators understand the site's time zone, particularly when working across regions.
Where: Site settings > General
↳ Resources
Set the appropriate primary language or locale code to help browsers, screen readers, and translation tools interpret your content correctly.
Tip: If you're using Webflow Localize, locale-specific language codes are managed through the Localize panel and override the legacy language-code setting in Site settings.
Where: Site settings > General; Localize panel > Locales
↳ Resources
If you're using Webflow Localize to support multiple languages or regions, plan which locales you'll offer, how localized URLs will be structured, and how your team will manage translations, localized content, and publishing. Follow the dedicated Localize checklist for detailed guidance.
Where: Localize panel > Locales
↳ Resources
Review the Webflow branding settings and disable the "Made in Webflow" badge where appropriate to maintain a consistent branded experience.
Where: Site settings > General
↳ Resources
Use web-optimized font files to minimize downloads and improve compatibility. WOFF2 is recommended for modern browsers. Where appropriate, use variable fonts to reduce the number of font files required.
If you're using Google Fonts, consider downloading and uploading them as custom fonts rather than relying on the Google Fonts API, particularly where privacy requirements apply.
Where: Site settings > Fonts
↳ Resources
Use font-display: swap where appropriate so text remains visible using a fallback font while custom fonts load. Review the display behavior for your uploaded fonts and any third-party font integrations.
Where: Site settings > Fonts
↳ Resources
Review the automatically assigned fallback fonts for your custom font families. Choose suitable alternatives to help maintain readability and layout consistency if custom fonts fail to load.
Where: Site settings > Fonts
↳ Resources
Agree on how designs will translate to Webflow, then hand off the assets and specs developers need.
Before handing off your designs, align on how styles, components, and layouts will be implemented in Webflow. Consider whether to use an existing CSS or Webflow framework, and establish naming conventions, responsive behavior, spacing systems, and reusable design patterns. These decisions help reduce rework and create a more maintainable site.
↳ Resources
If your team uses compatible AI tools, explore the Webflow MCP server to assist with design-system setup, creating and editing pages, or managing site content. Confirm supported capabilities and permissions before incorporating MCP into your workflow.
↳ Resources
Provide the approved font families, styles, and weights used in your designs. Limit unnecessary font variants to help keep the site performant, and include licensing or usage information where relevant.
Document your brand colors using web-ready values such as HEX, RGB, or HSL. Include meaningful names and intended uses for primary, secondary, neutral, and semantic colors.
Identify reusable values for colors, typography, spacing, and sizing. Establish consistent naming conventions and document how these design tokens should map to Webflow variables during implementation.
↳ Resources
Prepare images and other visual assets at appropriate dimensions and compression levels. Use SVG for suitable vector assets and consider WebP or AVIF for raster images, based on compatibility and quality requirements.
Check contrast between text, icons, interface elements, and their backgrounds. Address contrast issues during design rather than waiting until the site is built.
↳ Resources
Align design frames with Webflow's available breakpoints while ensuring layouts can adapt fluidly between viewport sizes. Document how key elements should resize, stack, or reflow.
↳ Resources
Provide a consistent typography scale for headings, paragraphs, labels, and other text styles. Document how font sizes, line heights, and spacing change across breakpoints.
↳ Resources
Establish standard content widths and container patterns to maintain visual consistency and reduce unnecessary styling variations during implementation.
Use a defined spacing scale throughout your designs and document how spacing adapts to different layouts and breakpoints.
Design important states such as hover, keyboard focus, active, disabled, and open. Include interaction details where appropriate so developers can implement consistent and accessible behavior.
↳ Resources
Design form validation, success, and error states. Include clear messaging and accessible feedback so visitors understand what happened and how to resolve problems.
↳ Resources
Design what visitors should see when a Collection list has no items. Use helpful text or relevant next steps instead of relying on the default empty state.
↳ Resources
Design an informative 404 page that helps visitors recover from a broken or unavailable URL and navigate to relevant content.
↳ Resources
Create a branded experience for password-protected content, including clear instructions and appropriate error messaging.
↳ Resources
If your site uses Webflow Site search, design the search results page, including result styling and helpful messaging for unsuccessful searches.
↳ Resources
Turn your design decisions into reusable variables, classes, and components the rest of the site builds on.
If your team selected a framework during design planning, set it up in Webflow before creating additional styles and components. Follow its conventions and adapt the framework to your approved design requirements.
Where: Designer
↳ Resources
Create reusable Webflow variables based on the design tokens defined during handoff. Organize and name them consistently so your team can maintain shared values across the site.
Where: Designer > Variables panel
↳ Resources
Build a centralized style guide page showing your typography, colors, spacing, buttons, forms, and reusable patterns. Include representative elements to make testing and maintenance easier.
Tip: Preserve examples of classes that custom code or other integrations depend on before running automated style cleanup.
Where: Designer > Pages panel
↳ Resources
Create reusable classes for frequently used styles such as spacing, alignment, typography, and layout. Follow the naming conventions established during design planning.
Where: Designer > Style panel
↳ Resources
Use combo classes to build variations of existing classes without duplicating complete style definitions.
Where: Designer > Style panel
↳ Resources
Create reusable text, background, border, and other color classes where appropriate. Connect these styles to your color variables to maintain consistency.
Where: Designer > Style panel
↳ Resources
Build reusable classes for common dimensions, padding, margins, and gaps. Connect values to variables where practical and avoid unnecessary spacer elements.
Where: Designer > Style panel
↳ Resources
Create classes for headings, paragraphs, labels, and other text patterns. Use consistent font, size, and spacing variables to simplify maintenance.
Where: Designer > Style panel
↳ Resources
Define default typography and other foundational styles for HTML elements. Use classes to override those defaults where needed.
Where: Designer > Style panel
↳ Resources
Create consistent classes for text links, link blocks, and buttons. Build variations using your design system's established patterns.
Where: Designer > Style panel
↳ Resources
Implement hover, focus, active, and other relevant states. Make keyboard focus indicators clearly visible and ensure state changes communicate meaning.
Where: Designer > Style panel
↳ Resources
Build reusable layout patterns using grid, flexbox, and other appropriate display settings. Define how these patterns respond at different breakpoints.
Where: Designer > Style panel
↳ Resources
Apply consistent styles to form inputs, labels, buttons, validation messages, and success and error states.
Where: Designer > Style panel
↳ Resources
Create consistent styles for rich text content, including headings, lists, links, and other nested elements. Use an appropriate class on the Rich text element when its styles need to differ from the site's global defaults.
Where: Designer > Style panel
↳ Resources
Use components for repeated patterns such as navigation bars, footers, and common content sections. Use component properties where individual instances need unique content, and avoid unnecessary complexity or excessive nesting.
Where: Designer > Components panel
↳ Resources
If your site requires additional global CSS, consolidate it in a maintainable location. Use a shared Embed component for appropriate Designer-previewable CSS or an externally hosted stylesheet for larger implementations.
Where: Designer; Site settings > Custom code
↳ Resources
Build your site's static and dynamic pages, connect the services your team needs, and implement accessibility, SEO, and AEO best practices throughout development.
Structure your static pages and URL paths, and set up the utility pages and locales your site needs.
Organize related static pages into folders to create logical URL paths and make your site easier to navigate and maintain.
Where: Designer > Pages panel
↳ Resources
Use available collaboration features, such as page branching and real-time collaboration, to coordinate work across designers, developers, and content teams.
Where: Designer
↳ Resources
Build the utility pages defined during design handoff, such as the 404 page, password page, and search results page.
Where: Designer > Pages panel
↳ Resources
If you're using Webflow Localize, configure your primary and secondary locales, their URL structures, and the options for navigating between languages or regions. Follow the Localize checklist for guidance on translating content, localizing assets and SEO settings, and managing publishing.
Where: Localize panel > Locales
↳ Resources
Plan your CMS schema, prepare content for import, and set up the pages and URLs that CMS content will live on.
Define your CMS Collections, fields, relationships, and content requirements before building or importing dynamic content. A well-planned schema makes it easier to scale and maintain your site.
Where: Designer > CMS Collections
↳ Resources
Organize content from external sources and map it to your CMS schema. Use CSV imports, APIs, or supported MCP workflows where appropriate.
Where: Designer > CMS Collections; external data source
↳ Resources
Review the publishing settings for CMS Collections and template pages. Prevent empty, internal, or otherwise unnecessary Collection pages from being publicly published.
Where: Designer > CMS template page settings
↳ Resources
Use supported folders and Collection URL settings to create logical paths for CMS content.
Where: Designer > Pages panel; CMS template page settings
↳ Resources
Set up where custom code is stored, tested, and hosted so it stays manageable and reliable in production.
Use a version-controlled repository for custom JavaScript, CSS, and other site-specific code. Establish clear ownership and review practices so your team can track and manage changes.
Where: GitHub or another source-control platform
↳ Resources
If your team uses externally hosted code during development, establish a suitable testing environment, such as GitHub Pages, that makes those files available to your Webflow staging site.
Where: External hosting service
↳ Resources
Prepare production hosting for external code files. Choose infrastructure that supports reliable delivery, versioning, caching, and your team's security requirements.
Where: CDN or external server
↳ Resources
Consider managing marketing, analytics, and other third-party tags through a tag management platform. This can centralize administration and provide more granular control over when and where scripts run.
Where: Tag management platform; Site settings > Custom code
↳ Resources
Connect analytics, forms, and other third-party services, and set up consent management.
Connect your site to Google Search Console using an appropriate verification method so your team can access search performance, indexing, and sitemap tools.
Where: Site settings > SEO; Google Search Console
↳ Resources
Set up Google Analytics using Webflow's integration or an approved tag management approach. Avoid installing duplicate tracking tags.
Where: Site settings > Apps & Integrations
↳ Resources
If you're using Webflow's Map element, configure a Google Maps API key and restrict it appropriately for your site's domains.
Where: Site settings > Apps & Integrations
↳ Resources
Configure Meta Pixel using your team's approved integration or tag management method. Coordinate with your consent setup and avoid duplicate pixel events.
Where: Site settings > Apps & Integrations; tag management platform
↳ Resources
Map Webflow form fields to your marketing platform using an appropriate native integration or App. Confirm data fields and submission destinations before testing.
Where: Designer > Form settings; Apps & Integrations
↳ Resources
Configure webhooks, custom actions, or Apps to send form submission data to other services. Review the data flow, security requirements, and any limitations of your chosen method.
Where: Designer > Form settings; Apps & Integrations
↳ Resources
Connect the additional services your site needs using Webflow Apps, approved custom code, or APIs. Document configuration details and dependencies so they can be reviewed during QA.
Where: Apps & Integrations; Site settings > Custom code
↳ Resources
If your site uses tracking technologies that require visitor consent, implement an appropriate consent management solution. Coordinate consent behavior with analytics, Webflow Analyze or Optimize, and third-party integrations. Confirm the configuration doesn't inadvertently prevent essential functionality, such as form submissions.
Where: Consent management platform; Site settings > Custom code
↳ Resources
Build in accessibility from the start so people of all abilities can navigate, understand, and use your site.
Choose appropriate HTML elements for headings, lists, tables, and landmarks. Maintain a logical heading hierarchy and reading order.
Where: Designer > Canvas; Element settings; Audit panel
↳ Resources
Check that text, icons, and essential interface elements have adequate contrast with their backgrounds, including when placed over images or video.
Where: Designer > Style panel
↳ Resources
Pair colors with labels, text, icons, or other indicators to communicate status, errors, and important information.
Where: Designer > Canvas; Style panel
↳ Resources
Write descriptive alternative text for informative images and mark decorative images appropriately. Avoid putting meaningful text into images unnecessarily.
Where: Designer > Assets panel; Image settings
↳ Resources
Ensure visitors can use navigation, links, buttons, menus, modals, and other interactive controls with a keyboard. Avoid keyboard traps and illogical focus order.
Where: Designer > Canvas; Element settings
↳ Resources
Provide visible focus indicators for links, buttons, form inputs, and other interactive elements.
Where: Designer > Style panel
↳ Resources
Provide a keyboard-accessible link that lets visitors bypass repeated navigation and reach the primary content directly.
Where: Designer > Canvas
↳ Resources
Write meaningful link and button labels, give icon-only controls accessible names, and use semantic elements or appropriate ARIA attributes.
Where: Designer > Canvas; Element settings
↳ Resources
Provide clear labels, instructions, required-field indicators, and error messages. Ensure forms can be used and submitted using a keyboard.
Where: Designer > Form settings
↳ Resources
Test text resizing, browser zoom, and responsive layouts. Ensure content remains usable without clipping, overlap, or unnecessary horizontal scrolling.
Where: Designer > Style panel; Breakpoints
↳ Resources
Provide appropriately sized click and touch targets and clear visual feedback for different interaction states.
Where: Designer > Style panel
↳ Resources
Add captions, transcripts, audio descriptions, or equivalent alternatives as appropriate. Give visitors control over media playback and avoid unexpected autoplay with sound.
Where: Designer; media player
↳ Resources
Avoid flashing content, unnecessary scrolljacking, and distracting motion. Respect reduced-motion preferences where appropriate.
Where: Designer > Interactions; Style panel
↳ Resources
Write understandable content using descriptive headings, concise sentences, and familiar language. Avoid instructions that depend only on appearance or position.
Where: Designer > Canvas
↳ Resources
Structure your content and metadata so search engines and AI answer engines can find and interpret it.
Group pages and CMS content by topic and user needs. Create descriptive URLs and logical hierarchies that are easy to navigate and maintain.
Where: Designer > Pages panel; CMS Collections
↳ Resources
Organize pages with clear primary headings, meaningful subheadings, and semantic content structures.
Where: Designer > Canvas
↳ Resources
Write accurate, relevant content that meets your audience's needs. Address important questions clearly and include enough context to support understanding.
Where: Designer > Canvas; CMS Collections
↳ Resources
Write unique page titles and meta descriptions. Use dynamic CMS fields where appropriate to manage metadata at scale.
Where: Designer > Page settings > SEO settings
↳ Resources
Implement suitable structured data for your page types. Ensure markup is accurate, relevant, and consistent with visible page content.
Where: Page settings > Custom code
↳ Resources
Connect related pages and content through relevant internal links with descriptive anchor text.
Where: Designer > Canvas; CMS Collections
↳ Resources
Review security, performance, and cleanup, then run QA across functionality, accessibility, SEO, and AEO.
Lock down security headers and add required site files before you publish.
Determine whether your site should be prevented from appearing inside iframes. Enable secure frame headers where appropriate to help protect against clickjacking.
Where: Site settings > Publishing > Advanced publishing options
↳ Resources
If your Enterprise site requires custom security headers, work with your security team to determine the appropriate directives. Test the configuration carefully to avoid breaking site functionality or required integrations.
Where: Site settings > Publishing > Custom Headers
↳ Resources
Add required .well-known files for supported verification, security, or deep-linking workflows. Confirm the file format and contents meet the requirements of the relevant service.
Where: Designer > Assets panel
↳ Resources
Optimize images, fonts, and scripts to keep load times fast and layouts stable.
Compress images and size them appropriately for their displayed dimensions. Use approximately 200 KB as a useful optimization target where practical, rather than a strict requirement for every image.
Where: Designer > Assets panel
Use modern image formats (e.g., WebP or AVIF) when they provide smaller files without unacceptable quality loss. This helps web pages load faster and saves website storage space.
Note: Check which browsers support WebP or support AVIF.
Where: Designer > Assets panel
↳ Resources
Review images that are immediately visible when a page loads, particularly important hero or navigation images. Avoid lazy loading images that are critical to initial rendering.
Where: Designer > Image settings
↳ Resources
Defer loading noncritical images until they're needed to reduce initial page weight and improve loading performance.
Where: Designer > Image settings
↳ Resources
Ensure images have appropriate dimensions or reserved layout space to reduce unexpected shifts as the page loads.
Where: Designer > Image settings; Style panel
↳ Resources
Remove unneeded font files and references to reduce asset downloads and CSS overhead. Check where a font is used before deleting it.
Where: Site settings > Fonts; Designer
↳ Resources
Review global and page-level custom code. Remove scripts, styles, and embeds that are no longer needed.
Where: Site settings > Custom code; Page settings
↳ Resources
Audit analytics, marketing, consent, chat, and other vendor scripts. Confirm each loads only where needed and follows the vendor's recommended configuration.
Where: Third-party platforms; Site settings > Custom code
Consider async or defer for eligible external scripts to reduce render-blocking behavior. Test each change because some scripts depend on execution order.
Where: Site settings > Custom code
↳ Resources
Enable the appropriate minification options to reduce published code size. Test the site after making changes.
Where: Site settings > Publishing > Advanced publishing options
↳ Resources
Consider Webflow's available optimization settings, including Per page CSS and asynchronous JavaScript where supported. Test custom code, shared Libraries, and interactions carefully before enabling them in production.
Where: Site settings > Publishing
↳ Resources
Remove unused styles, interactions, components, and assets, and keep unfinished pages unpublished.
Prevent internal, unfinished, or private pages from being published publicly when they aren't intended for visitors.
Where: Designer > Page settings
↳ Resources
Verify that team members can publish only the site changes or CMS content permitted by their roles.
Where: Designer; Workspace and Site settings
↳ Resources
Identify and remove unused classes to reduce unnecessary styles and keep your design system maintainable. Preserve classes required by custom code or other dependencies.
Where: Designer > Style selectors panel
↳ Resources
Remove obsolete interaction triggers and animations to reduce clutter and avoid unnecessary code.
Where: Designer > Interactions panel
↳ Resources
Delete components that are no longer part of the site, including unused framework or template components.
Where: Designer > Components panel
↳ Resources
Review the Assets panel and remove files that aren't required by the final site. Confirm an asset isn't referenced elsewhere before deleting it.
Where: Designer > Assets panel
↳ Resources
Create restore points so you can recover quickly if anything goes wrong at launch.
Create a clearly labeled backup restore point before launching. This provides a reference version that your team can return to if needed.
Tip: If significant changes are made after QA, consider creating another named backup before launch.
Where: Designer > Settings panel > Backups; Site settings > Backups
↳ Resources
If permitted by your plan and workflow, duplicate the site to create an additional independent copy. Remember that a duplicate does not preserve every aspect of the original site's history or configuration.
Where: Webflow Dashboard; Site settings
↳ Resources
Test layouts, forms, interactions, and integrations on staging to catch issues before visitors do.
Run PageSpeed Insights or Lighthouse against suitable staging URLs and record results for representative desktop and mobile pages. Compare performance again after launch.
Where: Published staging site; third-party tools
↳ Resources
Review pages across relevant screen sizes, including real mobile and desktop devices. Check for layout issues, overflow, missing content, and unexpected changes.
Where: Designer > Breakpoints; published staging site
Confirm that key pages and interactions work correctly across the browsers and operating systems your audience uses.
Where: Published staging site
If you're using Webflow Localize, test translations, navigation, links, forms, locale switching, localized SEO settings, URL routing, and locale publishing status.
Where: Published staging site; Localize panel
↳ Resources
Confirm forms have descriptive names and the correct submission destinations. Check notification recipients, field names, and connected services.
Where: Designer > Form settings; Site settings > Forms
↳ Resources
Complete realistic form submissions, including required-field validation, success and error states, and any downstream integrations. Remove test data when appropriate and permitted.
Where: Published staging site; Site settings > Forms
↳ Resources
Verify that tabs show the correct content, use the intended default active tab, and function properly across relevant devices.
Where: Designer; published staging site
Check that interactive elements open, close, and respond to user input as expected. Include keyboard and responsive behavior where relevant.
Where: Published staging site
Confirm interactions play correctly and don't prevent visitors from navigating or completing important actions. Test responsive and reduced-motion behavior where applicable.
Where: Designer > Interactions; published staging site
Test each critical integration from the triggering action through the receiving system. Validate expected data, error handling, and logging where available.
Where: Published staging site; connected third-party tools
↳ Resources
Verify that analytics tags and important conversion events fire as expected, subject to consent settings. Test form submissions, buttons, and other meaningful user actions.
Where: Published staging site; analytics platforms
↳ Resources
Audit and manually test with a keyboard and screen reader to confirm your site works for everyone.
Run automated audits and manual reviews to identify accessibility issues. Prioritize problems that prevent visitors from completing important tasks.
Where: Designer > Audit panel; third-party tools
↳ Resources
Navigate important pages and user journeys using only a keyboard. Check logical tab order, visible focus indicators, and keyboard-accessible controls.
Where: Published staging site
↳ Resources
Test critical pages and workflows with screen readers. Confirm content order, headings, links, landmarks, forms, and interactive controls are understandable.
Where: Published staging site; screen reader
↳ Resources
Verify metadata, structured data, indexing, and sitemaps so your site is ready to be found at launch.
Check that page titles and meta descriptions are accurate, descriptive, and appropriately unique. Review dynamic metadata on CMS pages.
Where: Designer > Page settings > SEO settings
↳ Resources
Verify the titles, descriptions, and images displayed when site URLs are shared. Confirm dynamic Open Graph fields resolve correctly on CMS pages.
Where: Designer > Page settings > Open Graph settings
↳ Resources
Check that schema types and properties match the visible content and meet relevant validation requirements.
Where: Page settings > Custom code; validation tools
↳ Resources
Check that canonical tags point to the intended URLs and that pages don't emit conflicting canonical tags. Pay special attention to domain migrations, localized content, and reverse proxy setups.
Where: Site settings > SEO; Page settings
↳ Resources
Ensure public pages can be discovered and internal or excluded content is handled appropriately. Check page indexing controls, robots.txt directives, and staging indexing.
Where: Site settings > SEO; Designer > Page settings
↳ Resources
Ensure the sitemap contains the intended public URLs. Use Webflow's auto-generated sitemap or a custom sitemap as required, and plan to submit it to search engines after launch. For localized sites, review hreflang support.
Where: Site settings > SEO > Sitemap
↳ Resources
Crawl your site to identify broken links, unexpected error responses, and outdated paths. Repair links and set up redirects for URLs that have permanently changed.
Where: Site settings > Publishing > 301 redirects; third-party crawler
↳ Resources
Confirm that important pages have useful content, clear headings, descriptive URLs, and relevant internal links. Check that key visitor questions are answered accurately and directly.
Where: Designer > Canvas; CMS Collections
↳ Resources
Establish a baseline for search visibility and determine how your team will monitor performance after launch. For AEO, consider tracking relevant AI citations, brand mentions, answer accuracy, and visibility trends using a consistent methodology.
Where: Google Search Console; Webflow Analyze or approved third-party tools
↳ Resources
Connect your domain, publish to production, and confirm everything works on the live site.
If you're serving your Webflow site through a reverse proxy, follow the specialized Reverse Proxy checklist before launch. Confirm the origin domain, DNS, SSL, canonical URLs, routing, query string forwarding, and caching configuration. Don't use a Webflow staging subdomain as your reverse proxy origin.
Where: Site settings > Publishing; reverse proxy or CDN configuration
↳ Resources
Connect the domains and subdomains your production site will use. Coordinate any special DNS or hosting requirements with your IT or infrastructure team.
Where: Site settings > Publishing > Production
↳ Resources
Complete the required domain ownership verification steps before publishing your site to its production domain.
Where: Site settings > Publishing; DNS provider
↳ Resources
Select the primary domain that visitors should use. Confirm that other connected domains redirect to the intended default domain.
Where: Site settings > Publishing > Production
↳ Resources
Update your domain's DNS records using the current values displayed in Webflow. Confirm that the domain is connected and SSL is active before publishing.
Tip: Follow the instructions shown in your Webflow Dashboard, especially if your site is part of a hosting or DNS migration.
Where: DNS provider; Site settings > Publishing
↳ Resources
After your domain configuration is ready and pre-launch checks are complete, publish your site to the appropriate production domain.
Where: Designer > Publish; Site settings > Publishing
↳ Resources
Visit your production URLs and verify that critical pages, navigation, forms, redirects, analytics, and integrations work correctly. Check for production-only issues that may not have appeared in staging, and confirm that your sitemap and indexing settings reflect the live domain.
Where: Published production site; third-party monitoring tools
↳ Resources