Changes not appearing on the live site

Before anything else — check which site you're on!

Make sure you're logged into the live site's Umbraco, not the development (dev) site. Changes made on the dev site will never appear on the live site. The URL in your browser should match your actual website address, not a dev or staging URL.


Did you publish the page?

Saving a page in Umbraco does not make it go live, you need to click the green Save and publish button. If you only clicked Save, the changes are sitting in draft and no one can see them yet.


Hard refresh your browser

Your browser often shows a saved (cached) version of the page rather than the latest one. Try a hard refresh to force it to load fresh content. Go to your browser history > clear cache.


Check the page isn't hidden or unpublished

In the Umbraco content tree (the list of pages on the left), look at the icon next to your page. A grey or faded icon means the page is unpublished and hidden from visitors. Right-click the page and choose Publish to make it visible.


Check if the page is scheduled

Umbraco lets you schedule pages to publish at a future date and time. If someone set a schedule on this page, it won't appear until that time. In the editor, look for a Schedule section to see if a future publish date has been set.


Are you editing the right page?

It's easy to accidentally edit a different page than the one you're looking at on the live site. Double-check the page name and URL in Umbraco matches the page you want to update.


Check a parent page isn't unpublished

Pages in Umbraco sit in a tree, like folders inside folders. If a parent page (one above yours in the tree) is unpublished, all of its child pages will be hidden too, even if those child pages themselves are published.


Still not showing? Contact us!




Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article