http://72.14.207.104/ still shows low numbers for me. INV, does your domain contain any hyphens? This could just be the same old problem revisited, on some d/c's. There was a problem with hyphenated domains about the time I launched this site... but I thought it was fixed.
http://72.14.207.104 is still a problem. However, the other ones are back to normal. I am still not sure whats the deal on this dc and what tests are being run. I dont have any Hyphens. Just to clear that up.
216.239.57.99 216.239.57.104 216.239.53.104 216.239.53.99 http://66.102.7.104 http://66.102.7.99 These are the godaddy testers. I still use them though as they seem to update quickest in the past.
The decreased number d/c's may very well be correct for site: searches... http://forums.digitalpoint.com/showthread.php?t=118261 discusses a site that is pretty new, and is a good one to study across d/c's. You can tell if you are using one of these d/c's if the main page comes up first in the results for a site: search. But if we accept those d/c's as good, there are either a bunch of pages missing from the site:search or allinurl: is broken... and it may well be the latter.
About 60 seconds into this video: http://video.google.com/videoplay?docid=-3494613828170903728 Matt Cutts mentions two changes to site: command that will make the count more accurate. I guess that is what we are looking at, some kind of fix. I hope the site: database is just smaller for now, and the actual number of indexed pages is closer to an allinurl: search...
The issue bounced back again. It seems some changes are still in process. Here are some of the datacenters in effect. http://216.239.57.104 http://216.239.53.104 http://216.239.53.99 http://66.102.7.104 http://66.102.7.99 http://216.239.53.107 ----- http://216.239.57.99 is still working really good. Seems to be indexing leading along side the 66.102's 66.102.11.99 66.102.9.99 66.102.9.104 66.102.11.104
I think they are out to make fools of us, INV. http://216.239.57.99/ is now part of the first set... It is definitely spreading.
I definately hope this thing isn't over yet. But Cutts seems pretty sure of himself when he suggest that it might be over-optimization causing it. Funny thing is, a couple seconds ago, google couldn't find mattcutts.com....when I tried. How ironic is that?
This would be a perfect way to get the folks at Google to listen that something don't smell right with the latest updates. Has someone thought of using their coop weight to promote Matt's site? (bad Ken, such evil thoughts )
Your right. It seems it joined the dark side. Just I thought I would mention this happened to all the larger websites I have. I dont use the co-op, I also dont over optimise and know the limits to keep it completly clean. I am hoping its tweaking or something because this isnt a correct way google is display results, google just messed up its not the websites. I dont even listen to Matt Cutt's because most of the things he says are washed up. He blends the real truth of what does work with what google wishes you would do.
It's one thing if Google is just changing things around, it's a whole another thing when they blame us for it. That's misdirection, and that's evil.
ascensions I did this accidentally one day site:domain (without the .com) and realized it's a great way to find scrapers. It will list everyone using your domain (scrapers often don't link to your site so you can't find them with inurl). I found one that had the domain (without the dot com) in a header tag pretending to be another site. It will also bring up sites with your domain on other tlds, i.e., yourdomain.net, yourdomain.uk etc. It also brings up sites with your title in their title which can be very damaging depending on how many pages they do this on or if they repeat it on the page too many times, as they are now competiting with your main keywords. Check carefully any site ranking above your own site in this search.
http://216.239.37.104/search?nl=en&num=10&query=site:www.digitalpoint.com http://216.239.59.99/search?nl=en&num=10&query=site:www.digitalpoint.com The first one has 184,000 results. The second one has 623,000. This is a HUGE MESS! Almost every site has been effected and you can see DP has got a huge hit too.
I'm not sure whats happened to my site. The number of indexed pages in the API has crashed from 105,000 to 1 When doing a site:domain.ext query it returns 105,000 indexed pages, the same number the API used to report. However the indexed pages in the API have now dropped to 1. Any ideas whats happened? I did have an error in my google sitemap (I deleted it by accident and it failed loading) and wondered if this caused the cockup with API indexed pages. I am not 100% sure when this all happened, but it was only noticed in the last few days.
Just used a datacenter checker, and it appears most datacenters now show 105k indexed but most are supplemental. Only 6 proper pages are shown in the results. However it seems now that all of the indexed results have a cache date of Auguest 2005 so are a year old. :/