🔍 What Is Happening?
When you ask the AI assistant in Website Studio to make a visual change — such as removing a duplicate hero image, adjusting a layout, or modifying a section — the platform may trigger a container rebuild. During this process, dynamically generated routes, including published blog articles, can be stripped from your live site. Your content is not permanently deleted, but the routes that make those pages publicly accessible are removed until they are republished.
⚠️ Why Does This Happen?
Website Studio serves blog articles through dynamic routes that are registered at publish time. A container rebuild essentially resets the site's routing layer to match the current saved state of your pages. If the rebuild does not re-register your blog routes automatically, those articles will disappear from the live site even though the underlying content still exists inside the platform. This is a known behaviour that our engineering team has addressed in recent releases, but certain edge-case edits may still trigger it.
✅ How to Check Whether Your Posts Still Exist
- Open Website Studio from the left navigation menu.
- Click Blog or navigate to your blog management section.
- Review the list of articles. Posts that were previously published will still appear here with a Published status even if they are no longer live on the site.
- If you can see the articles in this list, your content is intact and can be restored quickly.
🔄 How to Restore Disappeared Blog Posts
- Inside Website Studio, go to your Blog section and locate the affected articles.
- Open each affected article individually.
- Click Unpublish (if the option is available) and then click Publish again. This re-registers the route on your live site.
- If the Unpublish option is not shown, click Publish directly to force the route to be re-created.
- Wait up to 5 minutes for the changes to propagate and then visit the live URL of each article to confirm it is accessible.
- Repeat this process for every article that disappeared.
🛡️ How to Prevent This in the Future
- Note your published articles before requesting AI edits. Keep a quick record of your live blog URLs so you can immediately identify if any go missing after a change.
- Request one small change at a time. Larger or more complex AI instructions are more likely to trigger a full container rebuild. Breaking requests into smaller steps reduces the risk.
- Avoid structural edits while actively publishing content. If you are in the middle of a content publishing session, complete and confirm all posts are live before asking the AI to make layout or design changes.
- Verify your live site after every AI-assisted edit. After any change is applied, do a quick check of your blog index page to confirm all published articles are still visible.
- Use the Blog section in Website Studio as your source of truth. The publish status shown inside the platform reflects whether your content exists, not necessarily whether the live route is active. A re-publish step is always safe to perform.
📋 What to Tell Support If Posts Cannot Be Restored
If republishing does not restore your articles, or if the articles no longer appear in your Blog section inside Website Studio, gather the following information before contacting support:
- The titles or URLs of the missing blog articles.
- The date and approximate time the content disappeared.
- A description of the AI edit you requested immediately before the content disappeared.
- Any error messages you saw on the live URL (for example, a raw XML message or a 404 page).
If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.