Solve Adult Content 302 Issue
What (summary)
As described on ErrorLog#Google caching issue, we are using a 302 temporary redirect for our Adult Content Splash page. This means that search engines keeps the cached version of the page before we put the flag on it. This is bad and we need to fix it.
Why this is important
- On a normal page, if we have personal information and someone requests it off, we no-bot the page and search engines re-spider at some point, removing that personal information. With our 302 response, search engines cannot re-spider and just keeps this personal information forever.
- Our AdultContentPolicy says that people have to log in to see our pages that refer to adult content. Seach engine bots cannot log in so they should not see these pages at all. They should not maintain cached versions of the pages before we flagged them. If 302 is telling them this is only temporary, then that's a problem.
DoneDone
- Search engine bots no longer cache information from pages we have flagged as adult content.
Steps to get to DoneDone
- decide if 301 or 404 or ??? is the most appropriate response - or if there's some other solution
