Forum Moderators: Robert Charlton & goodroi
Almost looks like a hybrid of J1 and J2.
>>Reseller,
are u there? are u checking 66.102.11.99? can this be the real J3? <<
I´m checking few DCs including the one you mentioned. We shall see the "real" J3 when we reach the flux that follow J3, IMO.
At present the folks are just spotting the Front Troops of Jagger3, I guess ;-)
edit:
What happened is we have 500 pages or so that when using the site: command would bring a mixture of url only pages and pages that were fully indexed. Now the fully indexed pages are first. And the home page of the site is almost back on top of things.
[edited by: arubicus at 10:28 pm (utc) on Nov. 4, 2005]
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
I agree, not sure if it is J3 but a major difference from what I have seen before.
However as far I am concerned there is something better going on 216.239.53.104...IMO this looks cleaner
EDIT: yep currently cleanest results on 216.239.53.104, really :) I bet on this DC.
[edited by: followgreg at 10:46 pm (utc) on Nov. 4, 2005]
That still looks like J1 post "the twist". If the DC i mentioned above is the start of J3 and accorind to GG J3 is an indexing update, then it would make sense that it would be a hybrid of J1 and J2.
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?
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)
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]
Seeing the same thing. Why is visible through mcdar but not when checking the ip in a new window?
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! ;-)
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>
It is stuffed full of ancient supplemental results (cache dates back to January 2004), and has been for several months.
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.
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.
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 :)
--------------------------------------
Second that.
Yes, I see different results depending on whether you use the ie? method (like mcdar) or the search? method (the "normal" view)... regardless of datacenter. Now THAT is weird.
===
Yup that ordering thing Dayo posted is now totallt different than before... both are a mix.
[edited by: steveb at 11:06 pm (utc) on Nov. 4, 2005]
I too saw vast drops in some places on 18th October, but I didn't at first assign it to the canonical issue, but thanks. I'm just looking for indications that, whatever the symptoms, Google has resolved the problem.
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"
yeah strange. didn't know that. so what are the real results than? the mcdar results or the ip results? kind of confusing.
yeah we know that now. so which of the 2 are the real results? I would guess it are be the ip results because that's how you normally search.
The 301 redirect from www to non-www was added in March, and Google started to list all of the non-www pages within just a few days. It added a title and description to every one of the non-www pages. It took more than a month for the www pages to drop out (and some re-appeared again briefly before being finally dropped).
In July, Google suddenly added a load of www pages back in to a site:www.domain.com search, but those pages did NOT appear when doing a site:domain.com search (re-read that last bit again). Those www pages had full title and description and represented about 40% of the real number of pages on the site (except that the site was actually fully indexed under the non-www URLs too, and a redirect from www to non-www had been in place for many months). The www pages were flagged as supplemental.
It took several months for the www URLs to turn into URL-only listings - this happened just a few weeks ago or less.
>> 66.102.7.104
This datacentre has the www URLs all back as fully indexed, with full title and description (and all flagged as supplemental results again). The site has had www redirected to non-www for about 8 months now. This datacentre has old data - the cache dates are from December 2004 and January 2005.
okay, i ve checked 66.102.11.99 and i can tell you that this results are definetely VERY OLD. not just pre-jagger, but ancient-jagger ;)
