Google updates existing guidelines around modifying the AdSense ad code.
“Going forward, we will permit publishers to make modifications to the AdSense ad code so long as those modifications do not artificially inflate ad performance or harm advertisers and otherwise comply with our Terms and Conditions and program policies,” explains Google.
Google notes, that “
- AdSense code modifications that “are not permitted by our program policies” should not be made;
- Publishers should always use caution when modifying the AdSense code and must not use techniques like hiding ad units, implementing the AdSense code in a way that covers content, creating ‘floating ads’, or manipulating ad targeting as they are a violation of our policies.”
Further Google notes, the new flexibility will enable you to try:
- “Responsive design: Enabling publishers to create a single webpage that will adapt to the device on which it’s being viewed, whether it’s a laptop, smartphone or tablet, to maximize user experience.
- A/B testing: Running a test by creating multiple versions of a page, comparing user behavior to see which page is the most effective.
- Setting custom channels dynamically: Tracking performance of segments of users, sections of your site, or other behavior to maximize ad and user experience.
- Ad tag minification: Enabling your site pages to load faster by reducing the amount of data to be transferred,” added Google.
Update 05/25: The AdSense team just posted a video talking about…”adult content and keeping AdSense family-safe.”
“We’ve made a commitment to our users, advertisers and publishers to keep the AdSense network family-safe. A general rule of thumb when it comes to the adult content policy is: if you wouldn’t want to share this content at a family dinner or view it in your boss’s office, you shouldn’t place AdSense code on it,” the team wrote.
Watch the video for closer look at the AdSense adult content policy:
Google also announced upcoming changes to SSL Certificates services–specifically, “all of our SSL certificates will be upgraded to 2048-bit keys by the end of 2013,” informs Google adding, “(W)e will begin switching to the new 2048-bit certificates on August 1st, to ensure adequate time for a careful rollout before the end of the year,” google said.
In addition, Google will also change the root certificate that signs all of its SSL certificates because it has a 1024-bit key.
Google notes, that for a “smooth upgrade,” client software that makes SSL connections to Google (e.g. HTTPS) in addition to following, also, should support the Server Name Indication (SNI) extension because clients may need to make an extra API call to set the hostname on an SSL connection.
- “Perform normal validation of the certificate chain;
- Include a properly extensive set of root certificates contained. We have an example set which should be sufficient for connecting to Google in our FAQ. (Note: the contents of this list may change over time, so clients should have a way to update themselves as changes occur);
- Support Subject Alternative Names (SANs),” informs google.
Any client unsure about SNI support can be tested against https://googlemail.com–this URL should only validate if you are sending SNI.
Google Fonts together with Adobe’s Typekit team has optimized “Rosario,” a humanist sans serif based font on the classic proportions of Garamond’s type.
After making following improvements, “Typekit sent their version back to the foundry to review and release on the Omnibus Type homepage,” google said.
- “Convert and/or clean up outlines, for design fidelity and file size efficiency
- Re-componentize source fonts, for file size efficiency
- Remove/reassign glyphs with incorrect Unicode code points, for semantic value
- Add common missing glyphs (non-breaking space, soft hyphen)
- Set vertical metrics values according to best practices
- Set underline and strike-through values, for design consistency
- Contribute PostScript hints and (if a typeface was designed for small sizes like paragraph text) TrueType instructions (also called hinting), which consist of instructions to the rasterizer embedded in the font file itself.”
The updated Rosario family is now available in Typekit, Adobe Edge Web Fonts and Google Fonts.
Update 05/30: To help people communitcate better, Google is releasing an open standard for “color fonts” and have also added support for it to one of the most popular font rendering engines in the world–“FreeType.”
“We want to make color Emoji available in an open and free way anywhere that you use text,” Google stated. Further, “the changes to FreeType have also been integrated into the main code repository.”
These are all freely available to download and use from the Color Emoji Font Project site.