# Nofollow, sponsored and ugc: choosing link attributes

> Choose rel values by the actual relationship: editorial reference, paid placement, user contribution or a combination.


**Sponsored identifies paid links, ugc identifies user contributions and nofollow describes a link you do not want to endorse when the other categories do not fit.** These values belong in a link's `rel` attribute. An ordinary editorial link can work without any of them.

Start with who added the link and why it exists. One page might cite a source, include a commercial placement and accept a comment containing an external URL. Applying one value to every link obscures those differences.

## An ordinary editorial reference

A pottery studio writes an article and links to a technical explanation it selected as a source. This illustrative example uses the reserved domain `example.com`:

```html
<a href="https://www.example.com/materials/">
Read the material specifications
</a>
```

There is no need to add `rel="dofollow"`. Google's [outbound link qualification documentation](https://developers.google.com/search/docs/crawling-indexing/qualify-outbound-links) explains that ordinary links do not need these attributes. Nor must every external reference carry nofollow.

## A paid placement or affiliate link

When the business is compensated for placing a link, `sponsored` describes the relationship:

```html
<a href="https://www.example.com/kit/" rel="sponsored">
View the partner's kit
</a>
```

Google prefers `sponsored` for advertising and paid placements; `nofollow` remains an accepted way to qualify them. The attribute does not replace a visible explanation of the commercial relationship. Readers need understandable disclosure in the publication itself.

## A link submitted by a user

For links in comments or forums, `ugc` identifies user-generated content:

```html
<a href="https://www.example.com/project/" rel="ugc">
Project shared in a comment
</a>
```

Ugc describes the source of the contribution without declaring the destination bad. Keep moderation and publishing controls: an attribute does not review content or protect readers from harmful pages.

## Combining values

A link can have more than one relationship. A comment system that identifies user contributions and also applies nofollow can emit:

```html
<a href="https://www.example.com/project/"
rel="ugc nofollow">
Project shared in a comment
</a>
```

Spaces can separate the values. Before changing a CMS-wide setting, inspect the links it generates and the policy it applies. A manually added value may coexist with another supplied by a template or plugin.

## What the attributes leave unresolved

These values do not remove the destination page from the index or prevent Google from discovering it elsewhere. They cannot protect a private document either. For indexing controls on your own page, review [robots meta tags and noindex](/en/guides/robots-meta-tag/); privacy requires restricted access.

Google's [spam policies](https://developers.google.com/search/docs/essentials/spam-policies#link-spam) address manipulative link practices. Offering or buying links with a promise of transferring ranking signals warrants reviewing the arrangement as well as its HTML. An attribute cannot turn a deceptive campaign into an editorial recommendation.

Inspect the published link's destination and emitted `rel`. When another site changes a link to yours, you do not control its markup. Assess the relationship and request a correction where appropriate, without treating every attribute change as a demonstrated traffic loss.

## Plan your next post in HeyMark.

Keep the idea, review the draft with your team, and see how it performed in the accounts you connected.

[Start free](https://app.heymark.ai) · [See how it works](https://heymark.ai/en/#product)

## Developer and agent resources

- [HeyMark MCP documentation](https://heymark.ai/en/mcp/)
- [llms.txt](https://heymark.ai/llms.txt)
- [Full site content for language models](https://heymark.ai/llms-full.txt)
- MCP protocol endpoint: `POST https://mcp.heymark.ai`
- OAuth protected-resource metadata: [/.well-known/oauth-protected-resource](https://mcp.heymark.ai/.well-known/oauth-protected-resource)
- MCP server card: [/server-card](https://mcp.heymark.ai/server-card)
