Hacker News new | comments | show | ask | jobs | submit login

Hopefully I can help some. :)

I see a couple of problems with your redirects:

1) http://www.MelonCard.com uses a 302 redirect to the https version. You have inbound links to that domain pointing to the http version, so the 302 negates the following 301.

2) Furthermore, your 301's seem to be implemented incorrectly. It works for me in Safari/Chrome, but if I use curl on the command line, or any crawling software I see an infinite redirect:


This is likely interrupting Googlebot's crawl too. Certainly worth a fix!

A couple of other bits to note:

1) The redirect in Chrome sends me to:


which Google believes could be different to:


You should add a rel=canonical meta tag to the page to help Google out.

2) Your internal links point to safeshepherd.com without the www., but your MelonCard redirect redirects to the www. version. You should probably make this consistent, and also 301 one version to the other.

This latter points may seem picky, but Google can be troublesome with this.

Hope this helps! :)

Since the OP is using nginx, here is how you properly do a 301 redirect straight from nginx.conf (in the 'server' section for meloncard.com):

        rewrite  ^/(.*)$  http://safeshepherd.com/$1  permanent;

That's actually more complicated than it needs to be, see http://wiki.nginx.org/Pitfalls#Taxing_Rewrites


    rewrite ^/(.*)$ http://domain.com/$1 permanent;

    rewrite ^ http://domain.com$request_uri? permanent;

    return 301 http://domain.com$request_uri;

Awesome - thanks!

Nice tip. Perhaps with https instead of http in the redirect URL, though? :)

True! It does look like Google will accept https as a canonical homepage link. They do it for Twitter.

Guidelines | FAQ | Support | API | Security | Lists | Bookmarklet | Legal | Apply to YC | Contact