One of the easiest ways to lose search traffic during any site migration is missing or botching redirects.
Because of the importance of redirects in the move to HTTPS it isn’t a good idea to trust it to a redirect plugin,
the best way to implement them is at a server level or via the .htaccess/web.config or equivalent file.
A catch-all redirect from HTTP to HTTPs will ensure the smoothest transition. Then creating the redirect
rule it is wise to look at previous redirect rules to ensure there are no existing catch-all redirects in
place that will lead to link chains. For instance, if your site automatically redirects to the trailing slash
“/” version of a page, it is possible that the following chain could occur:
As previously noted, it is advisable to avoid redirect chains, especially on such as large scale, as they have the potential
to eat into the crawl budget of the site and render some pages unreachable during a bot’s crawl.
It is also necessary to ensure you update your redirect rules for the hostname. For instance, if you have a redirect
rule in place for all non-www. to redirect to the www. version this will need to be updated, i.e. from
A crucial step in the HTTP to HTTPS migration is remaining calm once you’ve pulled the trigger. No matter how well you follow
guides there will always be nuances for your particular site that could mean a step gets overlooked or executed incorrectly.
A level head throughout the process and a keen eye on the metrics will mean you are able to spot and react to any issues as they arise.