Hi everyone
We're looking into the reported issues -- thanks for your patience!
Keep the reports coming!
JLH, I imagine your blog has a special button style defined. If you
could put the code back on, I'm sure we can work out some CSS to make
the button look more buttony :)
Is URL that inspires the great-googley suggested URL (nice!).
The "Google Search" is very much un-googley which seems odd for a
company who probably is into branding a bit. Looks the same in
firefox and IE, except that it actually works in firefox, and in IE is
creates a whole new url that also is a 404 after clicking the gray
area that suppose to be a button: http://www.jlh-design.com/latest-coments/?q=latest+comments
> Hi everyone
> We're looking into the reported issues -- thanks for your patience!
> Keep the reports coming!
> JLH, I imagine your blog has a special button style defined. If you
> could put the code back on, I'm sure we can work out some CSS to make
> the button look more buttony :)
Hi JLH
Firebug helps you to find and try out CSS really easily -- you could
for instance try the following CSS code (you can place it in the
stylesheet or just within the widget snippet):
The missing borders are caused by your style.css, line 16:
* {margin: 0; padding: 0; border: 0; list-style: none;}
Without "border: 0" it will show the borders properly (though it also
changes other elements within your design, so I wouldn't remove it
before making a backup :-)).
Hope it helps!
John
PS The engineers are looking at that IE issue too.
> Hi JLH
> Firebug helps you to find and try out CSS really easily -- you could
> for instance try the following CSS code (you can place it in the
> stylesheet or just within the widget snippet):
> The missing borders are caused by your style.css, line 16:
> * {margin: 0; padding: 0; border: 0; list-style: none;}
> Without "border: 0" it will show the borders properly (though it also
> changes other elements within your design, so I wouldn't remove it
> before making a backup :-)).
> Hope it helps!
> John
> PS The engineers are looking at that IE issue too.
The CSS controls are provided to you so that you can customize the
appearance of the information that Google supplies through the
JavaScript so that they meld with your site's overall look and
appearance. The page in the Webmaster Tools console that generates
the code includes a link to documentation for adjusting them, but it's
strictly optional. The default settings are pretty benign and
shouldn't cause any problems. Note that the article on
seoroundtable.com has been updated to report that the problems they
encountered were due to the server not returning a 404 response code.
I've put this code on three sites now across two Apache-based servers
with an ErrorDocument setting in the .htaccess file which points at
custom a 404 page on each of them. That seems to be the key.
My server does return a 404 and uses a default error page called
404.shtml .
The way it actually works is to show the content of the 404.shtml page
while preserving the original url that was requested and returning a
404 response code.
I believe this is why this script isn't working for me properly.
> The CSS controls are provided to you so that you can customize the
> appearance of the information that Google supplies through the
> JavaScript so that they meld with your site's overall look and
> appearance. The page in the Webmaster Tools console that generates
> the code includes a link to documentation for adjusting them, but it's
> strictly optional. The default settings are pretty benign and
> shouldn't cause any problems. Note that the article on
> seoroundtable.com has been updated to report that the problems they
> encountered were due to the server not returning a 404 response code.
> I've put this code on three sites now across two Apache-based servers
> with an ErrorDocument setting in the .htaccess file which points at
> custom a 404 page on each of them. That seems to be the key.
> My server does return a 404 and uses a default error page called
> 404.shtml .
> The way it actually works is to show the content of the 404.shtml page
> while preserving the original url that was requested and returning a
> 404 response code.
> I believe this is why this script isn't working for me properly.
> I will try to override this and see how it goes.
> On Aug 20, 8:57 pm, RainboRick wrote:
> > The CSS controls are provided to you so that you can customize the
> > appearance of the information that Google supplies through the
> > JavaScript so that they meld with your site's overall look and
> > appearance. The page in the Webmaster Tools console that generates
> > the code includes a link to documentation for adjusting them, but it's
> > strictly optional. The default settings are pretty benign and
> > shouldn't cause any problems. Note that the article on
> > seoroundtable.com has been updated to report that the problems they
> > encountered were due to the server not returning a 404 response code.
> > I've put this code on three sites now across two Apache-based servers
> > with an ErrorDocument setting in the .htaccess file which points at
> > custom a 404 page on each of them. That seems to be the key.- Hide quoted text -
Hi everyone
It looks like the engineers here were able to tweak some things to
improve how it works in some browsers, yay! While returning a proper
404 result code is really, really, REALLY important for file-not-found
pages, it's not required for this widget (but if I catch you not
returning a 404 I'll... uhm... be unhappy). You can verify the 404
code by using one of the many server header checkers out there.
Also, keep in mind that if you're using your .htaccess file to point
to the 404 page, accessing the 404 page directly might not return a
404 code - that is normal. However, if you access a URL that doesn't
exist, you should see the proper result code. It can be confusing at
first :-).
This looks very promising. I will have to give it a try. Is there a
possibility that in the near future Google can come up with a snippet
of code for websites that cannot be verified by a meta tag or html
page? I have a blog that is with quickblogcast from GoDaddy (and
millions of others have this same template based blog format) and I
cannot get it to verify for Google webmaster tools. Just thought that
maybe a snippet of code that could be installed in the side bar or
somthing similar would do the job and make it so virtually everyone
could use Google webmaster tools for their websites. :)
> Hi everyone
> It looks like the engineers here were able to tweak some things to
> improve how it works in some browsers, yay! While returning a proper
> 404 result code is really, really, REALLY important for file-not-found
> pages, it's not required for this widget (but if I catch you not
> returning a 404 I'll... uhm... be unhappy). You can verify the 404
> code by using one of the many server header checkers out there.
> Also, keep in mind that if you're using your .htaccess file to point
> to the 404 page, accessing the 404 page directly might not return a
> 404 code - that is normal. However, if you access a URL that doesn't
> exist, you should see the proper result code. It can be confusing at
> first :-).
Hi bluegill,
You do not need to verify site ownership in
Google Webmaster Tools for the
Google error 404 widget.
Add your site URL to Google Webmaster Tools,
go to Tools, and from there to
Enhance 404 pages
and follow the instructions.
You do not need to verify site ownership for that.
> This looks very promising. I will have to give it a try. Is there a
> possibility that in the near future Google can come up with a snippet
> of code for websites that cannot be verified by a meta tag or html
> page? I have a blog that is with quickblogcast from GoDaddy (and
> millions of others have this same template based blog format) and I
> cannot get it to verify for Google webmaster tools. Just thought that
> maybe a snippet of code that could be installed in the side bar or
> somthing similar would do the job and make it so virtually everyone
> could use Google webmaster tools for their websites. :)
JLH indirectly asked how we find the HTML sitemap pages in his blog
post at http://www.jlh-design.com/2008/08/sitemap/ so I'd like to make
a short comment on that. It's actually pretty simple, we just look for
a URL that looks like an HTML sitemap page, something like "/
sitemap.htm" or just "/sitemap" (etc). So if you would like the widget
to point to your HTML sitemap page, you can either make sure that your
sitemap page is called "/sitemap.htm" (or similar) or, this might be
even easier, just put the link on your 404 page yourself :-).
Also, we've seen that some people have preferred to hide the search
box for whatever reason. You're certainly free to do that, if you
want. The simplest way to do that is just to add the following to your
CSS code in the "style" section:
#goog-wm form {display:none;}
If you decide to do that, I would recommend using either a search box
for your site below the widget, using a Google Custom Search Engine
( http://www.google.com/cse ) or even Google Site Search (
http://www.google.com/sitesearch/ ) instead. The setup for a CSE &
Site Search gives you a lot of options, it might be worth trying out
in any case. Don't leave your visitors hanging without a way to find
what they want on your site!
My page works, sort of, depending on what you type in. If you add or
subtract a letter of an internal URL it works, but for more generic
errors it will give nothing at all?
Also I read the section on adjusting the CSS but could not seem to be
able to insert a space between the seatch box and the button and or
just make it look like my custom search which is very nice looking on
my page.
To add a space between the search box and the button you either add
some margin-top to the button or margin-bottom to the text input, all
under the id what applies.
> My page works, sort of, depending on what you type in. If you add or
> subtract a letter of an internal URL it works, but for more generic
> errors it will give nothing at all?
> Also I read the section on adjusting the CSS but could not seem to be
> able to insert a space between the seatch box and the button and or
> just make it look like my custom search which is very nice looking on
> my page.
This is fantastic! I just found it in my Webmaster Tools and installed
it on my website. Thank you so much for continuing to increase the
offerings that you provide users with. I really love Google!
> Feel free to post your questions & comments here -- and of course
> links to 404 pages which you have created that use this widget! I hope
> I'm not the only one who likes finding pages that don't exist :-).
> This is fantastic! I just found it in my Webmaster Tools and installed
> it on my website. Thank you so much for continuing to increase the
> offerings that you provide users with. I really love Google!
> > Feel free to post your questions & comments here -- and of course
> > links to 404 pages which you have created that use this widget! I hope
> > I'm not the only one who likes finding pages that don't exist :-).
Hi Webado,
Thank you so much for taking a look...I removed the images because I
think they could be misleading. Hopefully the page looks better now.
Thank you again, I really appreciate your feedback.
> > This is fantastic! I just found it in my Webmaster Tools and installed
> > it on my website. Thank you so much for continuing to increase the
> > offerings that you provide users with. I really love Google!
> > > Feel free to post your questions & comments here -- and of course
> > > links to 404 pages which you have created that use this widget! I hope
> > > I'm not the only one who likes finding pages that don't exist :-).
> Hi Webado,
> Thank you so much for taking a look...I removed the images because I
> think they could be misleading. Hopefully the page looks better now.
> Thank you again, I really appreciate your feedback.
> > > This is fantastic! I just found it in my Webmaster Tools and installed
> > > it on my website. Thank you so much for continuing to increase the
> > > offerings that you provide users with. I really love Google!
> > > > Feel free to post your questions & comments here -- and of course
> > > > links to 404 pages which you have created that use this widget! I hope
> > > > I'm not the only one who likes finding pages that don't exist :-).
> > Hi Webado,
> > Thank you so much for taking a look...I removed the images because I
> > think they could be misleading. Hopefully the page looks better now.
> > Thank you again, I really appreciate your feedback.
> > > > This is fantastic! I just found it in my Webmaster Tools and installed
> > > > it on my website. Thank you so much for continuing to increase the
> > > > offerings that you provide users with. I really love Google!
> > > > > Feel free to post your questions & comments here -- and of course
> > > > > links to 404 pages which you have created that use this widget! I hope
> > > > > I'm not the only one who likes finding pages that don't exist :-).
I think it's because you have a form inside a form. Or rather the
Google 404 error script which produces a form is located within the
scope of another form you have on your page.
Or so it seems to me from looking at the source code.
> Really? You can't see it? I just checked it and it's there.
> Wait, I just checked in IE7 and it's missing but it works fine in
> FireFox. I wonder why it doesn't work in IE?
> On Aug 24, 6:38 pm, webado wrote:
> > OK, so where's the search box?
> > LOL
> > On Aug 24, 5:09 pm, kandi111777 wrote:
> > > Hi Webado,
> > > Thank you so much for taking a look...I removed the images because I
> > > think they could be misleading. Hopefully the page looks better now.
> > > Thank you again, I really appreciate your feedback.
> > > > > This is fantastic! I just found it in my Webmaster Tools and installed
> > > > > it on my website. Thank you so much for continuing to increase the
> > > > > offerings that you provide users with. I really love Google!
> > > > > > Feel free to post your questions & comments here -- and of course
> > > > > > links to 404 pages which you have created that use this widget! I hope
> > > > > > I'm not the only one who likes finding pages that don't exist :-).
> > > > > > John- Hide quoted text -
> > > > > - Show quoted text -- Hide quoted text -
> Really? You can't see it? I just checked it and it's there.
> Wait, I just checked in IE7 and it's missing but it works fine in
> FireFox. I wonder why it doesn't work in IE?
> On Aug 24, 6:38 pm, webado wrote:
> > OK, so where's the search box?
> > LOL
> > On Aug 24, 5:09 pm, kandi111777 wrote:
> > > Hi Webado,
> > > Thank you so much for taking a look...I removed the images because I
> > > think they could be misleading. Hopefully the page looks better now.
> > > Thank you again, I really appreciate your feedback.
> > > > > This is fantastic! I just found it in my Webmaster Tools and installed
> > > > > it on my website. Thank you so much for continuing to increase the
> > > > > offerings that you provide users with. I really love Google!
> > > > > > Feel free to post your questions & comments here -- and of course
> > > > > > links to 404 pages which you have created that use this widget! I hope
> > > > > > I'm not the only one who likes finding pages that don't exist :-).
> > > > > > John- Hide quoted text -
> > > > > - Show quoted text -- Hide quoted text -
I seem to be having some problems with getting my site index once
again. It was once index at 13000 pages and now it only has 4000.
www.medchoiceny.com. Can you tell me what is going wrong with my site?
> I seem to be having some problems with getting my site index once
> again. It was once index at 13000 pages and now it only has 4000.www.medchoiceny.com. Can you tell me what is going wrong with my site?
It looks like you have a "form" element across your complete page.
This is most likely confusing IE as our JavaScript also uses a "form"
to let the user search (and nested forms are by definition not
allowed, meaning browsers can interpret it differently). If possible,
I would suggest removing the "form" on your page as it doesn't seem to
be required there - or moving the JavaScript so that it is outside of
your form. I know this is sometimes complicated on ASP.NET (I fought
with it myself for many years :-)), but it should be possible
somehow.
Let me know how it goes. I think the team is looking at a solution for
these kinds of situations as well, but who knows, perhaps you're
faster than we are :-).