: Free subdomain not indexed I currently use a free subdomain, https://vandenberg.us.to, but I'm having trouble getting it indexed by Google. From what I understand, Google should treat subdomains
I currently use a free subdomain, vandenberg.us.to, but I'm having trouble getting it indexed by Google. From what I understand, Google should treat subdomains as completely different websites from the root domain, but when I use "fetch as Google" in the webmaster console it fetches us.to.
Is this anything that's within my control? Could I solve this by using a different robots.txt or by uploading a sitemap? Or does us.to just not allow their subdomains to get indexed?
As per request of Goyllo, here's the response details. Unfortunately it's not possible to copy the text easily, so a screenshot is all I can give. (Click to make it readable.)
Other information I just realized might be important is that I registered this domain through FreeDNS. Therefore it should only be a DNS record, and the site us.to should not even be touched, as it's on a different IP.
More posts by @Courtney195
1 Comments
Sorted by latest first Latest Oldest Best
Your domain hasn't been published to Google
FreeDNS seems to treat Google differently. From that FAQ post:
No subdomains created via the shared domain system are visible to Google. You must own the domain itself that you are creating a subdomain off of to have it visible to Google by default.
That includes yours. It appears that in order to make your site visible to Google, you'd have to contact them first. It's an unusual policy as it seems to make those subdomains rather useless (and I'd be interested in finding out why they do this at all! I would hazard a guess that it's cookie-hijacking related, but blocking Google by default doesn't exactly solve that)
If you just want a free domain which works properly with Google on FreeDNS or some other free DNS provider, check out freenom. A quick search on there provided 3 results which are actually shorter than your shared domain anyway.
Aside in response to comments above: As you're only using DNS services from them, i.e. your server isn't under their control, it's essentially not possible for your HTTPS only problem to be the cause.
Terms of Use Create Support ticket Your support tickets Stock Market News! © vmapp.org2024 All Rights reserved.