Every Super site has a free default domain, [name].super.site, where [name] is the Default Domain set on your site's Domains page. When you connect a custom domain, for example example.com, the default domain does not switch off by itself: the same site is then live on two addresses.
This is not caused by Notion or by any setting in Notion. It is the Super default domain and your custom domain serving the same pages.
Why it matters
- Search engines see every page twice, once on
[name].super.siteand once on your custom domain, and treat it as duplicate content. - Google may pick the
[name].super.siteaddress for search results instead of your custom domain, or split ranking between the two. - Visitors and links can keep using the old
super.siteaddress.
That is why Site health shows the SEO warning Your site is also live on [name].super.site for sites with a connected custom domain.
How to fix it: redirect the default domain
- Open your site in the Super dashboard and go to Domains.
- Turn on Redirect Default Domain (or click Turn on redirect in the notice at the top of the page).
- Save your changes.
From then on, every page on [name].super.site permanently redirects to the same page on your custom domain, for example [name].super.site/blog to example.com/blog. The sitemap and robots.txt of the default domain redirect too, so search engines move to your custom domain.
The warning in Site health goes away once the redirect is on.
After you turn it on
- Google drops the
super.siteresults gradually as it recrawls your pages. This can take from a few days to a few weeks. - Your custom domain must be connected and working. Redirect Default Domain is shown only when it is.
- If you remove the custom domain later, turn the redirect off so that
[name].super.siteserves the site again.
Redirect or Default Domain Indexing?
The SEO section has a separate setting, Default Domain Indexing. Disabling it only asks search engines not to index [name].super.site: the site is still reachable there and visitors are not sent to your custom domain. The redirect solves both, so it is the recommended fix.