Comments on: Checking Page HTTP Headers

By: Frederick Pearce

Frederick Pearce — Fri, 02 Sep 2011 01:36:04 +0000

Good job, Ann. The information about title and keywords was most useful. I was surprised that 3- and 4 -word keyphrases were considered and didn’t like the results my page produced. Back to the drawing board!

Thanks for your insight.

Frederick

By: blu star web design services in tipperary, ireland

blu star web design services in tipperary, ireland — Mon, 11 Aug 2008 16:24:30 +0000

nice fireox add-on, it is often useful to know more about http header when debugging websites

By: Adam Audette

Adam Audette — Thu, 31 Jul 2008 16:47:18 +0000

Other good tools to check headers:

Charles (OS X): http://www.charlesproxy.com/
does some sweet stuff, acts as a proxy between the web and client capturing http requests

Wireshark: http://www.wireshark.org/
goes way deeper and acts as a complete network diagnostics tool

And of course my favorite of all, good old wget -S

By: Ann Smarty

Ann Smarty — Wed, 30 Jul 2008 12:30:33 +0000

@Raghavan, @g1smd : agreed, I also gave the link to the full list of status codes in the post and here it is also.

By: g1smd

g1smd — Tue, 29 Jul 2008 22:38:02 +0000

I think 307 and 410 also deserve a mention these days, and I’ll second the call for mentioning 302 and why it can be a bad thing to use.

By: Raghavan

Raghavan — Tue, 29 Jul 2008 17:26:10 +0000

@Ann,

would suggest 302 to the list that SEOs must often deal it shouldn’t be there. Also how abt customized 404 page?

By: Mercy

Mercy — Tue, 29 Jul 2008 13:00:21 +0000

Ann,

Simple but effective write up! The Firefox extension comes in handy. Thanks for sharing.