302 vs. 301 redirect: Why you need to use a 301
So whats is in a redirect? Does it matter if it is a 302 redirect or a 301 redirect? Yes! Very much so. A 301 redirect informs Google that you are permanently moving a page to this new destination whereas a 302 redirect lets Google know this is only temporary. There is a time for a 302 and a time for a 301. If you are migrating a website across to a new one, say a .com to a .co.uk, you must use a 301 redirect.
Here is an example of what can happen if you do not setup your redirects correctly. The screenshot below shows domain A (the red line), with lots of authority, being 302 redirected to domain B: (This is ranking data for Google.co.uk)
The company will obviously remain nameless, but this is a glorious example of an IT department, probably not realising the impact of the change they’re making. This is an example for only one keyword, imaging the traffic they have lost across the board!? So, have you ever had to work with a client on this type of solution? How bad was the traffic drop? And did you see an immediate impact once the 301 redirect was implemented? Your comments, as always, are welcome below.
Well mate, as you can imagine, with over a decade of experience on my back I can write a book on errors made from IT depts that created mistakes everywhere, including the one you just mentioned.
The real problem is dev team is unaware at all of all the implications a little change can do. It’s our job educating them in the best way ever.
If they ignore our recommendation, well game over. But that’s their game to come to an end.