410-942-0220 Request an Estimate

13 Steps to a Successful Website Launch

We all have been there, the client pushes for a launch date that is about 3 days before everyone had planned on. It is now Friday at 3:00pm and you are being pulled in all directions trying to get everything ready for the big launch. You keep asking yourself, “Did I forget anything?” “What else do I need to do?” Hopefully you pulled through and made the launch a successful one without anyone knowing otherwise, but for those who were not as lucky I hope this list can save you some headaches on your next big launch.

Thanks Boss

General Advice for All Website Launches

Avoid the temptation to prematurely launch the website. Even if a client is breathing down your neck, trying to push for a fast launch, and just wants you to publish files… don’t. Instead work as fast as you can, in a methodical other and do not cut any corners. You are ultimately the one who suffers if you launch the site early and forget to update the navigation thus rendering the site unusable, not the client who forced you to launch early.

Plan to launch early in the day and early in the week. If you have the liberty of scheduling a time to launch the site, try to shoot for a date early in the week rather than Friday at 3:00. More often than not if you have that launch at Friday at 3:00 everyone does a quick test and goes home for the weekend. On Monday you come back to the office with a inbox full of SOS’s from your client for an error that has been around all weekend. Even if your traffic is higher on Monday at 10:00am, you will have a better chance of being the first one to pick up on a problem and fix it quickly causing only minimal damage. An error that goes uncaught for the entire weekend could be very bad news.

Inform the entire team of the launch. Make it a point to inform every member of the team involved with the website launch of the time and date of the launch BEFORE the actual launching of the website. By making sure everyone is on the same page about the date and time of the launch it will reduce the risk of someone going out to lunch at that critical moment when they are suppose to be publishing files.

Website Launch Checklist

  1. Go through entire site and check for spelling and grammatical errors.
  2. Validate all code using W3C Validator http://validator.w3.org/ . Validate all style sheets using W3C CSS Validator http://jigsaw.w3.org/css-validator/ .
  3. Check all forms. If you have a contact form make sure that you have changed your email address, which you used for testing, to the clients requested email address. Make sure the reply to address on the forms is the clients and not yours.
  4. Test your .htaccess file. Make sure your website redirects to www, and make sure all existing pages you are replacing have been successfully 301’ed.
  5. Ensure that any images that have been referenced absolutely have the production URL and not the development URL. (i.e. html emails)
  6. If any dummy data was added to database or to site while testing make sure to remove prior to launch.
  7. If you are launching an ecommerce website, make sure that you’re using the cheapest merchant services to minimize on processing fees, and confirm that your merchant account is out of TEST mode and DEBUG mode is turned OFF when it’s time to launch.
  8. If client has requested, install Google Analytics and/or tracking scripts
  9. Make sure all email addresses associated with the website have been setup and tested prior to launching the website. (i.e. contact@yourdomain.com)
  10. Test website on multiple browsers and on multiple computers if possible. Make sure site degrades nicely for IE6. (tip: Ask the client what browser they are running along with what toolbars/plugins that they have. Even though you have built the website for the general public make sure to please your client first.)
  11. If you are using SVN a version control system, (which you should be) follow these last steps.
    1. Commit all final files to the repository, including user submitted images and content to the repository to publish for the initial launch. (i.e. FCKeditor/TinyMCE user_files, product images from CMS, uploaded PDFs, etc)
    2. Update/push all of latest files to production server.
  12. If you are using traditional FTP publishing follow these last steps.
    1. Create final backup of all files from development server. Ideally you could go to your hosting control panel and gzip entire site directory to download as one file.
    2. Upload all final files to production level FTP. Make sure to check your final log to see if any files failed to upload for one reason on another.
  13. Repeat steps 3,4 and 10 Even though you have already done these steps, take the time and do them again. It can never hurt to do 5 minutes more of testing.


This list may not work for everyone so if I left something out which you do every time you launch a new site please tell us about it. We all have to launch sites and we all want them to go as smoothly as possible, the more information that gets shared on successful launches the better.

