"There is no justification for hiding the subdomain from the url."
I'm just curious how developers are so blind to the issues of showing a subdomain that they assert that there is NO justification?
Can we perhaps assume a bit more good faith, or just consider that perhaps google has SOME (maybe bad) justification for this change?
I can easily think of MANY reasons to hide the subdomain, starting with the classic secure.bank.chase.com-url.io type phishing sites.
And this is actually illustrated here, if you don't have control over root domain, should google be able to trust your subdomains?
I would suggest that in 2021, if you can't get content to your root domain (or a redirect), you should update how you approach your hosting. I've been able to get content on a root domain for over 15 years.
I'm just curious how developers are so blind to the issues of showing a subdomain that they assert that there is NO justification?
Can we perhaps assume a bit more good faith, or just consider that perhaps google has SOME (maybe bad) justification for this change?
I can easily think of MANY reasons to hide the subdomain, starting with the classic secure.bank.chase.com-url.io type phishing sites.
And this is actually illustrated here, if you don't have control over root domain, should google be able to trust your subdomains?
I would suggest that in 2021, if you can't get content to your root domain (or a redirect), you should update how you approach your hosting. I've been able to get content on a root domain for over 15 years.
Ie, look to yourself before ranting at google.