• Saturday, November 29, 2025

Understanding and Implementing 301 Redirects in Plesk

The HTTP response status code 301 Moved Permanently signifies a permanent redirection, indicating that any existing links or records using the original URL should be updated to reflect the new destination. This type of redirect is crucial for maintaining website SEO and user experience, as it seamlessly guides visitors and search engines from an old URL to a new one.

Various methods exist for effectively redirecting users from one domain or webpage to another. Among these, the 301 redirect is widely recognized as a highly effective and search engine-friendly approach. It communicates to browsers and search engines that a page or site has permanently moved, ensuring that link equity and search rankings are preserved.

Here are the primary methods for configuring a domain forward or redirect within Plesk:

  • Plesk Domain Alias: A versatile option that can be applied to DNS, web, and mail services, setting up a comprehensive redirect for an entire domain.
  • Plesk Domain Forwarding: Specifically designed for web traffic, allowing you to forward a domain to any specified URL.
  • Custom Web Server Directives or Code: For advanced configurations, enabling precise control over URL-to-URL redirection through server-level settings.

Redirecting an Entire Domain with a Domain Alias

If your goal is to forward a complete domain to another, such as directing visitors from mydomain.com to mynewdomain.com, Plesk simplifies this process. By adding the old domain as a domain alias, Plesk automatically configures a 301 permanent redirect for you, ensuring a smooth transition for your audience and search engine crawlers.

Plesk Add Domain Alias
  1. Log into your Plesk control panel and locate the Add Domain Alias button.
  2. Enter the domain name you wish to forward (the source domain) and then select the destination domain to which you want to direct traffic.
  3. Typically, you can keep all checkboxes at their default settings. However, if you do not intend to forward mail services for this alias, ensure that the “Mail Service” box is unchecked.
  4. Click the OK button to apply and save your changes.

Implementing Redirects via Domain Forwarding

For specific web-based redirections, Plesk’s domain forwarding feature offers a direct solution to steer visitors from one domain to any desired URL. This method is ideal when you need to redirect a domain's web traffic without affecting other services like mail or DNS.

  1. Access your Plesk control panel.
  2. Navigate to the Websites & Domains section, then click on Add Domain.
  3. In the Webspace section, choose the appropriate subscription name where the forwarder will be established. Subsequently, specify the domain name that will serve as the forwarder in the Registered domain name field.Plesk Add Domain
  4. Under the Hosting type section, select Forwarding.Plesk Hosting Type Forwarding
  5. Within the Forwarding Settings box, input the complete destination URL where you wish to redirect visitors. For the Forwarding type, it is recommended to select Moved permanently (code 301) for SEO benefits and to indicate a permanent move.Plesk Forwarding Settings 301
  6. Finally, click Add Domain to finalize the forwarding setup.

Advanced Redirects Using Web Server Configuration

For more granular control over redirects, particularly for specific paths or complex URL patterns, configuring redirects directly within your web server's settings offers significant flexibility. This method is often preferred by experienced administrators who need to implement custom redirection rules that go beyond simple domain-to-domain forwarding.

Nginx Redirect Configuration

To implement redirects using Nginx directives within Plesk, follow these steps:

  1. Log into Plesk and navigate to the "Apache & Nginx Settings" section for the domain where you intend to add the redirect.
  2. Scroll down to the "Additional Nginx directives" input box.
  3. Enter your chosen Nginx redirect rules into this box, selecting from the examples below, and then click Apply or OK.
# Simple path to path redirect:
rewrite ^/source_path$ https://www.destination.com/new_path permanent;

# Regex redirect to redirect *all* content from one domain to another:
rewrite ^/(.*)$ https://www.destination.com/$1 permanent;

Apache (.htaccess) Redirect Configuration

For Apache web servers, redirects are commonly managed through the .htaccess file, which allows for powerful and flexible rule-based redirections. Here’s how you can implement them:

  1. Access the file manager within Plesk for your domain, or connect via FTP/SFTP, to edit or create the .htaccess file in your document root.
  2. Add the following Apache rewrite rules to your .htaccess file. Remember to choose the rule(s) that best fit your redirection needs.
# Redirect everything:
RewriteEngine on
RewriteCond %{REQUEST_URI} !^.well-known/acme-challenge
RewriteRule ^(.*) https://yournewsite.com$1 [R=301,L]

# Redirect specific pages (use this OR the everything rule above, NOT BOTH):
redirect 301 / http://yournewsite.com/
redirect 301 /oldpage/ http://yournewsite.com/newpage/
redirect 301 /oldpage.html http://yournewsite.com/newpage/
Back