In the digital realm, the way you manage your domains can significantly affect your online presence. One of the critical aspects of domain management is the effective use of domain redirects. If you’re utilizing domain.com for your hosting needs, you have access to a user-friendly platform for setting up these redirects. In this tutorial, we will explore what domain redirects are, their benefits, how to configure them via the domain.com dashboard, and discuss certain limitations, including the lack of HTTPS support.

What are Domain Redirects?

Domain redirects, also known as URL forwarding, are techniques used to make a web page available under more than one URL address. When a web browser attempts to open a URL that has been redirected, a page with a different URL is opened. Essentially, it’s like instructing the browser, “Don’t go here; go there instead.”

Examples and Benefits of Using Domain Redirects

1. Consolidating Domain Variants: If you own multiple variants of your domain (e.g., .net, .org, .com), you can redirect all of them to a single primary site. This practice ensures brand consistency and prevents competitors from using similar domain names.
2. Rebranding or Changing Domain Names: If your business undergoes rebranding and changes its name, you don’t want to lose your existing SEO juice. A redirect will bring visitors to your new domain without affecting your search engine ranking.
3. Tracking Marketing Efforts: Redirects can be used for marketing campaigns, allowing you to track how traffic reaches your site by using different URLs for the same page.
4. Improving User Experience: Redirects eliminate the confusion caused by broken or outdated links, leading users to updated pages or an alternative resource, thereby enhancing the user experience.

Configuring Domain Redirects using the domain.com Dashboard and Domain-Forward.com

We understand your frustration about being unable to forward your domain with domain.com; that’s why we have built a powerful solution called Domain-Forward.com.

Using our all-in-one solution, anyone can forward a domain over HTTPS without any hassle. And guess what? It only takes a couple of clicks to set everything up. 

What makes Domain-Forward.com absolutely special is that it grants users access to built-in HTTPS support and analytics, making it insanely easy for anyone to forward their domain without stress. 

Forwarding your domain using Domain-Forward.com is easy. All you need to do is create an account, set up your sources and the destination address, and configure some things at your DNS provider. 

In our example, we will be forwarding the domain “my-old-domain.xyz” to “mysite.com”.

Step 1: Register an account 

The first thing you want to do is sign up for an account, which only takes a few minutes to complete.

Step 2: Add your domain to Domain-Forward.com

Once you have registered an account, it’s time to add the domain you’d like to redirect. All you need to do is click on the option for “Add Redirect.”

Since we already have a domain with domain.com called ‘my-old-domain.xyz’, we need to integrate it into the Source URL field. To make things hassle-free for your website visitors, we recommend adding both ‘www’ and the non-www version.

And that’s not all. We must also set the Destination URL, where all the magic happens – your forward-to spot.

With our Source URLs and Destination URL now set, all we need to do is create our redirect. We recommend you leave the redirect type as 301, but if you are unsure exactly what redirect type you need then here’s our basic guide about URL forwarding.

Note: After completing the domain redirect, you’ll notice the DNS status as checking. We need to fix that. 

Step 3: Navigate to domain.com

To complete redirecting using Domain-Forward.com, we need to head over to domain.com to tweak DNS changes. 

To do that, log into the domain.com platform.

After logging in, we are shown the dashboard where we can adjust all of our settings regarding our domains on domain.com. Then choose the domain you would like to manage. If you only have one domain there, you’ll be redirected to the domain details right away. Next, click on “DNS & Nameservers” on the left sidebar.

If you followed the steps exactly as we showed you, you should have a page that looks something like this:

Step 4: Change the DNS

Now, let’s tweak our DNS settings. First, you want to click the three dots at the end of the @ domain A-type record. Here, you want to change the Value to 34.159.171.73. With that done, click Edit. You can change the TTL value to 1/2 Hour if you want the DNS changes to propagate slightly faster in the future.

Next, we also want to add an entry for the www subdomain. Add the same IP as for the @ domain and optionally set the TTL to 1/2 Hour.

Now, that’s all we need to do here. Just so you know you did the right thing, it should look something like this: 

You might have some other records there as well, but you can leave them as is. Only if you run into some redirection issues should you consider debugging why it doesn’t work.

Step 5: Verify DNS changes at Domain-Forward.com

Once your changes have been effected on domain.com, head over to Domain-Forward.com to see if the DNS changes reflect there as well. In our testing, it took around 2 hours, but your mileage may vary.

Here is what ours looks like, showing that our DNS change at domain.com was successful. 

Note: The DNS change isn’t always instant. It can take an hour or even up to 48h for the changes to go live. So have some patience.

Step 6: Verify Redirect Using Online Tools

Now that we have set up the domain forwarding and the DNS entries, it’s time to check if the redirection is working correctly. Below is an image from an online “redirect testing tool,” confirming our redirection is functioning correctly.

Final thoughts 

If you’ve made it this far, you can finally say goodbye to the headaches of redirecting with domain.com because Domain-Forward.com has got you covered.

Here is the exciting part – with Domain-Forward.com, you get free and automatic HTTPS support, giving your website that extra layer of security and trust, unlike domain.com, where you miss out on this fantastic feature.

If you found this post helpful (and we hope you did), show us some love and support by subscribing to our paid plans. By doing so, you’ll help us continue offering top-notch services and take our magic to new heights.

The post Domain.com Domain Redirects – A Comprehensive Guide appeared first on Domain Forward.

In the digital realm, the way you manage your domains can significantly affect your online presence. One of the critical aspects of domain management is the effective use of domain redirects. If you’re utilizing Bluehost for your hosting needs, you have access to a user-friendly platform for setting up these redirects. In this tutorial, we will explore what domain redirects are, their benefits, how to configure them via the Bluehost dashboard and discuss certain limitations, including the lack of HTTPS support.

What are Domain Redirects?

Domain redirects, also known as URL forwarding, are techniques used to make a web page available under more than one URL address. When a web browser attempts to open a URL that has been redirected, a page with a different URL is opened. Essentially, it’s like instructing the browser, “Don’t go here; go there instead.”

Examples and Benefits of Using Domain Redirects

1. Consolidating Domain Variants: If you own multiple variants of your domain (e.g., .net, .org, .com), you can redirect all of them to a single primary site. This practice ensures brand consistency and prevents competitors from using similar domain names.
2. Rebranding or Changing Domain Names: If your business undergoes rebranding and changes its name, you don’t want to lose your existing SEO juice. A redirect will bring visitors to your new domain without affecting your search engine ranking.
3. Tracking Marketing Efforts: Redirects can be used for marketing campaigns, allowing you to track how traffic reaches your site by using different URLs for the same page.
4. Improving User Experience: Redirects eliminate the confusion caused by broken or outdated links, leading users to updated pages or an alternative resource, thereby enhancing the user experience.

Configuring Domain Redirects using the Bluehost Dashboard and Domain-Forward.com

We understand your frustration about being unable to forward your domain with Bluehost; that’s why we have built a powerful solution called Domain-Forward.com.

Using our all-in-one solution, anyone can forward a domain over HTTPS without any hassle. And guess what? It only takes a couple of clicks to set everything up. 

What makes Domain-Forward.com absolutely special is that it grants users access to built-in HTTPS support and analytics, making it insanely easy for anyone to forward their domain without stress. 

Forwarding your domain using Domain-Forward.com is easy. All you need to do is create an account, set up your sources and the destination address, and configure some things at your DNS provider. 

In our example, we will be forwarding the domain “myolddomain.site” to “mysite.com”.

Step 1: Register an account 

The first thing you want to do is sign up for an account, which only takes a few minutes to complete.

Step 2: Add your domain to Domain-Forward.com

Once you have registered an account, it’s time to add the domain you’d like to redirect. All you need to do is click on the option for “Add Redirect.”

Since we already have a domain with Bluehost called ‘myolddomain.site’, we need to integrate it into the Source URL field. To make things hassle-free for your website visitors, we recommend adding both ‘www’ and the non-www version.

And that’s not all. We must also set the Destination URL, where all the magic happens – your forward-to spot.

With our Source URLs and Destination URL now set, all we need to do is create our redirect. We recommend you leave the redirect type as 301, but if you are unsure exactly what redirect type you need then here’s our basic guide about URL forwarding.

Note: After completing the domain redirect, you’ll notice the DNS status as checking. We need to fix that. 

Step 3: Navigate to Bluehost

To complete redirecting using Domain-Forward.com, we need to head over to Bluehost to tweak DNS changes. 

To do that, log into the Bluehost platform.

After logging in, we are shown the dashboard where we can adjust all of our settings regarding our domains on Bluehost. Next, click on Domains on the left sidebar.

Then choose the domain you would like to manage. If you only have one domain there, you’ll be redirected to the domain details right away.

In the domain details page, scroll all the way down, and under “Advanced tools” and “Advanced DNS Records”, click “Manage”.

