| Welcome to WebmasterWorld Guest from 188.8.131.52 |
register, free tools, login, search, pro membership, help, library, announcements, recent posts, open posts,
|Become a Pro Member|
|Strange w3c Validation problem... |
w3c validation problem
We've noticed a few of our websites drop out of Google in the last few weeks. After trying various methods of altering code we've also found the same sites are failing the W3C Validation tests.
They are getting a 500 Internal Server error on validation attempts. Any ideas welcomed.
Welcome to WebmasterWorld, simonlilly! Check out Marcia's excellent WebmasterWorld Welcome and Guide to the Basics [webmasterworld.com].
Can you see the page(s) over http? Is the 500 error on the validator site, or is it telling you that it is getting a 500 error from your site?
Thanks for the quick response. On an attempted validation of several sites we get the following message:
"I got the following unexpected response when trying to retrieve <http://ourwebsite/>:
500 Internal Server Error"
[edited by: simonlilly at 3:33 pm (utc) on Feb. 13, 2003]
You could try running a page or two through Sim Spider [searchengineworld.com] over on our sister site. Might give you some more to go on.
Also, having two <body> tags won't help. A spider might render both, or neither, or just one.
Hi simonlilly, we're glad to have you in the forum. However you may want to read the Terms of Service (link at the bottom of this page).
Dropping your url is un-cool around here. Don't post your url. A big no-no around here.
But talking about your issue is cool. In fact, it helps more people out with their own issues if we keep url's out of the picture. Also, site reviews are not allowed either, for the same reason.
You can click the "owner edit" link to the left of your message in order to remove your url.
Thanks for the guideline reminder! I must admit to posting the message in a bit of a rush...
We've sorted the problem now. It was a Detect Browser script we were using that was causing the validator to crash and burn!
Thanks for all your help and input.
If you're getting 500 errors, then it likely has nothing to do with your HTML. I'd check your server logs to see what is causing this fatal error. Do you see this error yourself?
All trademarks and copyrights held by respective owners. Member comments are owned by the poster.
WebmasterWorld is a Developer Shed Community owned by Jim Boykin.
© Webmaster World 1996-2014 all rights reserved