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
-
We are redirecting http and non www versions of our website. Should all versions http (non www version and www version) and https (non www version) should just have 1 redirect to the https www version?
We are redirecting http and non www versions of our website. Should all versions http (non www version and www version) and https (non www version) should just have 1 redirect to the https www version? Thant way all forms of the website are pointing to one version?
Intermediate & Advanced SEO | | Caffeine_Marketing0 -
Redirect chains from switch to HTTPS
Hi, We have a client who recently switched their site to https:// The rule to force redirect non-secure URLs to https is in their .htaccess file: RewriteEngine on if non-SSL and one of these, redirect to SSL RewriteCond %{HTTPS} !on
Intermediate & Advanced SEO | | roundabout
RewriteRule ^(.*)$ https://www.clientdomain.com/$1 [R=301,L] However, they also have simple redirects below this rule that redirect one page to another, such as: Redirect 301 /old.php https://www.clientdomain.com/new.php This is causing redirect chains like this: (A) http://www.clientdomain.com/old.php > (B) https://www.clientdomain.com/old.php > (C) https://www.clientdomain.com/new.php Is there any way to rewrite the rules in .htaccess to get rid of these redirect chains? So that URL A goes directly to URL C? Thank you!1 -
Http > https Switch Before Platform Migration?
We are planning a series of large site migrations over the next 12-18 months, moving from one platform to another. It's likely the first will be completed by around Aug this year, with the process running until the back end of 2018. The sites are currently on http, and the plan is to first of all migrate all sites to https in the next couple of months. The concern is that, due to the http>https 301 redirects that will be in place, are we putting ourselves at unnecessary risk by effectively carrying out 2 migrations in the space of a year (in terms of loss of potential authority caused by redirects)? Would we be better to wait, and implement https at point of platform migration instead? Thoughts appreciated.
Intermediate & Advanced SEO | | Sayers0 -
Traffic has not recovered from https switch a year ago.
I have an ecommerce site that was switched to https a year ago almost to the day. Our category pages are about half of what they were. The redirects were put in properly, and everything in webmaster tools looks good. Anything out there I may not have thought of? Want to add that the drop is only in Google, Bing stayed just fine.
Intermediate & Advanced SEO | | EcommerceSite0 -
Fetch As Google Redirect from HTTPS to HTTP
Hi Moz Community, We just launched a redesigned site and moved our blog from http://sparkline.motifinvesting.com to https://www.motifinvesting.com/blog. When I went to check the site today I noticed something strange. When I Fetch a Blog URL as Google it is redirecting from https to http AND dropping the / <post-id>from the end of the URL.</post-id> So for the URL https://www.motifinvesting.com/blog/cleantech-obama-romney/1494 I am getting the attached results when I Fetch as Google. When I access the same URL in my browser, I see a 200 status code and no redirect. Why would Google Bot show that the URL is being redirected? Thanks,
Intermediate & Advanced SEO | | motif_marketing
Breanna https://www.motifinvesting.com/blog/cleantech-obama-romney/1494 I7yQPza.png0 -
From HTTP to HTTPS
Hi We have implemented HTTPS to the our website. Do we need to now redirect the whole site to HTTPS in the HTTACCESS file? Because when you enter the site via a google search or enter the domain directly the site is set to HTTP once we click on a URL on the page it sets it to HTTPS so do we require to redirect from the start? thanks
Intermediate & Advanced SEO | | Direct_Ram
E0 -
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 moz.org untrusted - invalid cert
https://www.moz.com/ has an invalid cert guys This Connection is Untrusted You have asked Firefox to connect
Intermediate & Advanced SEO | | irvingw
securely to www.moz.com, but we can't confirm that your connection is secure.
Normally, when you try to connect securely,
sites will present trusted identification to prove that you are
going to the right place. However, this site's identity can't be verified. What Should I Do? If you usually connect to
this site without problems, this error could mean that someone is
trying to impersonate the site, and you shouldn't continue. www.moz.com uses an invalid security certificate. The certificate is only valid for moz.com (Error code: ssl_error_bad_cert_domain) If you understand what's going on, you
can tell Firefox to start trusting this site's identification.
Even if you trust the site, this error could mean that someone is
tampering with your connection.
Don't add an exception unless
you know there's a good reason why this site doesn't use trusted identification.1