HTTPS during or after redesign
-
Performing a website redesign and with that we are going to be deindexing a lot of pages and make big changes to the site architecture.
With all of these big changes happening with the redesign, should we include the change to https during the redesign or about 4-6 months after? If we do it after we will have time to diagnose any shortcomings of the redesign.
Thanks!
-
Hi Trent,
Did of the awesome responses to your question help? What did you decide to do? We'd love to hear from you!
Christy
-
In Summary. I prefer to work on the site structure first, probably because is one my main skills and I have been investing a lot of time and money on that. Donna Duncan suggests you make https migration first, mainly because is a less complicated process and she is right. Anyway, the main idea behind is the same. The best way to perform the project is one step at a time.
KISS "Keep it simple, stupid"
-
Completly agree
-
Definitely don't do them at the same time (Google themselves advise that). From personal experience I would recommend doing any major changes/restructure first, waiting a bit, then implementing HTTPS
-
Hi Trent,
I agree with Roman in that I would definitely do one before the other - much easier to manage and troubleshoot. If it was me, however, I'd do the https migration first. Why? Because there will be less moving parts. You only have to worry about the protocol change and can put aside renamed or dropped URLs until a later date.
-
Keep in mind that you are facing two main changes, site-structure and _domain migratio_n, and on my experience that can be like a play with fire. I had to face the same process and it turned into a nightmare for some apparently small errors.
So my advice follows the tick-tock model, first, take care of the site structure and then you can proceed to the https migration, why I prefer work on site-structure first, mainly because there are fewer risks of losing Domain-Authority, I mean if you will rearrange your tags and categories, probably will not hurt you. In fact, if you perform a good optimization will help you a lot to improve your ranking. Why?
1 Category archives are landing pages
Your category archives are more important than individual pages and posts. Those archives should be the first result in the search engines. That means those archives are your most important landing pages. Thus, they should also provide the best user experience. The more likely your individual pages are to expire, the more this is true. In a shop, your products might change, making your categories more important to optimize. Otherwise, you’d be optimizing pages that are going to be gone a few weeks/months later.
2 Categories prevent individual pages from competing
If you sell boxers and you optimize every product page, all those pages will compete for the term ‘boxers’. You should optimize them for their specific brand and model, and link them all to the ‘boxers’ category page. That way the category page can rank for ‘boxer’, while the product page can rank for more specific terms. This way, the category page prevents the individual pages from competing.Also, I will suggest you my favorite tool for creating an outstanding site structure **Dyno Mapper **in my opinion is by far the best way to get the job done, also will help you to check where are your weak points.
Talking about your domain migration. The redirect will become a crucial task, I will suggest strongly you screaming-frog, (probably you already have it if not give it a try)mostly to get a deep analysis of your internal links.
Also, keep in mind to start to build quality links to your new domain in other to build and strong DA so when you move your site will take you less time to recover your ranks and traffic
**Hope this info will help you **
Regards
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
-
Changing URL's During a Site Redesign
What are the effects of changing URL's during a site redesign following all of the important processes (ie: 301 redirects, reindexing in google, submitting a new sitemap) ?
Intermediate & Advanced SEO | | jennifer-garcia0 -
Scary bug in search console: All our pages reported as being blocked by robots.txt after https migration
We just migrated to https and created 2 days ago a new property in search console for the https domain. Webmaster Tools account for the https domain now shows for every page in our sitemap the warning: "Sitemap contains urls which are blocked by robots.txt."Also in the dashboard of the search console it shows a red triangle with warning that our root domain would be blocked by robots.txt. 1) When I test the URLs in search console robots.txt test tool all looks fine.2) When I fetch as google and render the page it renders and indexes without problem (would not if it was really blocked in robots.txt)3) We temporarily completely emptied the robots.txt, submitted it in search console and uploaded sitemap again and same warnings even though no robots.txt was online4) We run screaming frog crawl on whole website and it indicates that there is no page blocked by robots.txt5) We carefully revised the whole robots.txt and it does not contain any row that blocks relevant content on our site or our root domain. (same robots.txt was online for last decade in http version without problem)6) In big webmaster tools I could upload the sitemap and so far no error reported.7) we resubmitted sitemaps and same issue8) I see our root domain already with https in google SERPThe site is https://www.languagecourse.netSince the site has significant traffic, if google would really interpret for any reason that our site is blocked by robots we will be in serious trouble.
Intermediate & Advanced SEO | | lcourse
This is really scary, so even if it is just a bug in search console and does not affect crawling of the site, it would be great if someone from google could have a look into the reason for this since for a site owner this really can increase cortisol to unhealthy levels.Anybody ever experienced the same problem?Anybody has an idea where we could report/post this issue?0 -
Https vs Http Link Equity
Hi Guys, So basically have a site which has both HTTPs and HTTP versions of each page. We want to consolidate them due to potential duplicate content issues with the search engines. Most of the HTTP pages naturally have most of the links and more authority then the HTTPs pages since they have been around longer. E.g. the normal http hompage has 50 linking root domains while the https version has 5. So we are a bit concerned of adding a rel canonical tag & telling the search engines that the preferred page is the https page not the http page (where most of the link equity and social signals are). Could there potentially be a ranking loss if we do this, what would be best practice in this case? Thanks, Chris
Intermediate & Advanced SEO | | jayoliverwright0 -
Help needed on HTTPS
Hi Can anyone help me. I need some help with some example of large e-commerce sites going to https. Ideally these need to be e-commerce sites but any large site will be great, so that I can show the impact. The site can be based anywhere in the world, its more the impact I am after. Thanks Andy
Intermediate & Advanced SEO | | Andy-Halliday0 -
Is a rebranding that calls for a domain change a good time to sneak in a change to HTTPS?
Assumed: The material around good migration/redesign practices recommend, logically enough, to change as few things as possible in any given step, thus giving search engines as little trouble as possible identifying and reindexing changes. So if someone is doing significant changes to content, including uri changes, and a rebranding that requires a domain migration, they are generally better off doing one, than the other. 1) Beyond immediate testing and checking for correct crawl health being reestablished after one change, any thoughts on rules of thumb for when to do the second change? Do you do it as soon as you see your rankings/traffic turn the corner and confirm an upward trend after the drop, or wait till you have it all back (or at least hit a plateau)? In the absence of data or best practice I'm thinking of just letting 1/3rd to 2/3rds come back. Is a change to HTTPS small enough/similar enough from the search engine's perspective that it makes more sense to do that at the same time as the rebrand driven domain change? Does this create any special risks or considerations beyond those that arise from the individual components of the change?
Intermediate & Advanced SEO | | JFA0 -
HTTPS sitewide move has resulted in huge rankings drop...
Hi all, An e-commerce site has recently moved protocol to https sitewide. The site ranked page one for some great terms and now appear to be page 2 or below. Brand terms seem unphased and are still very strong, on both Google and Bing. The following has been done; Everything 301'd from http to https Sitemap Edited Updated Webmaster Tools Robots.txt edited Crawled and Fetched all pages daily. Checked Paged are all follow,index. PPC Ads mass updated to new url's. Most terms were ranked 1 - 9 on Bing, and Page 1/2 on Google. HTTPS upgrade was done less than one week ago. The site is not payday loan related, nor was it hit by latest panda escapades. Everything on the site is relevant to the content. Has anybody else been in this position, what else can be done? I'd appreciate any help and advice. Thank You K9gB7hz
Intermediate & Advanced SEO | | Whittie0 -
Http to https conversion - what were your experiences?
Background: Our devs have been talking about changing some of our websites so that all pages are https vs just those that are a part of our logins and shopping carts. From what I have read things that need to be done as a part of this are make sure that https pages will allow caching setup new site in GWT put 301 redirects in place update all internal links, social profiles etc everywhere you can to https URLs can server handle the extra load so no impact on site speed There is an old MCutts video that says essentially, "works for Pay Pal" and "you can try it, but test it on a smaller site first" http://www.youtube.com/watch?v=xeFo4ytOk8M The comments below the video are all stories about loss in rank and traffic with some coming back. Not sure if these folks did the move correctly, but still, you never know. Question: Have any of you done a technically "correct" move of an entire site from http to https using the suggestions above? What was your experience? Any gotchas? Just to be clear, I am not talking about setting up a site from scratch, but wanted to know impact on an established site. Thx
Intermediate & Advanced SEO | | CleverPhD1 -
HTTPS in Rel Canonical
Hi, Should I, or do I need to, use HTTPS (note the "S") in my canonical tags? Thanks Andrew
Intermediate & Advanced SEO | | Studio330