> Your site responds very quickly to most request from the web sniffer
> tool that I am using.
> But when I select the googlebot-emulation, there is an indefinite
> wait.
> I suggest that you scrutinize your .htaccess file and any other script
> you can think of that is attempting to detect a googlebot and remove
> it.
> Robbo
> By the way I see that your .com has about 825,000 pages in the google
> indexed whereas your .co.uk has over 1.25 million.
> Is it possible this deindexing problem has been going on gradually for
> some time and it has now come to the fore because the Homepage is
> involved. Just a speculation.
> On Jan 15, 11:35 pm, ABE wrote:
> > Thanks JLH. I reported this to my operations team and they can see
> > that the server isn't directing the traffic correctly. So, they are
> > going to make some further changes.
> > Will you be able to check again as user agent once we can make some
> > changes to the servers?
Thanks JLH. I reported this to my operations team and they can see
that the server isn't directing the traffic correctly. So, they are
going to make some further changes.
Will you be able to check again as user agent once we can make some
changes to the servers?
Thanks JLH. I reported this to my operations team and they can see
that the server isn't directing the traffic correctly. So, they are
going to make some further changes.
Will you be able to check again as user agent once we can make some
changes to the servers?
We just set our DNS to bypass the server that was causing this
problem. It can take anywhere from 5min to 1 hour to update. Can one
of you guys check our site as a Google Agent in about an hour to see
if this worked or not?
We think we have narrowed down the problem to this one server causing
the time outs so now that we bypassed this Google Bot should be able
to access us fine.
Thanks guys... i dont know what we would have doe ewithout your help.
> We just set our DNS to bypass the server that was causing this
> problem. It can take anywhere from 5min to 1 hour to update. Can one
> of you guys check our site as a Google Agent in about an hour to see
> if this worked or not?
> We think we have narrowed down the problem to this one server causing
> the time outs so now that we bypassed this Google Bot should be able
> to access us fine.
> Thanks guys... i dont know what we would have doe ewithout your help.
Looks real good from here as well...hopefully that does it. The HTTPS
version is still being indexed, (1 hour ago), so we should see if that
fixed the normal HTTP version soon.
> > We just set our DNS to bypass the server that was causing this
> > problem. It can take anywhere from 5min to 1 hour to update. Can one
> > of you guys check our site as a Google Agent in about an hour to see
> > if this worked or not?
> > We think we have narrowed down the problem to this one server causing
> > the time outs so now that we bypassed this Google Bot should be able
> > to access us fine.
> > Thanks guys... i dont know what we would have doe ewithout your help.
It looks like the problem has been solved for now. Our sitemap is
being consumed and there are no more 404 errors being reported.
Now we need to get our homepage re-indexed. Do you guys know of a
quick way to get back into the index? Do you think we will be
penalized for the 404 errors?
Right now Google doesn't even think or homepage exists.
There's no penalty for 404s its just a normal part of the web.
Your home page should be indexed as most pages on the site link to it,
however they already have a copy of it indexed as the HTTPS version.
They may figure it out in some time, as they should, to inspire it you
could use a 301 redirect from the home page HTTPS version to the HTTP
version.
The problem with the site at the moment is that the use of relative
urls in the code, for example your internal links look like:
So if someone lands on your site, crawlers and humans alike, in the
https version, their next click will also be the HTTPS version. Using
absolute URLS with the HTTP in there, or at least a base reference
would get them off of the secure layer and back onto standard HTTP.
Right now, google has filtered out your regular homepage for the HTTPS
version, the 301 redirect will take care of that. Perhaps waiting and
hoping will also, but I wouldn't rely to heavily on it.
> It looks like the problem has been solved for now. Our sitemap is
> being consumed and there are no more 404 errors being reported.
> Now we need to get our homepage re-indexed. Do you guys know of a
> quick way to get back into the index? Do you think we will be
> penalized for the 404 errors?
> Right now Google doesn't even think or homepage exists.
It looks like the problem has been solved for now. Our sitemap is
being consumed and there are no more 404 errors being reported.
Now we need to get our homepage re-indexed. Do you guys know of a
quick way to get back into the index? Do you think we will be
penalized for the 404 errors?
Right now Google doesn't even think or homepage exists.
> It looks like the problem has been solved for now. Our sitemap is
> being consumed and there are no more 404 errors being reported.
> Now we need to get our homepage re-indexed. Do you guys know of a
> quick way to get back into the index? Do you think we will be
> penalized for the 404 errors?
> Right now Google doesn't even think or homepage exists.
It looks like the problem has been solved for now. Our sitemap is
being consumed and there are no more 404 errors being reported.
Now we need to get our homepage re-indexed. Do you guys know of a
quick way to get back into the index? Do you think we will be
penalized for the 404 errors?
Right now Google doesn't even think or homepage exists.