WordPress announced that WordPress 5.3, which will make its appearance next month, is going to support Google’s UGC Nofollow attribute by default. Beginning on November 12, 2019, all links in the comments section will automatically use the UGC nofollow link attribute.
UGC Nofollow Attribute
If there is a WordPress plugin that is involved with user generated content and links, updates to their code may need to be made in order to support the new code.
The old callback:
has been deprecated in favor of a new callback:
The WordPress announcement did not specify if plugins using the old code would break the site or simply gracefully degrade.
According to google, it will support rell=ugc. But, other search engines don’t have any indicated support for that code. To support all search engines, WordPress will output the UGC nofollow in a manner that supports all search engines.
This is the code:
There aren’t any ranking benefits to the publisher for using the UGC nofollow attribute.
The UGC nofollow attribute benefits Google because it helps Google understand that a link was created by someone outside of the publisher’s control and that the link should not be trusted.
This change is important for WordPress developers since it involves changes to the code.
Here is how WordPress explains the change:
“In WordPress 5.3, wp_rel_nofollow_callback() will be deprecated in favor of more generic callback function, wp_rel_callback(), which is now used to add other rel attribute values to a specified link.
wp_rel_callback() is used by the existing wp_rel_nofollow() function to add a single “nofollow” value, and with the new wp_rel_ugc() function, developers can add both “nofollow” and “ugc” values to the rel attribute.”
And this is an example that WordPress shared on how to use the new code:
$link = ‘<a href=”example.com”>User generated link example</a>’;
$ugc_link = wp_rel_ugc( $link );
// output: <a href=”example.com” rel=”nofollow ugc”>User generated link example</a>