We understand how frustrating it can be when your live site doesn’t reflect what you see in Notion. While our support team is always here to help, many common syncing issues can be resolved on your own by following the steps below.
This guide is designed to help you quickly identify and fix content-related sync issues before reaching out to support.
When should I use this guide?
Use this checklist if you notice any of the following:
A table, block, or section still appears on the live site even though it was removed in Notion
Gallery card properties are missing or not updating
Images, embeds, or text blocks behave unexpectedly after a sync
Self-service checklist for common syncing issues
1. If a block (like a table, embed, or section) still appears on the live site:
Temporarily remove the surrounding section in Notion by selecting all blocks above and below the area where the corrupted image or block appears, then delete those blocks from the page.
Run a manual sync in the Super by clicking the refresh button in the dashboard preview.
Once confirmed fixed, re-add the content manually and refresh again with dashboard preview.
This helps clear out any corrupted or cached block data.
2. Missing Properties for gallery or database issues
If gallery card properties aren’t showing or updating correctly:
Hide any properties in Notion
Run a sync in Super
Re-enable the property and sync again in Super Dashboard preview.
This forces the property to re-register and often resolves display issues.
3. Re-add instead of editing in place
For images, text blocks, or embeds that behave unexpectedly, deleting, refresh Super dashboard preview and re-adding them in Notion works more reliably than editing existing blocks.
4. Always run a manual sync after changes
After making adjustments in Notion, trigger a refresh button in the Super dashboard preview and wait for it to fully complete before checking the live site.
5. Confirm whether the issue is page-specific
If it only happens on one page, it’s usually related to that page’s structure rather than a site-wide problem.
When should I contact support?
If the issue persists after following all steps above, or if you’re unsure which content is causing the problem, please reach out to support. We’ll be happy to investigate further.