-
AuthorPosts
-
January 27, 2016 at 6:37 pm #573137
Info: The Content-Type was text/html. Using the HTML parser.
Info: Using the schema for HTML with SVG 1.1, MathML 3.0, RDFa 1.1, and ITS 2.0 support.
Warning: The banner role is unnecessary for element header.
From line 135, column 1; to line 135, column 420
_all’>↩↩ ↩<header id=’header’ class=’ header_color light_bg_color av_header_top av_logo_left av_main_nav_head…eader_border_disabled’ role=”banner” itemscope=”itemscope” itemtype=”https://schema.org/WPHeader” >↩↩<a i
Warning: Document uses the Unicode Private Use Area(s), which should not be used in publicly exchanged documents. (Charmod C073)
At line 137, column 72
data-av_icon=’’ data-av_icon
Warning: Element nav does not need a role attribute.
From line 145, column 355; to line 145, column 505
><nav class=’main_menu’ data-selectname=’Seite auswählen’ role=”navigation” itemscope=”itemscope” itemtype=”https://schema.org/SiteNavigationElement” ><div c
Warning: Section lacks heading. Consider using h2-h6 elements to add identifying headings to all sections.
From line 165, column 177; to line 165, column 281
us:0px; ‘><section class=”av_textblock_section” itemscope=”itemscope” itemtype=”https://schema.org/CreativeWork” ><div c
Warning: Section lacks heading. Consider using h2-h6 elements to add identifying headings to all sections.
From line 167, column 194; to line 167, column 298
us:0px; ‘><section class=”av_textblock_section” itemscope=”itemscope” itemtype=”https://schema.org/CreativeWork” ><div c
Warning: Section lacks heading. Consider using h2-h6 elements to add identifying headings to all sections.
From line 171, column 177; to line 171, column 281
us:0px; ‘><section class=”av_textblock_section” itemscope=”itemscope” itemtype=”https://schema.org/CreativeWork” ><div c
Warning: Section lacks heading. Consider using h2-h6 elements to add identifying headings to all sections.
From line 172, column 190; to line 172, column 294
us:0px; ‘><section class=”av_textblock_section” itemscope=”itemscope” itemtype=”https://schema.org/CreativeWork” ><div c
Error: The itemtype attribute must not be specified on elements that do not have an itemscope attribute specified.
From line 178, column 195; to line 178, column 313
us:0px; ‘><div class=’avia-video avia-video-4-3 avia-video-html5 ‘ itemprop=”video” itemtype=”https://schema.org/VideoObject” ><video
Warning: Section lacks heading. Consider using h2-h6 elements to add identifying headings to all sections.
From line 181, column 1; to line 181, column 105
iv></div>↩<section class=”av_textblock_section” itemscope=”itemscope” itemtype=”https://schema.org/CreativeWork” ><div c
Warning: Section lacks heading. Consider using h2-h6 elements to add identifying headings to all sections.
From line 184, column 1; to line 184, column 105
iv></div>↩<section class=”av_textblock_section” itemscope=”itemscope” itemtype=”https://schema.org/CreativeWork” ><div c
Warning: Section lacks heading. Consider using h2-h6 elements to add identifying headings to all sections.
From line 187, column 1; to line 187, column 105
iv></div>↩<section class=”av_textblock_section” itemscope=”itemscope” itemtype=”https://schema.org/CreativeWork” ><div c
Warning: Section lacks heading. Consider using h2-h6 elements to add identifying headings to all sections.
From line 190, column 1; to line 190, column 105
iv></div>↩<section class=”av_textblock_section” itemscope=”itemscope” itemtype=”https://schema.org/CreativeWork” ><div c
Error: No p element in scope but a p end tag seen.
From line 192, column 1; to line 192, column 4
on></div>↩</p>↩</div
Warning: Section lacks heading. Consider using h2-h6 elements to add identifying headings to all sections.
From line 208, column 1; to line 208, column 105
iv></div>↩<section class=”av_textblock_section” itemscope=”itemscope” itemtype=”https://schema.org/CreativeWork” ><div c
Warning: Section lacks heading. Consider using h2-h6 elements to add identifying headings to all sections.
From line 231, column 75; to line 231, column 131
ne_third’><section id=”text-2″ class=”widget clearfix widget_text”> <di
Warning: The contentinfo role is unnecessary for element footer.
From line 258, column 5; to line 258, column 142
↩↩ ↩ <footer class=’container_wrap socket_color’ id=’socket’ role=”contentinfo” itemscope=”itemscope” itemtype=”https://schema.org/WPFooter” >↩
Warning: Element nav does not need a role attribute.
From line 263, column 1190; to line 263, column 1312
<nav class=’sub_menu_socket’ role=”navigation” itemscope=”itemscope” itemtype=”https://schema.org/SiteNavigationElement” ><div cJanuary 27, 2016 at 9:31 pm #573272Hey DerNeumi!
Can you please explain us your question and the issue you are having?
Best regards,
BasilisJanuary 28, 2016 at 10:00 pm #574123wie bekomme ich diese Fehler weg, denn das ist nicht gut für Google Seo
January 31, 2016 at 11:20 am #575230Hey!
For the first error you could try disabling schema tags in Enfold theme options and for the second one make sure there’s no extra space in your text block paragraphs.
Cheers!
JosueFebruary 16, 2016 at 7:50 pm #584342ich habe die Schema tags deaktiviert. die Fehler sind nicht weg.
der andere Fehler ist okFebruary 16, 2016 at 9:39 pm #584363Hi!
Reported the ticket to our german speaking support, so they can help you out.
Cheers!
BasilisFebruary 17, 2016 at 1:53 pm #584710Hi!
can you explain further please? where are you seeing those error messages? In backend? frontend? If it’s in backend please provide us admin access, so we can see it.
Best regards,
AndyFebruary 17, 2016 at 5:24 pm #584854Answer Private Content
February 18, 2016 at 10:51 am #585276Hey!
any advanced WordPress theme would have such errors. If you don’t want any errors from such a validator you would need to use a very basic (standard) WordPress theme. You can try to deactivate all plugins, to get less errors.
Regards,
Andy -
AuthorPosts
- You must be logged in to reply to this topic.