301 redirects shouldn't be followed #9
I ran into an issue while trying to handle 301 redirects:
When the prerender server (either self-hosted or on prerender.io) sends a 301 redirection, django-seo-js responds with a 200, it seems to follow redirections.
IMHO this is not the expected behaviour, Google needs to know that the url has changed. I think the simple fix should be to add
Is there any scenario where we want redirects to be followed? If so, we can add a global setting, otherwise this should be disabled by default.