Using a 302 redirect to "age" pages that don't exist as of yet...

[caketaker]

Hi,

I've got a theory that I'd like to share and hopefully get some good feedback as to whether this would be a good idea or not.

Let's say may website, www.example.com, consisted of a page www.example.com/something/. I plan to create new content for my website that may take several months to develop/create. So my theory is that if I create the URL now called, www.example.com/something-else/ and include a 302 temporary redirect to the most relevant page, in this case www.example.com/something/. I would then include the new URL into the Google Webmaster Tools sitemap so that it is accessible by the Googlebot. As a 302 redirect will crawl the URL and not pass any PR or bad equity to the redirected page (www.example.com/something/) meanwhile indexing that URL in Google.

As my actual page won't be ready for a couple/few months it would give the URL www.example.com/something-else/ time to gain some sort of trust and recognition in Google. So once it eventually does go live, it would take less time to start ranking for a competitive keyword.

As I've mention, this is a theory and may raise a number of issues. Would this be something worth testing and potentially risking my site or would it be a straight 'NO DON'T DO IT!'

I appreciate anyones help as I am still pretty new to the SEO world!

Thanks

[tedster]

With an internal 302 redirect, Google will index the source url but with the title and content of the target url. So if the target url can be accessed in other ways, you could accumulate a lot of duplicate content across different urls, and that's not a help but rather a confusion at best.

I would say don't do it.