PHP header redirect 301 - what are the implications?

Question

I have domain.com. If the user is logged in, it should load automatically domain.com/option-X where X is a predefined choice of the user.

So, I do this at the top of index.php:

header("Location: /option-X"); 

But, if the user is not logged in, I just choose automatically the first option like this:

header("HTTP/1.1 301 Moved Permanently"); 
header("Location: /option-a"); 

So, i have two questions regarding the implications of doing so:

1. Since the search engines crawlers won't be logged in, they will always get domain.com/option-a - does it affect them that it has a 301 header?
2. What could be the server cpu load of doing those redirects? I don't know how to make a test out of it. The current site (which has no redirects) has about 100k daily visits.

Solution 1

The effect of the 301 would be that the search engines will index /option-a instead of /option-x. Which is probably a good thing since /option-x is not reachable for the search index and thus could have a positive effect on the index. Only if you use this wisely

After the redirect put exit(); to stop the rest of the script to execute

header("HTTP/1.1 301 Moved Permanently");
header("Location: /option-a");
exit();

Solution 2

This is better:

<?php
//* Permanently redirect page
header("Location: new_page.php",TRUE,301);
?>

Just one call including code 301. Also notice the relative path to the file in the same directory (not "/dir/dir/new_page.php", etc.), which all modern browsers seem to support.

I think this is valid since PHP 5.1.2, possibly earlier.

Solution 3

Just a tip: using http_response_code is much easier to remember than writing the full header:

http_response_code(301);
header('Location: /option-a'); 
exit;

Solution 4

Search engines like 301 redirects better than a 404 or some other type of client side redirect, no worries there.

CPU usage will be minimal, if you want to save even more cycles you could try and handle the redirect in apache using htaccess, then php won't even have to get involved. If you want to load test a server, you can use ab which comes with apache, or httperf if you are looking for a more robust testing tool.

Solution 5

Make sure you die() after your redirection, and make sure you do your redirect AS SOON AS POSSIBLE while your script executes. It makes sure that no more database queries (if some) are not wasted for nothing. That's the one tip I can give you

For search engines, 301 is the best response code

View more solutions

Comments

[Andres SK]

im assuming that using ob_start('ob_gzhandler'); before the header call will have no positive effect neither, am i right?

[pixeline]

Yes, indeed. To the contrary: more work for the server for no benefits.

[justinhartman]

This is truly a great solution and I thank you for sharing it with us. I normally would have just used the Location header to redirect to my primary domain but the fact that you include a header for search engines and, equally important, added the exit() function makes perfect and logical sense to me. This is great, thanks once again.

[RAMM-HDR]

i think shorting the code this way is more cleaner : Exit( header("Location: /option-a", true, 301) );

[Accountant م]

What would be the effect of this header on http2 protocol ?

[mehmet]

Syntax header(header, replace, http_response_code)

[mehmet]

Syntax header(header, replace, http_response_code)