Can I test the changes before they are visible to everyone?

Why test before publishing?

Key points • Check your changes without impacting the live site • Ensure an optimal user experience • Detect errors before publishing • Work confidently without fear of breaking a page

Testing changes is essential to avoid publishing errors that are visible to your visitors. Fortunately, the editor allows you to preview your modifications without making them public. This is perfect for checking a layout, testing an animation, adjusting text, or validating a new form before publishing.

Use the internal preview

In the editor, all your changes remain invisible until you publish the site. Therefore, you can: • freely edit your text, images, and buttons • adjust the layout • test an interaction • check a form

The preview shows you exactly what your visitors will see, but only for you.

💡 Tip: Use the adapted views (desktop, tablet, mobile) to test your design on multiple resolutions.

Check the changes with the restricted public preview

In some cases, you can also share a preview link with a collaborator, which is useful for validating text or layout before publication. This link does not affect the online version: only the person with the URL can see the temporary state of the site.

This allows for: • internal review • visual testing • team validation before publication

💡 Tip: This link expires or can be deactivated, ensuring the confidentiality of changes.

Testing dynamic content

For pages using Collection Items (rooms, offers, restaurants, etc.), you can check: • modified fields • new images • display conditions • linked elements

Until you publish, your edits to this content remain invisible to the public.

💡 Tip: If a Collection item is in draft, it will never be publicly visible, even after publication.

Test the forms before putting them online

Before publishing, you can: • check the form structure • test the confirmation message • check the mobile appearance • add or modify custom fields

However, to test the actual submission of a form, you will need to publish the change. 👉 Solution: publish to a test domain or use a temporarily duplicated page.

💡 Tip: Remember to delete the test page after validation.

Use a staging domain (if available)

If your site has a staging domain, you can publish your changes only to that pre-production environment. The public will continue to see the old version while you test the new one.

This is ideal when: • you are redesigning an entire section • you are testing a new menu • you are preparing a seasonal campaign

💡 Tip: once validated, simply publish on the main domain.

Conclusion

Yes, you can test your changes without them being visible to your visitors. Between internal previews, preview links, the Collections draft, and the potential staging area, you have reliable solutions for validating each update before publishing.