Skip to main content
<NuxtLink> is a drop-in replacement for both Vue Router’s <RouterLink> component and HTML’s <a> tag. It intelligently determines whether the link is internal or external and renders it accordingly with available optimizations (prefetching, default attributes, etc.)

Internal Routing

In this example, we use <NuxtLink> component to link to another page of the application.

Passing Params to Dynamic Routes

In this example, we pass the id param to link to the route ~/pages/posts/[id].vue.
Check out the Pages panel in Nuxt DevTools to see the route name and the params it might take.
When you pass an object into the to prop, <NuxtLink> will inherit Vue Router’s handling of query parameters. Keys and values will be automatically encoded, so you don’t need to call encodeURI or encodeURIComponent manually.
By default, <NuxtLink> uses Vue Router’s client side navigation for relative route. When linking to static files in the /public directory or to another application hosted on the same domain, it might result in unexpected 404 errors because they are not part of the client routes. In such cases, you can use the external prop with <NuxtLink> to bypass Vue Router’s internal routing mechanism. The external prop explicitly indicates that the link is external. <NuxtLink> will render the link as a standard HTML <a> tag. This ensures the link behaves correctly, bypassing Vue Router’s logic and directly pointing to the resource.

Linking to Static Files

For static files in the /public directory, such as PDFs or images, use the external prop to ensure the link resolves correctly.
[app/pages/index.vue]

Linking to a Cross-App URL

When pointing to a different application on the same domain, using the external prop ensures the correct behavior.
[app/pages/index.vue]
Using the external prop or relying on automatic handling ensures proper navigation, avoids unexpected routing issues, and improves compatibility with static resources or cross-application scenarios.

External Routing

In this example, we use <NuxtLink> component to link to a website.
[app/app.vue]

rel and noRel Attributes

A rel attribute of noopener noreferrer is applied by default to links with a target attribute or to absolute links (e.g., links starting with http://, https://, or //).
  • noopener solves a security bug in older browsers.
  • noreferrer improves privacy for your users by not sending the Referer header to the linked site.
These defaults have no negative impact on SEO and are considered best practice. When you need to overwrite this behavior you can use the rel or noRel props.
[app/app.vue]
A noRel prop can be used to prevent the default rel attribute from being added to the absolute links.
[app/app.vue]
noRel and rel cannot be used together. rel will be ignored.
Nuxt automatically includes smart prefetching. That means it detects when a link is visible (by default), either in the viewport or when scrolling and prefetches the JavaScript for those pages so that they are ready when the user clicks the link. Nuxt only loads the resources when the browser isn’t busy and skips prefetching if your connection is offline or if you only have 2g connection.
[app/pages/index.vue]

Custom Prefetch Triggers

We now support custom prefetch triggers for <NuxtLink> after v3.13.0. You can use the prefetchOn prop to control when to prefetch links.
  • visibility: Prefetches when the link becomes visible in the viewport. Monitors the element’s intersection with the viewport using the Intersection Observer API. Prefetching is triggered when the element is scrolled into view.
  • interaction: Prefetches when the link is hovered or focused. This approach listens for pointerenter and focus events, proactively prefetching resources when the user indicates intent to interact.
You can also use an object to configure prefetchOn:

Enable Cross-origin Prefetch

To enable cross-origin prefetching, you can set the crossOriginPrefetch option in your nuxt.config. This will enable cross-origin prefetching using the Speculation Rules API.
[nuxt.config.ts]

Disable prefetch globally

It’s also possible to enable/disable prefetching all links globally for your app.
[nuxt.config.ts]

Props

When not using external, <NuxtLink> supports all Vue Router’s RouterLink props
string | RouteLocation
Any URL or a route location object from Vue Router.
boolean
Whether <NuxtLink> should wrap its content in an <a> element. It allows taking full control of how a link is rendered and how navigation works when it is clicked. Works the same as Vue Router’s custom prop.
string
default:"router-link-exact-active"
A class to apply on exact active links. Works the same as Vue Router’s exactActiveClass prop on internal links.
string
default:"router-link-active"
A class to apply on active links. Works the same as Vue Router’s activeClass prop on internal links.
boolean
Works the same as Vue Router’s replace prop on internal links.
string
An aria-current attribute value to apply on exact active links. Works the same as Vue Router’s ariaCurrentValue prop on internal links.
string
An alias for to. If used with to, href will be ignored.
boolean
If set to true, no rel attribute will be added to the external link.
boolean
Forces the link to be rendered as an <a> tag instead of a Vue Router RouterLink.
boolean
When enabled will prefetch middleware, layouts and payloads of links in the viewport.
'interaction' | 'visibility' | object
Allows custom control of when to prefetch links. Possible options are interaction and visibility (default). You can also pass an object for full control, for example: { interaction: true, visibility: true }. This prop is only used when prefetch is enabled (default) and noPrefetch is not set.
boolean
Disables prefetching.
string
A class to apply to links that have been prefetched.

Anchor Props

string
A target attribute value to apply on the link.
string
default:"noopener noreferrer"
A rel attribute value to apply on the link. Defaults to "noopener noreferrer" for external links.

Overwriting Defaults

In Nuxt Config

You can overwrite some <NuxtLink> defaults in your nuxt.config.
These options will likely be moved elsewhere in the future, such as into app.config or into the app/ directory.
[nuxt.config.ts]
You can overwrite <NuxtLink> defaults by creating your own link component using defineNuxtLink.
[app/components/MyNuxtLink.ts]
You can then use <MyNuxtLink /> component as usual with your new defaults.
string
default:"NuxtLink"
A name for the component.
string
default:"noopener noreferrer"
A default rel attribute value applied on external links. Set it to "" to disable.
string
default:"router-link-active"
A default class to apply on active links. Works the same as Vue Router’s linkActiveClass option.
string
default:"router-link-exact-active"
A default class to apply on exact active links. Works the same as Vue Router’s linkExactActiveClass option.
'append' | 'remove'
An option to either add or remove trailing slashes in the href. If unset or not matching the valid values append or remove, it will be ignored.
boolean
Whether or not to prefetch links by default.
object
Granular control of which prefetch strategies to apply by default.
string
A default class to apply to links that have been prefetched.