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
-
Moving to old site to new domain sub directory
Hi, we've moved our old site to a new domain but in a subdirectory (the shopping site has been consolidated into overarching company website's shopping section, thus the move to sub dir). Are 301 redirects from old URLs to new domain's subdirectory ex newsite.com/shopping/page-1/ sufficient for site migration? I wasn't able to use Google's site address change tool since we're moving to a subdirectory on the new domain. Thanks
Technical SEO | | SoulSurfer80 -
Hard-working newbie question: benefit of moving my blog to my online store's domain?
Hi all, I've been running an online wine store in Switzerland for a month and have been working hard on SEO (I love learning about it). Anyway, for a couple of years prior to launching the store, I had been running a wine blog whose articles are ranking well in Google. I now want to link the two. My questions are: A) will the addition of the blog (store.com/blog) contribute to the store's domain authority (currently, the blog authority is higher than the site authority)? B) technically, can I 301 the whole blog to store.com/blog? Any help and tips would be appreciated. Thank you!
Technical SEO | | fkupfer0 -
Blog is outranking my root domain - Why and Help
I have an odd question concerning SERP rankings on Google along with PageRank and Google Trust. I have a website created in HTML with a WP blog created in a sub-directory. I am finding that the blog is getting relatively good rankings yet it seems the root domain is not getting any of the rank or trust passed onto it as it consistently is outranked by the blog. In fact, for a few of our targeted keywords the root domain does not even show up at all, yet the blog does. Our blog is #2 in Google SERPs, a top Google Place ranking, a Youtube video in the top 10 and a Google Ad place somewhere in the mix of first page ads. The root domain is nowhere to be found. Is there something I need to correct either on the site, in Google Webmaster or in WP Settings that I am not aware that is pushing all the Google Rank and Trust to the blog instead of the other way around? I considered changing the WP Site URL to the root domain thinking it will pass more SEO mojo to the root. But I don't think this is the way to go. I am kind of at a loss, any help is appreciated.
Technical SEO | | SEO-Novice0 -
301 Redirect / cross-domain canonical to a URL w/ Ampersand
I have a question regarding ampersands, we are needing to redirect to a URL w/ an ampersand in the URL: http://local.sfgate.com/b18915250/Sam-&-Associates-Insurance-Agency Will Google pass page authority/juice despite the fact that there is an ampersand in the URL, if we were to 301 redirect or cross-domain canonical to the url? Should we 301 redirect to http://local.sfgate.com/b18915250/Sam-%26-Associates-Insurance-Agency instead of http://local.sfgate.com/b18915250/Sam-&-Associates-Insurance-Agency? I don't have the option of removing the ampersand Thank you for your time!
Technical SEO | | Gatelist0 -
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 -
We have been keeping other sites on our domain while we build them for clients and not taking them off afterwards
So when I look in wmt its telling me our site is about fish oil etc when we are web designers. We have blocked these pages in robots text and removed them. WMT is showing 500 errors in crawl errors and telling us we have health issues on our site. what should we do and how do i bulk select these errors is wmt to mark as fixed (if they are fixed)
Technical SEO | | duncan2740 -
Will 301 redirecting a site multiple times still preserve the original site value?
Hi, All! If site www.abc.com was already 301 redirected to site www.def.com, and now the site owner wants to redirect www.def.com to www.ghi.com - is there any concern that it's not going to work, and some of the original linkjuice, rank, trust, etc. is going to vanish? Or as long as the 301s are set up right, should you be able to 301 indefinitely? Does anyone have any experience with actually doing this and seeing good/bad/neutral results? Thanks in advance! -Aviva B
Technical SEO | | debi_zyx0 -
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