Forum Moderators: open
domain.com/campaign1
domain.com/campaign2
Which redirect to something like
domain.com/page.asp?pn=1&tracking_param=1
domain.com/page.asp?pn=1&tracking_param=2
But the "canonical" url is:
domain.com/page/1
Now, theoretically, the "link juice" from both of those 301 should be transferred to the canonical url, so that whenever the page is indexed, the Search Engine know that's it's really looking at "domain.com/page/1"
BUT - the platform I'm using insists on doing a 302 to "domain.com/campaign1/" before it 301s to the actual page.
My understanding is that 302 redirects do not "transfer" the ranking like a 301 does (in other words, it assumes that that "domain.com/campaign1/" and "domain.com/campaign1" are in fact different places altogether. (Since they are not, this would be a bad thing.)
Of course, the wrinkle here is that the page that I ACTUALLY want indexed is only referenced by the <link rel="canonical"> and never actually landed on.
How should I implement this so that the canonical url is always the one indexed?
My thoughts on this are that I want all the redirects to be 301 in these cases.
Yours?
the best solution is to use your server's rewrite module to externally redirect (301) your initial request to the canonical url and bypass the "platform's" 302 redirect.
then if your platform needs to see a url like example.com/page.asp?pn=1&tracking_param=1 do that with an internal rewrite.