Tags , , , ,
Categories News, Tips, Website Design, Website Development

  • 14. Politely tell your client “yes, this would be too late to add all those new features, we’re launching in 10 minutes”.

  • htaccess would be better. 😉

  • Ben

    One more important item, have a rollback plan if things go sour.

  • That’s a pretty good generic checklist. I think it may be better to suggest using a “Version Control System” instead of saying that you should be using Subversion. Git, CVS, and others are also very good solutions.

    It may also be better to know which browser and/or plugins the client/user is using way before launch. Preferably when signing a contract or deciding whether or not to take on the project.

    “6. If any dummy data was added to database or to site while testing make sure to remove prior to launch.”
    I take it this means the same database server is being used for testing and production. I don’t think that’s a good idea in general, but that’s my own personal thoughts. I think it may be better served to “removed dummy data pre-installed with Product.” An example of this would be removing the “Hello World” post from a WordPress install and it’s associated “This is a comment” entry.

    All in all. Great write up.

    • John,
      Thanks for commenting, you are correct I should have used “Version Control System” rather than classifying them all as SVN. You are also correct about #6, in a perfect world you should have a dev database and a production db, however that is not always the case.

  • Rob

    I mean, this blog was good, but I think the best word of advice I got was to use the phrase “Thanks for being a champ.”

    • Rob, Thanks for being a champ and posting a comment. What are the steps that you use when you launch a website? Anyones different than what I have mentioned above?

  • Pingback: Towards A Successful Website Launch | KillerBlog()

  • Rob

    I think you’re right on Matt. The only other thing I can think of is building a quick “Site Is Being Updated! Check back at 2:00PM to see our updated design” or something like that.

  • Pingback: Graphic Euphoria » Blog Archive » Checklist for a Successful Website Launch()

  • Pingback: Linkit 20.2. - 20.2. | Valontuoja()

  • Thanks for the post!! I’ll be launching a blog soon and this list really helped.

  • Pingback: links for 2009-03-02 | Static-Romance.Org()

  • Pingback: FTW Friday - 06 March 2009 | Border7 Studios()

  • ohhh nice info

  • Haha ^^ nice, is there a section to follow the RSS feed

  • Very helpful check-list, thanks.

  • piyush

    cool matter ……………

  • Rob
    • Damn… Well at least theirs has some items that are not on my list. It looks like their list is more for SEO with a lot of items that are non critical for a successful site launch, but rather if you have time go and put these items in.

  • rocky

    That’s a pretty good generic checklist. I think it may be better to suggest using a “Version Control System” instead of saying that you should be using Subversion. Git, CVS, and others are also very good solutions. It may also be better to know which browser and/or plugins the client/user is using way before launch. Preferably when signing a contract or deciding whether or not to take on the project.

  • This article has been shared on favSHARE.net.

  • Pingback: Essential Checklist’s For Successful Website Launches | Web Media Magazine()

  • It was interesting to browse trough 🙂 keep up the good work and thanks for sharing.

  • Pingback: Portfolio David Dylan Jessurun()

  • Friday at 3p does always seem to be the case doesn’t it? Thought it was just my clients…

  • Nice list, will make for a good checklist to verify against prior to launch.

  • Pingback: Website Launch to be anounced! « New Community Horizons()

  • Pingback: MyInkTrail: Best of the Web, February 2009 | MyInkBlog()

  • Jim

    Client: I NEED to launch by 3 pm Friday. Me: Well.. that will be an additional 3,000 dollars, or you can wait till Monday at 7 am. Client: Monday at 7 sounds great. Me: oh well, see you Monday.

  • Seems like this a “checklist” of things to prepare your website to be launched, but not to actually launch it and make money with it…

    • Rick, you are correct, that is why the title of the article is 13 Steps to a Successful Website Launch, and not just 13 steps to a Successful Website. I hope it could at least help you in launching your site, having your site make money for you is a whole different ballgame!

  • Pingback: Why You Need A Business Website()

  • Thanks for the tips. I hope I can follow them 🙂

  • Steve

    Good article. However, I was hoping to find other things like: go to PRWeb and make a press release. And, other suggestions to let the citizens of the world wide web know about my new site that I hadn’t thought of. I don’t know if this falls under the previous comment of launching a successful site as opposed to a site.

    If anyone knows of an article that covers this I’d be interested in seeing it.

  • Some good tips, sometimes it’s difficult to remember all of these things, but get in the habit of every time with no exception helps.

Client Login

Invalid username and/or password

Forgot your Password?

Invalid username