3 min read

Website Launch Checklist: How We Do It

admin : March 08, 2019

Websites

Chapter 1: Pre-launch Tasks

Chapter 2: Launch Tasks

Chapter 3: Post-Launch Tasks

Chapter 1: Pre-Launch Tasks

Save the Photoshop file in the directory for the active project.

https://www.xml-sitemaps.com
Save files in the directory for the active project.

The main item needed is the Google Web Property ID which looks
something like this: UA-12345678-1
If the client already has a Google/Gmail account set up for their business
use that account for Analytics.
If the client has no Google account, create one for them, set up Google
Analytics, and give the client the credentials for the account. Please add
the account login information to LastPass as well for future reference.

All In One WP Security & Firewall – https://wordpress.org/plugins/all-in-
one-wp-security-and-firewall/

WP Mail SMTP – https://wordpress.org/plugins/wp-mail-smtp/

Public website record(s)
1 Record edits/additions for SMTP2GO

Check to make sure site is still functioning properly after doing this.

Chapter 2: Launch Tasks

https://hostsfileeditor.codeplex.com/

TASKS: WORDPRESS SITE LAUNCH

HTTPS Rewrite Rule

# BEGIN Website HTTPS Redirect
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteCond %{SERVER_PORT} 80
RewriteRule ^(.*)$ https://www.WEBSITEADDRESSHERE.COM/$1 [R,L]
</IfModule>
# END Website HTTPS Redirect
o User Enumeration Security Rule
# BEGIN User Enumeration Security Fix
&lt;IfModule mod_rewrite.c&gt;
RewriteEngine On
RewriteCond %{REQUEST_URI} !^/wp-admin [NC]
RewriteCond %{QUERY_STRING} ^author=d+ [NC,OR]
RewriteCond %{QUERY_STRING} ^author={num
RewriteRule ^ - [L,R=403]
&lt;/IfModule&gt;
# END User Enumeration Security Fix

User Enumeration Security Rule

# BEGIN User Enumeration Security Fix
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteCond %{REQUEST_URI} !^/wp-admin [NC]
RewriteCond %{QUERY_STRING} ^author=d+ [NC,OR]
RewriteCond %{QUERY_STRING} ^author={num
RewriteRule ^ - [L,R=403]
</IfModule>
# END User Enumeration Security Fix

Chapter 3: Post-launch Tasks

If you use the Chrome you can use the Google Tag Assistant to check the
script. https://support.google.com/tagassistant/answer/2947093?hl=en

Update DNS records to point to the new website.
Once DNS has completed propagation generate and install an SSL certificate for the site either through Plesk or GoDaddy depending on the site and client’s needs.
SSL clean-up, fix any mixed content errors on the site.
Log in to the clients Google account if we have access to it and verify the site in Search Console.
Add the Yoast site map to Google Search Console.