Welcome to WebmasterWorld Guest from 18.104.22.168
Would have thought GG would have jumped in over night (well my night) and jumped in if anything significant was happening on 22.214.171.124 & 126.96.36.199 (or .99 as people keep calling it.)
Sorry Dayo_UK, one of the other hats I wear kept me hopping yesterday. It looks like people probably noticed Jagger3 changes at 188.8.131.52, starting yesterday. I believe that data center includes Jagger1, Jagger2, and Jagger3.
all the new DC's show me my home page and MAJOR subsections now first on a site:www.example.com instead of the random mix u got before.
This is a definite major change. Generally traffix has dropped on my pages although I got an upgrade from 5 -> 6 on the homepage.. :(
[edited by: Ankhenaton at 5:10 pm (utc) on Nov. 5, 2005]
To follow the progress of Jagger3, one can specify the DCs which have shown/ showing the different stages of Jagger3 while its in progress.
We can assume that the following DCs are showing at present Jagger3 Beta-2
While previously the following DCs had shown Jagger3 Beta-1 ;-)
What I like most in todays posts is that not so many fellow members are talking about Jagger2 and whether Jagger3 has started or not anymore. IMO, that shall allow us to focus on Jagger3 progress.
P.S. New part of Jagger3 thread has started while I´m posting this message on the previous thread part. Therefore I'm posting this message again.
Is this DC still in flux - last night I noticed a few of my sites logically ordered in site:domain.com searches - not so many today.
Also.... I guess for us with Canonical url problems that if the homepage is top on the site search then it looks like G recognizes that as the homepage/canonical - obv canonical url problem sites have had crawling problems - Crawling likely to improve due to this?
So in other words - a way to go on this DC/new Index?
My sites still doing badly :(
However, there is improvement in SERPs quality.
I don't see that very often, idolw. :) If you want to report spam, then use the kw jagger3 at [google.com...]
But if you want to report indexing (non-spam) issues, then do a search on google.com and click the "Dissatisfied? Help us improve" link at the bottom right part of the page. Use the keyword jagger3 in that form as well.
Last night I was very encouraged - the sites that I monitor for a site:domain.com search were in the format.
Recently Crawled Pages
Although I have seen a few sites where the homepage has not been indexed recently - and they were not in that format - so I guess it was below the recently crawled pages?
Soooo - even though the rankings (as in ones user use ;)) were still rubbish for the sites with the problem it looked like G understood the most important page - which is good for the future I hope :)
Today - not so many sites like that.
Ok - so let it settle before the Canonical url reports come in.
I bet you would be happy if you never had another one of those reports ;)
Just to confirm - if I want to ask about indexing problem; should I be clicking on the "dissatisfied" link now or what to see what happens over the next couple of days?
My site has plunged down the SERPS for nearly all keywords but I don't know why - is there still a chance this should change?
site:domain.com lists 400 non-www pages and ZERO www.domain.com pages, and
site:www.domain.com lists 70 www pages that are all old supplemental pages from a year ago?
Is Jagger3 going to fix this?
Note: the 70 www pages that appear in the site:www.domain.com search do not appear in the site:domain.com search! These pages re-appeared in the SERPs about 3 or 4 months ago, after having been previously fixed by adding the proper 301 redirect way back in March this year.
In some datacentres those 70 pages recently turned into URL-only listings, and in others they are still fully listed. Those 70 pages (and a few dozen more) are excluded by robots.txt as they are cgi pages. The non-www version of the same cgi pages has always been URL-only in the SERPs; Google respected the disallow right from the beginning.