Any Way to Hide onrender.com when custom domain is Linked

Can we hide project.onrender.com as I want the deployed app to be only accessible through my custom domain if cant remove onrender can we just make it password protected or something like a static page that says this service is archived and can be accessed using custom domain only

Hi @Mitesh_Metha ,

Can you help me understand why you’d want to not have the project.onrender.com domain available? If you are using custom domains and not sharing your project.onrender.com domain, it shouldn’t be visible to your users.

Not a specific reason but I would like the Nodeapp restapi should be access using api.domain.com rather than app.onrender.com

Althought I would be using api.domain.com everywhere but Just didnt want user to know theres another way to reach service via onrender.com

Thanks for the clarification—that makes sense. As long as you only share the custom domain (Custom Domains | Render · Cloud Hosting for Developers) and don’t share your onrender.com, you should be good. If you run into any issues with that, just let us know and I’ll be happy to help.

It would be nice if the project.onrender.com domain automatically redirected to the custom domain. For example, this is something that GitHub Pages does (username.github.io => custom domain if set up).

1 Like

That’s a great idea :slight_smile: I’ve added that as a comment to a general domain redirect feature request we’re tracking at Domain level redirects | Feature Requests | Render

1 Like

Does Render prevent indexing of projectname.onrender.com sites by search engines? I tried to retrieve a domain-level robots.txt from onrender.com but it redirected me to render.com.

I’d imagine that would be really important. (A project obviously can’t serve its own robots.txt disallowing everything, it would show up on the custom domain.)

Re the projectname.onrender.com when you already have a custom domain, I’d like three options:

  1. Disable it completely <== This is what I’d use
  2. Redirect to the custom domain with a 301 (moved permanently)
  3. Serve the site (what it does currently)

(Or you could also offer a 302 option.)

TIA,

– T.J.