Google starts using the link attributes rel=”sponsored” and rel=”ugc” for ranking

Google this month announced that it is starting to use rel=”sponsored” and rel=”ugc” for ranking purposes, along with rel=”nofollow”.

Links in guest posts should be nofollow
Links in guest posts should be nofollow

Google this month announced that it is starting to use rel=”sponsored” and rel=”ugc” for ranking purposes, along with rel=”nofollow”.

Google introduced rel=”sponsored” and rel=”ugc” last year, to evolve the “nofollow” link attribute. However, only now announced that it has began to incorporate them for ranking purposes.

Google says the nofollow link attribute was originally introduced as a way to help fight comment spam and annotate sponsored links.

Google search team stated it saw an adoption of the new 2 link attributes (rel=”sponsored” and rel=”ugc”) by webmasters around the world.

rel=”sponsored”

Mark links that are advertisements or paid placements (commonly called paid links) as sponsored. More information on Google’s stance on paid links.

rel=”ugc”

Marks user-generated content (UGC) links, such as comments and forum posts.

rel=”nofollow”

Marks links that webmasters do not want to associate their website with.

John Mu, Webmaster Trends Analyst at Google, wrote on twitter that links in guest posts should be “nofollow”, Search Engine Roundtable reported.


PPC Land is an international news publication headquartered in Frankfurt, Germany. PPC Land delivers daily articles brimming with the latest news for marketing professionals of all experience levels.

Subscribe to our newsletter for just $10/year and get marketing news delivered straight to your inbox. By subscribing, you are supporting PPC Land.

You can also follow PPC Land on LinkedIn, Bluesky, Reddit, Mastodon, X, Facebook, Threads, and Google News.

Know more about us or contact us via info@ppc.land

Our latest marketing news:

Subscribe via email

Don’t miss out on the latest marketing news. Sign up now to get the articles directly in your email.
jamie@example.com
Subscribe