Is there a way to prevent the on-premise version from being index on Google by using a robots.txt or setting the noindex with the meta tag?
We have a feature request for this on Cloud! If you deploy your self-hosted Retool instance within your virtual private cloud (VPC) or behind your virtual private network (VPN) to restrict access exclusively to users inside the network, the browser would show a 404 error when someone outside the network tries to access it.
2 Likes
HI @Tess - any update on how we can achieve this? Thanks!
+1 on the demand, having this feature would be a nice QOL update
Hi folks,
Thanks for checking in! This feature request is still in our backlog 
We are still tracking interest for this feature, but I don't have an eta yet
In the meantime, have you tried removing the URL from your Google Search Console account (with any of the steps outlined here here)?
Specifically for self-hosted Retool orgs, most customers who self-host put their instance behind an internal VPN which won’t allow crawling.
1 Like
Commenting here to express our interest in the feature as well!
2 Likes