Support » Algemeen WordPress » Veel fouten als ik mijn blog valideer met W3C

  • Niet dat ik er veel vanaf weet, maar dit lijkt me allemaal niet erg goed, dit in het licht van SEO ?

    Validation Output: 31 Errors
    .	  document type does not allow element X here ✉ 
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 205, column 23: document type does not allow element "td" here </td>	<td id="sidebar">
    .	  end tag for X omitted, but OMITTAG NO was specified ✉ 
You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">". 

    		Line 7, column 56: end tag for "meta" omitted, but OMITTAG NO was specified 	<meta property="og:site_name" content="girls-on-film">
    		Line 8, column 75: end tag for "meta" omitted, but OMITTAG NO was specified 	<meta property="og:title" content="Welcome to Johny Willemyns photoblog">
    		Line 155, column 372: end tag for "div" omitted, but OMITTAG NO was specified …<a id="BingExtDefault.translate" class="BingExtSearchForLink">Translate</a></p>
    		Line 155, column 372: end tag for "div" omitted, but OMITTAG NO was specified …<a id="BingExtDefault.translate" class="BingExtSearchForLink">Translate</a></p>
    		Line 155, column 372: end tag for "div" omitted, but OMITTAG NO was specified …<a id="BingExtDefault.translate" class="BingExtSearchForLink">Translate</a></p>
    		Line 155, column 372: end tag for "div" omitted, but OMITTAG NO was specified …<a id="BingExtDefault.translate" class="BingExtSearchForLink">Translate</a></p>
    		Line 164, column 6: end tag for "p" omitted, but OMITTAG NO was specified </div>
    		Line 164, column 6: end tag for "p" omitted, but OMITTAG NO was specified </div>
    		Line 197, column 8: end tag for "td" omitted, but OMITTAG NO was specified 		</div><!-- .entry content -->
    		Line 197, column 8: end tag for "tr" omitted, but OMITTAG NO was specified 		</div><!-- .entry content -->
    		Line 197, column 8: end tag for "table" omitted, but OMITTAG NO was specified 		</div><!-- .entry content -->
    .	  ID X already defined ✉ 
An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element). 

    		Line 179, column 39: ID "BingExtDefault.about" already defined <div class="BingExtFooterLink"><a id="BingExtDefault.about">About Bing Highligh…
    .	  there is no attribute X ✉ 
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. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash. 

    		Line 7, column 17: there is no attribute "property" 	<meta property="og:site_name" content="girls-on-film">
    		Line 194, column 87: there is no attribute "data-count" …ass="twitter-share-button" data-count="none" data-via="willemyns"></a><script …
    		Line 194, column 103: there is no attribute "data-via" …re-button" data-count="none" data-via="willemyns"></a><script type="text/javas…
    .	  document type does not allow element X here; missing one of Y start-tag ✉ 
The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element. 
One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>"). 

    		Line 150, column 31: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag <p style="text-align: center;">
    		Line 151, column 31: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag <p style="text-align: center;">
    		Line 152, column 75: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag <div id="BingExt" style="left: 0px; top: 25px; opacity: 1; display: none;">
    		Line 156, column 34: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag <div class="BingExtBottomSection">
    		Line 194, column 11: document type does not allow element "center" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag <p><center><a href="http://twitter.com/share" class="twitter-share-button" data…
    .	  end tag for element X which is not open ✉ 
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 187, column 222: end tag for element "p" which is not open …" style="display: none;" title="Maps" for="BingExtButtonMapsRadio"></label></p>
    		Line 188, column 245: end tag for element "p" which is not open …lay: none;" title="Translations" for="BingExtButtonTranslateRadio"></label></p>
    		Line 189, column 255: end tag for element "p" which is not open … none;" title="Flight Status" for="BingExtButtonFlightStatusRadio"></label></p>
    		Line 205, column 5: end tag for element "td" which is not open </td>	<td id="sidebar">
    		Line 226, column 5: end tag for element "tr" which is not open </tr>
    		Line 227, column 8: end tag for element "table" which is not open </table>	<div id="copyright-footer" class="content-bg">
    		Line 233, column 6: end tag for element "div" which is not open </div><!-- #inner-wrap -->
    		Line 234, column 6: end tag for element "div" which is not open </div><!-- #main-wrap-inner -->
    		Line 235, column 6: end tag for element "div" which is not open </div><!-- #main-wrap-outer -->
    		Line 236, column 6: end tag for element "div" which is not open </div><!-- #outer-wrap-centered -->
