As discussed in the following thread 7 months ago ( http://premium.wpmudev.org/forums/topic/domain-mapped-subdomains-using-302-redirect ), the domain mapping plugin is redirecting using a temporary 302 vs 301 redirect. It doesn't look like the fix that was discussed was ever implemented. I think the reasons for why this is undesirable are self explanatory, can we get this fixed?
As discussed in the following thread 7 months ago ( http://premium.wpmudev.org/forums/topic/domain-mapped-subdomains-using-302-redirect ), the domain mapping plugin is redirecting using a temporary 302 vs 301 redirect. It doesn't look like the fix that was discussed was ever implemented. I think the reasons for why this is undesirable are self explanatory, can we get this fixed?
Many would consider inserting an unnecessary 302 redirect in front of your domain to be a dangerous and unnecessary risk from an SEO point of view. Actually, some guys I know would go apesh*t is they saw this was being caused by a plugin.
There is no upside and potentially lots of downside (depending on whom you talk to) to leaving this broken. I've got the fixed version, you've got the fixed version, why isn't this sucker upload and fixed already? :)
Responses (6)
Keeper of the Dark Chocolate — 27th December 2010 #
I just downloaded version 3.0.2 of the plugin and it has the 301 redirect.
edit: Never mind. That was Donncha's plugin that used the 302. The one from here is missing the true statement. That is still missing.
Sales & Support Lead — 27th December 2010 #
Hiya Tracy,
Nice catch! I'll make sure Ulrich and Aaron are aware of this and we'll work to get an update released soon.
Thanks again!
Lead Developer — 28th December 2010 #
Tracy, are you using nginx? I've discovered that 301 redirects often have issues when using php FastCGI.
Member — 29th December 2010 #
I'm not using nginx, but any headers tool like http://www.seoconsultants.com/tools/headers will show that this is not a 301 redirect.
Many would consider inserting an unnecessary 302 redirect in front of your domain to be a dangerous and unnecessary risk from an SEO point of view. Actually, some guys I know would go apesh*t is they saw this was being caused by a plugin.
There is no upside and potentially lots of downside (depending on whom you talk to) to leaving this broken. I've got the fixed version, you've got the fixed version, why isn't this sucker upload and fixed already? :)
Keeper of the Dark Chocolate — 29th December 2010 #
Just to clarify since I made the mistake, the issue isn;t the 301/302 debate but the missing TRUE bit in the header call.
At least that's what I;m looking at.
Member — 5th February 2011 #
It looks like the update failed to make into 3.0.4 version of the plugin as well.
Become a member