Moz Q&A is closed.
After more than 13 years, and tens of thousands of questions, Moz Q&A closed on 12th December 2024. Whilst we’re not completely removing the content - many posts will still be possible to view - we have locked both new posts and new replies. More details here.
I have a question about the impact of a root domain redirect on site-wide redirects and slugs.
-
I have a question about the impact (if any) of site-wide redirects for DNS/hosting change purposes.
I am preparing to redirect the domain for a site I manage from https://siteImanage.com to https://www.siteImanage.com. Traffic to the site currently redirects in reverse, from https://www.siteImanage.com to https://siteImanage.com.
Based on my research, I understand that making this change should not affect the site’s excellent SEO as long as my canonical tags are updated and a 301 redirect is in place. But I wanted to make sure there wasn’t a potential consequence of this switch I’m not considering. Because this redirect lives at the root of all the site’s slugs and existing redirects, will it technically produce a redirect chain or a redirect loop? If it does, is that problematic?
Thanks for your input!
-
@mollykathariner_ms said in I have a question about the impact of a root domain redirect on site-wide redirects and slugs.:
I have a question about the impact (if any) of site-wide redirects for DNS/hosting change purposes.
I am preparing to redirect the domain for a site I manage from https://siteImanage.com to https://www.siteImanage.com. Traffic to the site currently redirects in reverse, from https://www.siteImanage.com to https://siteImanage.com.
Based on my research, I understand that making this change should not affect the site’s excellent SEO as long as my canonical tags are updated and a 301 redirect is in place. But I wanted to make sure there wasn’t a potential consequence of this switch I’m not considering. Because this redirect lives at the root of all the site’s slugs and existing redirects, will it technically produce a redirect chain or a redirect loop? If it does, is that problematic?
Thanks for your input!When implementing site-wide redirects for DNS/hosting change purposes, it's essential to consider the potential impact on SEO and any potential issues that may arise. In your specific case of redirecting from https://siteImanage.com to https://www.siteImanage.com, there are a few things to keep in mind.
Firstly, updating your canonical tags and implementing a 301 redirect is indeed the recommended approach to maintain SEO value during the domain redirection process. These measures ensure that search engines understand the change and transfer the ranking signals appropriately.
Regarding your concern about redirect chains or loops, it's important to handle the redirects correctly to avoid any negative consequences. If the current redirect from https://www.siteImanage.com to https://siteImanage.com exists, and you add a new redirect from https://siteImanage.com to https://www.siteImanage.com, it could potentially create a redirect chain or loop.
To prevent this issue, you should ensure that the old redirect from https://www.siteImanage.com to https://siteImanage.com is removed once the new redirect is in place. This way, you have a single 301 redirect directly from the non-www version to the www version of the site, without creating a redirect chain.
By implementing the redirect correctly and ensuring there are no redirect chains or loops, you can minimize any potential negative impact on SEO. It's always a good practice to carefully monitor your website's performance after making such changes to address any unforeseen issues promptly.
If you have any further questions or concerns, please feel free to ask.
-
@mollykathariner_ms Redirecting a domain from https://siteImanage.com to https://www.siteImanage.com should not have a significant impact on the site's SEO as long as you handle the redirect properly. However, you are correct in considering the possibility of redirect chains or loops, which can have negative consequences if not handled correctly.
A redirect chain occurs when there are multiple redirects in a sequence before reaching the final destination. For example:
https://siteImanage.com redirects to https://www.siteImanage.com
https://www.siteImanage.com redirects to https://www.siteImanage.com/page1
https://www.siteImanage.com/page1 redirects to https://www.siteImanage.com/page2
If you have a redirect chain like this, it can impact performance and user experience, as each redirect adds an additional request and increases the page load time.On the other hand, a redirect loop occurs when two or more pages continuously redirect to each other. For example:
https://siteImanage.com redirects to https://www.siteImanage.com
https://www.siteImanage.com redirects back to https://siteImanage.com
A redirect loop can prevent users from accessing your site and negatively affect search engine crawling and indexing.To avoid these issues, it's important to set up a proper redirect from https://siteImanage.com to https://www.siteImanage.com. You should implement a single 301 redirect from the non-www version to the www version of the site. This ensures that all traffic, including search engines and users, is directed to the correct URL in a single step.
Once you have implemented the 301 redirect, it's a good practice to update the canonical tags on your web pages to reflect the preferred URL (https://www.siteImanage.com). This helps search engines understand the preferred version of your site and consolidate ranking signals.
By implementing the redirect correctly and updating the canonical tags, you should be able to make the domain change without significant negative consequences for SEO. However, it's always a good idea to monitor your site's performance and rankings after the switch to ensure everything is functioning as expected.
-
Depending upon how you've set up your previous redirects, it could be a problem, but I suspect you'll be fine.
In my experience, a small redirect chain won't cause a massive issue and unless you already have some multi-step redirects going on, your new plan won't put you at risk of more than two steps anyway. Obviously, a loop would cause serious issues, but I don't think you are at risk of this.
Your redirects should be relative to absolute, i.e. /oldpage to https://siteImanage.com/newpage. In this case, you would just need to update your absolute paths to the new url. If you ensure these are matched first, then you would only have one redirect regardless of whether the client hits the www or non-www domain. If the full domain redirect is matched first, you'll end up for two steps for those people hitting only pages on the old domain
If your redirects are matching based on relative links and redirecting to relative urls (as some plugins do), i.e. /oldpage redirects to /newpage, then you'll end up with a two-step process if someone follows an old link; First, the site will redirect from non-www to www, and then it will redirect to the correct page.
If you have redirects such as "https://siteImanage.com/oldpage" redirecting to "https://siteImanage.com/newpage" then you would create a two-step process again, first to the new page and then to the new domain. Of course, your redirects wouldn't work on the new domain as they wouldn't match, which may or may not be a problem for you.
Got a burning SEO question?
Subscribe to Moz Pro to gain full access to Q&A, answer questions, and ask your own.
Browse Questions
Explore more categories
-
Moz Tools
Chat with the community about the Moz tools.
-
SEO Tactics
Discuss the SEO process with fellow marketers
-
Community
Discuss industry events, jobs, and news!
-
Digital Marketing
Chat about tactics outside of SEO
-
Research & Trends
Dive into research and trends in the search industry.
-
Support
Connect on product support and feature requests.
Related Questions
-
Our clients Magento 2 site has lots of obsolete categories. Advice on SEO best practice for setting server level redirects so I can delete them?
Our client's Magento website has been running for at least a decade, so has a lot of old legacy categories for Brands they no longer carry. We're looking to trim down the amount of unnecessary URL Redirects in Magento, so my question is: Is there a way that is SEO efficient to setup permanent redirects at a server level (nginx) that Google will crawl to allow us at some point to delete the categories and Magento URL Redirects? If this is a good practice can you at some point then delete the server redirects as google has marked them as permanent?
Technical SEO | | Breemcc0 -
Google is still indexing the old domain a year after 301 redirects are put in place
Hi there, You might have experienced this before but for me this is the first. A client of mine moved from domain A (www.domainA.com) to domain B (www.domainB.com). 301 redirects are all in place for over a year. But the old domain is still showing in Google when you search for "site:domainA.com" The HTTP Header check shows this result for the URL https://www.domainA.com/company/cookie-policy.aspx HTTP/1.1 301 Moved Permanently =>
Technical SEO | | iQi
Cache-Control => private
Content-Length => 174
Content-Type => text/html; charset=utf-8
Location => https://www.domain_B_.com/legal/cookie-policy
Server => Microsoft-IIS/10.0
X-AspNetMvc-Version => 5.2
X-AspNet-Version => 4.0.30319
X-Powered-By => ASP.NET
Date => Fri, 15 Mar 2019 12:01:33 GMT
Connection => close Does the redirect look wrong? The change of address request was made on Google Console when the website was moved over a year ago. Edit: Checked the domainA.com on bing and it seems that its not indexed, and replaced with domainB.com, which is the right. Just Google is indexing the old domain! Please let me know your thoughts on why this is happening. Best,0 -
Forwarding a .org domain to a .com domain: any negative impact to consider?
Hello! I have a question I've been unable to find a clear answer to. My client's primary domain is a .com with a satisfactorily high DA. My client owns the .org version of its domain (which has a very low DA, I suppose due to inactivity) but has never forwarded it on. For branding/visibility/traffic reasons, I'd like to recommend they set up the .org domain to forward to the .com domain, but I wanted to ask a few questions first: 1. Does forwarding low-value DA domains to high-value DA domains have any negative authority/SEO impact? 2. If the .org domain was to be forwarded, am I correct that an SSL cert is not necessary for it if the .com domain has an SSL cert? Thanks in advance!
Technical SEO | | mollykathariner_ms1 -
We switched the domain from www.blog.domain.com to domain.com/blog.
We switched the domain from www.blog.domain.com to domain.com/blog. This was done with the purpose of gaining backlinks to our main website as well along with to our blog. This set us very low in organic traffic and not to mention, lost the backlinks. For anything, they are being redirected to 301 code. Kindly suggest changes to bring back all the traffic.
Technical SEO | | arun.negi0 -
URL Structure On Site - Currently it's domain/product-name NOT domain/category/product name is this bad?
I have a eCommerce site and the site structure is domain/product-name rather than domain/product-category/product-name Do you think this will have a negative impact SEO Wise? I have seen that some of my individual product pages do get better rankings than my categories.
Technical SEO | | the-gate-films0 -
Domain prefix changed, will this impact SEO?
Our web development team have changed our domain prefix from www to non www due to a server change. Our SSL certificate would not be recognised under www and would produce a substantial error message when visiting the secure parts of our website. To prevent issues with old links they have added a permanent 301 redirect from www. to non www. urls until our sitemap catches up. Would this impact our SEO efforts or would it have no impact as a redirect has been placed? Thanks
Technical SEO | | Jseddon920 -
Transfer a Main Domain to a Sub-Domain
My IT department tells me they want to transfer my main site domain, which has been in existence since 1999 as an e-commerce site (maindomain.com) to a sub-domain (www2.maindomain.com) or a completely new domain (newdomain.net). This is because we are launching a new website and B2C e-commerce engine, but we still have to maintain the legacy B2B e-commerce engine which contains hard-coded URLs, and both systems can't use the same domain. I've been researching the issue across SEOmoz, but I haven't come across this exact type of scenario (mostly I've seen a sub-domain to new domain). I see major problems with their proposal, including negative SEO impact, loss of domain authority/ranking and issues with branding. Does anyone know the exact type of impact I can expect to see in this scenario and specific steps I should go about to minimize the impact? Btw, I will be using Danny Dover's guide on properly moving domains where appropriate. Thanks!
Technical SEO | | AscendLearning0 -
First click on SEO redirecting to a competitor site?
I just experienced something VERY odd and wondered if any of you had an idea of what it might be. When I did a search on Google and clicked the top SEO listing I was taken to a competitor of the number 1 listed site i.e. NOT the site I clicked on. When I clicked the back button and clicked it again, I was taken to the correct site. This happened with two different searches and I was taken to two different sites. Could this be a clever/sinister cookie implemented by the competitor; a site I frequent regularly? Could this be malware implemented by an affiliate? Could this be a Google glitch?
Technical SEO | | Red_Mud_Rookie0