Should new.nodejs.org be showing up in Google SEO results?

[danjenkins]

I searched for node.js on google and got given back some results. It seems wrong that new.nodejs.org is showing up. It does redirect to nodejs.org when visited which to me confirms that google shouldn't be indexing new.nodejs.org

Do we have Google Webmaster tools setup etc? If so we can remove the url/ask google to change how ti indexes etc.

Should we also add to robots.txt to stop this happening on other subdomains I know are being played around with?

Sorry, written in a bit of a rush but wanted to do it before I forgot about it.

[Fishrock123]

It probably shouldn't show up, but it also just redirects to the main site, so it's not a huge problem.

doesn't show up for me:

weird.

[danjenkins]

@hg how very odd!

[stevemao]

Tried both nodejs and node.js, it doesn't show up for me. But the result is different than @hg's. since I live in Australia, I see nodejs.org.au before nodejs.org. @danjenkins try a different country? I believe the cached server in your area is outdated.

[danjenkins]

Yeah I'm currently in the bahamas (google.bs) and it's outdated - google.co.uk is fine

Seems like we shouldn't just ignore this though

[fhemberger]

I created a PR on the @nodejs/build repo.

[UroosaSehar]

It's working fine with me!

[fhemberger]

@danjenkins We have a canonical meta tag on each page referencing nodejs.org, so this shouldn't happen. I also tried to reproduce this in an incognito session, but everything works fine for me:
https://www.google.de/search?as_sitesearch=new.nodejs.org

Does this issue still occur for you?

[jbergstroem]

I can't really reproduce this either but catered for it in my updated commit.

[danjenkins]

I couldn't reproduce except when I was in the bahamas - using google.bs it seems like it doesn't happen anymore so can close this issue

[jbergstroem]

So, should we take it into consideration or not?

[fhemberger]

PR is already there, 'new.nodejs.org' is not used …