mimjannat
New Member
Posts - 1
Likes - 0
Joined - January 1970
|
Post by mimjannat on Jan 13, 2024 23:06:25 GMT -5
Keep a check on the Google Search Console for any indexing issues Google runs into. Check for index count, crawl errors, and search queries, etc. Make sure your new site is getting indexed and crawled correctly. Google has a full list of everything to check. Redirect HTTP to HTTPS Checklist After the HTTPS migration is done you need to check whether you have taken care of all essential points. Pick up an HTTP to HTTPS checklist or create your own with extra points specific to your websites. Follow the checklist as you work with the migration. In the end, go over the checklist and check if you have marked all the points completed. Summarising all that we discussed above is the below checklist C Level Email List you can use to redirect HTTP to HTTPS. Start with a test server. Crawl the current website. Read any documentation regarding your server or CDN for HTTPS. Get a security certificate and install on the server.Update references in content. Update references in content. Update references in templates.Update canonical tags. Update canonical tags. Update hreflang tags. Update any pluginsmodulesaddons. Change any CMSspecific settings that may need to be changed.Crawl the site to make sure nothing is broken. Crawl the site to make sure nothing is broken. Make sure any used external scripts support HTTPS. Force HTTPS with redirects. Update old redirects currently in use. Crawl the old URLs for any broken redirects or any redirect chains.
|
|