Tweet
W3-Validation Errors From Lightbox And Other Errors
Hello, Can someone help me?
My homepage has 75 errors and 5 warnings, see copy and paste below of a sample from W3 Validator. I tried to fix the errors myself as I was told it was from html that I had added, but I cannot see where it is from anything that I have physically coded. I checked all of my html boxes on this page that I added (only 4 or 5) and cannot find these errors in html that I have added.
I can see there are errors from what appears to be from Blue Voda sitebuilder that were added, such as the lightbox below.
Could it be that some of these errors may be the cause of our site losing google keyword postions on google search? Since moving to Vodahost on 2/19/2011 we have lost all keyword postion/rankings that were on pages 1-3 of googles search engine... We are losing sales big time. This is a problem that I must figure out. I have been 'pulling my hair out' trying to figure this out.. Thanks for any and all help!... Cindy
Validation Output: 76 Errors
My homepage has 75 errors and 5 warnings, see copy and paste below of a sample from W3 Validator. I tried to fix the errors myself as I was told it was from html that I had added, but I cannot see where it is from anything that I have physically coded. I checked all of my html boxes on this page that I added (only 4 or 5) and cannot find these errors in html that I have added.
I can see there are errors from what appears to be from Blue Voda sitebuilder that were added, such as the lightbox below.
Could it be that some of these errors may be the cause of our site losing google keyword postions on google search? Since moving to Vodahost on 2/19/2011 we have lost all keyword postion/rankings that were on pages 1-3 of googles search engine... We are losing sales big time. This is a problem that I must figure out. I have been 'pulling my hair out' trying to figure this out.. Thanks for any and all help!... Cindy
Validation Output: 76 Errors
Line 29, Column 75: NET-enabling start-tag requires SHORTTAG YES <link rel="stylesheet" href="lightbox.css" type="text/css" media="screen" />
The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HTML 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.
Line 71, Column 23: 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).- Line 74, Column 7: 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 occurred in a script section of your document, you should probably read this FAQ entry. - Line 75, Column 300: document type does not allow element "BODY" here …t-color:#FFFFFF;scrollbar-shadow-color:#A0A0A0;scrollbar-track-color:#C8C8C8;">✉
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). - Line 92, Column 4: 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).
Comment