shaunm - 7:52 am on May 6, 2013 (gmt 0)
Thank you, again :-)
Thank you! I must admit it was informative for me. And I hope you'll answer my following questions as well :-)
First: If you're using a CMS, your own server will always record a 200:
So, this cannot happen with hosting the website in some other server right?
Second: The blank page may mean that the CMS isn't doing its thing, so bad parameters lead to an empty page accompanied by a 200 header.
I am sorry that I was wrong. It's neither a blank page nor a custom 404 error page. But a page with with all the top menus, navigation which says 'Error - Page Not Found
You are seeing this error because you tried to access a web page that does not exist' but still the server response is 200 when checked with seobooks server response tool or any other server response checker tools.
Third: In the slightly better alternative, the CMS meant to return a 404 response, but by the time it figured out that the parameters were bad, it had already output some content-- maybe a <head> section
Can this actually happen? I mean it's not going to take a minute or an hour, everything performed within 3 to 5 secs right? Can this occur within that time frame?
maybe just a humble line break-- so it was no longer able to send the 404.
What is a link break?
Final and very eagerly question
Once google discovers that requesting absolutely anything results in a 200
How does Google actually discovers that requesting anything returns in a 200 for a website? I mean it only follows the internal links through its crawling process right? And those any pages that result in a 200 are not even getting crawled or indexed for that matter. Then how can Google do it?
Thanks for all your help :-)