Update Jagger - Part 2

[Brett_Tabke]

Continued from
[webmasterworld.com...]

[Patrick Taylor]

Could someone please clarify exactly what signifies Google having corrected the canonical URL problem? I understand the basic issue of not wanting both www and non-www URLs to be indexed, but are we expecting a search for 'site:domain.com -www' to return no results when the fix is in place?

Second try... how does one know when the problem has been fixed on a particular website? What indicates the fix? Google is going to resolve the canonical URL problem of having indexed both versions (www and non) and having split the PR, but by doing what? Removing one or other from the index? And assigning the whole PR to the remaining version?

[AlexK]

Patrick Taylor:

Could someone please clarify exactly what signifies Google having corrected the canonical URL problem? I understand the basic issue of not wanting both www and non-www URLs to be indexed, but are we expecting a search for 'site:domain.com -www' to return no results when the fix is in place? (or vice versa)

Correct.

If I do a "-www nocompress site:mysite.com" (both canonical + supplemental issues fixed back in Feb) some DCs--including 66.102.11.99, cristinita--give just 2 results, others give lots more.

PS

Added: page rank on Home page has drooped to 4 (was 5), and HP is not affected by Canonicalisation issue (at least on 66.102.11.99).

[edited by: AlexK at 10:54 pm (utc) on Nov. 4, 2005]

[Roolio]

"same thing, changes are only visible through mcdar...not if directly checked in the ip address...and as someone also said those new results at mcdar seem to be bringing back similar (not same) results to those pre J1 & J2"

Seeing the same thing. Why is visible through mcdar but not when checking the ip in a new window?

[followgreg]

That's exactly what i see on 216.239.53.104. But you know, I'm not qualified to tell if Google is a good search engine / broken or not, but i can tell one thing, these guys MASTER public relations! ;-)

[AlexK]

Now, that's what you call a fast reply.

[Patrick Taylor]

Yes! Thanks AlexK.

So I assume that if a search still shows listings for the non-www (when the correct URL is www) that the fix is not yet in place on that DC? (and will at the end of Jagger be fixed on all DCs)

<added>I mean a search for 'site:domain.com -www'</added>

[g1smd]

That 216.239.53.104 datacentre has old results on it.

It is stuffed full of ancient supplemental results (cache dates back to January 2004), and has been for several months.

[stubear]

"Seeing the same thing. Why is visible through mcdar but not when checking the ip in a new window?"

The change only seems visible when using the /ie?query tag rather than the standard /search?query tag.

The ie tag is the one used by McDar to show numbered positions which is why its showing there - bit of a weird one though, can't see why it should make a difference.

[AlexK]

Patrick Taylor>>

It is assumption, of course, but the issue for my site is that for the last 9 months there has been NO movement on this, and a vast drop on Sep 22. The fact that some DCs on McDar show just 2-of-3 results for the search indicates to me that there are an updated set of SERPs making their way through and--for my site at least--they are better.

[reseller]

Dayo_UK

Do you still see the same right now as per your post?

Thanks!
----------------------------------

Site search on Webmasterworld on 66.102.11.104:-

[66.102.11.104...]

Brett - you might want to add your 301 back from non www to www BTW

Notice that it is very logically ordered - eg Homepage followed by direct links from homepage (eg forum indexes)

Compared to this:-

[66.102.7.104...]

Pages not really in an order (which I understand)

Now the 66.102.7.104 is giving me better results on some searches as I say - so this has got something about it too, however my main site is still not fixed - but encouraged :)

--------------------------------------