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.
WPEngine Causing Redirect Chain
- 
					
					
					
					
 Hi guys, Had a quick question that I wanted to verify here. After reviewing a Moz report we received some redirect chain error on all of our sites hosted with WPEngine. We noticed that the redirect chain appears to be coming from how the domains are configured in their control panel. Essentially, there is a redirect: - from staging/temp -> to live
- from non-www -> to www
- SSL redirect from http -> https
 The issue here is that the non-www is redirecting to www and then redirected again to https://www According to support the only way to get rid of this error is to drop the www version of the domain and to host everything under https://domain.com. To me it seems very odd that you cannot just go from http://non-www to https://www in just 1 301 redirect. Has anyone else experienced this or am I just not looking at the situation correctly? 
- 
					
					
					
					
 @AaronHenry This works. i had numerous redirect hops on wpengine. i followed these industructions and my issue went away. Make sure you clear cache when you do this (on the site and wpengine cache)... also make sure you dont have any redirects on the domain or cloud flare dns file level. Remove any redriects of the primary and set www. as the primary. 
- 
					
					
					
					
 Hi Jared, In the WPE redirect rule editor, it doesn't provide an option for the non-www domain. Only "All domains" and "www.mywwwdomain.com". What do you suggest doing here to eliminate the redirect chain? 
- 
					
					
					
					
 Hi Donna, Thanks for the followup! This method would work for both www and non-www to get it over to https://. We handle redirects on the Nginx layer, so by adding in a Redirect Rule it overwrites any default platform redirect rules in the User Portal and ensures your preferred setup is handled first. If you run into any trouble getting it configured, please reach out to us and we'll be glad to ensure it gets set up properly. Should anyone tell you it's not possible, request that they reach out to me and I'll be sure to instruct them on the method to get it squared away. Cheers, 
 Jared Arnold
- 
					
					
					
					
 Hi Aaron, You're very welcome and I'm glad that you've been overall enjoying the platform! It's very possible that they didn't quite grasp the request, though it is a bit of an SEO quirk to configure. I'll be following up with some of our team to help ensure our internal documentation's up to date so that should this be asked in the future, we can provide a more consistent experience for you. Thanks! 
 Jared Arnold
- 
					
					
					
					
 Same question but for the www version of the site. Can it route directly to HTTPS without a redirect? Do I just have to delete the existing non-www to www redirect and follow your logic above? It will take care of both www and non-www redirecting to HTTPS? I have also asked the help desk several times for a solution, although not recently. I was told it wasn't possible. 
- 
					
					
					
					
 Thanks for this information! All of the support agents I spoke with told me that it was not possible. They were all extremely professional, but perhaps they didn't understand what I was asking. I'm glad to hear there is a way to make it happen. WPE is a great platform for us. 
- 
					
					
					
					
 Hey Aaron! Jared from WP Engine here. I just wanted to reach out and provide a bit of clarification on the redirect chain here. On our platform, it is possible to have non-www go to https://www directly. To do so, it requires adding each domain individually within the User Portal under 'Domains'. (not combining them under redirects) Once done, you then create a Redirect Rule within the 'Redirect Rules' section with the following parameters: Name: (this can be anything) 
 Domain: (your non-www domain)
 Source: ^/(.*)
 Destination: https://www.yourwwwdomain.com/$1Once configured and the cache purged, a request to the non-www version of your address will skip the http://www redirect and go directly to the secure https://www version. If you run into any trouble getting it set up, please reach out to our team and we will be glad to help configure it for you. Thanks, 
 Jared Arnold
- 
					
					
					
					
 Just thought I'd shoot an update - according to WPEngine the redirect will always be there. No way around it on their platform. 
Browse Questions
Explore more categories
- 
		
		Moz ToolsChat with the community about the Moz tools. 
- 
		
		SEO TacticsDiscuss the SEO process with fellow marketers 
- 
		
		CommunityDiscuss industry events, jobs, and news! 
- 
		
		Digital MarketingChat about tactics outside of SEO 
- 
		
		Research & TrendsDive into research and trends in the search industry. 
- 
		
		SupportConnect on product support and feature requests. 
