# Optionally add noreferrer to external links

**URL:** <https://meta.discourse.org/t/optionally-add-noreferrer-to-external-links/79474>\
**Category:** Product Support\
**Created:** [January 31, 2018, 5:34pm UTC](https://meta.discourse.org/t/optionally-add-noreferrer-to-external-links/79474 "2018-01-31T17:34:41Z")\
**Posts on this page:** 1\
**Showing post:** 7

<div class="post-metadata">

**Author:** ![riking](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/riking/32/170938_2.png) [@riking](https://meta.discourse.org/u/riking)\
**Post date:** [February 3, 2018, 7:54pm UTC](https://meta.discourse.org/t/optionally-add-noreferrer-to-external-links/79474/7 "2018-02-03T19:54:00Z")

</div>

For a dynamic web app like Discourse, referer policy is probably more useful to be set at a page scope rather than for individual links.

To dynamically set referer policy, use the `<meta>` element, and the _last set policy prevails_, which makes it very easy to code.

An example policy:

- " `no-referrer-when-downgrade` " by default
- " `strict-origin-when-cross-origin` " when viewing private messages or secure categories

With a site setting to change it to always be “strict-origin-when-cross-origin”, turned on by default for login required sites.

If we decide Discourse doesn’t need its own referer information, strict-when-cro can be upgraded to “`strict-origin`” to save bandwidth.

---

_[View the full topic](https://meta.discourse.org/t/optionally-add-noreferrer-to-external-links/79474)._