Update Jagger - Part 2

[Brett_Tabke]

Continued from
[webmasterworld.com...]

[arubicus]

"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."

Second that.

[steveb]

"What is wierd is I can see it when using mcdar but not when I open it in a new window/tab"

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]

[Patrick Taylor]

AlexK:

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.

[Roolio]

"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"

yeah strange. didn't know that. so what are the real results than? the mcdar results or the ip results? kind of confusing.

[fredde]

hey, if you wonder why not getting the same serps when opening a new window with the same IP (66.102.11.99), just check out which URL is REALLY used. hint: its not just the IP.

[steveb]

And now the "Jagger1 with a twist" results are gone from all datacenters. Either a step back, or possibly Jagger3 will hit everything in a few hours.

[Roolio]

fredde: "hey, if you wonder why not getting the same serps when opening a new window with the same IP (66.102.11.99), just check out which URL is REALLY used. hint: its not just the IP."

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.

[g1smd]

There was a site with a mix of both www and non-www listings, many URL-only results, and so on, at the beginning of the year.

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.

[fredde]

@roolio
damn, this board is lightning ;)

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 ;)

[fredde]

p.s.: this is related to mcdars query-string, not the IP itself.