Timeline for 301 redirects in main navigation menu of WordPress website - is this okay for SEO?
Current License: CC BY-SA 3.0
8 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
Apr 13, 2017 at 12:33 | history | edited | CommunityBot |
replaced http://webmasters.stackexchange.com/ with https://webmasters.stackexchange.com/
|
|
Dec 21, 2016 at 16:59 | history | edited | Ilmari Karonen | CC BY-SA 3.0 |
deleted 8 characters in body
|
Dec 21, 2016 at 16:58 | comment | added | Ilmari Karonen | @GDav: Just in case you were one of the people who downvoted this answer because I originally claimed (citing Matt Cutts) that 301 redirects only lose "just a tiny little bit" of PageRank, I thought I'd point out that the "tiny little bit" is apparently now 0%. I've edited my answer to update it. | |
Dec 21, 2016 at 16:46 | history | edited | Ilmari Karonen | CC BY-SA 3.0 |
301 redirects are now confirmed to pass full pagerank
|
Sep 24, 2012 at 17:20 | comment | added | GDVS | .85 is the damping factor cited in the original PageRank formula, and a Google engineer has confirmed there is a decay of PR via redirect, so we could reasonably infer that the same factor is used for 301s. Obv. that's speculative, but not outlandishly so. en.wikipedia.org/wiki/PageRank#Damping_factor, seroundtable.com/archives/021832.html | |
Sep 24, 2012 at 16:57 | comment | added | Ilmari Karonen | @GDav: That .85 would be a pretty huge drop, if true. Any sources for that? | |
Sep 24, 2012 at 16:27 | comment | added | GDVS | As pointed out above, there are ways of providing desired functionality without redirects. Redirect damping factor reputed to be .85, so shaving more than "tiny" fraction. Also unnecessarily increases page load time, server load, etc. | |
Jun 30, 2012 at 13:37 | history | answered | Ilmari Karonen | CC BY-SA 3.0 |