Forum Moderators: Robert Charlton & goodroi
>> Homepage Gone <<
You need to check very carefully that it isn't indexed at an alternative URL:
domain.com/
www.domain.com/
domain.com/index.html
www.domain.com/index.html
For a lot of sites, some other variant is indexed and it can take a bit of searching to discover.
.
Also, make sure you are very intimate with all of these searches:
site:domain.com
site:domain.com -inurl:www
site:www.domain.com
because there are some hidden surprises (nasty ones) to be found there for many sites.
.
Oh yes, I do most of my searches with &num=100 on the Google URL, and I always check both with &filter=0 and without it.
[edited by: Brett_Tabke at 1:29 pm (utc) on June 17, 2006]
Sorry to pour cold water on those two DC's but they include pages that have been a major no no in G's algo for years e.g. linking a network of sites together.
Unless this is a seismic shift in the Google algo, I can't see those DC's as the way forward.
linking a network of sites together.
this is fine post bd..actually more than fine...it works great....
For sites that show both www and non-www as being indexed, with both directly accessible, and both returning a "200 OK" status in the HTTP header, they need to get the site-wide 301 redirect in place to get this fixed.
At the moment, I see a number of www sites that show OK for a site:www.domain.com search, but when you search for site:domain.com -inurl:www you can still see some www pages in the SERPs (to be clear the -inurl:www search says to exclude all www pages from the results) and all these pages are old pages, all marked as Supplemntal Results and all with very old (about a year or so) cache dates.
I am seeing this all over the place.
.
It looks like yet another bug in the Supplemental Results.
inurl:www - returns www pages from the normal database.
-inurl:www - returns non-www pages from the normal database (if there are any), and any type of pages that it feels like from the Supplemental database.
.
[edited by: g1smd at 9:33 pm (utc) on June 17, 2006]
The -inurl:www search says to "EXCLUDE all www pages from the results".
That is the Google Bug. They do show them for some (many?) sites.
[edited by: g1smd at 9:37 pm (utc) on June 17, 2006]
The first time this happened there were reports of a hyphenated url bug. Once that was supposedly fixed, our pages were back.
Is there a new problem or is that one returned? Or is it just us?
Cheers,
Berry
However, it also affected searches for, say, an email address with hyphens in it. Do a search for someone@some-where and get a few results. Repeat the search, replacing the hyphen with a space, like someone@some where and suddenly you get a large pile of extra results, all of which are marked as Supplemental and all for pages that used to contain the actual email address that you were searching for. That bug is still there.
The main bug described earlier in this thread also affects hyphens - such that the -inurl:www command isn't being correctly interpreted by the bit of the system that returns Supplemental Results. You ask for everything except www pages to be shown in the results, and still get www pages if there are any that are Supplemental.
www.my-site.com
Hmmm.. So I am confused as to why our pages during that time went from 70k+ pages down to under 500 pages and then back to around 70k pages. Now, the number of pages is dropping again. From 70k pages to currently around 30k pages. I checked a lot of the pages that I know are missing and they show as de-indexed yet they still have their PR. It's a spitting image of what happened last time.
I am obviously being dense here but is this the same bug as before or is this a new bug? I take it from your response that others are also being de-indexed similarly. The pages came back before so hopefully they will again but I would like to zero in on the exact problem so I don't go and start making all sorts of changes to try to fix something on my site that isn't broken.
Maybe it's just part of the weekend insanity I am seeing all over the DC's.
It sounds like this new de-indexing doesn't have anything to do with that previous problem. Whole new can of worms. :/
[edited by: berrysharpie at 9:50 pm (utc) on June 17, 2006]
How does this look for everyone else?
That DC just now looks like it has the Copra results on it and is showing good results for me also.
Pete
At the same time that Google was talking about their "hyphenated-domain" bug, all these other things (many also seemingly to do with hyphens) were also happening.
Google has never acknowledged these other issues as being a part of the original bug, or as a separate bug. I am not even sure that the people that need to know about it, really do actually know about it.
Looks absolutely great for me but not a pre-update look. I was never doing that well ever. I.m in the top twenty on most search terms and even #10 in one search. Never, ever did that well before.
linking a network of sites together.this is fine post bd..actually more than fine...it works great....
It IS happening. The threads here have been deleted because they named sites and because those sites could belong to members. If you would like examples sticky me. I personally think these people should not be protected. They should be treated like horse thieves in the old west.
Just think about that for a moment.
What a huge waste of Google's resources in spidering and indexing all of that junk; and it is utter junk; not worthy of even a single electron being wasted on it.
[edited by: lawman at 7:12 pm (utc) on June 21, 2006]
This DC : [72.14.203.107...] , seems to show good results, and pre-update results where many sites magically re-appear.
How does this look for everyone else?
I how I wish that this DC comes live my newish site is ALIVE. I have been showing 16 pages at 2 levels for weeks and weeks now it is indexing 3 levels and I am hitting nearly 300 pages.... All good original content.
Here's hoping
72.14.203.x
72.14.205.x
72.14.207.x
72.14.209.x
72.14.211.x
72.14.215.x
72.14.217.x
72.14.219.x
72.14.221.x
72.14.223.x
72.14.235.x
72.14.253.x
where x = 99, 101, 102, 104, 107, 147, etc.
There may be others.
I did the only thing that made sense this saturday eve, had a party and got drunk. And guess what - any answers on the forum on my return?
Nope! Just people running about watching how the paint drips (and betting on how, why and where it's dripping).
My moneys on in two weeks time we'll have an answer (of sorts).
Need I say it - get a life (and get me one while youre out there) :}
What's that about.
...and that no-one at the 'plex seems to have noticed yet.
default firefox mac osx UK dc (can someone tell me what that is?)
Look at (or just hover over) the "cached" link to see the ip address of the data center.
Click on the tenth page ...... and theres no more!
Is there an "omitted results" link at the end?
I was wondering why I do less in adsense earnings on weekends even though some of the industries I promote are for weekend traffic.
Weekend : google datacenters salsa(dancing)+ Advertisers low bid(weekend)+Advertisers confused bid since conversions are erratic(salsa of google) = low earnings on adsense:(.
here: 216.239.59.104
my domain will probably disappear again just to put a smile on my face..
hehe
The Florida update killed me and my partner site. We were #1 for four major keywords, and getting tons & tons of traffic and sales.....
THEN NOVEMBER 2003 BOOM!
Completely out of the top 1000
After the last three+ years of cleaning up and linking and seo...finally when bigdaddy hit we were around the 100 orso mark. Much better, but nowhere near the money making pages.
Then about 4-5 days ago we started showing up in the top 10 for three of the keywords, and around 22-23 for the fourth (all highly searched terms---Results 1 - 10 of about 51,400,000 for blah blah).
Hopefulley whatever is going on sticks....
I also check the DC's and only the 64's are still showing the old "bad" #'s...
Would be nice to see that 3+ years of Seo'ing finally worked....LOL
