Member Avatar for anupish

Below google adsense code pointing the WC3 eroor please give any solution to the wc3 passing?

<script async src="//pagead2.googlesyndication.com/pagead/js/adsbygoogle.js"></script>

<ins class="adsbygoogle"
     style="display:block"
     data-ad-client="ca-pub-xxxxxxxxxxxxxxxx"
     data-ad-slot="7441003235"
     data-ad-format="auto"></ins>
<script>
(adsbygoogle = window.adsbygoogle || []).push({});
</script>
  • 5 Contributors
  • 5 Replies
  • 118 Views
  • 3 Days Discussion Span
  • Latest Post Latest Post by almostbob

Dani AI

Generated

The AdSense snippet in the first post commonly trips the W3C validator because third‑party JavaScript can inject or write markup at runtime. That makes the validator report errors on the rendered DOM even when the static source (the HTML you actually control) is fine. and were on the right track — start by proving whether the validator is complaining about the source you ship or about script-generated content.

Quick, practical checks:

  • Feed the page HTML to the W3C validator using "Direct Input" or "File Upload" rather than validating the live URI. If the uploaded/source copy passes, the errors are coming from runtime DOM insertion and are not present in your static markup.
  • If the source fails, read the validator messages closely: common, fixable items are unescaped ampersands in URLs (escape & as &amp;) or a mismatched DOCTYPE (use the HTML5 doctype if you rely on data-* attributes and modern markup).
  • If you serve pages as XHTML (application/xhtml+xml), the XML parser will choke on raw script content unless you make it XML-safe. In that case wrap inline scripts in a CDATA section or otherwise escape characters that violate XML syntax.

Example CDATA pattern (wrap your inline script contents when serving XML):

<script type="text/javascript">
//<![CDATA[
  /* inline JS that includes characters like & */
//]]>
</script>

Keep changes minimal and test in multiple browsers. If validation errors only appear on the rendered page and not in your static source, they can generally be ignored for the purpose of source validation. Before altering any official AdSense snippet, keep a backup of the original and follow AdSense guidance — small, XML- or HTML-escaping tweaks for validator compatibility are the safe route. For quick validation use the W3C Markup Validation Service: https://validator.w3.org/

Recommended Answers

All 5 Replies

Member Avatar for hericles

What error?

Member Avatar for Sukhpreet_1

I can't find the error?

Member Avatar for almostbob

ALL google products show w3c tester errors
NONE of the sripts are code compliant, they all contain entities not defined by w3c standards
This does not mean the code is bad
google have not escape coded all the
?1=this&2=that&3=the_other that the javascriipts require, as
&#63;1=this&#38;2=that&#38;3=the_other because they get too bloody big

guess ~2 million hits a minute, 40byte less per hit, is a big drop in server load

Edited by almostbob
Member Avatar for Dani

I believe that the OP is referring to getting a W3C invalidation error from the snippet of Javascript code inserted onto his own page to display Google AdSense ads. Google has stated in the past that you are not allowed to make any changes to the javascript snippet with the sole exception being to make it W3C-compliant.

Member Avatar for almostbob

There is no error in that code
the w3c validator has quirks, and limitations
Validate by URI. there are errors in the rendered page,
Validate by file upload. those errors vanish: the scripts are not rendered, only examined

google are not code compliant
this element <ins class="adsbygoogle"></ins>
is populated with the dirtiest code ever mis-written to make it small and still function

it is a miracle of miniature mayhem

Google don't feel the need, it just has to work. Who is gonna tell em they can't?

Errors found while checking this document as HTML5!
28 Errors, 4 warning(s)
https://www.google.com/

a name, an input box, 2 buttons: 28 errors
billions of hits, a few bytes saved on every hit, lots of $data saved

Edited by almostbob
Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.