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.
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
-
301 Redirects Relating to Your XML Sitemap
Lets say you've got a website and it had quite a few pages that for lack of a better term were like an infomercial, 6-8 pages of slightly different topics all essentially saying the same thing. You could all but call it spam. www.site.com/page-1 www.site.com/page-2 www.site.com/page-3 www.site.com/page-4 www.site.com/page-5 www.site.com/page-6 Now you decided to consolidate all of that information into one well written page, and while the previous pages may have been a bit spammy they did indeed have SOME juice to pass through. Your new page is: www.site.com/not-spammy-page You then 301 redirect the previous 'spammy' pages to the new page. Now the question, do I immediately re-submit an updated xml sitemap to Google, which would NOT contain all of the old URL's, thus making me assume Google would miss the 301 redirect/seo juice. Or do I wait a week or two, allow Google to re-crawl the site and see the existing 301's and once they've taken notice of the changes submit an updated sitemap? Probably a stupid question I understand, but I want to ensure I'm following the best practices given the situation, thanks guys and girls!
Technical SEO | | Emory_Peterson0 -
Sudden drop in Rankings after 301 redirect
Greetings to Moz Community. Couple of months back, I have redirected my old blog to a new URL with 301 redirect because of spammy links pointed to my old blog. I have transfer all the posts manually, changed the permalink structure and 301 redirected every individual URL. All the ranking were boosted within couple of weeks and regained the traffic. After a month I have observed, the links pointed to old site are showing up in Webmaster Tools for the new domain. I was shocked (no previous experience) and again Disavowed all links. Today, all the positions went down for new domain. My questions are: 1. Did the Disavow tool worked this time with new domain? All the links pointed to old domain were devaluated? Is this the reason for ranking drop? Or 2. 301 Old domain with Unnatural links causes the issue? 3. Removing 301 will help to regain few keyword positions? I'm taking this as a case study. Already removed the 301 redirect. Looking for solid discussion.Thanks.
Technical SEO | | praveen4390 -
Is there a tool to see all redirects?
I'm thinking this is a silly question, but I've never had to deal with it I thought I'd ask. Ok is there a tool out there that will show all the redirects to a domain. I'm working on a project that I keep stumbling on urls that redirect to the site I'm studying. They don't show up in Open Site or ahrefs as linking domains, but they keep popping up on me. Any thoughts?
Technical SEO | | BCutrer0 -
CNAME vs 301 redirect
Hi all, Recently I created a website for a new client and my next job is trying to get them higher in Google. I added them in OSE and noticed some strange backlinks. To my surprise the client has about 20 domain names. All automatically poiting to (showing) the same new mainsite now. www.maindomain.nl www.maindomain.be
Technical SEO | | Houdoe
www.maindomain.eu
www.maindomain.com
www.otherdomain.nl
www.otherdomain.com
... Some of these domains have backlinks too (but not so much). I suggested to 301 redirect them all to the main site. Just to avoid duplicate content. But now the webhoster comes into play: "It's a problem, client has only 1 hosting account, blablabla...". They told me they could CNAME the 20 domains to the main domain. Or A-record them to an IP address. This is too technical stuff for me. So my concrete questions are: Is it smart to do anything at all or am I just harming my client? The main site is ranking pretty well now. And some backlinks are from their copy sites (probably because everywhere the logo links to the full mainsite url). Does the CNAME or A-record solution has the same effect as a 301 redirect, from SEO perspective? Many thanks,
Hans0 -
301 Redirect & Cloaking
HEllo~~~~ People. I have a question regarding on cloaking. I will be really greatful if you can help me with question. I have a site www.example.com and it is targeting for multi countries. So I use sub directories for targeting multi countries. e.g. www.example.com/us/ www.example.com/de/ www.example.com/hk/ ....... so on and on. Therefore, when people type www.example.com, I use IP delivery to send users to each coutries. Here is my question. I use 301 redirect for IP delivery, which means when user enter www.example.com, my site read user's IP and send them to right country site by 301 redirect. In this case, is there any possibility that Google considers it as cloaking? Please people.... share me some ideas and thoughs.
Technical SEO | | Artience0 -
How do I redirect index.html to the root / ?
The site I've inherited had operated on index.html at one point, and now uses index.php for the home page, which goes to the / page. The index.html was lost in migrating server hosts. How do I redirect the index.html to the / page? I've tried different options that keep giving ending up with the same 404 error. I tried a redirect from index.html to index.php which ended in an infinite loop. Because the index.html no longer exists in the root, should I created it and then add a redirect to it? Can I avoid this by editing the .htaccess? Any help is appreciated, thanks in advance!
Technical SEO | | NetPicks0 -
How to Redirect only specific pages to new domain
My HTACCESS FILE IS AS FOLLOWS: rewriteengine on
Technical SEO | | askthetrainer
rewritecond %{HTTP_HOST} ^mydomain.com$
rewriterule ^mydomain/(.*)$ "http://www.mydomain.com/$1" [R=301,L] #4d864805b49b5 I want to move ONLY specific pages from this domain to a new domain How do I edit my HTACCESS (which redirects http:// to www.) to move specific pages from old domain (which I have to delete) to new domain.... I.e. http://mydomaon.com/move.html needs to move to http://mynewdomain.com/move.html Where i can delete the original domains0
