You Can Now Drop F-Bombs on YouTube Without Getting Demonetised

YouTube Eases Ad Restrictions on Videos with Early Profanity

YouTube has announced a significant shift in its ad guideline policy regarding profanity, granting content creators more flexibility in monetising their videos. Effective immediately, videos featuring strong swear words, including the “f-bomb,” within the first seven seconds are now eligible for full monetisation.

YouTube Monetisation

This marks a notable relaxation of previous rules. In 2022, YouTube implemented a policy that restricted advertising on videos containing profanity early on. This rule was partially eased in 2023, allowing videos with moderate profanity (such as “asshole” or “bitch”) in the opening seconds to be fully monetised, while stronger language still faced limited ad revenue. Now, even videos with strong profanity at the outset can earn full advertising income.

Conor Kavanagh, YouTube’s head of monetisation, explained the policy change in a video announcement. He stated that the original restrictions were put in place to accommodate advertisers who wished to avoid association with explicit language. However, the advertising landscape has evolved, and advertisers can now target content based on their preferred level of profanity.

Despite this newfound freedom, Kavanagh cautioned creators that certain restrictions remain. Using strong swear words in video titles or thumbnails will still result in limited advertisements. Furthermore, excessive use of strong profanity throughout a video, such as in a compilation of a character swearing repeatedly, will continue to violate the platform’s advertiser-friendly content guidelines.

In essence, while creators can now use strong language at the beginning of their videos without immediate monetisation penalties, they must still exercise discretion to ensure their content remains appealing to advertisers and avoids broader policy violations.

Advertisement

Source

Article Navigation

Leave a Reply

Your email address will not be published. Required fields are marked *