The free subdomain is the most expensive thing on your site
It is free in the sense that you do not pay money for it. You pay in credibility with every visitor who looks at the address bar, and in standing with search engines, and again later when you finally move.
Run the free checkA generated platform subdomain undermines you in three ways: visitors read it as an unfinished experiment, any reputation the address earns belongs to the platform's domain rather than to you, and moving later means redirecting every URL and waiting for search engines to transfer what little standing you had. Base44's documentation states plainly that its SEO setup is designed and supported for apps published on a custom domain.
What the address bar says about you
Somebody has just decided your product looks interesting enough to try. They are about to type an email address, or upload a photo, or connect an account. In that moment they glance at the address bar.
An address like my-project-a7f3.lovable.app says this is a weekend experiment by somebody who has not committed to it. That is often unfair, and it is what the address communicates.
A real domain says somebody stood behind this enough to buy a name for it. The cost of that signal is roughly two coffees per year, which makes it the best value purchase available to a new product.
What the platforms themselves say
This is not our opinion imposed on the platforms. Several of them state it directly.
Base44's documentation says its SEO setup is designed and supported for apps published on a custom domain, and describes the free generated URLs as not intended for long-term production SEO. The generated address can still be crawled, but the platform is telling you plainly which arrangement it supports.
The reasoning is straightforward once stated. On a shared platform domain, thousands of apps sit under one name, most of them abandoned experiments. Whatever a search engine learns about that domain is learned from all of them together, and your good app is averaged in with a great deal of noise.
The compounding cost of waiting
This is the argument that matters most and it is the one people find least intuitive.
Every week you spend on the free subdomain, you are accumulating whatever small standing your work earns onto an address you do not own and will eventually abandon. The pages that get indexed are indexed at that address. Any link anybody makes points at that address.
When you finally move, you have to redirect every URL, wait for search engines to process the change, and accept that some of what you built does not transfer cleanly. The move is not free and it gets more expensive the longer you leave it.
So the honest framing is that buying the domain later costs strictly more than buying it now, and the difference grows every week. There is no version of this where waiting is the cheaper option.
Choosing a name without overthinking it
Builders lose weeks here. A few rules that resolve most of the deliberation.
- Short enough to say out loud without spelling it. If you have to spell it, it is wrong.
- A common extension where you can get one. Unusual extensions are fine and are slightly harder for people to remember and retype.
- Avoid hyphens and numbers, both of which cause trouble every time somebody says the address aloud.
- Do not wait for the perfect name. A good name you own today beats a perfect name you are still deliberating about in a month, and the product matters more than the name.
- Check that the name is not already a company in your category, since competing for your own name against an established business is a fight you do not need.
Connecting it without breaking anything
The mechanics vary by platform and the shape is consistent. Buy the domain at a registrar, add the DNS records the platform tells you to add, then confirm in the platform's dashboard. It usually takes minutes of work and up to a day for the change to propagate everywhere.
Two things to get right at this stage, because they are easy now and annoying later.
Decide whether your canonical address includes www and stick to it, redirecting the other version to the one you chose. Serving both without redirecting means every page effectively exists at two addresses.
Make sure the old generated URL redirects to the new one rather than continuing to serve the same content, so anything already indexed transfers rather than competing with you.
What to do immediately afterwards
The domain change resets several things that were tied to the old address, and forgetting these is the usual reason a move produces a dip that lasts longer than it should.
- Verify the new domain in Google Search Console as a fresh property. The old one does not carry over.
- Regenerate and resubmit your sitemap with the new addresses.
- Update any structured data that names a URL, since a schema block pointing at the old address is now wrong.
- Update every directory listing, repository description and profile link that points at the old address.
- Check your social preview image still resolves, since a relative path may now point somewhere that does not exist.
Part of a larger guide
This page is one part of The fixes. The other parts:
Questions people ask
- Do I really need a custom domain for my app?
- Yes, and the platforms say so themselves. Base44's documentation states its SEO setup is designed and supported for apps published on a custom domain and describes the free generated URLs as not intended for long-term production SEO. The cost is roughly two coffees a year.
- Why is a free subdomain bad for search?
- Thousands of apps sit under one shared platform domain, most of them abandoned experiments, and what a search engine learns about that domain is learned from all of them together. Your good app gets averaged in with a great deal of noise, and none of the standing it earns belongs to you.
- Can I just move to a custom domain later?
- You can, and it costs strictly more than moving now, with the gap growing every week. Everything indexed is indexed at the old address, every link points there, and moving means redirecting every URL and accepting that some of what you built will not transfer cleanly.
- How do I choose a domain name?
- Short enough to say out loud without spelling it, on a common extension if you can get one, no hyphens or numbers, and not already a company in your category. Most importantly, do not wait for a perfect name, because a good name you own today beats a perfect one you are still deliberating over.
- Should my site use www or not?
- Either is fine, and what matters is choosing one and redirecting the other to it. Serving both without a redirect means every page effectively exists at two addresses, which splits whatever standing each one earns.
- What do I need to update after connecting a domain?
- Verify the new domain in Search Console as a fresh property since the old one does not carry over, regenerate and resubmit the sitemap, update any structured data naming a URL, update every directory listing and profile link, and confirm your social preview image still resolves.
Keep reading
Check the domain you are on now
The free Get Found Check tells you what your current address is doing for you and what is still open once the domain is connected.
Run the free check Have Licheo do it for you