A | B | C | D | E | F | |
---|---|---|---|---|---|---|
1 | Which | What | How | Where | Who | When |
2 | 1.1. | SSL Certification Setting | Get, configure and test the TLS certificate using SHA-2 for SSL. You can do it for free too in case you don't have many resources as it's shared here: https://raventools.com/blog/free-ssl-http2/ | Server | Name, Last Name | dd/mm/yyy |
3 | 1.2. | Google Search Console Registration | Register both domains http & https in Google Search Console, along your www and non-www versions. If you also had registered individual sub-domains or sub-directories in the Google Search Console, replicate that registration & configuration with their https version. | Google Search Console | ||
4 | 1.3. | Rankings Monitoring | Start monitoring the site rankings in parallel with the https domain | Rank tracking software | ||
5 | 1.4. | Current top site pages & queries identification | Identify the top pages -and related queries- attracting organic search visibility & traffic to be prioritized when validating & monitoring the site performance | Google Search Console & Google Analytics | ||
6 | 1.5. | Current site crawling | Crawl the http site to identify and fix any internal broken links & the current Web structure before moving. | Stage Environment | ||
7 | 1.6. | New HTTPS Web setting w/ updated internal links | Set the new Web version to make the changes, test & update the links on a stage environment, to point to the URLs (pages & resources such as images, js, pdfs, etc. too) with HTTPS | Stage Environment | ||
8 | 1.7. | New HTTPS Web canonicalization | Update the canonical tags to include absolute URLs using https on the stage environment | Stage Environment | ||
9 | 1.8. | New HTTPS Web canonicalization | Verify in the stage environment that all of the already existing rewrites & redirects behavior (non-www vs. www; slash vs. non-slash, etc.) are also implemented in the https Web version as they used to work on the http one | Stage Environment | ||
10 | 1.9. | Redirects preparation | Prepare & test the Rewrite Rules that will 301 redirect from all of the identified existing URLs (pages, images, js, etc) on the http domain to the https one | Server | ||
11 | 1.10. | New XML Sitemap Generation | Generate a new XML Sitemap with the URLs with https to be uploaded in the HTTPs Google Search Console Profile once the site is moved | XML Sitemap Generator | ||
12 | 1.11. | Robots.txt preparation | Prepare the robots.txt to be uploaded on the https domain version when the site is launched replicating the existing directives for http, but by pointing to the https URLs if necessary | Robots.txt | ||
13 | 1.12. | Campaigns updates preparation | Prepare changes on any ads, emailing or affiliates campaigns to start pointng to the https URLs versions when the migration is done | Campaigns Platforms | ||
14 | 1.13. | Disavow Configuration | Verify if there were any disavow requests submitted in the past that will need to be resubmitted again for the https URLs versions in its own Google Search Console profile | Google Search Console | ||
15 | 1.14. | Geolocation Configuration | If you're migrating a gTLD that you are geotargeting through the Google Search Console (as well as its sub-domains or subdirectories, in case you're individually geotargeting them), make sure to geotarget them again with the https domain version | Google Search Console | ||
16 | 1.15. | URLs Parameters Configuration | If URLs parameters are handled through the Google Search Console the existing configuration should be replicated in the HTTPs site profile | Google Search Console | ||
17 | 1.16. | CDN Configuration Preparation | If a CDN is used verify that they will be able to properly serve the https domain version of the site and handle SSL when the migration is done | CDN Provider | ||
18 | 1.17. | Ads & 3rd-Party Extension Preparation | Verify that any served ads code, 3d party extensions or social plugins used on the site will properly work when this is moved to https | Ads & Extensions Platforms | ||
19 | 1.18. | Web Analytics Configuration Preparation | Make sure that the existing Web Analytics configuration will also monitor the traffic of the https domain | Web Analytics Platform |