Skip to main content

Redirect an Old Domain to Your New Subdomain Permanently

Set up 301 permanent redirects to send visitors from an old domain to your new is-cool-me subdomain while preserving search engine rankings and maintaining analytics.

Written by Mayank Baswal

Founder of is-cool-me · DNS & Platform Infrastructure

Mayank Baswal maintains the is-cool-me platform and writes technical guides focused on DNS configuration, subdomain infrastructure, SSL troubleshooting, deployment workflows, and platform reliability.

Reviewed by is-cool-me Technical Review
## Introduction to Domain Migration When setting up a new project on is-cool-me, such as `myproject.is-pro.dev`, you might find yourself in a situation where you need to redirect an old domain to your new subdomain permanently. This could be due to a rebranding effort, a change in project scope, or simply to consolidate your online presence. A permanent redirect, also known as a 301 redirect, is the most SEO-friendly way to redirect users and search engines to your new subdomain, preserving your search engine rankings and minimizing disruption to your visitors. ## Prerequisites for Domain Redirect Before you begin the process of redirecting your old domain to your new subdomain, ensure you have the following: - Ownership or control over the old domain (e.g., `oldproject.com`). - A new subdomain set up on is-cool-me (e.g., `myproject.is-pro.dev`). - Access to your domain registrar's control panel for the old domain. - Basic understanding of DNS settings and HTTP redirects. ## Step-by-Step Redirect Setup To permanently redirect `oldproject.com` to `myproject.is-pro.dev`, follow these steps: 1. **Log in to your domain registrar** for `oldproject.com` and navigate to the DNS management section. 2. **Create a new DNS record**. You will typically need to add a CNAME record that points to your is-cool-me subdomain. However, for a 301 redirect, you will actually be modifying or adding an A record or using a domain forwarding service provided by your registrar. 3. **Use Domain Forwarding**: Many registrars offer a domain forwarding service that allows you to redirect your domain to another URL. Look for this option in your DNS settings, and set the forwarding address to `http://myproject.is-pro.dev`. Ensure that the "Permanent (301)" option is selected if available. 4. **Alternatively, use DNS and HTTP Redirect**: If your registrar does not offer a straightforward domain forwarding option, you can set an A record to point to an IP address that you control (or use a third-party redirect service), and then configure your server to issue a 301 redirect to `myproject.is-pro.dev`. For example, if you're using an Apache server, you can add the following to your `.htaccess` file: ```apache Redirect 301 / http://myproject.is-pro.dev/ ``` 5. **Verify the Redirect**: After setting up the redirect, visit `oldproject.com` in your web browser to ensure you are correctly redirected to `myproject.is-pro.dev`. Also, use tools like `curl` from the command line to verify the HTTP status code of the redirect: ```bash curl -I http://oldproject.com ``` You should see a `301 Moved Permanently` status code in the response headers. ## Common Pitfalls and Solutions - **Incorrect DNS Setup**: Double-check your DNS settings to ensure records are correctly pointing to your new subdomain or redirect service. - **Temporary vs. Permanent Redirects**: Always use a 301 redirect for permanent changes to preserve SEO rankings. - **Chain Redirects**: Avoid setting up a chain of redirects (e.g., `oldproject.com` -> `anotheroldproject.com` -> `myproject.is-pro.dev`). This can negatively impact SEO and user experience. ## Best Practices for Domain Migration - **Plan Ahead**: Schedule your redirect during a period of low traffic to minimize disruption. - **Test Thoroughly**: Verify that all parts of your site are correctly redirected, including subpages and resources. - **Update Internal Links**: Once the redirect is in place, update all internal links on your site to point to the new subdomain to avoid redirect chains. ## Performance Considerations - **Redirect Impact on Load Times**: While redirects are generally fast, having too many can increase page load times. Minimize the number of redirects in a chain. - **Caching and Redirects**: Be aware that redirects can sometimes be cached by browsers and intermediaries, potentially causing issues if you need to change the redirect target. ## Troubleshooting Redirect Issues - **Use Browser Developer Tools**: The Network tab in browser developer tools can help diagnose redirect issues by showing the redirect chain and response codes. - **Check Server Logs**: Server logs can provide detailed information about redirects, including any errors that might occur during the redirect process. - **Test from Different Locations**: Sometimes, DNS changes can take time to propagate globally. Test your redirect from different geographic locations to ensure it's working as expected worldwide. ## Conclusion and Next Steps Redirecting an old domain to your new subdomain on is-cool-me is a straightforward process that, when done correctly, can help maintain your online presence and search engine rankings. After setting up your redirect, monitor your website's performance and analytics to ensure a smooth transition for your users. Remember to update any external links to your site and notify search engines of your domain change to expedite the update of their indexes. ## FAQ 1. **Q: Can I redirect a subdomain of my old domain to my new subdomain?** A: Yes, you can redirect a subdomain (e.g., `blog.oldproject.com`) to your new subdomain (`myproject.is-pro.dev`) using the same methods described, by setting up a CNAME or A record for the subdomain. 2. **Q: How long does it take for a 301 redirect to be recognized by search engines?** A: The time it takes for search engines to recognize and update their indexes based on a 301 redirect can vary, but it's typically within a few weeks to a couple of months. 3. **Q: Will a 301 redirect preserve my website's backlinks?** A: Yes, a 301 redirect is the best way to preserve backlinks to your old domain. Search engines will transfer the link equity to the new URL. 4. **Q: Can I use a 301 redirect for HTTPS to HTTP or vice versa?** A: Yes, but ensure that your target URL (in this case, `myproject.is-pro.dev`) is correctly set up for HTTPS if that's what you're redirecting to, to avoid security warnings. 5. **Q: How do I handle email addresses associated with my old domain?** A: You will need to set up email forwarding or migrate your email service to your new domain to continue receiving emails sent to addresses at your old domain. ## Further Reading - **Is-cool-me Documentation**: For specific details on setting up and managing your subdomain on is-cool-me. - **Apache HTTP Server Documentation**: For detailed information on configuring redirects and other settings on an Apache server. - **Google Search Console Help**: For guidance on managing domain changes and redirects in the context of Google search rankings. - **Mozilla Developer Network (MDN)**: For comprehensive information on HTTP redirects, including 301 and other status codes.
Share this article Share on X Share on LinkedIn
Previous Set Up Uptime Monitoring for Your Subdomain Services Next A Step-by-Step Guide to Setting Up a Custom Subdomain for Your Blog

Related Articles

DNS

DNS Records Explained: A-Z Guide for Developers

Understand every DNS record type — A, AAAA, CNAME, MX, TXT, SPF, DKIM, DMARC, SRV, and CAA — with practical examples and common use cases for subdomain configuration.

Read More