1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

301 Redirecting Previously-Cloaked URLs to other Internal URLs

Discussion in 'Cloaking and Content Generators' started by irishiwasdrunk, Apr 15, 2014.

  1. irishiwasdrunk

    irishiwasdrunk Newbie

    Joined:
    Apr 15, 2014
    Messages:
    1
    Likes Received:
    0
    I recently started working at a fairly widely known ecommerce company. Our domain has strong domain authority and brand name recognition.


    The company had an SEO agency that for years was cloaking - based on user-agent. One version of the page had very little content, was simply created for driving conversions and sales alone, and was utilized by all major channels of the company. The other version was a keyword stuffed URL with tons of crawlable, spammy content that was provided for search engines alone.


    Of course, eventually the site was penalized. One day it was completely removed from the index, but within a few weeks the site was restored to it's original coverage in SERPs (all URLs, cloaked and non-cloaked versions). No Manual Actions messages were provided via GWT.


    After giving the agency the heave-ho, the SEOs at the time decided to redirect each and every optimized/cloaked URL to their non-optimized but non-penalized counterparts. We are talking thousands upon thousands of pages here.


    For example:
    w3.exampledotcom / keyword-stuffed-cloaked-URL-with-over-optimized-content.php


    redirected to:


    w3.exampledotcom / ecommID39392392392/dynamic-content/


    Questions:
    Does utilizing 301 redirects from the previously-cloaked URLs to our current, native URLs hurt us? To what degree could this impact us?


    I've come across a lot of discussion around 301 redirecting entire domains that were penalized, but nothing around single URLS on such a large scale.


    Appreciate any and all feedback.