1. Moving to HTTPS
Tips for Success
#httpsmigration at #FOS17 by @aleyda from @orainti

2. Hallo #FOS17
#httpsmigration at #FOS17 by @aleyda from @orainti

3. I’m Aleyda Solis
#httpsmigration at #FOS17 by @aleyda from @orainti

4. ORAINTI.COM @ALEYDA FB.COM/ALEYDASEOTIPS/
I Do SEO
BITLY.COM/LIBROSEOALEYDA
I’m Aleyda Solis
I PublishI Share
#httpsmigration at #FOS17 by @aleyda from @orainti

5. I Blog I Speak I’m Featured
I’m Aleyda Solis
#httpsmigration at #FOS17 by @aleyda from @orainti

6. I help my clients move to
HTTPS
#httpsmigration at #FOS17 by @aleyda from @orainti

7. https://letsencrypt.org/stats/
Over 50% of the pages loaded by
Firefox are now using HTTPS
#httpsmigration at #FOS17 by @aleyda from @orainti

8. bit.ly/spreadhttps
HTTPS is already becoming
the “default” in top SERPs
#httpsmigration at #FOS17 by @aleyda from @orainti

9. It’s about security, users safety, trust
& experience
#httpsmigration at #FOS17 by @aleyda from @orainti

10. The perfect opportunity to start using
HTTP/2 & improve your site speed too
bit.ly/http2seo
#httpsmigration at #FOS17 by @aleyda from @orainti

11. Provide another Positive Ranking signal
#httpsmigration at #FOS17 by @aleyda from @orainti

12. The goal is that your users can browse
securely, earning their trust
#httpsmigration at #FOS17 by @aleyda from @orainti

