How noindex works on Dub

Learn how Dub supports noindex response headers for short links with custom domains.

Steven Tey

Written by Steven Tey

If you're familiar with SEO best practices, you might have heard of the noindex meta tag that tells search engines not to index a page.

This is particularly important if you're using Dub with a custom domain – specifically a subdomain – for your short links, since having them indexed could potentially have a negative impact on your SEO.

To prevent this, Dub automatically serves short links with a noindex response header when you're using a custom domain. This tells search engines not to index your short links, keeping them out of search results.

GET /noindex HTTP/2
Host: d.to
User-Agent: curl/8.6.0

HTTP/2 302
location: https://dub.co/changelog/noindex-support
X-Robots-Tag: noindex
X-Powered-By: Dub.co

If you're using Dub with a default Dub-branded domain (e.g. dub.sh, git.new), the noindex response header is not applied by default.

noindex support for root domains

By default, if you don't have a desination URL configured for the root domain of your custom domain (e.g. example.com), it won't be served with a noindex response header.

However, if you were to add a destination URL, it will automatically be updated to have the noindex header. If you would like your root domain to be indexed anyway, you can easily disable that by following these steps:

  1. Go to the Dub dashboard.
  2. Click on the Domains tab on the top navigation bar.
  3. Click on the button of domain that you want to set as thenoindex header for, which will open a dropdown menu.
More options popover
More options popover
  1. In the dropdown menu, click on the Edit button, which will open the Edit domain modal.
  2. Toggle the Advanced options section.
  3. Toggle the Disable Search Engine Indexing switch to enable/disable the noindex response header for the root domain.
Default expiration URL for a domain
Default expiration URL for a domain

This feature is only available for Pro plans and above.

Did this answer your question?