Prepare for Launch

Launching a website requires more work than just publishing the site to the web. There are many tasks required on the back end to ensure that things work properly. The domain name settings must be updated, redirects put in place so old weblinks get users to the new corresponding pages, search engines must be alerted to the changes and more.

University Communications and Marketing and MSU IT Services manage all these activities as part of the launch process. A website is typically launched in approximately one to two weeks from the time that the University Communications and Marketing project lead is notified. The launch will be scheduled in conjunction with the unit and MSU IT Services.

Prelaunch Checklist

When the website is ready for launch (i.e., content is complete or very close), units should:

If replacing an existing website or making major changes to a website, contact University Archives and Historical Collections to determine if the original website needs to be crawled for archival purposes in accordance with MSU's electronic records management practices. To initiate a request, email archives@msu.edu.
Complete any peer reviews or leadership reviews and approvals.
Run scripts to check for very large (uncompressed) files or unused files.
Remove any test pages or unused pages and components in Sitecore.
For existing websites only: Develop a plan for decommissioning the current website after launch (if applicable). Your University Communications and Marketing project lead can assist.
Optional, but encouraged: Contact the MSU Digital Accessibility Team to schedule a website accessibility review.
Notify your University Communications and Marketing platforms group project lead that you are ready to launch.
1. Select a preferred launch date — this must be confirmed with IT Services.
2. Determine if a soft launch will be needed. This means the site is live and visible, but the domain name and URL has not been transferred from the old site. The public could find the new site if they know the URL.
3. Provide Gmail accounts for those who will access your Google analytics. Users can utilize the Google account associated with an MSU NetID but must request enhanced Google feature activation from MSU IT to use these usernames with Google Analytics.
4. Confirm which QA users should have Production access after launch.
Technical review: Complete any changes your University Communications and Marketing project lead recommends based on the website’s technical review.
Redirects: Users with site admin level access can add redirects to the system.

Documentation updated: June 15, 2026