Related Questions
- 
		
		
		
		
		
		Should we set up redirects for all deleted TAGS?
 We recently found our site had 65,000 tags (yes 65K). In an effort to consolidate these we've started deleting them. MOZ is now reporting a heap of 404 errors for tag pages. These tag pages should not have links to them so not sure how come they're being crawled. Any suggestions from experience in this area would be useful. Technical SEO | | wearehappymedia0
- 
		
		
		
		
		
		What could cause Google to not honor canonical URLs?
 I have a strange situation on a website, when I do a Google query of site:example.com all the top indexed results appear to be queries that users can perform on the website. So any random term the user searches for on the website for some reason is causing the search result page to get indexed - like example.com/search/query/random-keywords However, the search results page has a canonical tag on it that points to example.com/search, but that doesn't seem to be doing anything. Any thoughts or ideas why this could be happening? Technical SEO | | IrvCo_Interactive0
- 
		
		
		
		
		
		Intermittent 404 - What causes them and how to fix?
 Hi! I'm working on a client site at the moment and I've discovered a couple of pages that are 404ing but producing a 200 OK response. However, I have checked these URLs again and some are now producing a 404 Error response. No changes have been made (that I'm aware of) so it appears that the URLs are returning both 200 OK and 404 Error responses intermittently. Any ideas what could cause this and the best solution? Thanks! Technical SEO | | daniel-brooks0
- 
		
		
		
		
		
		Robots txt. in page with 301 redirect
 We currently have a a series of help pages that we would like to disallow from our robots txt. The thing is that these help pages are located in our old website, which now has a 301 redirect to current site. Which is the proper way to go around? 1- Add the pages we want to disallow to the robots.txt of the new website? 2- Break the redirect momentarily and add the pages to the robots.txt of the old one? Thanks Technical SEO | | Kilgray0
- 
		
		
		
		
		
		301 redirect: canonical or non canonical?
 Hi, Newbie alert! I need to set up 301 redirects for changed URLs on a database driven site that is to be redeveloped shortly. The current site uses canonical header tags. The new site will also use canonical tags. Should the 301 redirects map the canonical URL on the old site to the corresponding canonical for the new design . . . or should they map the non canonical database URLs old and new? Given that the purpose of canonicals is to indicate our preferred URL, then my guess is that's what I should use. However, how can I be sure that Google (for example) has indexed the canonical in every case? Thx in anticipation. Technical SEO | | ztalk1120
- 
		
		
		
		
		
		301 Redirect vs Domain Alias
 We have hundreds of domains which are either alternate spelling of our primary domain or close keyword names we didn't want our competitor to get before us. The primary domain is running on a dedicated Windows server running IIS6 and set to a static IP. Since it is a static IP and not using host headers any domain pointed to the static IP will immediately show the contents of the site, however the domain will be whatever was typed. Which could be the primary domain or an alias. Two concerns. First, is it possible that Google would penalize us for the alias domains or dilute our primary domain "juice"? Second, we need to properly track traffic from the alias domains. We could make unique content for those performing well and sell or let expire those that are sending no traffic. It's not my goal to use the alias domains to artificially pump up our primary domain. We have them for spelling errors and direct traffic. What is the best practice for handling one or both of these issues? Technical SEO | | briankb0
- 
		
		
		
		
		
		If a redirecting URL has more value than the website should I move it?
 Client has two website addresses: Website A is a redirect to Website B. It has one indexed page. But this is the URL being used in collateral. It has the majority of back links, and citations everywhere list Website A as the URL. Website B is where the actual website lives. Google recognizes and indexes the 80+ pages. This website has very few backlinks going to it. This setup does not seem good for SEO. Moreover, the analytics data is completely messed up because Website B shows that the biggest referral source is... you guessed it Website A. I'm thinking going forward, I should: Move all the content from Website B to Website A. Setup Website B to permanently 301 Redirect to Website A. Is that the best course of action? Technical SEO | | flowsimple0
 
			
		 
			
		 
			
		 
			
		 
			
		 
					
				 
					
				 
					
				 
					
				 
					
				 
					
				 
					
				