When a custom domain is connected to a Framer site, the default URL remains publicly accessible with a 200 response and cannot currently be disabled or redirected to the custom domain.

This can create an SEO/canonicalization problem. In my case, both the custom domain and the URL correctly declared my custom domain as canonical, but Google still selected the URL as the Google-selected canonical. As a result, my custom domain was excluded from Google's index as a duplicate.

I was able to resolve the issue by adding custom JavaScript that detects the hostname and dynamically applies:

Google Search Console confirmed that Googlebot detected the directive. After Google recrawled both URLs, the URL was excluded by , my custom domain became Google's selected canonical, and the custom domain was successfully indexed and began appearing in Google Search.

It would be very helpful if Framer provided a native option when connecting a custom domain to either:

* Automatically apply to the default URL, or

* Redirect the URL to the configured custom domain.

Ideally, the redirect would be the preferred solution, with available as an alternative.

This would prevent the Framer staging/default domain from competing with customers' production custom domains in search results and eliminate the need for a JavaScript workaround.