Every tool that builds websites on top of Notion, Notion's own Sites included, puts the IDs of your Notion pages and blocks into the public code of your site by default. At the time of writing, Super is the only one we know of that lets you hide them. Every newly created Super site has this protection turned on automatically.
Every Notion page and block has a unique ID. When Super turns your Notion page into a website, those IDs end up in the site's code: in element IDs like #block-…, in links, and in the data the page loads. Anyone who opens the page source can copy them.
On their own, these IDs look harmless. But they point straight back to the Notion page your site is built from, and from there to the workspace it lives in. The advanced protection layer closes that gap.
Why Notion IDs in your site's code matter
Your Super site has to be built from a Notion page that is shared to the web. Its address is long and hard to guess, so in practice nobody finds it unless they know the ID. The published site is where they could learn it: with a Notion ID from the page source, a visitor can find the original Notion page and see what you may not want public, such as pages you never added to your site, draft content, or the name of your workspace.
For most sites this is not a problem. For a company handbook, a client portal or a site with password-protected pages, it can be.
What the advanced protection layer does
When it is on, Super replaces every Notion ID in your published site with a different code that only your site can translate back. The codes look like this:
block-3f9c1a7e5b2d4c8e9a0f6b1d2c3e4f5a-superThe -super ending tells you the protection is on. Each site has its own key, so the same Notion block gets a different code on two different sites.
Everything keeps working as before:
- Links, anchors and the table of contents use the new codes. Old links that still contain a Notion ID are redirected to the right page and section.
- Forms, search, RSS feeds, file downloads and the sitemap are translated the same way.
- Custom code in your site's Code settings is translated too. If your CSS targets
#block-<notion id>, Super rewrites it to the new code when the page is rendered, so you don't need to change anything.
What it can affect
The protection only changes the IDs in your site's code, never your Notion content. Most custom code is not affected, but a few setups need attention:
- CSS and scripts in files you upload or host elsewhere are not rewritten. Super only translates code stored in your site's Code settings, so a Notion block ID inside a linked file stops matching after you enable the protection, and anyone who opens the file can still read it. Replace those IDs with the new codes, or move the rules into your site's Code settings.
- Scripts that read Notion IDs from the page, for example to build a link back to Notion or to send a block ID to another service, will now receive the new codes instead.
- External tools that saved a Notion ID from your site (analytics filters, bookmarks to a page by its ID) keep working through the redirect, but will show the new address from now on.
- Links to Notion that you added yourself (
notion.site,embed.notion.co) stay as they are. If you link to Notion directly, that link still points to Notion.
How we tested it
Before releasing the option, we ran it against a copy of live data from hundreds of published Super sites whose custom code targets Notion blocks. Together they get about 94% of the traffic of all sites that use this kind of custom code. We checked 1,000+ pages, including the subpages that hold the blocks the custom code points at, and compared each one with the live site: every Notion ID was replaced, and the custom code still matched its blocks.
How other Notion website tools compare
On 20 October 2026 we ran the same check on a live site built with each of the best-known Notion website tools. We loaded the home page and a subpage in a browser, collected everything the browser received, and asked Notion's public API whether the IDs found there belong to real Notion pages and blocks. An ID counts only if Notion itself, without logging in, returns the page or block behind it.
Tool | Notion IDs a visitor can see | Confirmed by Notion | Workspace ID revealed |
Super, advanced protection layer on | None | 0 of 60 checked | No |
Super, protection off | Yes | 59 of 60 checked | Yes |
Potion | Yes | 57 of 60 checked | Yes |
Notaku | Yes | 59 of 60 checked | Yes |
HelpKit | Yes | 42 of 60 checked | Yes |
Yes, also in page addresses | 48 of 60 checked | Yes | |
Matrizen | Yes | 14 of 19 checked | Yes |
Feather | Yes | 59 of 60 checked | Yes |
We checked the 60 most frequent ID-shaped values on each site (the Matrizen site had only 19). Popsy is no longer online, so it is not in the table.
How to turn it on
New sites have the protection on from the start. For an existing site:
- Open your site in the Super dashboard and go to Settings.
- Under Security, find Advanced protection layer and click Enable, then confirm.
- Your pages switch over automatically within a few hours as they are rebuilt. With manual publishing on, they switch over when you next publish the site.
The protection can't be turned off once it's enabled. Custom code you write after enabling it may use the new codes, and those would stop matching if the protection were removed.
FAQs
Does this make my Notion page private?
No. Your Notion page stays shared to the web, because Super needs that to build your site. The protection removes the easiest way to find it: the IDs in your site's code.
Do I need to change my custom code?
Usually not. Custom code that targets #block-<notion id> keeps working, because Super rewrites the ID when the page is rendered. Two things need an update: CSS and scripts in files you upload or host elsewhere that contain Notion block IDs, and scripts that read Notion IDs from the page and use them outside it.
Can I write new custom code with the new codes?
Yes. Open your published site, inspect the element and copy its #block-…-super ID. Writing the original Notion ID works too.
Which plans include it?
All plans. New sites have it on automatically; existing sites can enable it in Settings.
What if something looks broken after enabling it?
Pages can take a few hours to switch over, and with manual publishing on they switch when you publish, so make sure the page has been rebuilt first. Then check any uploaded or externally hosted CSS and scripts for Notion block IDs. If something is still wrong, contact our support with the page address and the custom code involved.
