Partner with experts to accelerate your digital transformation journey
Bobcares

Plesk Redirect a Subdomain to Another Domain in 3 Simple Ways

PDF Header PDF Footer

Learn how to use Plesk to redirect a subdomain to another domain with simple methods like Forwarding, .htaccess, and server directives.  Our Plesk Support Team is always here to help you.

Plesk Redirect a Subdomain to Another Domain in 3 Simple Ways

Sometimes, you may need to move traffic from one subdomain to a different domain. It could be for branding reasons, merging websites, or just pointing visitors to a new destination. Luckily, setting this up is simple if you know where to look. In this guide, you’ll learn how to plesk redirect a subdomain to another domain using three proven methods: Forwarding, .htaccess, and server directives. Each method works well depending on your needs, and you’ll see all the details with exact steps and code included.

plesk redirect a subdomain to another domain

Using Plesk Forwarding Hosting Type

This option is the most user-friendly inside Plesk. However, you should note that it does not support HTTPS.

1. Log into Plesk
First, sign in to your Plesk control panel with your username and password.

2. Navigate to Websites & Domains
From the sidebar, click on Websites & Domains to view all domains and subdomains.

3. Select the Subdomain
Find the subdomain you want to redirect and click on its name to open the settings page.

4. Access Hosting Settings
Next, click on the Hosting Settings icon next to the subdomain.

5. Change Hosting Type
Inside Hosting Settings, locate the Hosting type option and hit the Change button.

6. Select Forwarding
From the dropdown menu, choose Forwarding as the new hosting type.

7. Enter Destination Address
Type in the complete URL of the target domain, such as:

http://www.targetdomain.com

8. Choose Forwarding Type

  • Moved Permanently (301): Permanent redirect
  • Moved Temporarily (302): Temporary redirect

9. Confirm Changes
Finally, click OK to save. If you see a warning about losing existing data, proceed only if you are sure.

Using the .htaccess File

For more flexibility and HTTPS support, you can redirect via .htaccess.

1. Access File Manager
Go to Domains > subdomain.example.com > File Manager in Plesk.

2. Create or Edit .htaccess File
If there’s no .htaccess file in the root of your subdomain, create one. Otherwise, edit the existing file.

3. Add Redirect Rules
Insert this code into the .htaccess file:

RewriteEngine On
RewriteBase /
RewriteRule ^(.*)$ http://www.example.com/$1 [L,R=301,NC]

Replace http://www.example.com/ with your target domain.

4. Save Changes
Make sure to save the file so the rules apply immediately.

Using Additional Directives

For those comfortable with server-level settings, directives can handle redirection cleanly.

1. Access Apache & Nginx Settings
Go to Domains > subdomain.example.com > Apache & nginx Settings.

2. Add Additional Directives
In the additional nginx directives field, add:

return 301 http://www.example.com/;

Replace with your desired destination.

3. Save Configuration
Click OK to apply the changes.

Important Considerations

  • HTTPS Support: Forwarding type doesn’t support HTTPS. Use .htaccess or directives instead if SSL is required.
  • Backup Data: Before switching hosting types, back up any existing data linked with the subdomain.
  • Test the Redirect: Once done, type the subdomain URL in your browser and check if it redirects properly.

[If needed, Our team is available 24/7 for additional assistance.]

Conclusion

Setting up a plesk redirect a subdomain to another domain is quick once you know these methods. The choice depends on your needs, simple forwarding, flexible .htaccess rules, or direct server directives. Follow these steps, and your visitors will reach the right destination every time.

0 Comments

Submit a Comment

Your email address will not be published. Required fields are marked *

Get featured on the Bobcares blog and share your expertise with a global tech audience.

WRITE FOR US

GET UP TO 25% OFF

Plesk Support

Spend time on your business, not on your servers.

Managing a server is time consuming. Whether you are an expert or a newbie, that is time you could use to focus on your product or service. Leave your server management & end-user tech support to us, and use that time to focus on the growth and success of your business.

TALK TO USOr click here to learn more.

Speed issues driving customers away?
We’ve got your back!

Privacy Preference Center

Necessary

Necessary cookies help make a website usable by enabling basic functions like page navigation and access to secure areas of the website. The website cannot function properly without these cookies.

PHPSESSID - Preserves user session state across page requests.

gdpr[consent_types] - Used to store user consents.

gdpr[allowed_cookies] - Used to store user allowed cookies.

PHPSESSID, gdpr[consent_types], gdpr[allowed_cookies]
PHPSESSID
WHMCSpKDlPzh2chML

Statistics

Statistic cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously.

_ga - Preserves user session state across page requests.

_gat - Used by Google Analytics to throttle request rate

_gid - Registers a unique ID that is used to generate statistical data on how you use the website.

smartlookCookie - Used to collect user device and location information of the site visitors to improve the websites User Experience.

_ga, _gat, _gid
_ga, _gat, _gid
smartlookCookie
_clck, _clsk, CLID, ANONCHK, MR, MUID, SM

Marketing

Marketing cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user and thereby more valuable for publishers and third party advertisers.

IDE - Used by Google DoubleClick to register and report the website user's actions after viewing or clicking one of the advertiser's ads with the purpose of measuring the efficacy of an ad and to present targeted ads to the user.

test_cookie - Used to check if the user's browser supports cookies.

1P_JAR - Google cookie. These cookies are used to collect website statistics and track conversion rates.

NID - Registers a unique ID that identifies a returning user's device. The ID is used for serving ads that are most relevant to the user.

DV - Google ad personalisation

_reb2bgeo - The visitor's geographical location

_reb2bloaded - Whether or not the script loaded for the visitor

_reb2bref - The referring URL for the visit

_reb2bsessionID - The visitor's RB2B session ID

_reb2buid - The visitor's RB2B user ID

IDE, test_cookie, 1P_JAR, NID, DV, NID
IDE, test_cookie
1P_JAR, NID, DV
NID
hblid
_reb2bgeo, _reb2bloaded, _reb2bref, _reb2bsessionID, _reb2buid

Security

These are essential site cookies, used by the google reCAPTCHA. These cookies use an unique identifier to verify if a visitor is human or a bot.

SID, APISID, HSID, NID, PREF
SID, APISID, HSID, NID, PREF