13. Instead of this :(
#httpsmigration at #FOS17 by @aleyda from @orainti

14. While also migrating your rankings
& traffic from your HTTP to HTTPS URLs
#httpsmigration at #FOS17 by @aleyda from @orainti

15. Without traffic drops
#httpsmigration at #FOS17 by @aleyda from @orainti

16. Instead of this
#httpsmigration at #FOS17 by @aleyda from @orainti

17. bit.ly/httpsmigration
Let’s see the most critical steps as well as dos
& dont’s to maximize chances of success
#httpsmigration at #FOS17 by @aleyda from @orainti

18. Before Moving
#httpsmigration at #FOS17 by @aleyda from @orainti

19. Don’t show and allow access to content via
your HTTPS version if you haven’t migrated yet
#httpsmigration at #FOS17 by @aleyda from @orainti

20. You want to avoid having mixed indexation,
cannibalization & content duplication issues
#httpsmigration at #FOS17 by @aleyda from @orainti

21. Make sure to canonicalize and
refer consistently to your HTTP URLs
301-redirect Canonicalize Link
Include in
XML
Sitemaps
HTTP
#httpsmigration at #FOS17 by @aleyda from @orainti

22. To later facilitate the migration towards HTTPS
301-redirect Canonicalize Link
Include in
XML
Sitemaps
HTTP HTTPS
#httpsmigration at #FOS17 by @aleyda from @orainti

23. Create GSC profiles for your HTTPS domains &
subdomains to start monitoring them
#httpsmigration at #FOS17 by @aleyda from @orainti

24. Don’t mix HTTPs migrations with
other structural Web changes
#httpsmigration at #FOS17 by @aleyda from @orainti

25. Verify the type of SSL Certificate you need,
like wildcard ones for multiple subdomains
sslshopper.com
#httpsmigration at #FOS17 by @aleyda from @orainti

26. It doesn’t need to be expensive! You can even
do it for free by using Cloudfare
bit.ly/freehttps
#httpsmigration at #FOS17 by @aleyda from @orainti

27. Check with your hosting provider if they offer
them, as it might be easier to enable it too
#httpsmigration at #FOS17 by @aleyda from @orainti

28. If you work with CDNs you will also need to
activate it for your subdomains zones
#httpsmigration at #FOS17 by @aleyda from @orainti

29. Create a list of your top pages from a visibility
& conversion perspective to monitor closely
#httpsmigration at #FOS17 by @aleyda from @orainti

30. When Moving
#httpsmigration at #FOS17 by @aleyda from @orainti

31. https://www.sslshopper.com/
ssl-checker.html
Make sure that the SSL certificate
is effectively installed
#httpsmigration at #FOS17 by @aleyda from @orainti

32. For HTTP to HTTPS migrations you can’t use
GSC “Change of address” feature
#httpsmigration at #FOS17 by @aleyda from @orainti

33. You need to 301-redirect, canonicalize, link
and refer to your HTTPs URLs consistently
301-redirect Canonicalize Link
Include in
XML
Sitemaps
HTTPSHTTP
#httpsmigration at #FOS17 by @aleyda from @orainti

34. Update your canonical & hreflang tags
so they refer to the HTTPS URLs
#httpsmigration at #FOS17 by @aleyda from @orainti
Don’t
do this

35. If your links use absolute URLs they need
to be updated with your HTTPS ones
#httpsmigration at #FOS17 by @aleyda from @orainti
Don’t
do this

36. Generate a new XML sitemap
with your HTTPS URLs
Don’t
do this
#httpsmigration at #FOS17 by @aleyda from @orainti

37. Implement 301-redirect from each of your
HTTP URLs to their HTTPS versions
bit.ly/redirectgenerator
#httpsmigration at #FOS17 by @aleyda from @orainti

38. http://searchengineland.com/chromes-
devtools-seo-10-ways-use-seo-audits-266433
Be careful if you’re hotlinking, all resources
(images, css, js) need to be moved to HTTPS too
#httpsmigration at #FOS17 by @aleyda from @orainti
Don’t
do this

39. Remember these should be permanent
301-redirects & not 302s
#httpsmigration at #FOS17 by @aleyda from @orainti

40. Make sure to also update your robots.txt
to your HTTPS domain & update URLs if needed
#httpsmigration at #FOS17 by @aleyda from @orainti

41. If you use Wordpress there’s a plugin that
facilitates it
https://es.wordpress.org/
plugins/really-simple-ssl/
#httpsmigration at #FOS17 by @aleyda from @orainti

42. After Moving
#httpsmigration at #FOS17 by @aleyda from @orainti

43. Validate your SSL certificate & secure content
status
https://www.whynopadlock.com/
#httpsmigration at #FOS17 by @aleyda from @orainti

44. Crawl your migrated site emulating both
desktop & smartphone Googlebots
#httpsmigration at #FOS17 by @aleyda from @orainti

45. Do also a list crawl of those top pages
that you wanted to prioritize
#httpsmigration at #FOS17 by @aleyda from @orainti

46. Have all URLs been migrated? Is there a
performance change?
#httpsmigration at #FOS17 by @aleyda from @orainti

47. Do you find HTTP URLs in the crawl?
Errors, redirects & canonicalization issues?
#httpsmigration at #FOS17 by @aleyda from @orainti

48. See which old HTTP URLs you’re still linking,
if they’re showing errors or are redirected
#httpsmigration at #FOS17 by @aleyda from @orainti

49. Do the same looking for canonical tags
pointing to old HTTP URLs
#httpsmigration at #FOS17 by @aleyda from @orainti

50. Have XML sitemaps also been updated?
What’s the gap vs. the crawled URLs?
#httpsmigration at #FOS17 by @aleyda from @orainti

51. Check if the Page-to-Page Redirects are
Effectively Implemented with 301s
#httpsmigration at #FOS17 by @aleyda from @orainti
Don’t
do this

52. … and that they’re redirecting to the
relevant and indexable HTTPS URLs
#httpsmigration at #FOS17 by @aleyda from @orainti
Don’t
do this

53. That there are no chain redirects
between them
#httpsmigration at #FOS17 by @aleyda from @orainti
Don’t
do this

54. For independent mobile sites, verify redirects
and rel alternates & canonicals w/ desktop
#httpsmigration at #FOS17 by @aleyda from @orainti
Don’t
do this

55. Prioritize to fix pages w/ erroneous protocol,
status & canonicalization w/ high traffic
#httpsmigration at #FOS17 by @aleyda from @orainti

56. Look for orphan URLs by identifying which
URLs with organic traffic are not in the crawl
#httpsmigration at #FOS17 by @aleyda from @orainti

57. Once fixed, you can submit your HTTP & HTTPS
URLs & XML sitemaps to be re-crawled
#httpsmigration at #FOS17 by @aleyda from @orainti

58. Check in your log files for googlebot
“before” & “after” behavior & crawled URLs
#httpsmigration at #FOS17 by @aleyda from @orainti
Screaming Frog Log Analyzer

59. And start monitoring how your index status
moves to HTTPS in Google Search Console
#httpsmigration at #FOS17 by @aleyda from @orainti

60. Dank Je!
#httpsmigration at #FOS17 by @aleyda from @orainti