Forum Moderators: Robert Charlton & goodroi

Message Too Old, No Replies

Update Saga. Part 5

         

Brett_Tabke

8:26 pm on Nov 9, 2005 (gmt 0)

WebmasterWorld Administrator 10+ Year Member Top Contributors Of The Month



What say you?

Over and done with?

All done all through?

zikos

9:48 am on Nov 21, 2005 (gmt 0)



J3 is now on 35 out of 45 DC's at Mcdar

petehall

10:11 am on Nov 21, 2005 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



Yup, J3 has rolled out.

Looks like it's all over at last and the 9 won in the end. Never underestimate the power of the 9!

Dayo_UK

10:15 am on Nov 21, 2005 (gmt 0)



Yep, Agreed what seems to be what J3 is all about has just about rolled out.

My results are different on every DC though just about - but that has been the way for my sites for 9-10 months.

My theory has developed into that Google can not determine the root page of some sites - this may be caused by either 302, supplementals or the Canonical misery.

Unfortunately, there does not seem to be any indication that Google are getting any closer to a fix.

petehall

10:16 am on Nov 21, 2005 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



Hold on a minute... is it retreating again?

j_do

10:16 am on Nov 21, 2005 (gmt 0)

10+ Year Member



It seems to be everywhere now, except on my default (Dutch) Google :( Never has been as far as i know. Come on Jagger3, I need you bad :)

colin_h

10:25 am on Nov 21, 2005 (gmt 0)



I notice than when I used to enter google.com I used to get auto-forwarded to google.co.uk. This is not happening anymore ... does it matter?

lee_sufc

10:32 am on Nov 21, 2005 (gmt 0)

10+ Year Member Top Contributors Of The Month



what are the results on a few of the DCs (such as [64.233.167.99...] all about then?

zikos

10:41 am on Nov 21, 2005 (gmt 0)



"My theory has developed into that Google can not determine the root page of some sites - this may be caused by either 302, supplementals or the Canonical misery.
Unfortunately, there does not seem to be any indication that Google are getting any closer to a fix. "
Unfotunately Dayo your theory seems to be true :(

Dayo_UK

10:50 am on Nov 21, 2005 (gmt 0)



Yep - Zikos - that is where the evidence points.

The site ordering seems to lend support to that theory, I mean is the root supposed to be top? - if so then Google are missing the target a lot.

and again - searching for "www.domain.com" and the first page being an internal rather than the root again backs up this theory that Google maybe having problems determing the root page for a site.

Miop

10:51 am on Nov 21, 2005 (gmt 0)

10+ Year Member



Sorry...have got behind. Which datacenter can I see J3 on as it is now rolling out?
I'm looking at 216.239.59.104.

Regarding the root page issue, I have had to redirect my index.php and every reference to it on the site to /.
The problem is now cured for me since I have done that (though it was never a problem prior to the past few months!)

petehall

11:14 am on Nov 21, 2005 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



My local DC now shows it which is normally always one of the last to receive an update 64.233.183.104.

Now it's live, I think J3 looks a bit of a mess?!

stateless

11:45 am on Nov 21, 2005 (gmt 0)

10+ Year Member



My guess is that they will still be cleaning it up a bit, for a while yet.

A point of interest: The results at the datacentres differ slightly from the google results I'm getting, which doesn't appear to be at any of the mcdar.net/dance/ datacentres. How io I find out which datacentre I'm hitting?

petehall

11:51 am on Nov 21, 2005 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



Ping www.google.com

maschu

11:55 am on Nov 21, 2005 (gmt 0)

10+ Year Member



or use firefox with the "show IP" extension

reseller

12:07 pm on Nov 21, 2005 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member Top Contributors Of The Month



Dayo_UK

>>The site ordering seems to lend support to that theory, I mean is the root supposed to be top? - if so then Google are missing the target a lot.<<

I read somewhere that Google is doing great efforts to help webmasters with canonical issues. Part of that effort is that Google itself gonna decide in future which page to consider as homepage. And depending on algos, the homepage might change with time of course.
Google call it democracy among webpages :-)

Dayo_UK

12:23 pm on Nov 21, 2005 (gmt 0)



>>>>I read somewhere that Google is doing great efforts to help webmasters with canonical issues.

Where did you read this - sticky me is probably best as link is probably against TOS unless on a trusted news source etc

>>>>Part of that effort is that Google itself gonna decide in future which page to consider as homepage.

Surely this happens now? - I was thinking that perhaps sitemaps might be a good idea for somewhere where you can set the root.

stateless

12:26 pm on Nov 21, 2005 (gmt 0)

10+ Year Member



Firefox tells me I'm hitting 64.233.183.104 , though when I type in the IP as opposed to the domnain name, I still get slightly differing results. I'm aware that makes little sense, but it's true :).

reseller

12:46 pm on Nov 21, 2005 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member Top Contributors Of The Month



Dayo_UK

>>Where did you read this - sticky me is probably best as link is probably against TOS unless on a trusted news source etc<<

LOL..

I read it on "Reseller's News Productions & Developements.. ONLY On WebmasterWorld" :-)

Dayo_UK

12:49 pm on Nov 21, 2005 (gmt 0)



Huh? - so you are saying that it was never said - and just what you think might happen?

taps

12:51 pm on Nov 21, 2005 (gmt 0)

10+ Year Member



