HTML/SEO Critical BUG

  • Just a heads up

    I noticed this when doing an HTML/SEO Compliance scan of one of my sites
    After activating, and setting up the plugin I get the following warnings.

    CRITICAL: “<head> contains a <noscript> tag, which includes an image”
    CRITICAL: “<head> contains invalid HTML elements”

    Code that is present in the <Header> causing the above errors. (Code has been snipped for security)

    
<noscript> 
	<img height="1" width="1" style="display:none" alt="fbpx" src="https://www.facebook.com/tr?...codensipped" />
</noscript>

    Warning’s given:
    1, “URLs where the <head> contains a <noscript> tag, which includes an image. Including an tag in the <head> is invalid. This can be problematic for search engines crawlers that do not render JavaScript (i.e. most crawlers, most of the time), as the presence of the tag breaks the <head>, which may cause important tags (e.g. meta robots) to be missed.”

    2. “URLs where the <head> contains invalid DOM elements. Valid elements that can be used inside the <head> element are <title>, <meta>, <base>, <link>, <script>, <noscript>, <style> and <template>. Including invalid elements can lead to the HTML document not being parsed correctly, as the presence of other elements breaks the <head>, which may cause important tags (e.g. meta robots) to be missed.”

Viewing 2 replies - 1 through 2 (of 2 total)

  • Just remove the:

    <noscript> 
	<img height="1" width="1" style="display:none" alt="fbpx" src="https://www.facebook.com/tr?...codensipped" />
</noscript>

    That specific tag is solely for the less than 2% of the internet that has scripts turned off in their browser. Will fix your problem immediately and won’t affect your Pixel stats.

    Thread Starter Lollipops

    (@emcthemes)

    The only issue with removing that section of code from the plugin is your overriding core plugin files and generally bad practise as the next time the plugin receives an update the “custom” changes will revert.

    this really needs to be removed by the plugin developers or alternatively made togglable via a settings option, so those that require it can enable it and those that don’t and disable it.

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘HTML/SEO Critical BUG’ is closed to new replies.