I have just inherited a lingerie site, and 10% of the items could be considered adult (novelties). It runs x-cart, which is currently set to 302 redirect to a disclaimer page for any of these items and populates the link for the enter button on that page. I know this is bad. Google has indexed 2 seperate product urls as the warning page. This disclaimer is necessary, but there has to be a better way. Any ideas would be appreciated. Thanks
I appreciate all the help so far. Does anyone have a comment on this idea? Instead of redirecting to a disclaimer page, have a layer that displays over the main content page. The layer will contain the disclaimer, and if the user clicks i agree, it will change a variable setting, and remove the layer. If they click no, it will link to some other site. The variable that is changed, is always checked when a page is deemed to need a disclaimer. This way they only have to click it once. Seeing as how the layer wouldn't be hidden, it shouldn't have any kind of negative effect, right?
Hmm, still no love on this? What about this idea? Have the stuff needing a disclaimer, hosted on a subdomain like adult.whatever.com On the main page, the links needing a disclaimer would not be directly linking to the contet yet. Instead, they would be grayed out a bit, and clicking anywhere on that section would link to whatever.com/disclaimer.html If/when they click yes, it takes them to the adult.whatever.com. The links to the adult related products would be then be active. The links to the non-adult stuff would not be hosted on the adult subdomain, therefore all links on the adult subdomain would go back to the regular domain. On this domain, links to the adult section would now be active per some variable check related to what was done on disclaimer.html That seems a bit convoluted to set up, and I'm wonderng if it could cause duplicate content issues. Has not one single person on this forum never had to deal with this? If you can't help CAN YOU PLEASE point me to a place where I might find help. Thank You.
Okay scratch all those other ideas. Today I found a site that appears to do it right. According to Live HTTP Headers, the redirect is being done through javascript based on a cookie. The redirect that is done is a 304! I was not familiar with this one. The only thread I found on here about it, was someone that was banned talking about how it could be exploited. According to SeoConsultants.com This sounds like the answer. Does anyone have experience with 304s? Can you confirm this would be a good solution for the problem?
YEAH!!! I believe I can prove that the answer is yes. I have found a working example. Check the redirects in live headers on this site that has excellent serps for its main keyword.. (link is to landing page of adult dvd site, hxxx://www.adultdvdempire.com and adult.dvdempire.com They both do a 304!!!! You have the main page load, but run a .js that will check for a cookie. If it's not there, it 304s to the disclaimer page. Disclaimer page loads cookie, user clicks link back to main page. I'll follow up when it's all done.
wooow...your building a thread talking to yourself is this for backlinks, or you are for real (sorry my question, but when i talk to myself, and yes i talk alot to myself, i don't write it in public )
you caught me. I hatched this plot on Feb 22, and chose to do it only on this thread where NOONE was responding. You put Sherlock to shame!