It’s possible that you will be prompted whether you are sure that you are an advanced user. If you feel confident, then click continue.

If you followed the steps exactly as we showed you, you should have a page that looks something like this:

Step 4: Change the DNS

Now, let’s tweak our DNS settings. First, you want to click the edit button next to the @ domain A-type record. Here, you want to change the Value to 34.159.171.73. With that done, click Edit. You can change the TTL value to 15 minutes if you want the DNS changes to propagate slightly faster in the future.

Next, we also want to adjust the www domain records. Add the same IP as for the @ domain and optionally set the TTL to 15 minutes as well.

Now, that’s all we need to do here. Just so you know you did the right thing, it should look something like this: 

You might have some other records there as well, but you can leave them as is. Only if you run into some redirection issues should you consider debugging why it doesn’t work.

Step 5: Verify DNS changes at Domain-Forward.com

Once your changes have been effected on Bluehost, head over to Domain-Forward.com to see if the DNS changes reflect there as well. 

Here is what ours looks like, showing that our DNS change at Bluehost was successful. 

Note: The DNS change isn’t always instant. It can take an hour or even up to 48h for the changes to go live. So have some patience.

Step 6: Verify Redirect Using Online Tools

Now that we have set up the domain forwarding and the DNS entries, it’s time to check if the redirection is working correctly. Below is an image from an online “redirect testing tool,” confirming our redirection is functioning correctly.

Final thoughts 

If you’ve made it this far, you can finally say goodbye to the headaches of redirecting with Bluehost because Domain-Forward.com has got you covered.

Here is the exciting part – with Domain-Forward.com, you get free and automatic HTTPS support, giving your website that extra layer of security and trust, unlike Bluehost, where you miss out on this fantastic feature.

If you found this post helpful (and we hope you did), show us some love and support by subscribing to our paid plans. By doing so, you’ll help us continue offering top-notch services and take our magic to new heights.

The post Bluehost Domain Redirects – A Comprehensive Guide appeared first on Domain Forward.

Whether you’re rebranding, shifting to a new website, or preventing dead links, domain redirects are your go-to solution. In this tutorial, we’ll explore the concept of domain redirection, its benefits, and how to effectively configure redirects using the IONOS dashboard. Plus, we’ll delve into some crucial considerations, including the HTTPS limitations with IONOS redirects and other potential downsides.

What Are Domain Redirects and What Are They Used For?

Domain redirects, often known as URL forwarding, are techniques to make a web page available under more than one URL address. When a browser attempts to access a page with a redirected domain, it’s automatically sent to a different address. This process is seamless to the user and happens in a matter of milliseconds.

Some common uses for domain redirects include

1. Rebranding or changing domain names: Redirect old URLs to a new domain to maintain SEO rankings.
2. Simplifying complicated URLs: Create easy-to-remember access points to sections of your website.
3. Tracking marketing efforts: Redirect to the same destination through different URLs to track the effectiveness of marketing campaigns.
4. Preventing broken links: Ensure users never land on a dead page.

Benefits of Domain Redirects

• SEO Preservation: When done correctly, redirects can transfer the search engine ranking power from the old domain to the new one.
• User Experience: Redirects ensure your site visitors always end up where they’re supposed to, leading to a positive user experience.
• Simplified Maintenance: Managing content across several domains becomes easier, as everything points back to a single destination.

Configuring Domain Redirects in the IONOS Dashboard

Here’s a step-by-step guide to setting up your IONOS domain redirect. We have added images to make the process more visual. We have also listed some downsides and potential issues you might run into. Please read through them so that you understand the risks. In our example, we will be forwarding the domain “my-old-website.info” to “mysite.com”.

Step 1: Login to Your Account

Visit the IONOS website and sign in to your account dashboard.

Step 2: Manage Domains

After you have logged in, you’ll see the dashboard. In the menu at the top of the page, locate the section titled “Domains & SSL.” Click on it to view your registered domains.

Step 3: Select Domain

Choose the domain you want to redirect from your list of active domains. Just click on the name that looks like a link.

Step 4: Adjust Domain Settings

At the top of the screen, click on the button “Adjust Destination”.

After that, from the list of options, select “Forward Domain”.

Step 5: Set up your Redirect

First, input the destination where you want to redirect your domain. Next, look for the “Redirect type” setting. Here, you can choose between an HTTP redirect or a Frame redirect. You probably want to use the HTTP if you are planning to keep the redirects like that for a longer period. Frame redirects are not great for SEO.

Just to make sure you know which one you need, here’s our blog post on redirect types.

Step 6: Save Settings

After ensuring all information is accurate, save your settings. It might take a while for the redirect to propagate across the internet. It might take anywhere from 5 minutes to 24 hours.

Step 7: Test your Redirect

All that is left to do is to test whether the redirect works as expected or not. In our case, we configured an SSL certificate for the redirect as well, but we recommend you check whether it costs extra for you.

Important Security Considerations

It’s vital to note that IONOS domain redirection doesn’t support HTTPS out of the box since it doesn’t automatically install a certificate for the domain being redirected. This limitation means that visitors trying to access your site via HTTPS could encounter security warnings or browser messages indicating the connection is not secure. For most visitors, this means they won’t continue to your site.

There is a way to add certificates to your domain manually, but it isn’t clear whether these are paid or not. It doesn’t show the price while configuring it but the main IONOS site does show the certificate to cost around 10 USD per year.

Other Downsides of Using the IONOS Domain Redirection

While domain redirects are immensely beneficial, there are potential downsides within the IONOS environment:

1. SEO Impact: IONOS will configure the redirects as 302 (Found/Temporary) which will not carry over the SEO juice unlike 301, which does carry over the SEO juice.
2. Lack of automatic SSL: As mentioned, the absence of automatic HTTPS support for redirects can be a significant drawback, given the emphasis on web security today.
3. Propagation Delay: Changes to redirect settings can take up to 48 hours to reflect globally due to DNS propagation.
4. Limited Configuration Options: Advanced redirect rules, such as those based on the visitor’s location or device, are not supported.

Domain-Forward.com: Free and Automatic HTTPS Support

We understand your frustration about being unable to forward your domain over HTTPS with IONOS; that’s why we have built a powerful solution called Domain-Forward.com to help you resolve any domain redirect issues you might have with IONOS. 

Using our all-in-one solution, anyone can forward a domain over HTTPS without any hassle. And guess what? It only takes a couple of clicks to set everything up. 

What makes Domain-Forward.com absolutely special is that it grants users access to built-in HTTPS support and analytics, making it insanely easy for anyone to forward their domain without stress. 

Forwarding your domain using Domain-Forward.com is easy. All you need to do is create an account, set up your sources and the destination address, and configure some things at your DNS provider. 

If you are ready to overcome all the challenges you encounter when forwarding your domain with IONOS, you’re welcome to read our detailed step-by-step guide, which shows you how to use Domain-Forward.com to redirect your domain seamlessly. 

Step 1: Register an account 

The first thing you want to do is sign up for an account, which only takes a few minutes to complete.

Step 2: Add your domain to Domain-Forward.com

Once you have registered an account, it’s time to add the domain you’d like to redirect. All you need to do is click on the option for “Add Redirect.”

Since we already have a domain with IONOS called ‘my-old-website.info,’ we need to integrate it into the Source URL field. To make things hassle-free for your website visitors, we recommend adding both ‘www’ and the non-www version.

And that’s not all. We must also set the Destination URL, where all the magic happens – your forward-to spot.

With our Source URLs and Destination URL now set, all we need to do is create our redirect.

Note: After completing the domain redirect, you’ll notice the DNS status as checking. We need to fix that. 

Step 3: Navigate to IONOS

To complete redirecting using Domain-Forward.com, we need to head over to IONOS to tweak DNS changes. 

To do that, log into the IONOS platform, find your domain, and select the option for DNS.

If you followed the steps exactly as we showed you, you should have a page that looks something like this:

Step 4: Change the DNS

Now, let’s tweak our DNS settings. First, you want to click the edit button next to the A-type record. Here, you want to change the Value to 34.159.171.73. With that done, click Save. You can change the TTL value to 5 minutes if you want the DNS changes to propagate slightly faster in the future.

When you get a warning about the original redirect being disabled, just click Save again. The good thing with IONOS is that it also automatically adjusts the www domain records. That’s exactly what we would have done anyway so we don’t need to change anything there.

Now, that’s all we need to do here. Just so you know you did the right thing, it should look something like this: 

Step 5: Verify DNS changes at Domain-Forward.com

Once your changes have been effected on IONOS, head over to Domain-Forward.com to see if the DNS changes reflect. 

Here is what ours looks like, showing that our DNS change at IONOS was successful. 

Note: The DNS change isn’t always instant. It can take an hour or even up to 48h for the changes to go live. So have some patience.

Step 6: Verify Redirect Using Online Tools

