Duplicate Content: Canonicalization vs. Redirects

[marisolmarketing]

Hi all,

I have a client that I recently started working with whose site was built with the following structure:

domain.com
domain.com/default.asp

Essentially, there is a /default.asp version of every single page on the site. That said, I'm trying to figure out the easiest/most efficient way to fix all the /default.asp pages...whether that be 301 redirecting them to the .com version, adding a canonical tag to every .asp page, or simply NOINDEXing the .asp pages.

I've seen a few other questions on here that are similar, but none that really say which would be the easiest way to accomplish this without going through every single page...

Thanks in advance!

[marisolmarketing]

Thanks so much for your help. I'm working with the web dev team today to find out if they can get these redirects in place.

[WhoWuddaThunk]

Did you check the site function prior to the past few days?  The Google update targeting clustered domains has messed with the site search function for right now.

Anyway, if it isn't being indexed then you probably aren't in any trouble right now.  I'd still work to get the 301 redirects in place, though.

[marisolmarketing]

Hi Cody,

Using the site: function in Google, it doesn't look as if the pages are being indexed, however in the PRO tool, it's showing both the .com & /default.asp versions and saying that they are duplicate content.

The website company that developed the site says they should be 301 redirected, but they are not, because you can access the page by going to both versions, and they don't redirect to just one...

[WhoWuddaThunk]

How are the duplicates being created?

Best solution would be to redirect the pages you don't want, but a canonical should be sufficient.