How Content Syncing Works Between Notion and a Super Website
Super treats your published Notion page as the single source of truth for your site's content. You edit in Notion, and the changes appear on your live site automatically — there is no separate upload, re-publish, or rebuild step inside Super. This suits anyone who wants to update a site frequently without touching a CMS or writing code.
The sync model in one sentence
Your Super site does not store a copy of your content that you then maintain. It renders the Notion page you connected, so whatever that page says is what your site shows.
That single design decision explains almost everything about how updates behave:
- One place to edit. Content lives in Notion; Super handles hosting, theming, and delivery.
- No manual re-upload. You never push content into Super after the initial setup.
- Edits propagate on their own. When you change the Notion page, the site reflects it without you rebuilding anything.
How to set up the connection
The setup is what creates the sync in the first place, so it is worth doing carefully.
- Choose or create a Notion page. Super works with any Notion page — an existing one, a new one, or a template.
- Publish the page via Notion's Share menu. The page must be shared publicly for Super to read it.
- Paste the Notion page's web link into Super when creating the site.
- Share your site. Your content is now live on a site you control.
From this point on, the link between the Notion page and the Super site is what keeps them in sync.
What happens when you edit in Notion
Once the site is live, editing follows a simple loop:
| You do this in Notion | What happens on your Super site |
|---|---|
| Change text, add blocks, reorder sections | The site reflects the updated page |
| Add or remove content | The site shows the current version of the page |
| Keep editing over time | No re-upload or rebuild needed in Super |
Super's own description puts it plainly: edits in Notion are automatically synced. One customer quoted on the site, James, describes making changes in seconds that go live "without me having to touch a thing." Another, Matt, frames it as updating your Notion doc and watching changes appear on the site.
Why this matters for frequently updated sites
If your content changes often — pricing notes, announcements, a changelog, a resource list — the sync model removes the usual friction. You are not logging into a separate dashboard, formatting content twice, or waiting on a deploy. You edit the document you already work in.
This is the main reason people choose Super over a conventional site builder: the update path is short. The trade-off is that your site's content is only as current as the Notion page it points to, so the page you connected needs to be the one you actually maintain.
Common points to watch
- The connected page is the one that syncs. If you edit a different Notion page than the one you linked, the site will not change.
- Publishing is a prerequisite. The page has to be shared from Notion before Super can use it.
- You are not rebuilding anything. There is no "sync now" button to press in the workflow described — the connection does the work.
If your goal is a site you can update by editing a document, this is exactly the behavior you want. If you need content that lives outside Notion, that content is not part of this sync path.