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
-
New domain wipes out domain authority
A client wanted to change their domain name, which we have now done. The site content itself is exactly the same. We put 301 redirect links in so that Google searchers would redirect from the old site to the new one. However Moz then said that it couldn't crawl the old domain because of the redirects and advised creating a brand new campaign for the new domain. We have done this but now Moz says that the domain authority of the new site is 2 (it was 14 on the old domain). Specifics are:
Technical SEO | | mfrgolfgti
old domain: https://ryemeadcleaning.co.uk
new domain: https://ryemeadgroup.co.uk So basically it seems like we're starting again from scratch with the new domain and all the SEO from the old domain has been lost? Have we done it wrong?0 -
301 Multiple Sites to Main Site
Over the past couple years I had 3 sites that sold basically the same products and content. I later realized this had no value to my customers or Google so I 301 redirected Site 2 and Site 3 to my main site (Site 1). Of course this pushed a lot of page rank over to Site 1 and the site has been ranking great. About a week ago I moved my main site to a new eCommerce platform which required me to 301 redirect all the url's to the new platform url's which I did for all the main site links (Site 1). During this time I decided it was probably better off if I DID NOT 301 redirect all the links from the other 2 sites as well. I just didn't see the need as I figured Google realized at this point those sites were gone and I started fearing Google would get me for Page Rank munipulation for 301 redirecting 2 whole sites to my main site. Now I am getting over 1,000 404 crawl errors in GWT as Google can no longer find the URL's for Site 2 and Site 3. Plus my rankings have dropped substantially over the past week, part of which I know is from switching platforms. Question, did I make a mistake not 301 redirecting the url's from the old sites (Site 2 and Site 3) to my new ecommerce url's at Site 1?
Technical SEO | | SLINC0 -
Multiple domains pointing to same site
Over the years, we have acquired a great number of variations of our domains, or industry-specific domains to protect our brand. Currently, the majority of those domains are parked at the registrars. Would we do any harm to our rankings if we pointed the dormant domains to our website (www.ellsworth.com)? If not, are there any recommendations as the best way to do this, or just point them to the same IP?
Technical SEO | | Ellsworth0 -
Htaccess redirects how many can i have and does it slow site down
I have had to redesign my site this year www.in2town.co.uk because my hosting company made a huge mistake while trying to update the joomla on my site which resulted in me losing thousands of pages and links. What i would like to know is, i have put some of the old urls in my htaccess file but i would like to know how many old urls i can have in my htaccess file as i am unsure how to use it properly. my idea was, to have some of the lost url links to my site and put them in my htaccess file and have them pointing to similar pages. not sure if this is a good idea or not. i think i have lost a few hundred good links but i would like to know if these urls in the htaccess file would slow down my joomla site any advice would be great.
Technical SEO | | ClaireH-1848860 -
Are site wide links bad for web developers?
Like many web dev companies, we put an anchor text credit (varying the anchor text) in the footer of clients' sites. As it's a footer link, it's site wide. This strategy's been troubling me for a while and I've been anticipating a drop in our rankings ... especially in light of Penguin. But it hasn't happened. Any other developers our there taken a hit by having site wide links? anyone have any views on this? Anyone want to comment on the spurious and unlikely scenario that Google may recognise that web dev companies have always used site wide credits and may therefore be overlooking / not penalising them?
Technical SEO | | 2Stroke0 -
Will errors on a subdomain effect the overall health of the root domain?
As stated in the question, we have 2 sub domains that contain over 2000 reported errors from SEOMOZ. The root domain has a clean bill of health, and i was just wondering if these errors on the sub-domains could have a negative effect on the root domain in the eyes of Google. Your comments will be appreciated. Regards Greg
Technical SEO | | AndreVanKets0 -
Google Confusion: Two Sites and a 301 Redirect.
Hi, We have a client who just sprang a new project on us. As always, they went ahead and did some stuff before bringing us into the loop! (oh the joy of providing SEO services!) Anyway, i'm pretty swamped right now and need some extra brains on this. Basically the client had www.examplesiteA.com online for many years (an affiliate site which had built up a strong brand in the industry). They have now decided to turn this affiliate site into a full blown service platform and so with the new site being built they 301'd the whole thing over to www.examplesiteB.com - this is where they want all the old affiliate content to be hosted. So essentially examplesiteA.com is now examplesiteB.com and a new site is being placed on examplesiteA.com - still with me? So this has all happened and a brand new website is on examplesiteA.com and the old examplesiteA is now sitting exactly as it used to, but on the examplesiteB domain. The 301 redirect has been removed and the new examplesiteA seems to have been crawled, but the homepage is not indexed. When you search for examplesiteA, examplesiteB is the top result. Now they are similar domain names and to be fair I have very little data at this point i.e. I don't know when the 301 redirect was removed and it maybe that this all fixes itself with time. How is link equity effected now that examplesiteA.com was 301 redirected to examplesiteB.com and cached in this way, but now the 301 redirect has been removed and does not exist? Would link juice have been diluted throughout the process? Obviously if we had been in on all this before anything was implemented we would have done things differently. Interested to hear what others would do coming in at this point. Thanks and look forward to the advice!
Technical SEO | | MarcLevy0 -
What are the SEOmoz-suggested best practices for limiting the number of 301 redirects for a given site?
I've read some vague warnings of potential problems with having a long list of 301 redirects within an htaccess file. If this is a problem, could you provide any guidance on how much is too much? And if there is a problem associated with this, what is that problem exactly?
Technical SEO | | roush0