Now that we have set up the domain forwarding and the DNS entries, it’s time to check if the redirection is working correctly. Below is an image from an online “redirect testing tool,” confirming our redirection is functioning correctly.

Final thoughts 

If you’ve made it this far, you can finally say goodbye to the headaches of redirecting with IONOS because Domain-Forward.com has got you covered.

Here is the exciting part – with Domain-Forward.com, you get free and automatic HTTPS support, giving your website that extra layer of security and trust, unlike IONOS, where you miss out on this fantastic feature. Additionally, it doesn’t support 301 redirects which is probably the redirect you want to use anyway if you are redirecting your whole domain. So be careful that you consider that aspect when thinking about the effects on SEO.

If you found this post helpful (and we hope you did), show us some love and support by subscribing to our paid plans. By doing so, you’ll help us continue offering top-notch services and take our magic to new heights.

The post IONOS Domain Redirects – A Comprehensive Guide appeared first on Domain Forward.

Whether you’re a small business owner, a creative individual, or someone who just wants to know how domain redirects work on Hostinger, rest assured that today’s guide has you covered.

Let’s jump right in, shall we?

Understanding Domain Redirects

Domain redirect, often referred to as URL forwarding, is a unique website management technique that allows site owners to send visitors who visit a particular domain name to a different web page. 

Simply put, it’s like setting up a signpost that guides anyone who lands on a specific website to another destination on the internet. 

Imagine for a minute that you have two distinct domain names, let’s call them my-old-website.cloud and destination.my-old-website.cloud, you can configure it in such a way that visitors who visit my-old-website.cloud are automatically redirected to destination.my-old-website.cloud. Doing this is useful for a lot of purposes, including: 

• Branding and consistency: If you own multiple domains, you can leverage domain redirects to consolidate them under a single domain. Doing this ensures that no matter which of your domain visitors type, they will end up at your main website. How cool can that be?

• Content organization: Using domain redirect is a brilliant way to help you redirect visitors to specific sections or pages of your website. For example, you can set up a redirect so that a visit to my-old-website.cloud/about, redirects visitors to the About Us page on destination.my-old-website.cloud. 

• Website migration: When moving your website to a new domain, leveraging redirects ensures visitors who visit your old domain are redirected seamlessly to your new website without encountering dead links or confusion. 

• Marketing campaigns: Redirects are incredibly amazing for marketing campaigns. You can set up a unique and easy-to-remember URL for a campaign. And once the campaign ends, you can redirect all that traffic back to your main website. 

Domain redirects provide site owners with a reliable tool to manage online pathways and enhance user experience. They ensure that your visitors never miss the intended content. 

Domain providers like Hostinger provide users with an intuitive and hassle-free way to set up redirects. By taking advantage of Hostinger domain redirects, you can easily steer your online traffic to where you want it to go.

If you want to learn more about how URL redirects work and what the best practices are, do check out our blog post on that topic.

Steps for implementing Domain Redirects using Hostinger

Now that we have provided some background on domain redirects in general, let’s teach you how to redirect a domain on Hostinger. 

Redirecting a domain on Hostinger isn’t rocket science. As a matter of fact, the process is pretty straightforward, and even a novice can redirect a domain without much hassle. There might be some usage and security issues which we will get to a bit later on.

Step 1: Log in to your Hostinger account

To begin, log in to your Hostinger account. Once you have successfully logged in to your account, click on the menu item “Domains”. 

Step 2: Manage domains

On the next page, you’ll see a list of domains you have access to. Navigate all the way down, and select the option for Manage domains for the domain you want to change.

Step 3: Forward domain

Now that you have selected the option to Manage the domain, a new page should launch. Simply navigate all the way down and select the option for “Forward domain to an existing website.”

Step 4: Enter domain redirect information

With the option to “Forward domain to an existing website” selected, you only need to type in the domain URL you’d like to redirect to. For this example, we will use destination.my-old-website.cloud as the URL to which we would like to redirect our original domain.

After entering your domain information, simply hit the Create button, and you’re all set.

If you followed the steps as we showed you, you should  have something like this shown on the “Domain forwarding” page: 

