W3C validation errors related to the <noscript> tag and Facebook Pixel often occur because of improper placement or disallowed HTML elements in the <head> of your Webflow project.
<noscript> tag inside the <head> if it contains anything other than <link>, <style>, or text nodes.<noscript> fallback image tag, but Webflow allows custom code in the <head>, where such tags may trigger validation errors.
<noscript> Tag to the Body
</body>).<noscript> block (including the <img> tag Facebook provides) from the head section to this footer section.<head>, aligning your site with W3C specs.
<head>, as it uses a standard <script> tag that is allowed.<noscript><img></noscript> part needs to move to avoid validation errors.<noscript> snippet stays intact—don't alter the actual Facebook tracking URL or image properties like style or height.
<noscript> tag should now be resolved.
Move the <noscript> tag containing the pixel tracking image from the <head> to the footer custom code area in Webflow. This satisfies W3C HTML validation without affecting Facebook Pixel functionality.