Update Saga. Part 5

[Brett_Tabke]

What say you?

Over and done with?

All done all through?

[Dayo_UK]

Yes, but for most sites (well ones that are problem free) it is still there:-

[66.102.9.104...]

[66.102.9.104...]

[dfre]

Yes, but for most sites (well ones that are problem free) it is still there:-

I see your point.

[lxenterprise]

I am new, I see a googlebot crawled my site this morning but I go to the google caches of my site and only one is renewed as of today. Will this show up later? Also my PR on my outside pages went up but my homepage did not is that usual?

Thanks for helping a newbie

[reseller]

Dayo_UK

Why there are still few url only pages?

[66.102.9.104...]

Thanks!

[Dayo_UK]

Because Google never ever seems to give up (well rarely) on a url - they have been there for ages - dont seem to harm Webmasterworld rankings.

If WebmasterWorld homepage got indexed under the non-www again - that might be a different situation.

[reseller]

Dayo_UK

I see. Thanks.

[Dayo_UK]

This is the one worth watching Reseller:-

[66.102.9.104...]

Unless a fix is done then rankings should slide, Googlebot should visit less and pages go supplemental eventually. Although the site has a lot of links to the /blog page so I wonder if it might survive. Still getting crawled OK at the moment it seems by looking at the fresh dates.

[reseller]

Dayo_UK

>>Unless a fix is done then rankings should slide and pages go supplemental. Although the site has a lot of likes to the /blog page so I wonder if it might survive.<<

I understood from Matt that he doesn't intend to do a 301 redirect at present. He just want to wait and see.

Well Inigo can afford to do some test with his blog, I guess :-)

[Dayo_UK]

Yes, but it is not a great example of the problem - his blog probably has high pr on the non-www homepage and a lot of links go to /blog - so the fall may not be as dramatic.

It will therefore get sweeped under the carpet. :) IMO ;)

[BillyS]

Jagger has become a great example of the downside of making an update "public." To me, Yahoo's approach is much better - letting us know (at the last minute) that an update will be visible the following day.

J3 has been sitting on that DC for nearly two weeks and it has not spread. Clearly there is something Google does not like about those results or they would have let them loose. Matt mentioned they would spread early this week - well that has not happened.

Ignorance is bliss. Jagger - from an update process standpoint - is a fiasco and a disservice to the webmaster community.