Get basic tracking/SEO stuff situated.

Add the site to Google Webmaster Central. Get a tracking code from Google Analytics, and then remember to actually put the tracking code in the site. If you’re using WordPress there’s a Google Analytics plugin that makes it easy, although performance-wise you’re probably best off simply sticking it in the page footer.

Decide whether to www or not to www early on. You don’t want people accessing both www and non-www versions of your site – it can damage your page rank. Some people like www and some do not, but to me it’s a personal preference. I leave it in just out of habit.

Also, don’t forget to generate a sitemap when you’re ready for launch. Submit the sitemap to various search engines.

Configure Gmail.

Of course, if you aren’t using Gmail then this probably won’t be very useful. There are already some really good tutorials on how to make your domain work with Gmail, so I’m not going to write it out here. I did discover that not everybody has access to their DNS records, so you may need to contact support for your hosting to get everything squared away.

If you’re using WordPress, do a little prep work.

Get a WordPress API key for Akismet instead of ignoring the warning for weeks, unless you don’t plan on allowing comments. In that case, delete Akismet altogether, along with any other unused plugins (*ahem* Hello Dolly). Don’t just deactivate, delete. Check on your permalink settings before making the sitemap, so you don’t need to go back and forth. Install Google XML Sitemaps and generate the sitemap in the admin panel.

Do your social networking junk.

Make a Twitter account. Make a Facebook account (you probably already have one of these and are level 350 in Mafia Wars) and decide whether you want a page or group. Go claim your site on Technorati if it’s a blog, and plant a few networking seeds while you’re at it. Add your social networking buttons, either via plugins like Sociable which makes share buttons, and/or Social Links Sidebar, which pretty much does what it says. I went the hard-coding route to cut down on plugin overhead, but for most people this will not be a concern or issue.

So, there you have it. Next post will (hopefully) be more interesting!