Can mass different log-in pages result in SEO duplicate and/or low quality punishments?
- by Noam
I have internal pages that rely on an external API which I would like to build upon user request. Two options I thought about:
Make lots of 'thin' pages that specifies that if you want content about X, you need to log-in, and then the page will be built. Pros: user understands what he'll get when logging in. Cons: SEO implications of such a solution due to the mass 'low quality' and 'cross-sites duplicate content'
Make them all redirect to ONE same generic log-in page. Pros: No duplicate low quality content. Cons: Lots of internal links to the same log-in page.
Which would you recommend?