Want to get involved in developing SMF, then why not lend a hand on our github!
Started by badon, May 02, 2016, 06:19:20 AM
QuoteA 301 redirect is a permanent redirect. [...] All traffic intended for URL A is permanently routed to URL B, and all link popularity and existing SEO value for URL A should also be transferred to URL B. [...] A 302 redirect is a temporary redirect. [...]If you use a 302 redirect when you should use a 301, search engines have to try and determine which page is the "high value" page. Only one version of the page will likely be listed in search engine results, and you stand a chance of having the wrong page listed. This problem compounds over time as a chain of redirects can sometimes exist on older sites.
QuoteA good example of when to do a 302 redirect would be [if] you have a product that you no longer have for sale [but] is something that you might sell again. In this case, you might want to use a 302 redirect to send the user to the category page. If the product outage is going to be for any real length of time it might not make sense to send the user to a page that they cannot order from, so you redirect them to the category page allowing them to look at similar items. And with that 302 you are telling the search engine crawlers that your content is just offline temporarily [...]
Quote from: Arantor on May 02, 2016, 08:12:22 AMThe original use case was people using it to prominently display a link to something like we used to do here for the bug tracker (maybe we now use it for GitHub?)
Quote from: nend on May 02, 2016, 09:27:29 AMIf you don't care about stats you can ultimately just have the theme just show the link instead of linking to SMF to do the redirect.