Allow disabling the default .base44.app subdomain when a custom domain is active

Title: Allow disabling the default .base44.app subdomain when a custom domain is active Category: Domain / Publishing

Request: When a custom domain is connected to a Base44 app, please provide an option to fully disable (or block public access to) the default .base44.app subdomain, while keeping the app live on the custom domain.

Justification: Currently, when a custom domain is configured, both URLs remain publicly accessible. This creates two problems: SEO — Duplicate Content: Search engines can index both URLs simultaneously, splitting ranking signals and potentially penalising the site for duplicate content. While canonical tags partially mitigate this, they rely on search engine compliance and are not a guaranteed fix. The only robust solution is to ensure the duplicate URL is not publicly accessible.

Brand & Professional Integrity: For professional services — particularly in health, legal, and therapeutic contexts — having a .base44.app URL discoverable alongside a professional custom domain undermines client confidence and brand credibility. Clients or legal parties who encounter the .base44.app URL may question the legitimacy or permanence of the service. Proposed Solution: A toggle in Dashboard → Domains labelled "Disable built-in domain when custom domain is active" — when enabled, requests to the .base44.app URL would return a redirect (301) to the custom domain, or a 404/403. This would be the gold-standard behaviour offered by platforms such as Webflow, Squarespace, and Framer.

Thanks

Adelaide Narrative