I can see the first traffic coming in from post-J3-DCs. Quite exciting. Maybe my site will come back after two months dupe content ban.

Keeping fingers crossed and wishing the best to all of you.

reseller

1:01 pm on Nov 21, 2005 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member Top Contributors Of The Month



Dayo_UK

>>Huh? - so you are saying that it was never said - and just what you think might happen?<<

Yes.. I think so.

Dayo_UK

1:04 pm on Nov 21, 2005 (gmt 0)



>>>Yes.. I think so.

I dont. :(

Google dont seem to be able to get to grips with the situation and as time goes on more and more sites get hit.

Not good.

McMohan

1:07 pm on Nov 21, 2005 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member Top Contributors Of The Month



I am not sure if solving the Canonical problem is all that difficult. Will it not solve the problem if Google by default considers www.dmain.com as the canonical URL, and credit all links to the canonical?

What issues we may foresee in doing so?

petehall

1:13 pm on Nov 21, 2005 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



I'm seeing home pages out rank more relevant inner pages quite frequently.

Personally I don't think this offers the user the best result, I'd prefer them landing directly on the correct page.

Not on all search phrases though. Seems to be a bit random.

Anyone else seeing this?

Dayo_UK

1:21 pm on Nov 21, 2005 (gmt 0)



>>>Will it not solve the problem if Google by default considers www.dmain.com as the canonical URL, and credit all links to the canonical?

It is technically wrong to do this unless Google are 100% sure that content on the non-www mirrors the www.

Technically it is possible to have different content on:-

domain.com
www.domain.com
shop.domain.com
fish.domain.com
etc

There would be no way that Google will credit all links to the www by default.

The problem arises when Googles can not correctly identify when the non-www matches the content on the www.

Petehall,

Yes, obviously that is an important part of the algo that the page specific to the search outranks the page linking to it (eg the Homepage etc) - however for me it is the other way around - the homepage can not even rank for its own name, "www.domain.com" search etc... - beaten by internal pages.

I am not going to call it a Canonical url problem anymore - I am going to call it a problem when Google can not determine the root url - as this AFAIK is why rankings drop - I have a feeling that the problem determining the root page though is very much connected to the Canonical problem, 302 hijack and maybe supplementals.

zikos

1:31 pm on Nov 21, 2005 (gmt 0)



"I'm seeing home pages out rank more relevant inner pages quite frequently"
Yes I do,though I should be happy because my site hits #1 results in some targeted fields but the "money" keywords are RIP ,my theory on that is
1:the whole index update will start after all DC's migrate to J3
2:the index will stay like that until the next PR update
3:Matt or GG said something like "for those that doing well (even in a small chunk of cheese)things are positive....with Jagger
4:If some of us got some top ranking in some fields does that means that within the coming flux we will see some light at the end of the tunnel?
Comments are always welcome.

LegalAlien

1:32 pm on Nov 21, 2005 (gmt 0)

10+ Year Member



Morning everyone ;)

My local default is 66.102.9.104 today, and I was happy to see this -- until I checked our serps...

What happened last night? We're now out of the first 50 pages for all but 1 of our key phrases. I monitor 10 2-3 word phrases that have all been steadily progressing back to their pre-September top 10 positions, and were listed every day since their re-emergence on October 21st. As of yesterday, all phrases were in the top 30 results.

The site can't be under penalty, as one phrase is still #8 for a very competitive term (63 million results). How can this just be flux after 4 weeks of constant listings for us?

Someone please tell me not to worry and that you're seeing the same. Reseller, any chance a steaming hot cup of cappuccino to calm my nerves? :))

McMohan

1:35 pm on Nov 21, 2005 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member Top Contributors Of The Month



Dayo,
Agree technically www and non-www can have different content. We are not talking about sub-domains anyway here.

I was to write infact in the previous post, make www the default canonical, if "www and non-www are identical and both return 200 OK status" which will solve the problem in more than 90% of the cases IMO. In cases where the content is different (my suspicion is, it is a very small %), then leave them as is, with each canonical powered by their own links. I guess it will be a very simple solution to a large problem, (Unless I am missiing any other tech possibilities here)

Dayo_UK

1:43 pm on Nov 21, 2005 (gmt 0)



McMohan

But Googlebot does not visit the page at the same time - eg. the non-www might be visited on the 1st November and the www on the 15th November.

Lots of sites change there homepage daily, weekly, hourly - or even on every visit (different ads run from a database or something)

Sooo - unfortunately that is not the ideal solution.

and as far as we know 90% of the time Google do get it right now - so there will always be sites missing?

>>>with each canonical powered by their own links.

So the whole sites get indexed twice - hmmmz - as long as results from the domain.com/www.domain.com are restricted to 2 and it does not result in onsite duplicate content penalty then I wonder if that would work.

Not ideal - but better than the mess at the moment?

Zikos - I am very much hoping that once J3 has fully been implemented we will see a big crawl based on the J3 infastructure.

[edited by: Dayo_UK at 1:47 pm (utc) on Nov. 21, 2005]

McMohan

1:47 pm on Nov 21, 2005 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member Top Contributors Of The Month



Dayo
But Googlebot does not visit the page at the same time

Nor does the algo work at the same time the bot makes a visit.
Obviously I don't have the stats, but I am fairly sure the instances of sites having different content on www and non-www is far less than the no. of sites suffering from this Canonical mess now.

This 1356 message thread spans 46 pages: 1356