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
-
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 redirects delay in picking up
Hi I have been involved in the redesign/development of a website which has up until now had a lot of international traffic. On day of migration I uploaded all the 301 redirects to the website (wordpress) using Simple 301 redirect plugin. I tested a number of them and they appeared to be working. I also submitted the new sitemaps to Search Console. Since migration international traffic - particularly from countries such as india, Phillipines, Sri Lanka etc have significantly dropped off whereas the local traffic and some of the international traffic such as USA has remained fairly consistent. Looking at Analytics and entrances recently it appears as though search results are/were showing a number of pages with 404's (one in particular which received significant traffic and for which I had created a 301 redirection) - I have checked this page using the old url and it re-directs correctly for me and today asked a colleague in India to also check - he is getting the redirection fine. Does Google.in take a significantly longer time to pick these up in search results? Or am I missing something?
Technical SEO | | musthavemarketing0 -
301 Redirect non existant pages
Hi I have 100's of URL's appearing in Search Console for example: ?p=1_1 These go to on to 5_200 etc.. I have tried to do htaccess and the mod rewrite is on as I can redirect directories to the root i.e RewriteRule ^web_example(.*)$ /$1 [R=301,N,L] However I have tried all kinds of variations to redirect ?p= and either it doesn't work at all or it crashes the website. Can anyone point me in the right direction to fix this.
Technical SEO | | Cocoonfxmedia0 -
Is there a limit to Internal Redirect?
I know Google says there is no limit to it but I have seen on many websites that too many 301 redirects can be a problem and might negatively affect your rankings in SERPs. I wanted to know especially from people who worked on large ecommerce site. How do they manage internal redirect from one URL to other and how many according to you are too many. I mean if you get a website that contain 300 plus 301 redirections within the website, how will you deal with that? Please let me know if the question is not clear.
Technical SEO | | MoosaHemani0 -
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 -
Redirect root domain to www
I've been having issues with my keyword rankings with MOZ and this is what David at M0Z asked me to do below. Does anyone have a solution to this? I'm not 100% sure what to do. Does it hurt ranking to have a domain at the root or not? Can I 301 redirect a whole site or do I have to do individual pages. "Your campaign is looking for rankings for the www version of the campaign but the URL resolves as a root domain. This would explain the discrepancy. Since there is no re-direct between the two, you can have brickmarkers.com 301 re-direct to www.site.com which will prevent you from re-creating your campaign to track the root domain. Once the re-direct is in place it will take a while for Google to show the www version in the results in which your campaign rankings will be accurate." Thanks
Technical SEO | | SeaDrive0 -
Do search engines treat 307 redirects differently from 302 redirects?
We will need to send our users to an alternate version of our homepage for a few hours for a certain event. The SEO task at hand is to minimize the chance of the special homepage getting crawled and cached in the search engines in place of our normal homepage. (This has happened in the past so the concern is not imaginary.) Among other options, 302 and 307 redirects are being discussed. IE, redirecting www.domain.com to www.domain.com/specialpage. Having used 302s and 301s in the past, I am well aware of how search engines treat them. A 302 effectively says "Hey, Google! Please get rid of the old content on www.domain.com and replace it with the content on /specialpage!" Which is exactly what we don't want. My question is: do the search engines handle 307s any differently? I am hearing that the 307 does NOT result in the content of the second page being cached with the first URL. But I don't see that in the definition below (from w3.org). Then again, why differentiate it from the 302? 307 Temporary Redirect The requested resource resides temporarily under a different URI. Since the redirection MAY be altered on occasion, the client SHOULD continue to use the Request-URI for future requests. This response is only cacheable if indicated by a Cache-Control or Expires header field. The temporary URI SHOULD be given by the Location field in the response. Unless the request method was HEAD, the entity of the response SHOULD contain a short hypertext note with a hyperlink to the new URI(s) , since many pre-HTTP/1.1 user agents do not understand the 307 status. Therefore, the note SHOULD contain the information necessary for a user to repeat the original request on the new URI. If the 307 status code is received in response to a request other than GET or HEAD, the user agent MUST NOT automatically redirect the request unless it can be confirmed by the user, since this might change the conditions under which the request was issued.
Technical SEO | | CarsProduction0
