Super is built on top of Notion, meaning your website content is powered directly by your Notion pages. However, since Notion does not send real-time update notifications, Super uses a smart sync and caching system to keep your site fast and up to date.
How Page Sync Works
Notion does not notify Super when content is updated. Because of this, Super checks for updates when a page is accessed or manually triggered.
A sync is triggered in the following ways:
When a visitor loads a page on your live site
When you open a page from the Pages section in the Super dashboard
When either of these happens, Super checks the connected Notion page, compares it with the cached version, and rebuilds it if changes are detected.
For sites with regular traffic, this process happens naturally in the background.
Using the Pages Section to Force Sync
The most reliable way to manually trigger a sync during development or troubleshooting is to open the page from the Pages section in the Super dashboard.
This action forces Super to:
Re-check the latest content from Notion
Rebuild the page if changes are detected
Prepare the updated version for delivery via the CDN
This is especially useful when:
You are actively editing and testing changes
Content is not appearing as expected
You want to confirm whether sync is working correctly
How Caching Improves Performance
To ensure fast loading times, Super uses a Content Delivery Network (CDN).
A CDN stores cached versions of your pages so visitors can load content quickly from a nearby server location.
Here’s what happens behind the scenes:
Visitors receive a cached version of your page from the CDN
When Super detects a change in Notion, it rebuilds the page in the background
The updated version is then stored in the CDN
The next visitor will receive the updated content
This ensures your site remains both fast and up to date.
Understanding Update Delays
Because updates pass through multiple systems (Notion → Super → CDN), changes may not appear instantly.
Typical factors that affect visibility:
Short delay between Notion and Super syncing
CDN cache duration before updating globally
Background rebuild time after a page visit
As a result, newly updated content may take a short time to appear across all visitors.
Manual Publishing (Optional Control)
If you prefer more control over when updates go live, you can use Super’s Manual Publishing feature.
This allows you to:
Decide exactly when changes are published
Prevent automatic updates from appearing immediately
Batch multiple changes before going live
This is especially useful for production sites or team workflows.