Forum Moderators: Robert Charlton & goodroi
I've been ooccasionally reading about the canonical issues regarding non-www & www pages indexed by google. I confess to not concentrating too much on this cause I believed my sites never had non-www pages,
Well, I just discovered that a site i first put up , as a learning hobby site in 2004 has like 15 non-www pages indexed, an all thesepages have since been deleted by me many months ago
I've recently used the url removal tool extensively on www pages that i've also deleted but which remained cached by google,
However, even tho the whole site is only 40 pages, google has only the default. and my login pages indexed
And I submitted a sitemap
Question:
Should I delete all the non www urls, the pages are already deleted an I don't want to 301 any of the cause they where obsolute anyway, tis a kinda web application.
Sorry if this has been asked before, but if I saw it, i sure didn't get it :-)
Choose one, www or non-www, and set up a site-wide 301 redirect from one to the other. The one you redirect TO will be the one that will be listed.
Pages that are already marked as Supplemental Results will take a lot longer to be fixed, maybe years.
There is no other alternative.
I found this thread
[webmasterworld.com...]
I will be trying this asp code tonite, but another question I have is that, even if one off your sites does not appear to suffer from the canonical issue, would you use the redirect anyway?
just in case .
Pages that are already marked as Supplemental Results will take a lot longer to be fixed, maybe years.
Maybe never. I have pages from the later 90's still in there. I have tried just about everything and yet they remain. It is one aspect of G I wish they could clean up. You would figure the resources to keep such a DB would be huge. Do you think there ever will be a "supplemental fix?" Maybe they are saving it for "History of the Internet." Most of these pages still have cache.
Even if you can't see a problem with the site (i.e. all of the pages are already listed as either www or non-www, not a mixture) then I would still add the site-wide 301 redirect to stop it ever happening in the future.
the http://example.com for an number off my domains are simply given a dns error. Now , I'm sure its because I haven't setup the correct dns records
Does anyone know the correct dns record format to set up to resolve
http://example.com
i am currently trying
cname record example.com. examplesNIC.com