h3_html = ‘
cta = ‘
atext = ‘
scdetails = scheader.getElementsByClassName( ‘scdetails’ );
sappendHtml( scdetails, h3_html );
sappendHtml( scdetails, atext );
sappendHtml( scdetails, cta );
sappendHtml( scheader, “http://www.searchenginejournal.com/” );
sc_logo = scheader.getElementsByClassName( ‘sc-logo’ );
logo_html = ‘‘;
sappendHtml( sc_logo, logo_html );
sappendHtml( scheader, ‘
} // endif cat_head_params.sponsor_logo
Google lately up to date one in every of its developer paperwork to make clear that dynamic rendering is not cloaking.
As Google’s Martin Splitt says, this may increasingly not come as a shock, but it surely does get requested usually sufficient to warrant official clarification.
Yay! @LizziHarvey and I up to date the dynamic rendering docs to make clear a really frequent query: Is dynamic rendering thought-about cloaking? The reply should not shock you 😂 https://t.co/l4s3JkOLcx pic.twitter.com/IH4MY8firS
— Martin Splitt @ 🇨🇭🏡 (@g33konaut) August 22, 2019
The up to date documentation reads:
“Googlebot generally doesn’t consider dynamic rendering as cloaking. As long as your dynamic rendering produces similar content, Googlebot won’t view dynamic rendering as cloaking.”
Google additionally clarifies that error pages produced because of implementing dynamic rendering aren’t thought-about cloaking both.
The solely occasion through which dynamic rendering could possibly be thought-about cloaking is if it’s used to serve completely different content material to customers and crawlers.
“Using dynamic rendering to serve completely different content to users and crawlers can be considered cloaking. For example, a website that serves a page about cats to users and a page about dogs to crawlers can be considered cloaking.”
This is an vital clarification for Google to make as a result of cloaking is a violation of Google’s Webmaster Guidelines. That means it might impression rankings and even end in penalties.
However, in the event you’re utilizing dynamic rendering because it’s supposed for use, then you definitely received’t have to fret about violating Google’s pointers.
For extra details about dynamic rendering, see these sources: