Feature request / platform limitation discovered after launch: suppress default base44.app domain and allow SEO overrides on custom domains

Hi Base44 team,

We’re very happy with the platform and are planning to launch multiple additional sites on Base44.

However, after launching our live site on a custom domain (https://ics-cleaning.com), we discovered a number of platform-level SEO limitations that were not clear to us before launch.

Once the custom domain went live, the original Base44 domain (https://ics-cleaning.base44.app) remained live and publicly crawlable, serving the same pages and routes as the custom domain.

For example, both of these remain accessible:

• https://ics-cleaning.com/...

• https://ics-cleaning.base44.app/...

This has created several post-launch issues for us:

1. Two public versions of the same site are live at the same time
   This creates duplicate-domain / duplicate-content concerns and makes it harder to consolidate authority around the custom domain.

2. The Base44 domain cannot currently be suppressed
   As confirmed, there is currently no platform-level option to:

   • redirect the Base44 domain to the custom domain

   • force cross-domain canonicals from the Base44 domain to the custom domain

   • apply a domain-wide noindex / X-Robots-Tag to the Base44 domain

3. Canonical behaviour does not solve the problem
   Because canonicals are self-referencing, pages viewed on the Base44 domain point back to the Base44 domain rather than to the custom domain.

4. We also ran into indexing and sitemap issues after launch
   The platform-managed /sitemap.xml on the custom domain included pages and routes we did not want treated as the primary SEO version, while the sitemap we actually wanted Google to use had to be created separately and submitted manually through Google Search Console.

5. robots.txt and /sitemap.xml could not be overridden in the way we expected
   We discovered that the live platform-managed robots.txt and default /sitemap.xml could not simply be replaced with our preferred versions. This created confusion during launch and made it harder to control which URLs and sitemap Google should prioritise.

6. This was unknown to us before launch
   Had this been clearer in advance, we would have planned the launch, indexing strategy, and domain setup differently.

7. We are planning more sites on Base44
   We expect to launch four more sites, so this is not just a one-off issue for us. It affects confidence in launching public-facing, SEO-driven sites on the platform.

For future launches, we would strongly value platform-level controls such as:

1. A setting to suppress the default *.base44.app domain once a custom domain is connected
   Options could include:

   • redirect Base44 domain to custom domain

   • cross-domain canonical to custom domain

   • domain-wide noindex / X-Robots-Tag for Base44 domain

2. A way to override or replace the default /sitemap.xml on a custom domain
   So the builder can choose the sitemap they want Google to use as the primary one.

3. A way to override or directly manage the live robots.txt on a custom domain
   So the builder can point search engines to the correct preferred sitemap and crawling rules.

4. More explicit page/domain-level indexing controls
   For example, clearer options around noindex, public/indexable status, or excluding certain live routes from platform-managed sitemap behaviour.

From our perspective, these would be extremely valuable improvements for any business or agency using Base44 for production websites.

Happy to provide real examples from the ICS Cleaning launch if helpful.

Thanks,
John