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
-
302 redirects in Magento, trying to fix
Hi all, I'm assigned a site in Magento. After the first craw, we found almost 15k 302 redirects. A sample URL ends with this /stores/store/switch/?SID=qdq9mf1u6afgodo1vtvk0ucdpb&___from_store=default&___store=german&uenc=aHR0cHM6Ly9qdWljeWZsdXRlcy5jb20vP19fX3N0b3JlPWdlcm1hbg%2C%2C And they are currently 302 redirecting to the homepage as well as other main pages and also product pages it seems. Some of these point to account pages where customers log in. Probably best for me to de-index those so no issues there. But I'm worried about the 302 redirects to public pages. The extension we have installed is SEO Suite Ultimate by MageWorx. Does anyone here have experience here specifically and how did you fix it? Thanks, JC
Technical SEO | | LASClients0 -
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!
Technical SEO | | mollykathariner_ms0 -
Query Strings causing Duplicate Content
I am working with a client that has multiple locations across the nation, and they recently merged all of the location sites into one site. To allow the lead capture forms to pre-populate the locations, they are using the query string /?location=cityname on every page. EXAMPLE - www.example.com/product www.example.com/product/?location=nashville www.example.com/product/?location=chicago There are thirty locations across the nation, so, every page x 30 is being flagged as duplicate content... at least in the crawl through MOZ. Does using that query string actually cause a duplicate content problem?
Technical SEO | | Rooted1 -
DNS vs IIS redirection
I'm working on a project where a site has gone through a rebrand and is therefore also moving to a new domain name. Some pages have been merged on the new site so it's not a lift and shift job and so I'm writing up a redirect plan. Their IT dept have asked if we want redirects done by DNS redirect or IIS redirect. Which one will allow us to have redirects on a page level and not a domain level? I think IIS may be the right route but would love your thoughts on this please.
Technical SEO | | Marketing_Today1 -
Redirect URLS with 301 twice
Hello, I had asked my client to ask her web developer to move to a more simplified URL structure. There was a folder called "home" after the root which served no purpose. I asked for the URLs to be redirected using 301 to the new URLs which did not have this structure. However, the web developer didn't agree and decided to just rename the "home" folder "p". I don't know why he did this. We argued the case and he then created the URL structure we wanted. Initially he had 301 redirected the old URLS (the one with "Home") to his new version (the one with the "p"). When we asked for the more simplified URL after arguing, he just redirected all the "p" URLS to the PAGE NOT FOUND. However, remember, all the original URLs are now being redirected to the PAGE NOT FOUND as a result. The problems I see are these unless he redirects again: The new simplified URLS have to start from scratch to rank 2)We have duplicated content - two URLs with the same content Customers clicking products in the SERPs will currently find that they are being redirect to the 404 page. I understand that redirection has to occur but my questions are these: Is it ok to redirect twice with 301 - so old URL to the "p" version then to final simplified version. Will link juice be lost doing this twice? If he redirects from the original URLS to the final version missing out the "p" version, what should happen to the "p" version - they are currently indexed. Any help would be appreciated. Thanks
Technical SEO | | AL123al0 -
Https redirect when certificate expired
Hi, How do we 301 an https version of a domain to a page on another website when the security certificate has run out? We have 301 redirected the http version but IT stuck on how to do the expired https. Thanks
Technical SEO | | Houses0 -
What to do with 302 redirects being indexed
Hi there, Our site's forums include permalinks that for some reason uses an intermediary URL that 302 redirects to the URL with the permalink anchor. For example: http://en.tradimo.com/learn/chart-analysis/time-frames/ In the comments, there is a permalink to the following URL; en.tradimo.com/co/50c450005f2b949e3200001b/ (there is no content here, and never has been). This URL 302 redirects to the following final URL: http://en.tradimo.com/learn/chart-analysis/time-frames/?offset=0&limit=20#50c450005f2b949e3200001b The problem is, Google is indexing the redirect URL (en.tradimo.com/co/50c450005f2b949e3200001b/) and showing duplicate content even though we are using the nofollow tag on these links. Ideally, we would directly use the last link rather than redirecting. Alternatively, I'd say a 301 redirect would be preferable. But if both aren't available, is there a way to get these pages out of the index? Is the canonical tag the best way? I really wish I could just add /co/ to the robots.txt file, but I think they would still be in the index, right? Thanks for your help!
Technical SEO | | etruvian0 -
How long should I keep 301 redirects?
I have modified a the URL structure of a whole section of a website and used mod_rewrite 301 redirect to match the new structure. Now that was around 3 months ago and I was wondering how long should I keep this redirect for? As it is a new website I am quite sure that there are no links around with the old URL structure but still I can see the google bot trying from time to time to access the old URL structure. Shouldn't the google bot learn from this 301 redirect and not go anymore for the old URL?
Technical SEO | | socialtowards0