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
-
Old Redirected Domain is replacing my current domain on SERPs
Hello everyone, All of a sudden a 2 year old redirected domain is replacing my current domain for 2 weeks now, my site is apitus.com and my old domain is aptitus.pe (the redirect is still working), however this only happens on my country google results (google.com.pe), if you check my site on google.com, everything looks ok even with a sitelink, which I no longer have on my country search results. Back to the issue, the first thing I thought was go to Search Console and take it out from the index, so I asked for access by uploading a file but since everything on that old site redirects to my current site I can't make such action. While still waiting for such access, is there anything else I could do?. Thanks in advance. PD: I'm adding the images of my SERPs CmzN8kY G3zZwwj
Technical SEO | | JoaoCJ0 -
Canonicals & 301 Redirects to new Domain
We will be changing our domain name soon and I want to make sure I'm not painting myself into a corner. Of course, I want to transfer as much link equity as possible. Question #1: Do I need to define a canonical from the old domain to the new domain? Question #2: Do I also need to put 301s in place on the pages with link equity, or is there a way to apply 301s across the entire site on all pages? Any input would be appreciated greatly! Thanks!
Technical SEO | | BVREID0 -
Question about breaking out content from one site onto many
We have a website and domain -- which is well-established (since 1998) -- that we are considering breaking apart for business reasons. This is a content site that hosts articles from a few of our brands in portal fashion. These brands are represented in print with their own magazines so it's important to keep their presence separate. All of the content on the site is related to a general industry, with each brand covering a unique segment in the industry. For example, think of a toy industry site that hosts content from it's brands covering stuffed animals, electronics and board games. The current thinking is to break out the content from a couple brands to their own sites and domains. The business case for this branding purposes. I'm of the opinion that this is a bad idea as we would likely see a noticeable decline in search traffic across the board, which we rely on for impressions for our advertisers. If we take the appropriate steps to carefully redirect pages to the new domains what kind of hit should we expect to take from this transition? Would it make much difference if we were transition from 1 to 2 sites vs 1 to 4? Should this move be avoided all together? Any advise would be appreciated.
Technical SEO | | accessintel0 -
Redirect Impact - Moving From SEOmoz to Moz
Hey Guys, This has been on my mind ever since the big announcement, so today I did some searching around for some posts/talk about what the impact of their full site redirect has been for them and didn't find anything. Have they posted on this or are there any threads that I'm missing out on? I'd love to hear more about what the impact has been or any general thoughts/insights people may have. Thanks!
Technical SEO | | TakeLessons
Jon1 -
Redirect to new domain.... (which is penalised)
Hey - how's things? I have a client who wants to redirect his main domain to a new one.... there are a couple of problems I see and thought I'd ask on moz. 1 - The new domain has been incorrectly parked on the old domain with no redirection in place... when you do "site:domain.com" in Google, there are no serps for the new domain (the old domain still ranks well), it doesn't seem to rank anywhere and doesn't return any results in OSE. Is it wise to redirect to this domain or will rankings drop on both? 2 - The new domain uses .mobi as its suffix and will be replacing a .com - but is much more related to the business keyword wise. Is using mobi a problem. Overall the SEO on the site is abysmal and I will be reworking everything - so there will be lots of changes going on at the same time. I'm just wondering if it is worth redirecting the new domain at all, or trying to get brand new domain and use that.... or just to stick with the original aged domain... I think that is my only concerns at the moment
Technical SEO | | agua0 -
Redirection Impact on SEO
Need help urgently. There is the situation [This is how is it working now]: 1. Have a global landing page [say when user types in www.mysite.com - takes user to the global landing page: [www.mysite.com/global/en.html]](http://www.mysite.com/global/en.html] ) 2. Users from this landing page can select a country on his/her choice and get redirected say: [www.mysite.com/us/en.html] Would like to change the functionality as below: 1. When user types in www.mysite.com 1a. Would find the location of the request based on GEO IP and if the request is coming from North America region then would redirect the users to: www.mysite.com/us/en.html 1b. If the request is from any other location/region then it would continue to work as it is currently working: take the user to the global landing page: www.mysite.com/global/en.html Would this change have any negative impact or not found by search engines from SEO perspective? If it does then what are the impacts and if does not then why not. If it does then what is the best possible way to address this request. Appriciate your help. Thanks, Koushik Roy
Technical SEO | | KoushikRoy0 -
Webmaster Tools Site Map Question
I have TLD that has authority and a number of micro-sites built off of the primary domain. All sites relate to the same topic, as I am promoting a destination. The primary site and each micro-site have their own CMS installation, but the domains are mapped accordingly. www.regionalsite.com/ <- primary
Technical SEO | | VERBInteractive
www.regioanlsite.com/theme1/ <- theme 1
www.regioanlsite.com/theme2/ <- theme 2
www.regionalsite.com/theme3/ <- theme 3 Question: Should my XML site map for Webmaster Tools feed all sites off of the primary domain site map or are there penalties for this? Thanks.0 -
Parked Domain blog directory not redirecting
My newly parked domain name, (our main website had to switch primary domains) is not redirecting properly and is causing our blog to be duplicate content. My 301 redirects work for everything else, but our parked domain /blog directory is not redirecting. I can type in both urls and then the blog appears on both sites. Not good. If I delete my blog .htaccess file, then it redirects fine. However, then our blog links are broken. So it has to do something with our .htaccess files. I do have a .htaccess file for our website, saying redirect everything to correct location, so i think this is interfering, but I cannot pinpoint it. this is the .htaccess file for the blog. BEGIN WordPress <ifmodule mod_rewrite.c="">RewriteEngine On
Technical SEO | | hfranz
RewriteBase /blog/
RewriteRule ^index.php$ - [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /blog/index.php [L]</ifmodule> END WordPress main sites .htaccess (i am trying to pinpoint the issue here) Options +Includes
AddType text/html .htm .html
AddHandler server-parsed .htm .html
Options +FollowSymLinks RewriteEngine on RewriteBase / RewriteCond %{HTTP_HOST} ^(www.)?parkeddomain.com [NC,OR] RewriteCond %{HTTP_HOST} ^newdomain.com [NC] RewriteRule (.*) http://www.newdomain/$1 [R=301,L] RewriteCond %{THE_REQUEST} ^[A-Z]{3,9}\ /([^?]*)? RewriteRule (.*) /$1? [R=301,L] RewriteCond %{THE_REQUEST} ^.*/index.php RewriteRule ^(.*)index.php$ http://www.newdomain.com/$1 [R=301,L] RewriteCond %{THE_REQUEST} ^.*/index.htm RewriteRule ^(.*)index.htm$ http://www.newdomain/$1 [R=301,L] RedirectMatch 301 /index.php/(.*) /$1 Is there something obvious here, that does not look right?0