A 302 Redirect Question | Events Page Updates

[MarketingChimp10]

Hello Moz World,

I have a client that has a TON, like close to a thousand pages that have a 302 redirect set up. After further investigation, I found that every month they update their events page & Demo Request page, and the old events pages still exist but, get a 302 redirect to the updated page. From what I gather, this is a default mechanism set up by the hosting provider.

My questions; is this an example of when to use a Rel=canonical? Also, is there a method for integrating this without having to go into every page and integrate the code snippet? And Lastly, How should I go about ensuring this doesn't happen in the future?

Thanks ahead of time, you guys rock!

B/R

Will H.

[Martijn_Scheijbeler]

Hi Wil,

Well the ultimate fix would be to make sure that you won't create a new page for every piece of updated information that you would run into. It depends on which codebase or framework/CMS you're using in order to set this for all the pages you need, but in general it should be possible to do it.

[MarketingChimp10]

Hello Martjn,

We are using Castle.js and the Meteor platform. How can I ensure future pages are not created using the 302, is this when I would ref=canonical pages? Thanks for your quick response.

B/R

Will

[LoganRay]

Will,

I'm not familiar with the CMS you're using, but to answer your question about rel=canonical, no, that is not an instance of when to use that tag. Canonical tags are used for times when duplicate content is unavoidable, such as sorting a product category page and having different URL parameters based on the sort type.