When Super syncs your Notion workspace, it has to decide where each page belongs on your website.
The way Super does this is simple: it places a page where it first discovers it during the sync process.
For example:
- If Super first finds a page inside another page, it will add it as a child of that page.
- If Super first finds the same page through your main database, it may place it at the top level instead.
This is why pages in the same Notion database don't always appear under the same folder in Super. It depends on where Super encounters the page first while building your site.
Example
Imagine you have this structure in Notion:
- Projects
- Project A
- Project B
If Super first discovers Project A while scanning the Projects page, it may place it under:
/projects/project-a
However, if Project B is first discovered directly from your published database before Super reaches the Projects page, it may instead be added as its own top-level page.
Both pages still come from the same Notion database, the difference is simply the location where Super first found them during the sync.
Does this affect the page itself?
No. The page content, properties, and publishing status remain the same. This only affects how Super organizes the page within your site's page structure.
Can I control where pages are added?
The best way to keep your site structure consistent is to maintain a clear page hierarchy in Notion and avoid having the same page discoverable from multiple published locations. This helps Super identify the intended location for each page during syncing.