- Remove any dev output
- Logging should be recorded in a dedicated log file on the server
- The log files should be rotated. Kinsta does this automatically. For custom logs, you’ll have to setup yourself, although in general there shouldn’t be custom logging in production unless it’s being monitored for specific reasons and finite time.
- Make sure the site shares well on different social networks via OG properties.
Eg) Moving from preprod.site.com to site.com
- Update URLs: wp search-replace //preprod.site.com //site.com. Also run the same search-replace without the leading slashes (wp search-replace preprod.site.com site.com) as internal urls in WP Blocks have their slashes escaped and are ignored by the previous query.
- Update Emails: wp search-replace [email protected] [email protected]
- Clear Cache: wp cache flush
- Update Kinsta (or other hosts) domain config to accept site.com and www.site.com
- Test the new configuration from your local machine by adding to your /etc/hosts: 184.108.40.206 site.com (or whatever IP the site is on).
- Test for Broken Links or use Screaming Frog to crawl if it’s a smaller site.
- Point the DNS to the new site. A -> IP & CNAME -> www.site.com
- Install an SSL certificate and force HTTPS
- Activate Caching and/or any production environment variables
- Check the XML sitemap generated by Yoast SEO @ www.site.com/sitemap_index.xml, then set Yoast to prevent indexing of non pertinent content (for example the famous author archive pages).
- Setup 301 redirects in Kinsta for one main domain. By convention, HTTPS:// (non-www).
- Setup any 301 redirects if needed
- Pagespeed Test make sure it receives at lease 80+
- check for GA installed
- broken links / images
- presentable sharing preview on Facebook
- presentable SERP listings (configure SEO plugin to a sensible default)