Skip to content

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

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
danjenkins opened this issue Mar 10, 2016 · 14 comments
Closed

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

danjenkins opened this issue Mar 10, 2016 · 14 comments

Comments

@danjenkins
Copy link

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?

screen shot 2

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

@Fishrock123
Copy link
Contributor

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

@ghost
Copy link

ghost commented Mar 10, 2016

doesn't show up for me:
screen shot 2016-03-10 at 16 24 44

weird.

@danjenkins
Copy link
Author

@hg how very odd!

@stevemao
Copy link
Contributor

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
Copy link
Author

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
Copy link
Contributor

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

@UroosaSehar
Copy link

It's working fine with me!

@fhemberger
Copy link
Contributor

@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
Copy link
Member

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

@danjenkins
Copy link
Author

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
Copy link
Member

So, should we take it into consideration or not?

@fhemberger
Copy link
Contributor

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

@jbergstroem
Copy link
Member

Yes, as but part of my PR (ssl redirection) I already added this. I guess I should remove it again, then.

@fhemberger
Copy link
Contributor

@jbergstroem I think your PR is just fine …

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants