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 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
-
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 -
301 redirect syntax for htaccess
I'm working on some htaccess redirects for a few stray pages and have come across a few different varieties of 301s that are confusing me a bit....Most sources suggest: Redirect 301 /pageA.html http://www.site.com/pageB.html or using some combination of: RewriteRule + RewriteCond + RegEx I've also found examples of: RedirectPermanent /pageA.html http://www.site.com/pageB.html I'm confused because our current htaccess file has quite a few (working) redirects that look like this: Redirect permanent /pageA.html http://www.site.com/pageB.html This syntax seems to work, but I'm yet to find another Redirect permanent in the wild, only examples of Redirect 301 or RedirectPermanent Is there any difference between these? Would I benefit at all from replacing Redirect permanent with Redirect 301?
Technical SEO | | SamKlep1 -
Redirect and ranking issue
Hi there - was wondering whether someone might be able to help. For a period of a day and a half, all the traffic to our website's blog articles were mistakenly being redirected to our homepage. A number of these articles ranked in the top 5 in Google worldwide for their targeted keywords, so this was a considerable amount of organic traffic that was instantly being redirected. It was a strange site glitch and our web team rectified the error, but now all these articles have disappeared from Google rankings (not visible anywhere in the first five pages). I'm presuming this must be linked to this redirect issue - we've been advised to wait and see whether Google restores these rankings, but I'm still concerned as to whether this represents a more serious problem? We have re-indexed the pages we are most concerned about, but am not sure whether there is anything else obvious we should think to do. If anyone has any thoughts, I'd be happy to hear them!
Technical SEO | | rwat0 -
How to change 302 redirect from http to https
Hi gang. Our site currently has a 302 redirect from the HTTP version of the homepage to the HTTPS version of the homepage. I understand this really should be changed to a 301 redirect but I'm having a little trouble figuring out exactly how this should be done. Some places on the internet are telling me I can edit our htaccess file to specify the type of redirect, however our htaccess file seems to be missing some of the information in theirs. Can anyone tell me what needs to be changed in the htaccess file - or if there's a simpler way to change the 302 to a 301? Many thanks 🙂 htaccess: BEGIN WordPress RewriteEngine On RewriteBase / RewriteRule ^index.php$ - [L] RewriteCond %{REQUEST_FILENAME} !-f RewriteCond %{REQUEST_FILENAME} !-d RewriteRule . /index.php [L] END WordPress EXPIRES CACHING ExpiresActive On ExpiresByType image/jpg "access plus 6 months" ExpiresByType image/jpeg "access plus 6 months" ExpiresByType image/gif "access plus 6 months" ExpiresByType image/png "access plus 6 months" ExpiresByType text/css "access plus 10 days" ExpiresByType application/pdf "access plus 10 days" ExpiresByType application/x-shockwave-flash "access plus 10 days" ExpiresByType image/x-icon "access plus 6 months" ExpiresDefault "access plus 2 days" EXPIRES CACHING
Technical SEO | | davedon0 -
Redirect non slash to slash
Hello SEO gurus We have an issue here ( www.xyz.com.au) is having 200 responses www.xyz.com.au and www.xyz.com.au/ ( when i ran the crawl test i found this ) We have been advised to do a 301 from non slash to slash ( as our other pages are showing up with slash ) for the consistency we decided to go with this but our devs just couldnt do it. Error is - redirect loop and this site is a wordpress one Can anyone help us with this issue? Help is much appreciated.
Technical SEO | | Pack0 -
301 redirect not working
Hi there! I have recently moved a domain that has been indexed by google and setup redirects so that it forwards to the new domain. It seems like the only redirect that actually is working is the canonical and main domain but every other page and or page nested within a folder are not working. Here is an example of some of the redirects. Am I doing this wrong? It seems to be going to the new domain but can't find the actual pages.... RewriteEngine On
Technical SEO | | twotd
RewriteBase /
RewriteCond %{HTTP_HOST} !agoodsweep.com$ [NC]
RewriteRule ^(.*)$ http://agoodsweep.com/$1 [L,R=301]
redirect 301 woodstoveservicerepair.html http://agoodsweep.com/woodstoveservicerepair/
redirect 301 /westchesterchimney.html http://agoodsweep.com/west-chester-chimney/ Thanks in advance for any help!!0 -
Double 301 redirect
Hi together, due to some technical reasons I have redirect (301) an existing link two times. Example: www.mydomain.com/root/site.html > 301 > www.mydomain.com/site.html > 301 www.mydomain.com/site_new.html Is there anybody how has got some experience like doing a double redirect? What about link juice? Best regards Steffen
Technical SEO | | steffen_0 -
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