WordPress.org

Making WordPress.org

Opened 9 months ago

Closed 8 months ago

Last modified 6 months ago

#4958 closed enhancement (fixed)

Add rel="nofollow ugc" to user-generated links

Reported by: diddledan Owned by: dd32
Milestone: Priority: normal
Component: General Keywords: has-patch
Cc:

Description

Currently W.org adds rel=nofollow to links generated by users. Following recent changes referenced at https://webmasters.googleblog.com/2019/09/evolving-nofollow-new-ways-to-identify.html and the precedent by WordPress Core at https://core.trac.wordpress.org/ticket/48022 we should add to the rel attribute the additional ugc value to indicate User-Generated Content. Attached is a patch to do just this based in part on WordPress Core's implementation.

The bbpress ticket at https://bbpress.trac.wordpress.org/ticket/3318 contains the bbpress-specific changes to add ugc into topic and reply content. Once that is committed to bbpress trunk and filtered through onto W.org, combined with the patch attached here committed to W.org and deployed, the changes will be complete.

Attachments (1)

4958.diff (3.4 KB) - added by diddledan 9 months ago.
Patch to add rel="nofollow ugc" to user-generated content

Download all attachments as: .zip

Change History (7)

@diddledan
9 months ago

Patch to add rel="nofollow ugc" to user-generated content

#1 @diddledan
9 months ago

  • Keywords has-patch added

#2 @diddledan
9 months ago

  • Type changed from defect to enhancement

This ticket was mentioned in Slack in #bbpress by casiepa. View the logs.


9 months ago

#4 @dd32
8 months ago

In 9469:

Support Forums: Add the ugc class to user supplied URLs.

Props diddledan.
See #4958.

#5 @dd32
8 months ago

  • Owner set to dd32
  • Resolution set to fixed
  • Status changed from new to closed

In 9470:

Plugin Directory: Add ugc to rel="nofollow" links in user supplied content.

Props diddledan.
Fixes #4958.

#6 @Otto42
6 months ago

In 9708:

Support forums: Add ugc to links in topic and replies content (which already had nofollow). See #4958.

Note: See TracTickets for help on using tickets.