7 reacties aan het bekijken - 1 tot 7 (van in totaal 7)
  • W3C gevalideerde code is iets waar we allemaal naar moeten streven, echter heeft dit niet een dusdanige impact op het gebied van SEO.

    Waar je rekening mee moet houden is, “kan Google je hele website crawlen”. Of is het zo dat de fouten Google hiervan verhinderen. Als ik zo naar de meldingen kijk dan is dit niet het geval.

    Net zoals de meeste dingen die meetellen in Google algoritme is het niet bekend wat de waarde van W3C is, er is nooit gezegd dat het niet meetelt maar ook niet dat het wel meetelt en zo ja, hoeveel dat het meetelt.

    kort maar krachtig,
    in het licht van SEO hoef je je er geen zorgen om te maken maar een W3C gevalideerde website is altijd fijner.

    Thread starter johny willemyns

    (@johnyw)

    Bedankt Roswell voor de duidelijke uitleg. Daar maak ik me daar (voorlopig)verder weinig druk om.
    Wat me wel dwarszit is de structuur. Ik datzelfde rapport kreeg ik daar deze opmerking over de outline en de heading tags:

    Document Outline

    Below is an outline for this document, automatically generated from the heading tags (<h1> through <h6>.)
    [h2] girls-on-film
    [h1] Welcome to my photoblog
    [h3] recent posts
    [h3] please visit these interesting sites
    If this does not look like a real outline, it is likely that the heading tags are not being used properly. (Headings should reflect the logical structure of the document; they should not be used simply to add emphasis, or to change the font size.)

    Spijtig genoeg heb ik er geen idee van waar ik dat kan aanpassen zodat het altijd automatisch zo blijft ?

    In je template file zijn de dynamische elementen van wordpress, die worden ingevuld naarmate jij gebruikt maakt van je blog, binnen headings tags geplaatst op een aparte wijze.

    Wat je zou moeten doen is om de huidige stijl te behouden,

    de H2 stijl aan de H1 geven, de H1 stijl aan de H2. H3 kan blijven zoals het nu is.
    Vervolgens moet je de template aanpassen en de H1 en H2 verwisselen.

    Alleen is het zo dat ik als ik naar de waardes kijk weet ik niet hoe de website is opgebouwd. Het gebeurt weleens dat templates een H1 meegeven aan het logo. In dat geval zou je de logo een H1 maken wat ook niet goed is.

    Dit zou namelijk betekenen dat op elke pagina de H1, de blog titel, het belangrijkste is.

    Hier moet je dus even rekening mee houden.

    🙂

    Thread starter johny willemyns

    (@johnyw)

    thx 🙂

    Thread starter johny willemyns

    (@johnyw)

    oh, ja, waar zie je dat, waar de waardes aan wat meegegeven worden?

    In de stylesheet, waarschijnlijk style.css. Waarschijnlijk staat er iets zoals;

    h1{
    font-size: 16px;
    }

    en dan moet je dus alles wat binnen {} voor H1 omwisselen met alles wat bij H2 staat.

    Fouten in je validatie zijn misschien niet slecht voor je SEO, maar geven wel vaak problemen bij weergave van je site binnen verschillende browsers op verschillende platformen. Toch wel een punt om aandacht aan te besteden.

7 reacties aan het bekijken - 1 tot 7 (van in totaal 7)
  • Het onderwerp ‘Veel fouten als ik mijn blog valideer met W3C’ is gesloten voor nieuwe reacties.