How to set up a URL redirect on Namecheap

These steps follow Namecheap's Knowledgebase article on URL redirects. They work when the domain uses Namecheap's BasicDNS, PremiumDNS or FreeDNS. If it points to other nameservers, set the redirect wherever those are managed.

Option 1: the Domain tab (quickest)

1. Sign in to Namecheap and go to your Domain List.
2. Click Manage next to the domain.
3. In the Redirect Domain section, click Add Redirect.
4. In Source URL, enter the domain, for example yourdomain.com. In Destination URL, enter the full address to send people to, such as https://www.yournewsite.com.
5. To redirect www.yourdomain.com as well, add a second redirect for the www version.
6. Save with the green tick or Save All Changes.
7. Open the Advanced DNS tab and remove any records that conflict: A, CNAME or ALIAS records, or other URL redirect records, on the same host.

Option 2: a URL Redirect Record on Advanced DNS

Use this when you also manage other records, such as email, on the same domain.

1. Click Manage, open Advanced DNS and find Host Records.
2. Click Add New Record and choose URL Redirect Record as the type.
3. In Host, enter @ for the domain itself, www for the www version, or ***** for every subdomain.
4. In Value, enter the destination URL.
5. Change the redirect type from Unmasked to Permanent (301) if the move is for good.
6. Save, then remove conflicting A, CNAME or ALIAS records on the same host.

Namecheap explains that a URL Redirect Record works by adding a hidden A record that points the domain at its forwarding server. That's why other A, CNAME or ALIAS records on the same host get in the way.

Permanent, Unmasked or Masked?

Namecheap offers three types:

• Permanent (301): the address bar changes to the new site, and search engines treat the move as permanent. The HTTP standard says a 301 means links ought to use the new address from now on, and Google shows the new address in its results.
• Unmasked (302): the address bar changes too, but the move is marked temporary, so Google keeps showing the old address.
• Masked (URL frame): the visitor stays on your domain while the other site loads inside a frame. Some sites block being shown in a frame, so test it before you rely on it. The checker can't see inside a frame: it shows your domain answering 200.

For a domain you've moved for good, pick 301.

https and the same domain

Namecheap notes a limit: its redirect can send a domain to a different domain over https, but it can't redirect http://yourdomain.com to https://yourdomain.com. That has to happen on your hosting, for example in .htaccess, with an SSL certificate installed. See how to redirect with .htaccess.

Namecheap adds that redirecting from https://domain1 to https://domain2 needs SSL certificates on both domains.

Check the redirect

Give it the 30 minutes Namecheap mentions, then paste both yourdomain.com and www.yourdomain.com into the checker. Each should reach the new site in one hop with a 301.

When the redirect doesn't work

• The old site still loads. A conflicting A or CNAME record is winning. Remove it on the Advanced DNS tab.
• www works but the bare domain doesn't (or the other way round). Each needs its own redirect or record: @ and www.
• You get a 302. The type is still Unmasked. Change it to Permanent (301).
• Several hops. The destination redirects again, for example from http to https or to www. Point the redirect at the final address; see redirect chains.

For the bigger picture, including registrars other than Namecheap, read how to redirect a domain.