The screenshot above shows that we have successfully configured our original domain address to redirect to a new one (https://destination.my-old-website.cloud/). Next, let’s test if the redirect actually works as expected.

Step 5: Testing the redirect using HTTP

Now we want to check if the redirect works properly. After giving it some time for the DNS records to propagate, we can use a “redirect checker tool”. Using a tool like this we can see how the redirects are currently working for actual users visiting the original URL.

Looks like the HTTP redirects are working correctly. You can ignore the destination.my-old-website.cloud error. We haven’t set up an actual site on that address and that’s why the error “could not resolve host” is being shown.

Step 6: Testing if HTTPS redirection works

When we use HTTPS, we already get an error on the original domain itself. In the picture below you can see a technical description about the SSL certificate causing errors.

The issue here is that Hostinger domain forwarding does not configure an SSL certificate for the domain, which means that HTTPS (the secure protocol for websites) is not enabled. This is a significant downside as it can potentially impact the security and SEO ranking of your site. Visitors may also receive a warning that the connection is not secure, which may deter them from proceeding to your site.

As we can see from the picture below, when we use an “SSL checker” to validate whether the website is secure, no certificate is found for the domain. Let’s fix that.

Domain-forward.com: The Ultimate Solution to All Domain Redirect Issues

Using Domain-forward.com, you enjoy access to built-in HTTPS support and analytics, so you’re able to get a first-hand experience of how the redirects are used. 

When using Domain-forward.com to redirect your domain, you only need to create an account, set up your source and destination addresses, and configure your DNS provider. Trust us when we say it doesn’t get easier than this. 

Ready to bypass all of the roadblocks you are facing with your primary provider? Let’s show you how to use this incredible platform to redirect your domain.

Step 1: Create an Account

First things first, you need to create an account, which is pretty straightforward.

Step 2: Add your domain to Domain-forward.com

After successfully creating an account, it’s time to add the domain you’d like to redirect. To do that, click on the option to Add Redirect. 

Since we already have a domain with Hostinger, “my-old-web.site,” we will add the domain to the Source URL field. For a hassle-free experience, we recommend adding www and the apex (non-www). 

Also, we need to set the Destination URL, i.e., where we want to forward to. 

With all this information entered, we need to go ahead and create our redirect. 

Note: After creating the redirect, you’ll notice the DNS entries are detected. Unfortunately, the required values are different. We need to fix that. 

Step 5: Head over to Hostinger

To complete our domain redirect using Domain-Forward, we need to head to Hostinger to tweak the DNS changes. 

So log in to your Hostinger account, navigate to your Dashboard, and select the option for Manage for the domain you want to redirect. Under the domain forwarding settings, remove the old forwarding if it has been enabled.

Step 6: Change DNS settings

Now, it’s time to tweak our DNS settings. On the same page where you removed the domain forwarding, click on the “DNS records” menu item. In the list of records, you might have previously configured A or CNAME records that you will have to change. The image below shows the A record that we have to change. To do that, click on “Edit”.

Select the Type CNAME Record and enter @ as Name with edge.domain-forward.com as target. Please check that this is the value that is also provided for you in the Domain Forward app before you configure it like that. ALIAS or A records work as well, but we have opted for CNAME in this case.

It is possible that Hostinger will change the CNAME to ALIAS after you click “Update”, but that doesn’t matter.

With that done, we need to repeat the process. For the second option, select the CNAME record again and enter www as Name with ‘edge.domain-forward.com’ as the target.

Step 7: Verify DNS At Domain-Forward.com 

With our DNS changes now tweaked from the Hostinger backend, we only need to wait some time for the changes to be effected. Depending on the TTL set on those records, everything should be done in a few hours. 

Here is what it should look like after the changes have been effected. 

Step 8: Verify Redirect Using Online Tools

Now that we have configured the redirect in domain forward and the DNS entries as well, we can check if the redirection actually works. Below is an image that is taken from an online “redirect testing tool” and it does confirm that our redirection works correctly.

Conclusion

If you have read to this point, we are sure you’ll agree that the Domain-forward.com redirect option makes things much easier compared to when you only use Hostinger. The cool part is that the Domain-forward.com option offers full HTTPS support, something you don’t get with Hostinger. 

If you found this post helpful, you can support us by subscribing to our paid plans. It will go a long way to ensure we keep offering quality services. 

The post Hostinger Domain Redirects – A Simple Guide appeared first on Domain Forward.

This feature is crucial for maintaining the SEO ranking, managing multiple subdomains effortlessly, and ensuring a seamless user experience. Namecheap, a prominent domain and hosting service provider, offers a straightforward solution for configuring wildcard redirects. In this blog, we will delve into what wildcard redirects are, why they are beneficial, and how you can configure them via Namecheap’s dashboard.

What are Wildcard Redirects?

Wildcard redirects are a type of domain redirection that allows you to point all the sub-domains of a particular domain to another domain or sub-domain. This is extremely useful in cases where you have multiple subdomains and want them all to lead to a specific page or site.

Example: Suppose you own the domain my-old-web.site, and you have multiple sub-domains like blog.my-old-web.site, shop.my-old-web.site, and forum.my-old-web.site. If you decide to consolidate all these sub-domains into a new domain, say, mysite.com, a wildcard redirect will ensure that all traffic to your old sub-domains will be redirected to mysite.com seamlessly.

Benefits of Wildcard Redirects

SEO Preservation

Wildcard redirects are crucial for preserving SEO rankings when migrating to a new domain or consolidating sub-domains. They ensure that the link equity built over time is retained, as visitors and search engines are automatically redirected to the new domain. This seamless redirection maintains organic search performance and assists in building the authority of the new domain.

User Experience

A superior user experience is pivotal in retaining visitors, and wildcard redirects significantly contribute to this. They ensure that visitors are not met with broken links or 404 errors when trying to access old pages or sub-domains. Instead, they are smoothly redirected to the new domain, which is crucial for keeping the audience engaged and satisfied.

Simplified Management

Managing multiple sub-domains can be challenging, but wildcard redirects simplify this process significantly. By centralizing the redirection process, wildcard redirects eliminate the need to set up individual redirects for each sub-domain, saving time and effort. This simplified management is particularly beneficial for large websites or online enterprises with numerous sub-domains, allowing web administrators to focus on other essential aspects of website management and optimization.

How to Configure Namecheap Wildcard Redirects

Configuring a wildcard redirect on Namecheap is a simple process. If you aren’t sure how to set up redirects or you are not sure what the potential risks are then check out our URL redirection quick guide. For Namecheap, the steps you need to take to configure wildcard redirects are listed below:

Step 1: Sign Into the Namecheap Dashboard

If you aren’t logged in, you can log into the admin dashboard here. If you’re already logged in, you can continue to the second step. 

Step 2: Navigate to the Domain List 

After gaining access to your dashboard, scroll down and select the option for Domain List. The image below shows you exactly how to go about that: 

Step 3: Select the option for Manage

After clicking on the option for Domain List, a new page should launch. Scroll down to the domain you’d like to redirect and select the option for Manage. 

Step 4: Redirect Domains > Add Wildcard Redirect

Here is where things get interesting, so be patient while we walk you through. After clicking the option for Manage, scroll all the way down to the Redirect Domain section and click on the option for Add Wildcard Redirect. 

Step 5: Configure Wildcard Redirect

Enter the destination URL where all traffic should be redirected to. For the destination URL, you can also use HTTPS for a more secure experience. Once you’re happy, just click on the green checkmark to apply the changes.

Step 6: Check and Remove Unnecessary DNS Entries

If you already had some web hosting or other rules for the affected subdomains, then you also need to remove those entries from under the Advanced DNS view.

You can also see the created wildcard entry below highlighted. Make sure that you DO NOT delete that row because that also removes the wildcard configuration from the previous steps.

Step 7: Wait for Changes to be Applied

Save the changes, and the wildcard redirect should be active within 30 minutes. It can take longer depending on your previously used DNS settings and whether your computer is caching the old redirect somehow.

From the image below you can see that the wildcard redirect is configured in the “Redirect Domain” section.

Step 8: Test the Redirects

As we can see from using a redirect checker, the “shop.my-old-web.site” gets redirected correctly to the destination that we configured above.

We can see that the same is true for blog.my-old-web.site.

We had an already explicitly defined DNS entry configured for the root (and www) domains. This means that the wildcard does not apply to those two, and the traffic gets redirected to a different destination than the wildcard. In the image below, row #3 is showing a failure because “destination.my-old-web.site” isn’t hosted.

Step 9. HTTPS does not work

When we try the “shop” subdomain redirect with HTTPS, it unfortunately does not work. Let’s dig deeper into why it doesn’t work and what one of the options is to make it work.

Downsides of Namecheap Provided Redirects

The Lack of HTTPS Support

Even though the Namecheap solution was very easy to set up, there is a huge elephant in the room. Namecheap’s wildcard redirect solution does not support HTTPS since no SSL certificate is installed for your domain when you use the DNS-based redirects. An SSL testing tool shows us that there is no SSL certificate configured for the domain.

This is a significant downside as it can potentially impact the security and SEO ranking of your site. Visitors may also receive a warning that the connection is not secure, which may deter them from proceeding to your site.

Lack of Precise Control

Wildcard redirect is a one-size-fits-all solution, which might not work for those needing precise control over individual sub-domain redirection. For example, you might even have author-based subdomains for each author in the format of {author-user-name}.blog.my-old-web.site, which you might want to redirect to a different address and not mysite.com like the others.

Unfortunately, with Namecheap, it is not possible to achieve this with the default redirection toolkit. You can only configure one wildcard subdomain which will not let you define it detailed enough.

You can make it work by getting a hosting package from Namecheap and programming the webserver to redirect traffic using Apache redirects, but this might not be comfortable for most people. Especially if you don’t have much web development or technical background.

Domain-forward.com: The Ultimate Solution for Wildcard Redirects

Even though Namecheap provides basic support for forwarding your domain, their domain forwarding service is missing essential features like HTTPS and Analytics. 

When you execute a domain redirect on Namecheap, your destination domain won’t have an SSL certificate. Causing visitors to get SSL errors when visiting the domain via HTTPS. 

Thankfully, Domain-Forward is here to save the day. When you use our platform for domain redirects, we automatically install and manage the SSL certificate, ensuring it never expires. Read on for a step-by-step guide on how to forward a domain with HTTPS support. 

Step 1: Create an Account

First things first, you need to create an account, which is pretty straightforward.

Step 2: Add your domain to Domain-forward.com

After successfully creating an account, it’s time to add the domain you’d like to redirect. To do that, click on the option to Add Redirect. 

Since we already have a domain with Namecheap, “my-old-web.site,” we will add the wildcard version of the domain to the Source URL field. Also, we need to set the Destination URL, i.e., where we want to forward to. In our case, we want to forward all of the traffic to our new site, mysite.com.

If you have matching source paths (for example, both sites have a /contact page) for your pages also at your destination then you can leave “Path forwarding” on. If you want all of the traffic to be sent to the homepage, then leave it off.

With all this information entered, we need to go ahead and create our redirect using the button below.

Note: After creating the redirect, you’ll notice the DNS checking as detected, and the required values are different. We need to tweak that.  If no values are shown, try clicking “Check DNS” and see if the old value shows up.

Step 5: Head over to Namecheap

To complete our domain redirect using Domain-Forward, we need to head to Namecheap to tweak the DNS changes. 

So log in to your Namecheap account, navigate to your Dashboard, and select the option for Manage for the domain you want to redirect. 

When the domain details page loads, select the option for Advanced DNS

Step 6: Change DNS settings

Now, it’s time to tweak our DNS settings. If you have previously set up a URL redirect, you need to ensure you remove those records. 

After deleting any previous redirects you have, click on the option for ADD NEW RECORD.

Select the Type ‘CNAME Record and enter * as Host with edge.domain-forward.com as Value. Please check that this is the value that is also provided for you in the Domain Forward app before you configure it like that. IP entries work as well, but we have opted for CNAME in this case.

After providing all the necessary information, click on “Save all changes” or on the green checkmark at the end of the row.

Step 7: Verify DNS At Domain-Forward.com 

With our DNS changes now tweaked from the Namecheap backend, we only need to wait for a short while for the changes to be effected. Everything should be done in a few minutes or latest in a few hours depending on the old TTL set on those records. You can try clicking on “Check DNS” to have it update the entries in real-time.

Here is what it should look like after the changes have been detected by Domain Forward. 

Step 8: Verify Redirect Using Online Tools

Now that we have configured the domain and the DNS entries as well, we can check if the redirection actually works. Below are images that are taken from an online “redirect testing tool” and it does confirm that our redirection works correctly.

Conclusion

Wildcard redirects are a powerful tool for website owners looking to manage multiple sub-domains or migrate to a new domain while maintaining SEO rankings and a superior user experience. Although Namecheap provides an easy solution to configure wildcard redirects, the lack of HTTPS support is a noteworthy limitation. It’s advisable to weigh the pros and cons before opting for this solution, and perhaps consider alternative methods or providers if HTTPS redirection is crucial for your project.

If you have read to this point, we are sure you’ll agree that the Domain-forward.com redirect option makes things much easier compared to when you use Namecheap. The cool part is that the Domain-forward.com option offers full HTTPS support, something you don’t get with Namecheap.

If you found this post helpful, you can support us by subscribing to our paid plans. It will go a long way to ensure we keep offering quality services. 

The post Namecheap Wildcard Redirects: A Tutorial appeared first on Domain Forward.

What is domain forwarding?

For starters, domain forwarding is a unique process that allows domain owners to redirect users from one domain to another. Picture this scenario. Let’s say you have a domain called “my-old-domain.online” and you want to forward it to another website you own currently hosted on “destination.my-old-domain.online” you’ll need to set up domain forwarding.

This ensures that when users visit “my-old-domain.online in their primary browser, they will be automatically redirected to your main website at destination.my-old-domain.online. 

Why would you want to forward your domain?

Now, you might be wondering why anyone would want to forward their GoDaddy domain. To be honest, there are several reasons to implement a domain forward. On the one hand, forwarding your domain makes it easy for users to remember your website address. 

If you previously had a complicated or long domain name, forwarding it to something simpler and easy to remember allows users to remember your website easily. 

Another awesome reason to explore GoDaddy domain forward is to improve your website SEO. Here is the catch, when users enter your domain name in their preferred web browsers, Google and other popular search engines understand that your domain name has been forwarded to another website. So forwarding your domain name dramatically improves your site’s ranking in search results if your previous domain already had some ranking pages. This can eventually result in more traffic for your website. 

If you’re no longer interested in using the GoDaddy domain for your website but there is still some traffic going to the site, a smart thing to do is to forward. For instance, if you have decided to move your website to a new hosting provider and a new domain, you can forward your domain to your new website, making it easy for users with your old domain name saved or bookmarked to find your new website effortlessly. 

How to forward your GoDaddy domain

Now, let’s address the elephant in the room – forwarding your GoDaddy domain. If this is your first time attempting to forward a domain, it might be a little tricky. However, after reading our detailed step-by-step guide, you’ll be able to forward your GoDaddy domain easily. 

When you forward a domain registered with GoDaddy, you are essentially sending visitors to a different page or website any time they visit your domain. Domain forwarding is especially important when you already have a website designed elsewhere or, for example, want to connect your domain to a dedicated social media page. 

Here, check out our detailed guide for forwarding a GoDaddy domain. 

Step 1: Sign in to GoDaddy

Start by signing into your GoDaddy Domain Portfolio. If you don’t know how to navigate that page, clicking this link will take you there. After signing in, you should have a page that looks something like this: 

Looking at the image above, you’ll notice we have just one domain name. Yours might be more, in case you have different domain names. 

Step 2: Select domains to forward

With your domain portfolio page fully launched, you’ll need to select the check boxes next to the domain name. After selecting the checkbox next to the domain name, you’ll be presented with several options. 

Step 3: Start the forwarding process

From the options available, click on “More” and select Forward from the action menu.  

If you did everything exactly as we showed you, you should automatically be redirected to a new pop-up page where you need to make specific changes. Here is what that page looks like: 

Step 4: Select forwarding destination protocol

The next thing you want to do is choose between http:// or https://./ To do this, click the https:// dropdown button and select your preferred option. The video below shows you how that’s done. 

Keep in mind that this action is specific to the destination URL only. Let us also quickly add that the domain you are attempting to forward will not be SSL enabled or forwarded over HTTPS. If you need to set up HTTPS embedded forwarding, you must do that via your hosting platform. 

Step 5: Provide destination URL

After choosing between http:// or https://,/ you need to enter the destination URL your domain is forwarding to. Remember that the URL you need to enter here is where you want to send your visitors when they enter your domain name in their browser. 

Note: When entering your destination URL, there are some rules of thumb you need to adhere to strictly. 

• You must ensure your URL’s first and last character is a number or letter. 
• GoDaddy doesn’t support special characters such as period.
• You are allowed only a maximum of 1,000 characters. 
• Consecutive periods are prohibited
• Underscores are currently not supported by GoDaddy

Step 6: Select the forwarding type

Now that you have entered your destination URL, the next thing you need to do is choose your preferred forwarding type. Here are the current forwarding type supported by GoDaddy, along with their explanation: 

• Permanent (301): When you opt for this option, you’re basically sending users to a destination URL. More so, this option tells search engines to showcase your new site content as the permanent location for your domain name. This option will also carry over the SEO value from the old URL to the new one.

• Temporary (302): Choosing this option redirects users and search engines to a new site seemingly only for a limited time. None of the SEO value gets carried over and browsers will not cache the redirect type. 

• Forward with masking: This domain redirection option sends visitors to your domain to your preferred destination URL. The cool part is that it keeps your original domain name in the browser address bar. On top of that, it also provides you an option to set your preferred meta-tags for search domain info. 

If you opt for either the Permanent (301) or Temporary (302) redirect options, you won’t need to make any other changes. All you need to do is select Continue to save your forwarding settings. Alternatively, if you choose the Forward with Masking option, you’ll need to provide other additional details such as Title, Description, and Keywords. 

• Title: Typically, this entails providing a short phrase you want to be displayed on the search engine’s browser tab. 

• Description: Here, you’ll need to provide a brief explanation of your website. This shows up in search engine results. 

• Keywords: You need to provide a select list of keywords that describe the content and purpose of your website 

Note: You must verify your identity if you have activated Domain protection. Similarly, if you have two-step verification activated for at least 24 hours, you must provide the code sent via SMS by GoDaddy to complete the forwarding process.  

After executing the steps outlined in today’s guide, it will take GoDaddy between a few hours or, in some rare cases, up to 48 hours to update your domain records. 

That wasn’t too complicated, was it?

Issues with GoDaddy Domain Forward

While GoDaddy domain forwarding is straightforward, especially if you follow the steps we mentioned above, it still has some shortcomings. For instance, if you want to forward your domain name with HTTPS, you must do so through a hosting platform. This is because GoDaddy doesn’t offer SSL certificates for simply forwarded domains. 

We know this sounds a bit disappointing. But guess what? We have a brilliant solution that helps you solve the issue you have with GoDaddy domain forwarding, especially when it relates to not being able to forward over HTTPS. 

Domain-Forward.com: Forwarding With HTTPS Support

We understand your frustration about being unable to forward your domain over HTTPS with GoDaddy; that’s why we have built a powerful solution called Domain-Forward.com to help you resolve any domain redirect issues you might have with GoDaddy. 

Using our all-in-one solution, anyone can forward a domain over HTTPS without any hassle. And guess what? It only takes a couple of clicks to set everything up. 

What makes Domain-Forward.com absolutely special is that it grants users access to built-in HTTPS support and analytics, making it insanely easy for anyone to forward their domain without stress. 

Forwarding your domain using Domain-Forward.com is easy. All you need to do is create an account and set up your sources and the destination address, and configure some things at your DNS provider. 

If you are ready to overcome all the challenges you encounter when forwarding your domain with GoDaddy, you’re welcome to read our detailed step-by-step guide, showing you how to use Domain-Forward.com to redirect your domain seamlessly. 

Step 1: Register an account 

The first thing you want to do is signup for an account, which only takes a few minutes to complete.

Step 2: Add your domain to Domain-Forward.com

Once you have registered an account, it’s time to add the domain you’d like to redirect. All you need to do is click on the option for “Add Redirect.”

Since we already have a domain with GoDaddy called ‘my-old-domain.online,’ we need to integrate it into the Source URL field. To make things hassle-free for your website visitors, we recommend adding both ‘www’ and the non-www version.

And that’s not all. We must also set the Destination URL, where all the magic happens – your forward-to spot.

With our Source URLs and Destination URL now set, all we need to do is create our redirect.

Note: After completing the domain redirect, you’ll notice the DNS status as checking. We need to fix that. 

Step 3: Navigate to GoDaddy

To complete redirecting using Domain-Forward.com, we need to head over to GoDaddy to tweak DNS changes. 

To do that, log into the GoDaddy platform, find your domain, and select the option for DNS.

If you followed the steps exactly as we showed you, you should have a page that looks something like this:

Step 4: Change the DNS

Now, let’s tweak our DNS settings. First, you want to click the edit button next to the A-type record. Here, you want to change the Value to 34.159.171.73. With that done, click Save. 

With the changes above now effected, we also need to tweak DNS changes for the “www” record. So hit the edit button, under the option for value, change it to edge.domain-forward.com, and hit Save. 

Now, that’s all we need to do here. Just so you know you did the right thing, it should look something like this: 

Step 5: Verify DNS changes at Domain-Forward.com

Once your changes have been effected on GoDaddy, head over to Domain-Forward.com to see if the DNS changes reflect. 

Here is what ours looks like, showing that our DNS change at GoDaddy was successful. 

Note: The DNS change isn’t always instant. It can take an hour or even up to 48h for the changes to go live. So have some patience.

Step 6: Verify Redirect Using Online Tools

Now that we have set up the domain forwarding and the DNS entries, it’s time to check if the redirection is working correctly. Below is an image from an online “redirect testing tool,” confirming our redirection is functioning correctly.

As we happened to redirect to a page that does unfortunately not exist, we receive the error “Could not resolve host”. If we had redirected to an existing page then we would have received a successful response.

Final thoughts 

If you’ve made it this far, you can finally say goodbye to the headaches of redirecting with GoDaddy because Domain-Forward.com has got you covered.

Here is the exciting part – with Domain-Forward.com, you get full HTTPS support, giving your website that extra layer of security and trust, unlike GoDaddy, where you miss out on this fantastic feature.

If you found this post helpful (and we hope you did), show us some love and support by subscribing to our paid plans. By doing so, you’ll help us continue offering top-notch services and take our magic to new heights.

The post GoDaddy Domain Forwarding: Everything You Should Know appeared first on Domain Forward.

The Basics

AWS Route 53

This is Amazon’s scalable and highly available Domain Name System (DNS). It’s designed to give developers and businesses an extremely reliable and cost-effective way to route end users to Internet applications.

Amazon CloudFront

This is a fast content delivery network (CDN) service that securely delivers data, videos, applications, and APIs to your viewers globally with low latency and high transfer speeds. We are using CloudFront as it is one of the recommended methods from the official AWS Route 53 KB article. We also chose it as it is relatively easy to configure compared to the other AWS options.

Without further ado, let’s dive right in!

Step 1: Set up an AWS CloudFront Web Distribution

First, we will create a CloudFront web distribution for the domain we are redirecting from.

Sign in to the AWS Management Console and open the CloudFront console at https://console.aws.amazon.com/cloudfront/.

Choose Create Distribution.

In the Origin Settings section, type the domain you are redirecting to in the Origin Domain Name box.

In the Protocol radio, select the Match viewer option.

Leave the remaining settings in the Origin Settings section at their default values.

In the Default Cache Behavior Settings section, for Viewer Protocol Policy, choose Redirect HTTP to HTTPS and for Cache Policy, select CachingOptimized.

Leave the remaining settings in the Default Cache Behavior Settings section at their default values.

In the Web Application Firewall (WAF) section, you can select Do not enable security protections.

In the Settings section, for Alternate Domain Names (CNAMEs), type the domain you are redirecting from.

For SSL Certificate, in the Custom SSL Certificate, click on Request certificate.

The easiest is to select the DNS validation option and configure the validation CNAME entry under Domains that is given to you after you create the certificate.

You then have to go into your Route53 settings and input the CNAME entries for your redirected domain as requested from the certificate process.

It is possible that after a few minutes the DNS settings have been picked up and the certificate is also issued.

Once that is the case, go back to the browser tab where we input all of the information about the CloudFront distribution. In the Custom SSL certificate dropdown, select the ACM certificate that we just created. You might need to refresh the list with the button next to the dropdown.

Leave the remaining settings in the Settings section at their default values. Choose Create Distribution.

Step 2: Configure AWS Route53

Next, we will configure Route53 to redirect requests to the CloudFront distribution.

Open the Route53 console at https://console.aws.amazon.com/route53/.

In the navigation pane, choose Hosted zones and choose the hosted zone for the domain that you’re redirecting from.

Next, choose Create Record and in the Quick Create record dialog box, specify the following values:

• For Record name, type the domain you are redirecting from.
• For Record type, choose A – Routes traffic to an IPv4 address and some AWS resources.
• For Alias, choose Yes.
• For Alias target, choose the CloudFront distribution that you created in step 1.

And then choose Create records.

Voila! Your Route 53 and CloudFront are now configured to redirect traffic from one domain to another. The entire process can take some time, up to 24 hours, to propagate changes throughout the internet.

Now all we have to do next is to actually configure logic to redirect the users to the new domain.

Step 3: Configure a CloudFront Function

CloudFront Functions is a new serverless scripting capability that allows you to run JavaScript code at over 225+ Amazon CloudFront edge locations to augment, modify or generate HTTP(S) requests or responses. You can use these functions to implement lightweight, request/response manipulations that execute globally at low latency.

From the dashboard, select Create function.

In the Create function screen, provide a name and description that will make it easy to understand what the function is about. Then, click Create function.

Here’s an example of a CloudFront function that will redirect a request to a new domain, preserving the original path and query parameters.

/**
 * Patches lack of
 * https://developer.mozilla.org/en-US/docs/Web/API/Location/search in event.
 * Inspired by
 * https://github.com/aws-samples/amazon-cloudfront-functions/issues/11.
 * @param {import("aws-lambda"). CloudFrontFunctionsQuerystring} querystring The weird format exposed by CloudFront
 * https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/functions-event-structure.html#functions-event-structure-query-header-cookie
 * @returns {string} Tries to return the same as
 * https://developer.mozilla.org/en-US/docs/Web/API/URLSearchParams/toString
 */
function getURLSearchParamsString(querystring) {
    var str = [];

    for (var param in querystring) {
        var query = querystring[param];
        var multiValue = query.multiValue;

        if (multiValue) {
            str.push(multiValue.map((item) => param + '=' + item.value).join('&'));
        } else if (query.value === '') {
            str.push(param);
        } else {
            str.push(param + '=' + query.value);
        }
    }

    return str.join('&');
}

function handler(event) {
    var request = event.request;
    var newHost = "www.google.com";
    
    var query = request.querystring && getURLSearchParamsString(request.querystring) ? getURLSearchParamsString(request.querystring) : '';

    var response = {
        statusCode: 301,
        statusDescription: 'Permanent',
        headers: {
            "location": {
                "value": "https://" + newHost + request.uri + (query == "" ? "" : "?" + query)
            }
        }
    };
    
    return response;
}

PS. To make sure that your traffic gets redirected to the correct place, you need to replace the value of the newHost variable to your destination domain.

We then need to take the code snippet from above and paste it into the Function code section. After that, click on Save changes.

You then want to publish the function by clicking on Publish and then Publish function.

After that, you have to connect the function to the CloudFront distribution that we created in Step 1. You need to go back to the distribution and from the Behaviors, check the row, and click on Edit.

In the edit behavior view, scroll all the way down and configure the Viewer request and Viewer response as shown in the image above. You of course need to select your function which might have a different name.

If you don’t explicitly do this step then the function will not be used by the distribution and the users accessing the site receive a 404 error.

Step 4: Test the Setup

Once everything has been configured, then you can try to access them in the browser and see if the traffic is correctly forwarded. We can see from the image below that the traffic is forwarded and an HTTPS certificate is automatically assigned.

We can also see that the path (/images) and the query parameters (?x=1) are also forwarded.

Conclusion

That’s it for today’s tutorial. We hope you found it helpful. If you are using some other stack then feel free to check out our other posts to find a solution that fits for you.

Please note: AWS occasionally updates its interface, so the exact steps and descriptions may vary slightly. Always refer to the official AWS documentation for the most accurate information.

How can I do it without writing code?

If you are looking for an easy way to redirect a domain and not have to configure all of the technical infrastructure for it (including automatic HTTPS), then you should consider using the Domain Forward service.

When you use Domain Forward, then the whole process gets condensed to just Step 2. You can sign up using the link below and create your first redirect using the Getting Started guide.

The post Tutorial: How to Redirect Traffic from One Domain to Another Using AWS Route53 (& CloudFront) appeared first on Domain Forward.

What Are Redirects?

Redirects or URL forwarding is the process where a single URL is pointed to another URL. Essentially, when a user attempts to visit a specific URL (the source URL), they are automatically sent to a different URL (the target or destination URL). This action is usually seamless, and the user may not even be aware it has occurred.

Why Are Redirects Important?

Redirects are crucial for numerous reasons:

1. Website Renovation: Websites are often restructured, and as part of this, URLs might change. Redirects help ensure users and search engines find the correct pages after the changes.
2. SEO: By properly implementing redirects, you maintain your site’s SEO rankings. When a page with a high ranking is deleted or moved without a redirect, its search engine ranking is lost.
3. User Experience: Redirects prevent users from encountering broken links and ‘404 not found‘ errors, thereby enhancing their browsing experience. Additionally, they allow you to shorten or simplify your links which you can share with your users.
4. Security: HTTPS redirects are crucial for moving users from HTTP to the more secure HTTPS version of a site.

When to Use Redirects

Redirects should be used in the following instances:

1. Site or Page Moves: If you’re moving your site to a new domain or relocating specific pages, redirects will help maintain your SEO efforts and guide visitors to the correct location.
2. Making Links More Memorable: For example, your users are more likely to remember a link that looks like example.com/great-content as opposed to blog.example.com/2022/05/our-great-overview-of-the-current-trends.
3. Deletion of Pages: If you remove a webpage that users may have bookmarked or linked elsewhere, you can set up a redirect to send visitors to a relevant, existing page.
4. HTTP to HTTPS: As part of establishing a secure browsing environment, users trying to access the HTTP version of your website should be redirected to HTTPS.

Types of Redirects

There are several types of redirects, but the most common are 301, 302, and meta refresh redirects:

1. 301 (Permanent) Redirect: This indicates that the page has moved permanently. It is most commonly used when moving a site to a new domain or restructuring a website.
2. 302 (Temporary) Redirect: This is used when a page is moved temporarily, for instance, during a website redesign or maintenance.
3. Meta Refresh: This is a form of redirect implemented on the page level rather than the server level. It is often used for timed redirects (like “You will be redirected in 5 seconds”).

10 Redirect Best Practices

Here are some best practices for implementing redirects:

1. Use 301 Redirects for Permanent Moves: This tells search engines that the old page is no longer relevant and transfers the link equity to the new page.
2. Avoid Redirect Chains: These are multiple redirected jumps from the source to the final URL. They can cause slower loading times as each redirect requires additional processing and loss of link equity. The loss of link equity is considered to be up to 85% per redirect. This means that after 5 redirects, the carried-over value is only around 44%.
3. Update Your Internal Links: When you move a page, don’t just set up a redirect; also update the internal links pointing to that page.
4. Be Relevant: Make sure your redirects send users to a page with similar content. Misleading redirects can frustrate users and harm your SEO. Google is becoming more and more advanced when it comes to evaluating the usefulness (they call it people-first) of your content. If you are maliciously redirecting users and not showing them what they expected to see, you could be penalized.
5. Carefully Implement Wildcard Redirects: Wildcards can redirect large sets of URLs, but they should be used carefully to avoid unintentional redirects. With great power comes great responsibility – wildcard catch-all redirects can accidentally also overrule some explicit redirects that you wanted to redirect to some other place.
6. Prefer HTTPS over HTTP: Redirect users to the secure HTTPS version of your site to protect their information. This is now the standard way for most hosting providers and platforms anyway, but you might have to make some adjustments for some older pages.
7. Avoid Meta Refresh: These can confuse users and aren’t always recognized by search engines.
8. Test Your Redirects: Always test your redirects after implementation to make sure they work as intended. You can find various tools online, but the one we often come back to is this redirect checker.
9. Monitor Performance Post-Redirect: Keep an eye on your analytics to see if there are changes in traffic or search engine ranking after the redirect.
10. Regularly Audit Your Redirects: Ensure all redirects are still needed and functioning correctly.

Redirect FAQs

Q: Do redirects affect SEO?
A: Yes, poorly implemented redirects can harm your SEO, but correctly implemented ones can maintain or even boost your ranking. For example, 301 redirects will carry over the SEO value whereas 302 will not.

Q: Can redirects be undone?
A: Yes, you can remove a redirect anytime. However, this should be done carefully as it could affect your site’s SEO and user experience. Just make sure you only remove redirects that haven’t had any relevant traffic and that you don’t link internally anymore.

Q: How many redirects are too many?
A: It’s best to avoid chains of more than three redirects. Long redirect chains can slow site loading times and confuse search engines (confusing them means that your content will not be valued as high as it would be without the redirects).

Q: How can I set up redirects?

A: It really depends on the type of redirect you want to implement, your domain registrar, and your technical knowledge. We have put together a guide on how to redirect one domain to another using a variety of tools.

Conclusion

Redirects are a powerful tool when maintaining, moving, or restructuring a website. They allow for a smoother user experience, improved security, and the preservation of hard-earned SEO rankings. However, they should be used judiciously and monitored carefully to ensure they are achieving their intended purpose.

The post URL Redirects and Forwarding: The Basics appeared first on Domain Forward.

If you have a domain on Namecheap and want to know how to redirect your domain, this guide has everything you’re looking for and more. 

But before we jump into the nitty-gritty of Namecheap redirect domain, here are some benefits of using URL redirects you should know:

• Improve SEO: Domain redirecting is a brilliant strategy for improving a website’s SEO. You can significantly improve your site ranking across different search engines by simply passing link juice from an old URL to a new one. 

• Increase traffic: Sending users from an old to a new website increases your website traffic. It’s highly recommended for site owners who want to change their domain to a new URL structure without losing traffic. 

• Improved user experience: Redirecting your visitors to the new domain helps to improve their overall experience, and here is why. By redirecting your old domain to a new URL, users don’t need to know your new URL to visit it. 

Now that we have provided some background on URL redirects and listed a few benefits of domain redirects, let’s jump into the practical aspects of Namecheap domain redirects. 

How to Redirect a Domain on Namecheap 

Redirecting your domain on Namecheap might seem tricky, especially if you’re doing it for the first time. But don’t worry; we have compiled a detailed step-by-step tutorial to guide you. 

Let’s cut to the chase and bring you all the exciting details. 

Step 1: Sign into your Namecheap

If you aren’t logged in, you must do so immediately. If you’re logged in, you can continue to the second step. 

Step 2: Navigate to the Domain List 

After gaining access to your dashboard, scroll down and select the option for Domain List. The image below shows you exactly how to go about that: 

Step 3: Select the option for Manage

After clicking on the option for Domain List, a new page should launch. Scroll down to the domain you’d like to redirect and select the option for Manage. 

Step 4: Redirect Domains > Add Redirects

Here is where things get interesting, so be patient while we walk you through. After clicking the option for Manage, scroll all the way down to the Redirect Domain section and click on the option for Add Redirect. 

Step 5: Add your domain redirect credentials

With the option for “Add Redirect” selected, you should notice a new field where you need to type in your domain source URL (my-old-web.site), and another field where you need to enter the Destination URL (https://destination.my-old-web.site)/

Note: The Destination URL is where we are redirecting our domain to. 

With your Source URL and Destination URL entered, simply click on the checkmarks to save the changes. 

Step 6: Make Changes to Advanced DNS

After saving the changes for the domain redirect, you might need to make some changes to Advanced DNS, so navigate to the Advanced DNS tab and check if there are any conflicting records, such as CNAME or URL redirect records with different values but set for the same hosts. If you find any conflicting records, you must delete those for the domain redirect to work correctly. 

In our case, we don’t have any conflicting records, so we don’t need to make any changes. If you notice any conflicting changes, all you need to do is delete them. It’s as simple as that. 

Namecheap Domain Redirect Shortcomings

While redirecting your domain on Namecheap isn’t as challenging as you imagined, it’s important you know that Namecheap domain redirect isn’t compatible with custom nameserver configurations. And that’s because the Namecheap domain redirect service is only available if you’re using BasicDNS, PremiumDNS, or FreeDNS nameservers. 

What this means is that if you have recently tweaked the DNS settings of your domain to use a third-party name server, you’ll not be able to set domain redirects on Namecheap. 

As if that isn’t already frustrating enough, HTTPS traffic redirection doesn’t work. Even if you somehow managed to get around it, you’ll discover that HTTPS traffic will show errors for most browsers. 

The other not-so-cool aspect of Namecheap domain redirects is that it can take time to take effect. While Namecheap says domain redirects usually take effect in 30 minutes, users sometimes have to wait hours or even days for their domain redirects to go live. This can be an issue, especially if you need to redirect traffic to a new website quickly. 

Domain-forward.com: The Ultimate Solution to All Domain Redirect Issues

We know how frustrating it can be not to be able to use your preferred third-party DNS service or HTTPS with Namecheap redirects, that’s why we have created a powerful solution that helps you bypass all of the roadblocks you’re having with your primary provider. 

With Domain-foward.com, it takes only a few clicks to redirect your domain. And guess what, that’s not the most thrilling part. 

Using Domain-forward.com, you enjoy access to built-in HTTPS support and analytics, so you’re able to get a first-hand experience of how the redirects are used. 

When using Domain-forward.com to redirect your domain, you only need to create an account, set up your source and destination addresses, and configure your DNS provider. Trust us when we say it doesn’t get easier than this. 

Ready to bypass all of the roadblocks you are facing with your primary provider? Let’s show you how to use this incredible platform to redirect your domain.

Step 1: Create an Account

First things first, you need to create an account, which is pretty straightforward.

Step 2: Add your domain to Domain-forward.com

After successfully creating an account, it’s time to add the domain you’d like to redirect. To do that, click on the option to Add Redirect. 

Since we already have a domain with Namecheap, “my-old-web.site,” we will add the domain to the Source URL field. For a hassle-free experience, we recommend adding www and the apex (non-www). 

Also, we need to set the Destination URL, i.e., where we want to forward to. 

With all this information entered, we need to go ahead and create our redirect. 

Note: After creating the redirect, you’ll notice the DNS checking as detected, and the required values are different. We need to tweak that. 

Step 5: Head over to Namecheap

To complete our domain redirect using Domain-Forward, we need to head to Namecheap to tweak the DNS changes. 

So log in to your Namecheap account, navigate to your Dashboard, and select the option for Manage for the domain you want to redirect. 

When the new page loads, select the option for Advanced DNS

Step 6: Change DNS settings

Now, it’s time to tweak our DNS settings. If you have previously set up a URL redirect, you need to ensure you remove those records. 

After deleting any previous redirects you have, click on the option for ADD NEW RECORD.

Select the Type ‘ALIAS Record and enter @ as Host with edge.domain-forward.com as Value. Please check that this is the value that is also provided for you in the Domain Forward app before you configure it like that. CNAME or IP entries work as well, but we have opted for ALIAS in this case.

With that done, we need to repeat the process. For the second option, select the ALIAS Record and enter www as Host with ‘edge.domain-forward.com’ as value. If you did everything right, you should have something like this: 

After providing all the necessary information, click on “Save all changes.”

Step 7: Verify DNS At Domain-Forward.com 

With our DNS changes now tweaked from the Namecheap backend, we only need to wait some time for the changes to be effected. Depending on the TTL set on those records, everything should be done in a few hours. 

Here is what it should look like after the changes have been effected. 

Step 8: Verify Redirect Using Online Tools

Now that we have configured the domain and the DNS entries as well, we can check if the redirection actually works. Below is an image that is taken from an online “redirect testing tool” and it does confirm that our redirection works correctly.

Conclusion

If you have read to this point, we are sure you’ll agree that the Domain-forward.com redirect option makes things much easier compared to when you use Namecheap. The cool part is that the Domain-forward.com option offers full HTTPS support, something you don’t get with Namecheap. 

If you found this post helpful, you can support us by subscribing to our paid plans. It will go a long way to ensure we keep offering quality services. 

The post Namecheap Domain Redirect – Everything You Should Know appeared first on Domain Forward.

What Is URL Masking?

URL masking involves keeping the same URL (or the website address) in a browser’s address bar while the user navigates from page to page or even across different websites. In simple terms, even though a user navigates to different pages, the URL displayed remains constant.

This might sound odd to you, as typically, URLs are a direct indicator of the web page’s content and location on the server. However, URL masking serves specific purposes, as we’ll delve into later.

How Does URL Masking Work?

URL masking primarily involves two components: DNS (Domain Name System) and an HTML frame or iframe. Here’s the step-by-step process:

1. Domain Name System (DNS) Settings: The first step involves the domain settings. When a user types in a URL, the DNS looks up the corresponding IP address to find where the website is hosted. In URL masking, the DNS is set to point to a hosting service that serves an HTML frame instead of the intended website.
2. HTML Frame or Iframe: This frame contains the content from the actual URL the user is supposed to navigate to. The main page URL remains the same, while the frame content changes depending on the actual page the user navigates to.

Thus, URL masking can be thought of as a sort of ‘sleight of hand.’ The user thinks they’re at one place (as indicated by the URL), but they’re actually somewhere else (as indicated by the frame content).

What are the Benefits and Uses of URL Masking?

Although URL masking comes with its share of potential issues, it also offers several key benefits when used correctly and responsibly. Here’s a closer look at some of these advantages:

Simplifying Complex URLs

Long, complex URLs filled with parameters can be daunting for users and may discourage them from clicking a link. With URL masking, you can simplify these complex URLs, presenting users with cleaner, shorter URLs that are more appealing and user-friendly. This can especially be beneficial in areas like affiliate marketing, where the link’s appearance can significantly impact click-through rates.

Reinforcing Brand Identity

URL masking allows you to maintain consistent branding across your website by displaying a preferred domain name in the address bar. For example, if your site is hosted on a third-party platform that doesn’t allow custom domains, you can use URL masking to show a domain that aligns with your brand. This way, no matter what page a user is on, your chosen domain remains visible, strengthening brand recognition.

Streamlining Social Media and Marketing Campaigns

In marketing campaigns, especially on social media, having a consistent, recognizable URL can improve the visibility of your brand. It allows your audience to quickly identify the source of the content and can increase trust in your marketing communications.

Enhancing User Privacy

With URL masking, the underlying directory structure of a website remains hidden from the user, offering an added layer of privacy. While this is not a foolproof way to secure a website, it does provide a certain degree of obscurity that can make it more challenging for malicious users to understand your website’s structure.

Creating Memorable URLs

URL masking can be used to make web addresses more memorable or meaningful. This can be particularly advantageous in print advertising or any other format where a user needs to remember the URL.

While these benefits can significantly enhance user experience and marketing efforts, remember that URL masking should be used responsibly. Misuse can lead to significant issues, including potential ranking penalties from search engines and analytics complications. So, always weigh the pros and cons before deciding to implement URL masking on your website.

What Are the Drawbacks?

Despite these benefits, there are several significant downsides to URL masking:

• Search Engine Optimization (SEO) Issues: Search engines like Google value content transparency and accessibility. URL masking can hinder the ability of search engines to index a website properly, leading to potential ranking penalties.
• Analytics Complications: Because the URL doesn’t change as a user navigates through a site, it can be difficult to track user behavior accurately using standard analytics tools.
• Potential for Misuse: Because URL masking can hide the true destination of a link, it can be used maliciously, making it harder for users to identify phishing attempts or other forms of deceptive online behavior.

Alternatives to URL Masking

While URL masking can be helpful in certain scenarios, it’s important to remember that there are other, often better, alternatives available that can achieve similar results without the associated downsides. Here are a few alternatives to consider:

URL Redirects

A URL redirect, also known as URL forwarding, is a technique to send a visitor from one URL to another. Unlike URL masking, URL redirects allow the browser’s address bar to update with the new URL, maintaining transparency with the visitor. It’s also more SEO-friendly compared to URL masking.

One option is to use the Domain Forward tool to implement the redirects so that the SEO gods are not displeased.

URL Shortening

URL shorteners like Bit.ly, TinyURL, or Google’s Firebase Dynamic Links, condense long URLs into shorter ones that are more user-friendly. They don’t hide the destination URL completely, as most URL shorteners offer a preview feature to see the actual URL before clicking.

Custom Domain Names

Most third-party platforms nowadays offer custom domain functionality, allowing you to replace their domain with your own. This is the most straightforward way to keep your branding consistent without resorting to URL masking.

Subdomains and Subdirectories

Subdomains and subdirectories allow you to create unique URLs under your main domain. This way, you can have ‘blog.yourdomain.com’ or ‘yourdomain.com/blog’, maintaining your branding while being transparent about the URL structure.

Domain Forward has the functionality to implement the redirects in any way you would like to. From a subdomain to a subdirectory or from a subdirectory to a subdomain.

How to Use URL Masking From your Hosting Provider

If you still decide to implement URL masking, here are the general steps:

1. Purchase a domain from a domain registrar.
2. In the domain settings, set the DNS settings to forward to the desired URL.
3. Enable URL masking in the settings, which will keep the original domain in the address bar.
4. Add a title and meta description if necessary. This will display on search engines and when the site is shared on social media.

Please note that the specifics of how to enable URL masking will vary depending on the domain registrar and hosting provider you’re using.

How to Use URL Masking with an HTML Example

URL masking primarily uses an HTML <iframe> to display the content of another webpage within a page of your own domain. However, to change the title, description, and search terms, you need to add the appropriate meta tags in the <head> section of your HTML.

Here’s a basic example of what this might look like:

<!DOCTYPE html>
<html>
<head>
    <title>Your Custom Page Title</title>
    <meta name="description" content="Your short description for the page goes here.">
    <meta name="keywords" content="your,search,terms,go,here">
</head>
<body>
    <iframe src="http://example.com/" style="border:0px #ffffff none;" name="myiFrame" scrolling="no" frameborder="1" marginheight="0px" marginwidth="0px" height="100%" width="100%" allowfullscreen></iframe>
</body>
</html>

In the above example:

• The <title> tag is used to specify the page title. This is what appears in the title bar of the browser and as the title in search engine results.
• The <meta name="description"> tag provides a short description of the webpage. This often appears under the title in search engine results.
• The <meta name="keywords"> tag is where you would list your search terms (keywords). Note that many search engines have stopped using this tag for ranking purposes, but it can still be used for your own reference or other non-ranking purposes.
• The <iframe> tag is used to embed the actual content from another webpage. In the src attribute, replace http://example.com/ with the URL of the page you want to display.

Remember, the specifics of how to implement URL masking may vary depending on your domain registrar and hosting provider. Always ensure to follow their guidelines and maintain best practices for HTML coding.

Conclusion

URL masking is a potent tool in certain circumstances. It can lend a more professional appearance to a URL or protect user privacy. However, its potential for misuse and the issues it can cause with SEO and analytics means that it should be used carefully, and only when necessary.

Hopefully, this article has provided you with a good understanding of URL masking and its potential applications. Always remember to use it responsibly and consider the potential implications of your website’s usability and discoverability.

How can I do it without writing code?

If you feel that URL masking is the way to go for you but you don’t want to implement the HTML or web-server-based logic yourself, then you should consider using the Domain Forward service. You can sign up using the link below and create your first redirect using the Getting Started guide.

The post URL Masking: What is it and how does it work? appeared first on Domain Forward.