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
-
Redirection chain and Javascript Redirect
Hi, A redirection chain is usually defined as a page redirecting to another page which itself is another redirection. URL1 ---(301/302)---> URL2 ---(301/302)---> URL3 But what about Javascript redirect? They seem to be a different beast: URL1 ---(301/302)---> URL2 ---(200 then Javascript redirect)---> URL3 From what I know if the javascript redirect is instant Google counts it as a 301 permanent redirection, but I'm still not sure about if this counts as a redirection chain. Most of the tools (such as moz) only see the first redirection. So is that scenario a redirection chain or no?
Technical SEO | | LouisPortier0 -
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 -
Can I use a 301 redirect to pass 'back link' juice to a different domain?
Hi, I have a backlink from a high DA/PA Government Website pointing to www.domainA.com which I own and can setup 301 redirects on if necessary. However my www.domainA.com is not used and has no active website (but has hosting available which can 301 redirect). www.domainA.com is also contextually irrelevant to the backlink. I want the Government Website link to go to www.domainB.com - which is both the relevant site and which also should be benefiting from from the seo juice from the backlink. So far I have had no luck to get the Government Website's administrators to change the URL on the link to point to www.domainB.com. Q1: If i use a 301 redirect on www.domainA.com to redirect to www.domainB.com will most of the backlink's SEO juice still be passed on to www.domainB.com? Q2: If the answer to the above is yes - would there be benefit to taking this a step further and redirect www.domainA.com to a deeper directory on www.domianB.com which is even more relevant?
Technical SEO | | DGAU
ie. redirect www.domainA.com to www.domainB.com/categoryB - passing the link juice deeper.0 -
Old domain to new domain
Hi, A website on server A is no longer required. The owner has redirected some URLS of this website (via plugin) to his new website on server B -but not all URLS. So when I use COMMAND site:website A , I see a mixture of redirected URLS and not redirected URLS.Therefore two websites are still being indexed in some form and causing duplication. However, weirdly when I crawl with Screaming Frog I only see one URL which is 301 redirected to the new website. I would have thought I'd see lots of URLs which hadn't been redirected. How come it is different to using the site:command? Anyway, how do I move to the new website completely without the old one being indexed anymore. I thought I knew this but have read so many blogs I've confused myself! Should I: Redirect all URLS via the HTACESS file on old website on server A? There are lots of pages indexed so a lot of URLs. What if I miss some? or Point the old domain via DNS to server B and do the redirects in website B HTaccess file? This seems more sensible but does this method still retain the website rankings? Thanks for any help
Technical SEO | | AL123al0 -
Switching from a .org to .io (301 domain redirect)
I'm considering switching my main site from a .org to .io address; the .org is an exact match domain which helped to kickstart it a few years ago and now has about 50% repeat visitors, but was thrown off the Apple affiliation program for trademark infringement. I've found and purchased a nice (non-infringing) .io domain, and I've read the advice here on how to properly 301 the old domain; but my question is - does it matter that it's .io? Is this going to significantly hurt my rankings, even when everything has been 301'd properly? Another thought I had is that I may actually come out better off in the long run, what with Google penalties being applied to exact match domains. Is this a ranking suicide? If so, I'm tempted to leave it as is; even without the affiliation, it's making a good amount every month in ad fees that I don't want to disrupt. Thanks all!
Technical SEO | | w0lfiesmithUK0 -
We have set up 301 redirects for pages from an old domain, but they aren't working and we are having duplicate content problems - Can you help?
We have several old domains. One is http://www.ccisound.com - Our "real" site is http://www.ccisolutions.com The 301 redirect from the old domain to the new domain works. However, the 301-redirects for interior pages, like: http://www.ccisolund.com/StoreFront/category/cd-duplicators do not work. This URL should redirect to http://www.ccisolutions.com/StoreFront/category/cd-duplicators but as you can see it does not. Our IT director supplied me with this code from the HT Access file in hopes that someone can help point us in the right direction and suggest how we might fix the problem: RewriteCond%{HTTP_HOST} ccisound.com$ [NC] RewriteRule^(.*)$ http://www.ccisolutions.com/$1 [R=301,L] Any ideas on why the 301 redirect isn't happening? Thanks all!
Technical SEO | | danatanseo0 -
Redirecting Root domain to subdirectory by IP addresses (country specific)
We are using Wordpress Multisite. so www.mysite.com is our English website and www.mysite.com/sub is our Chinese website Can I redirect Chinese visitors who type "www.mysite.com" to "www.mysite.com/sub" ? so we want to force redirection to www.mysite.com/sub if our website is visited by Chinese IP Address. I've realized that this is called GeoIP Redirection. and our hosting company already has those database, I guess my job is just to simply insert some code in .htacess My question is, would it affect our SEO later on? and what .htacess code is the best practice here?
Technical SEO | | joony20080 -
Impact of 401s on Site Rankings
Will having 401s on a site negatively impact rankings? (e.g. 401s thrown from a social media sharing icon)
Technical SEO | | Christy-Correll0