Thread: W3c compliance.

    #1
  1. No Profile Picture
    Contributing User
    SEO Chat Explorer (0 - 99 posts)

    Join Date
    Feb 2006
    Posts
    85
    Rep Power
    14

    Question W3c compliance.


    Hello,

    I'm trying to validate my site using their HTML validator (http://validator.w3.org/). Here's my website's settings:

    Server: Apache/1.3.27 (Unix) (Red-Hat/Linux) PHP/5.0.5
    Content-Type: text/html
    Encoding: iso-8859-1
    Doctype: HTML 4.01 Transitional

    I'm getting the following errors and can't figure out how to fix them:

    Below are the results of attempting to parse this document with an SGML parser.

    Error Line 15 column 46: document type does not allow element "META" here.
    <Meta name="GOOGLEBOT" content="INDEX, FOLLOW">
    The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).



    Error Line 16 column 176: document type does not allow element "META" here.
    ...il; example1; example2; example3">
    The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).



    Error Line 17 column 243: document type does not allow element "META" here.
    ...h Engine Marketing and Optimization.">
    The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).



    Error Line 19 column 42: document type does not allow element "META" here.
    <meta name="Author" content="example.com" />
    The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).



    Error Line 20 column 22: document type does not allow element "STYLE" here.
    <style type="text/css">
    The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).



    Error Line 55 column 22: document type does not allow element "STYLE" here.
    <style type="text/css">
    The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).



    Error Line 75 column 6: end tag for element "HEAD" which is not open.
    </head>
    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occured in a script section of your document, you should probably read this FAQ entry.



    Error Line 77 column 5: document type does not allow element "BODY" here.
    <body>
    The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).



    Error Line 83 column 26: there is no attribute "HEIGHT".
    <table width="800" height="496" border="1" align="center" cellpadding="0" cellsp
    You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

    This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

    How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute.



    Error Line 83 column 102: there is no attribute "BORDERCOLOR".
    ...ding="0" cellspacing="0" bordercolor="#000000">
    You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

    This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

    How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute.



    Error Line 92 column 12: an attribute specification must start with a name or name token.
    <embed="images/example.swf" ></embed>
    An attribute name (and some attribute values) must start with one of a restricted set of characters. This error usually indicates that you have failed to add a closing quotation mark on a previous attribute value (so the attribute value looks like the start of a new attribute) or have used an attribute that is not defined (usually a typo in a common attribute name).



    Error Line 92 column 12: element "EMBED" undefined.
    <embed="images/example.swf" ></embed>
    You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:

    incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case.



    Error Line 187 column 43: document type does not allow element "TD" here.
    ... <td height="16" bgcolor="#EAEAEA"><hr align="right" size="1" noshade="nos
    The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).



    Error Line 188 column 15: document type does not allow element "TR" here.
    <tr>
    The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).



    Error Line 211 column 15: end tag for "DIV" omitted, but its declaration does not permit this.
    </table>
    You forgot to close a tag, or
    you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.
    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.



    Info Line 184 column 48: start tag was here.
    <td height="16" bgcolor="#EAEAEA"><div align="right">
    Error Line 213 column 36: end tag for "DIV" omitted, but its declaration does not permit this.
    <!-- InstanceEndEditable --></td>
    You forgot to close a tag, or
    you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.
    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.



    Info Line 104 column 6: start tag was here.
    <div align="center">
    -------------------------------

    Any help is appreciated.

    Thanks!

  2. #2
  3. Super Moderator
    SEO Chat Mastermind (5000+ posts)

    Join Date
    Mar 2004
    Location
    Gloucester (South West UK).
    Posts
    6,533
    Rep Power
    3522
    You want this fixed for free?

    Seriously... if you follow the links displayed on the error document from W3C you will get an even more in-depth explanation of each error.

    The first half (or so) seem to indicate that you have either got no <head> tag or you have two </head> tags...

    There are many coding errors on there, that's for sure, but if you work through each one alongside your source code, it's really just a question of fixing them one at a time.

    Without the website name it's impossible to check that or to help you any further.
    ClickyB
    "The quality of the visitor is more important than the volume..." (Egol 22nd Feb 2008)
    [New to SEO/SeoChat?] [Canonical Problems?] [Forum Rules & Posting Guidelines]
  4. #3
  5. No Profile Picture
    Contributing User
    SEO Chat Adventurer (500 - 999 posts)

    Join Date
    Feb 2006
    Location
    Northern Territory, Australia
    Posts
    658
    Rep Power
    16
    Just keep working on it and you will get it to validate
  6. #4
  7. Mr. Goober Guy ;)
    SEO Chat Good Citizen (1000 - 1499 posts)

    Join Date
    Aug 2004
    Location
    Tampa, Florida
    Posts
    1,320
    Rep Power
    24
    Yeah, few times I wish they offered a "quick code repair" button...lol


    Originally Posted by ClickyB
    You want this fixed for free?

    Seriously... if you follow the links displayed on the error document from W3C you will get an even more in-depth explanation of each error.

    The first half (or so) seem to indicate that you have either got no <head> tag or you have two </head> tags...

    There are many coding errors on there, that's for sure, but if you work through each one alongside your source code, it's really just a question of fixing them one at a time.

    Without the website name it's impossible to check that or to help you any further.
    Cheerios!

    New to SEO? See the FAQ!

    My Disclaimer:
    Don't Listen To Me - I know nothing!
  8. #5
  9. No Profile Picture
    Contributing User
    SEO Chat Adventurer (500 - 999 posts)

    Join Date
    Feb 2006
    Location
    Northern Territory, Australia
    Posts
    658
    Rep Power
    16
    I find that w3c validation is way overrated.
    Whenever someone ponts out my site dosent validate i send them a link to google.
    They soon shutup.
  10. #6
  11. Contributing User
    SEO Chat Discoverer (100 - 499 posts)

    Join Date
    Sep 2005
    Posts
    143
    Rep Power
    14
    Does HTML 4.01 Transitional allow tags like:

    <Meta name="GOOGLEBOT" content="INDEX, FOLLOW">

    I've been writing HTML that conforms to XHTML 1.0 Strict for ages now, so this could be irrelevant, but in XHTML the meta tage would require a forward slash before the last angle bracket:

    <Meta name="GOOGLEBOT" content="INDEX, FOLLOW" />

    Also, is GOOGLEBOT a tag that the W3C recognise?

Similar Threads

  1. Deadline for E-Voting Compliance Nears (AP)
    By RSS_News_User in forum Technology News
    Replies: 0
    Last Post: Nov 30th, 2005, 05:02 PM
  2. Ensuring Software-License Compliance (NewsFactor)
    By RSS_News_User in forum Technology News
    Replies: 0
    Last Post: Nov 16th, 2005, 04:03 PM
  3. Replies: 0
    Last Post: Aug 29th, 2005, 11:02 AM
  4. Microsoft Makes Changes for EU Compliance (AP)
    By RSS_News_User in forum Technology News
    Replies: 0
    Last Post: Jun 6th, 2005, 08:01 AM
  5. Replies: 0
    Last Post: May 11th, 2005, 11:01 AM

IMN logo majestic logo threadwatch logo seochat tools logo