Outline

This document is to clarify what needs to happen, and when, to ensure a smooth launch of your project.

Prior to Pre-live Deployment

These tasks can be completed at any point during the project.  They should all be completed at least 1 week before Launch.

Update Email Domain Settings (if you have DNS control of the email domain before launch)

Update your email domain settings for SPF, DKIM and (if required) MX.  Please see the Email Domain Recommendations and FAQs document for more information.

Prepare Domains (if using an existing subdomain for the new site)

Ask your domain name provider to reduce the Time to Live (TTL) to a minimum (such as 15 minutes) so that the new site propagates swiftly once the domain name is switched.

You can check your TTL by visiting http://mxtoolbox.com/DNSLookup.aspx and entering your domain.

Prepare Domains (if using a new domain / subdomain for the new site)

Ask your domain name provider to set the CNAME(s) for the Live URL(s).  Your Madgex Project Manager will supply this information as soon as it’s available.

If you would like the new Jobseeker or Recruiter/Employer Services sites to be password protected until launch, please inform your Project Manager.

Prepare for Final Data Cut (if migrating data)

Ensure that arrangements are in place to supply a final data cut to Madgex for the live, pre-launch data migration.

It's essential that the data is supplied in exactly the same format as it was during the test data cut, earlier in the project.

Prepare Data on Existing Site (if migrating data)

Ensure that the data is as up to date as possible (eg. all the latest jobs have been posted and unecessary data archived).

Prepare a Holding Page (if switching off an existing site which cannot be disabled)

If switching off an existing site, the site should be replaced with a holding page. Madgex can supply you with the HTML for a generic holding page.  If you would like help with a customised page, please let your Project Manager know.

Prepare Redirects (if you have job content on a different directory / domain / subdomain from the new site)

It is your responsibility to set up redirects if you have job content on a different directory / domain / subdomain from the new site.

Ensure that your redirects or redirect rules are ready to implement as soon as the site is launched.  If you require guidance on how pages will map between the existing and new site, please ask your Project Manager.

The redirects should be signed off by:

1. Your team responsible for SEO.
2. If the project includes data migration, your team resonsible for the source data.
3. If the project includes a reverse proxy (e.g. /jobs URL), your team responsible for the reverse proxy.

Prepare robots.txt and sitemap (if using a reverse proxy)

The robots.txt and sitemap for the top level domain will need to be updated to take account of the Job Board. For example, robots.txt should link to the sitemaps automatically generated by the Job Board.

Prepare Communications for Launch

Prepare the communications (including any marketing) for the launch of the new site.

If passwords will be reset as part of a data migration, users will need to go through the 'Forgotten password' process on the new site.  Madgex cannot provide password reset links for individual users.  

Switch on SSO (if you have SSO on the site)

Switch on the SSO IDP for Live and (if possible) for pre-live too.

Pre-live

Pre-live is the full pre-launch version of the sites and CMS.  Any changes made here will appear on the Live site after launch.

If required, your Project Manager can supply your pre-live access details in advance.

Populate Sites with Primary Content

Ensure that the content on the pre-live sites is populated, as per the guidelines in the Content Population Guide. The Primary Population elements should all be in place, and any relevant Secondary elements should follow as soon after launch as possible.

Test Web Services / REST API (if using Web Services or REST API)

If using the Job Posting, Job Export, or Billing Web Services, or the REST API, these can be tested from this point forward.  Please note that any changes made will be on the Live site after launch.

Test Redirects (if migrating data, or you have job content on a different directory / domain / subdomain from the new site)

Ensure redirects have been activated and are working as expected.

Test SSO (if you have SSO on the site)

If possible, the SSO IDP should be set up and tested on pre-live.

Launch

Any change requested on launch day adds a major risk (and potential delay) to the successful launch of the project.  At this point, changes should be avoided unless absolutely essential for launch.

Approve Soft Launch (if you are launching under password protection)

When you are ready to launch the sites under password protection, inform your Project Manager.

As soon as this is actioned, the pre-live URLs will no longer work.

Please note that the date of the soft launch is the contractual 'launch date' for billing purposes.

Switch Off or Disable the Existing Site (if you have an existing site)

The existing site will need to be disabled or switched off at this point.

If disabling the site, you will need to ensure that users (both Jobseekers, Recruiters and CMS Admin) are prevented from making any changes.

If switching off the site, replace it with the holding page that you have prepared.

Provide Final Data Cut (if migrating data)

After the existing site is disabled or switched off, create a final data cut and transfer it to Madgex by the method previously agreed on.

The final data cut should be transferred at least 3 working hours before potential launch (eg. 2pm the day before a launch at 9am).  You should take into account the time required to save and capture the data after the existing site is switched off.

Check Data Migration (if migrating data)

You will be informed as soon as the data migration is complete.  

At this point, you can update and perform any final checks on the migrated data.

Approve Launch

When you are ready to launch the sites, inform your Project Manager.

Madgex will remove any password protection for the Jobseeker and Recruiter Services sites at this point.

Update Domains (if using an existing domain or subdomain)

Ask your domain name provider to set the CNAME(s) for the Live URL(s).  Your Project Manager will have already supplied this information.

Once the update has been made, the sites are effectively launched, although Madgex does need to complete a number of final launch tasks to enable the launch completion.

It may take some time for the new CNAME(s) to propagate globally.  You can check on real-time propagation at www.whatsmydns.net, where you can input the site’s live URL and monitor its progress.

Activate Redirects (if you have job content on a different directory / domain / subdomain from the new site)

Activate the redirects you have prepared.

Activate robots.txt and sitemap (if using a reverse proxy)

Activate the robots.txt and sitemaps you have prepared.

Update Email Domain Settings (if you only have DNS control of the email domain at launch)

Update your email domain settings for SPF, DKIM and (if required) MX.  Please see the Email Domain Recommendations and FAQs document for more information.

Communicate Launch

Communicate the launch of the new site to Jobseekers, CMS Admin and (where appropriate) Recruiters.

Perform Post-Launch Checks

Perform your own post-launch checks.

If using online payments, these tests should include making a live payment via the recruiter site. You can award yourself a large discount to greatly reduce the cost of this - or you can always refund yourself via your own payment admin system.

After Launch

Populate Sites with Secondary Content

Ensure that the new site is populated with relevant content from the second section of the Content Population document. All of these items should be added to, and updated, during the lifetime of the site.

Checklist