New Google "Bigdaddy" Infrastructure Live, Data Center Open For Feedback

[ReSiever]

Hello all,

I've read something about this datacenter a few days ago, and i'm not sure if it was at SEW, but I think it is so important so spend my time on it here...

At this very moment, i'm seeing results at http://64.233.179.104 that got spidered only by the Mozilla Google Bot. The Mozilla bot is known not te be responsible for Google's main index, and my guts always told me it was also checking duplicate content, cause it got my pages out of Google's normal index.

I know that the content of some of my pages really get close to each other, so I figured they would get stuck in the duplicate content filter. After the Mozilla bot got around, they did, so that is why I think it also covers duplicate content problems.

But, now that i have some new pages launched i know that they only got spidered by the Mozilla bot. And what do you know? They all are indexed in http://64.233.179.104, but are not known in any normal datacenter. Next to that, I don't see as much portals as I see on other datacenters.

And, as Matt Cutts once stated: "the test data center certainly has some different crawling and indexing characteristics.", according to SERoundtable (http://www.seroundtable.com/archives/002962.html)'s interesting item about this discovery.

I also haven't seen supplemental results, or URL-only results... So, does anyone else have something so say about this? Maybe this really is a test datacenter? Anybody got any news on this one?

[bhartzer]

If you do a search for that IP address on Google (http://www.google.com/search?hl=en&lr=&q=%2264.233.179.104%22) you'll notice quite a few posts regarding the subject. Matt Cutts recently said:

I do expect that data center to eventually go live, but it will take a few months, in all likelihood.

[ReSiever]

I did read that. But the interesting part is, sometimes the datacenter shows the same results as other datacenters. Maybe they sometimes throw it in the regular results, just to measure user behaviour or something? Just guessing...

[dannysullivan]

I've renamed this thread to help make the data center name a bit clearer. Barry at Search Engine Roundtable called it the "Big Daddy" data center. That seems to have come off of this WebmasterWorld thread with lots of discussion of it:
http://www.webmasterworld.com/forum30/32409.htm

Dayo_UK over there says:

OK - Jagger is over - long live "Big Daddy" - as named by MC for the test DC.

I take MC to be Matt Cutts but for the life of me, I can't find anywhere online where Matt's actually used those words to name this data center. Someone finds the original reference, please post. In the meantime, we roll with it.

[Jenstar]

I was wondering about this bot too. I saw the Mozilla Googlebot on a new site of mine that went live only about 12 hours earlier that had no incoming links whatsoever. It had been registered only a few days earlier, so Google knew about it either through whois data or toolbar data, as far as I can figure. The cache date in http://64.233.179.104 matches the first Mozilla Googlebot visit.

It is a blog, and this site has already shown up in the blogsearch.google.com index... and has been live only 5 days now. I had come to the conclusion this bot was related to the blogsearch somehow, because it visits daily and always grabs the feed URL as well.

But what is most interesting, is that this site has only been visited by the Mozilla Googlebot at the same IP, but not by the regular Googlebot, and it shows up in this blog search from that one bot. Which makes me wonder if this Big Daddy DC is somehow getting weighting from the Google blogsearch?

So could this index be given weighting somehow through blog search?

[PhilC]

I did read that. But the interesting part is, sometimes the datacenter shows the same results as other datacenters. Maybe they sometimes throw it in the regular results, just to measure user behaviour or something? Just guessing...
Even when searching on a specific DC, we don't always get the results from that DC. It's probably due to various things, including load sharing, and the need to disconnect it while some types of changes are made.

added
I just went to Matt's blog and coincidentally...

We’re getting closer to calling for feedback on 64.233.179.104, but I probably won’t ask for reactions for another week or two. Right now that datacenter isn’t serving traffic 100% of the time as people pull it out of the rotation from time to time to tune things up under the hood

[SEOBrains]

Matt Cutts named the next major Algo Big Daddy at Webmaster World PUBCON10 in Vegas. During an informal Q&A after hie coffee talk session he asked the people in room for the next Algo Name and someone called out "Big Daddy", and Matt wrote it down, so thus the name "Big Daddy" for the DC changes.
:cool:

[ReSiever]

Hi PhilC,

We’re getting closer to calling for feedback on 64.233.179.104, but I probably won’t ask for reactions for another week or two. Right now that datacenter isn’t serving traffic 100% of the time as people pull it out of the rotation from time to time to tune things up under the hood

Nice catch. Matt Cutt is talking about it for a while now, but up till now he's just keeping the fire burning. Would be nice if he did some real talking haha..

Anyway, I can't test right now, cause the datacenter doesn't seem to be live now. But from what I've been seeing the following things might be true:


duplicate content filter does loosen up
Portal sites lose strength (or authority?) and their rankings decrease
Indexing by Mozilla Bot (more advanced bot)


Next to that, I personally haven't seen any progress with canonical or 301 problems. Maybe somebody else?

[Brian M]

Matt Cutts (a.k.a. GoogleGuy) is on a blog roll, and has posted some great information about Google's handling of 301 and 302 redirects, as well as canonical URLs, etc.

I highly recommend that you read his latest blog entries at:

http://www.mattcutts.com/blog/seo-advice-discussing-302-redirects/

:)

[dannysullivan]

Yep, Matt's been a madman today, but there's a method to his madness. It was all part of setting things up for taking feedback on the Bigdaddy data center, which will migrate to Google in the next month or two. So expect a Feb. 2006 or March 2006 Bigdaddy Update.

Key posts, which I'd suggest reading in this order:

Bigdaddy on the move (http://www.mattcutts.com/blog/bigdaddy-on-the-move/): Alert that one of the Bigdaddy data centers is back to showing regular results so fixes can be put into place. Want Bigdaddy, then go to http://66.249.93.103, where it's still live.

Feedback on Bigdaddy data center (http://www.mattcutts.com/blog/bigdaddy/) where he covers how the data center got its name, how this is an entire new infrastructure for Google web search coming online, how it will go live on "regular" Google in the next month or two, how ranking changes you may see now on regular Google are unrelated, how to send feedback about changes you see and more.

SEO advice: discussing 302 redirects (http://www.mattcutts.com/blog/seo-advice-discussing-302-redirects/) on how and why Google handles permanent redirects on regular Google and new Bigdaddy-flavored Google.

SEO advice: interpreting inurl (http://www.mattcutts.com/blog/seo-advice-interpreting-inurl/) on how to use the inurl operator at Google and why the results probably don't show a hijacking issue, in case you suspect that in regular Google or Bigdaddy.

SEO advice: url canonicalization (http://www.mattcutts.com/blog/seo-advice-url-canonicalization/) on my favorite word, how Google determines which domain to use for your listings when there are multiple options. Canonical issues are something Matt hopes Bigdaddy will improve.

By the way, for some additional background on two of the biggest problems that Bigdaddy aims to solve for Google -- hijacking and canonical issues, see these past pieces from Search Engine Watch:

Google Oct. 2005 Jagger Update Continues Into November & Hating The Term Canonical (http://blog.searchenginewatch.com/blog/051107-151659)

Matt Cutts Banned On Google? And Oct. 2005 Jagger Update Winds Down (http://blog.searchenginewatch.com/blog/051110-100404)

Revisiting Hijacking & Redirects: Moving To A Solution (http://blog.searchenginewatch.com/blog/050801-130330).

So far, I haven't had a chance to play with Bigdaddy, but I already have a big positive feeling from the effort Matt's put into to prepping people for it and to help them send feedback.

[projectphp]

So far, I haven't had a chance to play with Bigdaddy...
Oh man, that is GOLD!

[ReSiever]

Well, as I stated in another thread on here, I saw the results of the big daddy datacenter spreaded across more datacenters since 31 dec / 1 januari. This data was live for two to three days and was set back yesterday to the older data we have been viewing for the last few weeks. And with older data, I mean like a month back or so, cause I'm seeing Serps for specific keywords that I was also getting in the beginning of december.

Right now, they are tossing in the big daddy data(center) in the evening again(well, it's evening overhere :) )as Matt stated at his blog:

Q: Why did you wait so long to ask for feedback?
A: There were a couple reasons. First, I knew that Bigdaddy wouldn’t go live before the holidays were over. Second, the team working on this data center wasn’t showing it 100% of the time; at night, they’d take it out of our data center rotation to tinker with it. That would have been a recipe for confusion. Now we’re past the holidays and the Bigdaddy data center is live 100% of the time. In fact, Bigdaddy is now visible at two data centers: 66.249.93.104 and 64.233.179.104

Personally I'm in datacenter 66.249.93.104 when I'm searching via www.google.nl. So, maybe they are still 'confusing' people but started to collect feedback after being live for a few days...

Next to that, I'm thrilled about the fact that Google has done something about the canonical and redirect (301, 302) problems. Matt has given us a beautiful example of that:

So it looks like 66.249.93.104 is the best IP address to use when testing Bigdaddy. That data center should be showing Bigdaddy results more reliably. Also, it looks like [sf giants] is a fine query to see if you’re hitting Bigdaddy. If you get giants.mlb.com at #1, you’re searching Bigdaddy. If you get www.sfgiants.com at #1 and an uncrawled url http://sanfrancisco.giants.mlb.com/NASApp/mlb/sf/homepage/sf_homepage.jsp at #3, you’re hitting the older Google infrastructure.

Next to that, the data seems to be more recent, cause the Mozilla bot is going around the web like crazy..

So far, so good !

Already had a chance to play with BigDaddy Danny? Waiting to hear your reaction overhere ;)

[grnidone]

Where do you put the feedback?

[Brian M]

Hi grnidone,

Google would like to get the feedback in one of two ways:

From Matt's Blog:

"Reporting spam in the bigdaddy data center
I definitely want to hear about webspam that you see in Google. The best place to do that is to go to http://www.google.com/contact/spamreport.html . In the “Additional details:” section, I would use the keyword “bigdaddy” in your report.

Reporting other quality issues in Google’s index
Do the search that you’re interested in on 66.249.93.104 or 64.233.179.104, then click the “Dissatisfied? Help us improve” link at the bottom right of the page. Again, fill in details and use the keyword bigdaddy so that folks at Google can separate out feedback specifically about this data center."

Just remember that the DCs are in "flux" as Google makes changes. So, you may want to check this thread to make sure that the DC you choose has the "bigdaddy" changes on it before you start giving them feedback. Or, wait a few days for things to settle down...

Brian M

[claus]

(Just posted this on Matt's blog - thought you all might be interested)

---------------------------------------------------------------------
What? Is bigdaddy .. I don't even have a word for it... But, as you move around the pages in the listings for a search the SERPS *changes* (!)

I'm just investigating a search for a site with some problems and the first time, the problems started at page 3 - after looking a few pages forth I returned to page three, and then the problem strated at page four. Now it's at page five - no, damn... page 14!

And before the SERPS only went to page 11 before supplementals kicked in. Matt, what is this? It seems to be alive?
---------------------------------------------------------------------

I've never seen anything like this. Either I happened to investigate a search while it was updating, live (!), or somethig else was happening there. I tell you, the SERPS moved and changed as I browsed them! No, I'm not drunk!

FYI it was a [site:example.com] search returning around 5,000 results on the DC: 66.249.93.104. A whole lot were duplicates, but as I said it was a site with problems.

Right this moment the "view supplemental results" message comes at page 22 - as I wrote above it started at page 11 (that's also where it is with Google.com, and 64.233.179.104). Double the amount of visible results while I'm surfing the SERPS?

--
Added:
Most likely it was just a coincidence, and I happened to search while new data was being added or something. Afaik, nobody else have reported this?

OTOH, if I was searching really hard for something, as opposed to troubleshooting, I sure would appreciate this behaviour. It only makes it hard to tell a client "look at page three" ;)

[Robert_Charlton]

...FYI it was a [site:example.com] search returning around 5,000 results on the DC: 66.249.93.104. A whole lot were duplicates, but as I said it was a site with problems.

Right this moment the "view supplemental results" message comes at page 22 - as I wrote above it started at page 11 (that's also where it is with Google.com, and 64.233.179.104). Double the amount of visible results while I'm surfing the SERPS?...

claus - This is only going to touch on one tiny aspect of your post, and probably not your main question. But you, and everyone else who didn't catch this passing comment on Matt's blog should know that 64.233.179.104 is no longer showing Bigdaddy.

To see current Bigdaddy, go to http://66.249.93.104/

Here's the thread on Matt's blog....

Bigdaddy on the move (http://www.mattcutts.com/blog/bigdaddy-on-the-move/)

From Matt's blog:
Executive summary: if you want to play with a Bigdaddy data center, hit 66.249.93.104 instead of 64.233.179.104.

Longer explanation on the full post.

[Robert_Charlton]

Here's a quick observation about the instability on Bigdaddy, which wasn't my intention when I started writing this post...

Last night I chanced to run a search on Google, for [open source radio]. The Google search (http://www.google.com/search?hl=en&q=open+source+radio&btnG=Google+Search) returned two pages for the site I was seeking, radioopensource.org... the default domain as #1, as well as index.php of that domain as #2. "Aha!" I thought... "canonical problem. I'll check this out on Bigdaddy," and so I did.

Last night, the Bigdaddy search (http://66.249.93.104/search?hl=en&q=open+source+radio&btnG=Google+Search) also returned two pages from radioopensource.org #1 and #2, but index.asp was not #2... it was another page. I was pleased to see that Google had fixed this.

I thought I'd check that again before posting, and this evening Bigdaddy does return index.asp as #2. Maybe this an indication that the canonical fixes are in flux... or at least that results have changed in a period of about 16 hours. Of course your results may vary if you check this.

The Radio Open Source site, I should mention, is blog style, so the home page always changing, as are the caches, and I'm not even going to attempt to think about how that might be affecting this particular result. I'm also assuming that this is something that Google sees as a problem and is trying to fix.

[highpr]

I'm very interested in this development and have read this entire thread and the supplemental links.

For those of us who are just getting up to speed on Big Daddy - please answer me this:

1. Will it effect my search rankings?

2. Why is this change even needed? (what's the purpose here?)

Thanks in advance - great thread!

[PhilC]

Yes it will affect rankings. All changes affect rankings - both for better and for worse - some go up, and some go down.

The changes are necessary because search engines continually try to improve. The Big Daddy changes are more fundamental than the fixes and filters that most updates consist of.

[ReSiever]

seems to be very quite around this subject at the moment. I'm expecting Google to be looking through all the feedback they got after being live for a few days...

[BradBristol]

Anyone else notice that Matt Cutts blog has vanished again from 66.249.93.104?

66.249.93.104 is currently not returing any results for mattcutts.com

[DayoUK]

Matts site has gone missing for the domain search on all DC not just the Big Daddy DC.

As ReSiever mentioned it has gone very quiet on the DC - not seeing much progress from the outside looking in.

[rustybrick]

I see it at http://66.249.93.104/search?q=site:mattcutts.com

[BradBristol]

Looks like Matt's site is bouncing in and out of the data centers.

Can you say "Canonicalization Issues"...


Wonder how long before he puts up a 301?

Take a look at Matt's *NEW* home page. http://mattcutts.com
Minimalization at its worst. :D

[SEOBrains]

I noticed Sunday some results showing were obviously Big Daddy, now today it seems like Big Daddy is live, not sure about all of Google DC's, but Google seems to be very much producing Big Daddy Results. :cool:
Love the results...

[strategicrankings]

there is something going on in the Google SERPs ?

noticed some major changes in rankings for a bunch of keywords i'm tracking and those changes seem to be propagating around the DCs, see the previous SERP's in fewer DC's.

PS : i checked it with the mcdar tool.

[Brian M]

I don't know if the Big Daddy upgrade is complete yet, since the 66.249.93.104 data center still shows red X's for images:

http://66.249.93.104/search?hl=en&lr=&q=captain+kirk&btnG=Search

Also, Matt Cutts has been very quiet on the subject lately, so they are probably still working out the bugs...

Brian M

[gehrlekrona]

I have a couple of new sites and one of them, a localized version, finally showed up in BigDaddy but my main site is still not showing up at all :(
If I do a STE search in google.com nonw of them are showing up. It has been like this for a week now and before that my localized site went in an out several times a day. If this is a bug it is a HUGE one and they don't seem to find it.
One reason, I believe, that my main site is not showing up is that Google for some reason think it is a duplicate even though it is not in the same language. Since it is a localized version the theme is the same but the content is different. I have tried several things to see if they really think it is a copy and I have finally changed/removed the localized version to see if it help the main site to be listed.
I am not sure of the hierachy of Goolges datacenters but my thinking was that BigDaddy was the top one but to me it seems more like "BUGDADDY" :eek:

[ogletree]

It is still showing on the same data centers it has for a while.

[exi]

It seems to me that the displaying of SERPs between the new Google "Big Daddy" and the actual Google are tensing everybody's nerves quite a lot. I was analyzing a client's website today and in a matter of 5 minutes the display of its indexed had radically changed. The pages indexed had lost about 75 % of all those indexed in Big Daddy 5 minutes earlier. I honestly don't know how to react to these abrupt changes, much less how to explain this to my clients, as you can imagine. For instance, I search a website on the normal Google with site:website and it displays 500 pages. Then in the same minute I go to Big Daddy (http://66.249.93.104/) and perform the same search. But surprise, not is displaying 45000 pages and these ones are well indexed with the right text in it and all, whereas the old Google was showing the results of my pages with accent problems as the website we're talking about is a french launguage site. When I checked the cache for the date of indexation, it was the same on the actual Google and on Big Daddy. Does anyone make some sense out of what is going on in Google? And the problem is that all those changes affect websites as we speak because their traffic is descending day by day with this hide-and-seek play that is never ending. When on earth is it going to function for good the new version without all these ups and downs? I suppose that Google too is losing big money with this situation, not only the rest of the Internet community. Is someone else living the same "dancing" with his / her clients' websites or own websites? I'd appreciate any feed back on this issue. Thank-you.

[PhilC]

Big Daddy is being rolled out across the datacenters at a rate of one datacenter per 7 to 10 days, so it will take a while.

[gehrlekrona]

There's a lot of good stuff on his site at mattcutts.com
He's also saying that it takes 7-10 days for each datacdenter and that are 3 of them displaying BigDaddy's result..... and for me it is good since I can see my pages ranked higher up than before....

[gomer]

For me, BigDaddy shows a higher number of indexed pages when doing site: but I believe my acutal page count is less than in non-BigDaddy dc's as I know there are pages that are not in the cache. (This would mean that the site: function is even less accurate than normal.)

I am hoping these fluctations in page counts (which are affecting traffic) in a big way will settle down once the BigDaddy 'migration' is over.

[donelson]

We are seeing a big difference on Google.co.uk for "Pages from the UK", and for other national googles' "Pages from <nation>"

Even though we are based in the UK, and our hosts are in the UK, and one of our sites is about St Pauls Cathedral IN the UK, it has been dropped from google.co.uk "Pages from the UK" search.

Anyone else seeing "national" searches messed up?

[strategicrankings]

our hosts are in the UK

Don't see the relationship between the location of the host and the SERPs. :confused:

[outkast]

site: returns 56,000 on 64.233.161.99 and returns 21,000 on Big Daddy

I dont think I like Daddy newmore :(

[donelson]

Don't see the relationship between the location of the host and the SERPs. :confused:Go to google.co.uk or google.ca or google.co.in

You will see an option for "Search -- only pages in the XYZ", where XYZ is the local country.

We are frustrated because for "Search -- pages from the UK" at google.co.uk, our pages were listed well, are based in the UK, hosted in the UK, and about the UK --- and on last Monday 6 Feb, they suddenly disappeared from local country SERPs for the UK.

Their listings for "Search -- the web" have not changed. Only the local country SERPs.

If anyone knows any other reason why Only our Local SERPs have changed in the UK, please tell us! Thanks.

[mistera]

Can anyone look at my site under www.abcmodelsport.net and give me some feedback on ways of improving it.

Its gone up quite recently.

your help will be of great value. the more feedback the better.

regards

mistera

[mistera]

Hi guys,

I am quite new to this and was hoping if any of you guys could help me with my site. www.abcmodelsport.net. i've just got it live and added much more content. mod rewrite has been done, etc.. i am looking for more tips and improvements. Anything as my designers are still working on it and i have the chance to get everything done on it now.

your help will be greatly appreciated.

thanks

[Dock29]

If site 1 is cross-linked to site 2 and site 2 is engaging in the practive of duplicate content for the sake of enhancing search engine visibility, can site 1 be impacted negatively by this cross linking? (thoughts)?

Thanks,
CB

[aff_dan]

Hi dannysullivan,

I have an important question. I hope to reply me.
My site is indexed, but I saw in Google search results from 47th page results are only LINKS to my site. WHY??? :(

Awaiting reply from you, or all

Dan

[SEOBrains]

Many of you may have noticed major flux in the Google Data centers starting on the 9th of march and continuing today.

It appears that Big Daddy may be on hold for now and many European Google results have switched back from Big Daddy to Jagger or pre Jagger.

I have identified the following as "old" ranking data-centers

216.239.53.99
216.239.57.99
216.239.59.99
66.102.11.99
66.102.9.99
66.102.7.99
64.233.167.99
64.233.167.104
216.239.63.104
216.239.57.104
216.239.53.104
66.102.141.104
66.102.9.104
66.102.7.104
216.239.58.105
216.239.57.147
66.102.7.147
64.233.167.147

And these are new "Big Daddy" data-centers

64.233.161.99
64.233.161.104
64.233.161.105
64.233.161.147
64.233.171.99
64.233.171.104
64.233.171.105
64.233.171.147
64.223.179.99
64.233.179.104
64.223.183.99
64.223.183.104
64.233.185.104
64.233.187.104
66.249.93.104
216.239.37.99
216.239.37.104
216.239.39.99
216.239.39.104

Just from today's research, there may be more or less but it looks like for some reason big daddy is on hold, and some data-centers are showing pretty old results.

Why?

Ask Matt Cutts?

[roiannecox]

My website has been doing well (#1 on Google) up until March 6-8. As of this morning depending on which datacenter you look at I am between #10 -18.

Should I just wait this out, do we know if this is a temporary thing or should I start tweaking my site?

Any ideas?

Roianne

www.clarkcounty4sale.net

[FeldBum]

Yesterday, I had top 10 or top 20 placements for all keywords to one of my clients' sites. Now I'm buried on every server I check.

:(

[AussieWebmaster]

Yesterday, I had top 10 or top 20 placements for all keywords to one of my clients' sites. Now I'm buried on every server I check.

:(

We have noticed a fluctuation in results for link:domain.com - the totals are changing a lot... up and down.... so I guess they are juggling datacenter results today.

[rockcoastmedia]

I want to see how does my site rank if I do a search in Boston, and how will my site rank if I do a search in Paris. Does anyone, know of a specific way to find out this information? For example are there actaul IP addresses that would direct me to get results from a French data Center? I am in Boston, so I can get those just by going on Google and checking.

I appriciate any help out there.

[simons1321]

are there any new data centers out? recently within the past month?

I'm seeing results that I cant reproduce in any known data center, mcdar, etc.
And no, i dont have personalized search on nor am i signed into a google account. Ive verified the results on multiple computers in different parts of the US.

The results pop up about 50% of the time and the other 50% of the time they revert back to BD.

[AussieWebmaster]

Simon you will start all sorts of research and speculation with that post....
Google is having a company gathering in MountainView this week... maybe they are testing something.

[SEOBrains]

Simon, have your results settled down?

Curious, I am seeing big jumps in traffic from Google but we had some TV time in Germany this week so it may just be that.

[SEOBrains]

This answers many of the questions here...

Matt Said...
"Heh. I wrote this hugely long post, so I pulled a Googler aside and asked “Dan, what do you think of this post?” And after a few helpful comments he said something like, “And, um, you may want to include a paragraph of understandable English at the top.” :)

Fair enough. Some people don’t want to read the whole mind-numbingly long post while their eyes glaze over. For those people, my short summary would be two-fold. First, I believe the crawl/index team certainly has enough machines to do its job, and we definitely aren’t dropping documents because we’re “out of space.” The second point is that we continue to listen to webmaster feedback to improve our search. We’ve addressed the issues that we’ve seen, but we continue to read through the feedback to look for other ways that we could improve.

People have been asking for more details on “pages dropping from the index” so I thought I’d write down a brain dump of everything I knew about, to have it all in one place. Bear in mind that this is my best recollection, so I’m not claiming that it’s perfect."

Read More (http://www.mattcutts.com/blog/indexing-timeline/)

[Nomadic]

Okay I have a question re: relevancy. When I do a search for a keyword such as "pigeon forge cabins" I am seeing some very irrelevant results show up in the first few pages.

An example would be a German hotels site that gets listed in the results only because it has one burried link going to a Pigeon Forge cabin rental site. When I say burried I mean the link is on the 13th of 20 links pages (the kind of pages that contain nothing but dozens of loosely-related travel sites). That one link is absolutely that site's only relevance to the keyword query "pigeon forge cabins". I am seeing this for many of the keywords we seek out.

I know Matt Cutts says he doesn't see broad relevancy issues in Big Daddy, but in this particular industry something is definitely arry in the SERPs.

[hk997]

what's the news today, somebody update please, after all the changes, is it back to usual, or it's been changed for ever!

[SEO1]

Nomadic

There is the relevancy part that factors into it and there is the competitiveness level of the keyword term so "pigeon forge cabins" would only require a decent anchor text link of some age.

You could build a page and post a few anchor text links from blogger.com, msn spaces, yahoo 360, and perhaps a press release on openpr.com and a few decent directories.. and should hit Googles front page with some patience on your part....

Just things as I see them....

[SEO1]

what's the news today, somebody update please, after all the changes, is it back to usual, or it's been changed for ever!

Today is the first day of the rest of the search engines life.

Today is the Tomorrow you dreamed of Yesterday....

I could go on but suffice it to say change is constant, what is here today is gone tomorrow.

[offshelfnet]

[QUOTE=ReSiever]Hello all,

At this very moment, i'm seeing results at http://64.233.179.104 that got spidered only by the Mozilla Google Bot. The Mozilla bot is known not te be responsible for Google's main index, and my guts always told me it was also checking duplicate content, cause it got my pages out of Google's normal index.

------------------

Agree on Mozilla Google Bot suspicons , it also noted that every time I ad content pages it all get listed almost immidiatly, but after the bot goes through a number of them gets immidiatly delisted of google results page for the reason od duplication of content

[offshelfnet]

I want to see how does my site rank if I do a search in Boston, and how will my site rank if I do a search in Paris.

I appriciate any help out there.

I can tell you how your site ranks in Canada / Toronto / Montreal if you are interested , but yes actualy I have used the tool that tell you PR and results positioning by 20 google data centers. but unfortunatly the address has long been gone , cant find it again. If you be so lucky please forward it to me as well.