Technote

Development workflow Practical

Series Launching alone — WordPress from zero Part 8 of 8

The night-before launch checklist

Most problems found after launch could have been found in thirty minutes before it. Here is the list, in order.

This is the last part of the series. You have chosen a domain and host, fixed the install settings, picked a theme and plugins, built pages, registered with search engines and set up a mail path. One last pass before you open.

The order matters below: each stage is arranged so that a failure earlier makes the later checks meaningless.

Stage 1 — does it open?

Stage 1 — access and basic behaviour

Watch for mixed content in particular. If SSL is on but the padlock does not appear, something on the page is still loaded over http:// — usually an image or a script. The browser console flags it.

Stage 2 — can search engines see it?

The first line of this stage is the single most important line in the whole series.

Stage 2 — search visibility (miss the first line and the rest is pointless)

Stage 3 — do enquiries arrive?

Submit the form yourself. Send a test enquiry and check both the inbox and the spam folder. If it lands in spam you can still open, but revisit your domain authentication records.

If you configured an auto-reply, read it once. It is the first mail a customer receives from you.

Stage 4 — be ready not to lose anything

The last stage — make the state reversible before you open it

Take a backup of files and database together right before launch. If you can, restore it once somewhere safe — a backup you have never restored is not a backup.

Finally, tidy the accounts: temporary administrators from the build, test users, plugins you no longer use. Changing the password once at this point is worth it too, since it has probably been shared around during the build.

Closing the series

If you have followed this far, you have what you need to open a business site on your own. From here you accumulate content, take enquiries, and add things as the need appears.

When you get stuck in operations, the development workflow archive is a good place to look; and for the work that is genuinely hard to do alone — version upgrades, performance work, security review — our optimization program handles it as one job. How we work is published step by step on the process page.

More on this topic

All technotes

Development workflow Practical

Turning taste arguments into rule checks

"It feels a bit cramped" can be neither argued with nor fixed. Spacing off the scale, colour off the palette, contrast below threshold, missing states — four rules…

Designers 9 min read

Development workflow Practical

Do not swap everything at once

A full swap makes every problem appear at the same moment — which means none of them can be attributed. So you switch one template at a time.

Designers 6 min read

Development workflow Practical

Adding an SCSS build, and whether to commit the output

WordPress themes are expected to deploy without a build step, which leads to the opposite conclusion from ordinary application code — and to its own costs.

Developers 7 min read

₩270,000 · Join the program