By Sarah Dia, HostDroplet Support
Most website launch checklists hand you forty items and treat them all as equally urgent, which is why people either skip the list entirely or spend a fortnight on things that could have waited. The honest version is shorter: a handful of things genuinely need to be right before you go live, a few more want doing in the first week, and the rest can follow whenever.
Here’s that list, sorted by what actually happens if you get it wrong.
Before you launch
These are the ones with real consequences — either visitors see something broken, or fixing it later is significantly harder.
HTTPS working across the whole site. Without a valid certificate, browsers stamp your site “Not Secure” and visitors leave before reading a word. Install it and force every request to the secure version — see enabling SSL in cPanel and redirecting HTTP to HTTPS, then confirm with our SSL Checker. Our guide on what an SSL certificate is explains why it matters beyond the padlock.
Turn off the “discourage search engines” setting. WordPress switches this on during development and forgetting it is the single most common launch mistake we see. Check Settings → Reading and make sure it’s unchecked, then verify with our Indexability Checker. Sites have sat invisible to Google for months because of this one tick box.
Test that your email actually sends and receives. A contact form that silently fails is worse than no form — you never know what you’re missing. Set up a proper address on your domain (here’s how), send a test message both ways, and check it doesn’t land in spam. Our guide on why emails go to spam covers the DNS records that determine this.
Click every link and load every page. Boring, and it catches more problems than anything else on this list. Run our Broken Link Checker for the ones you’d miss, and if your site shows security warnings despite having SSL, our Mixed Content Checker will find the culprit.
Look at it on a phone. Most of your visitors will. Check that menus open, text is readable without zooming, and forms are usable with a thumb.
Set up backups before you need them. The worst time to discover you have no backup is after something breaks. See backing up your WordPress site, and our overview of website backups explains what a genuinely useful backup includes.
In the first week
Important, but nothing catastrophic happens if they slip a few days.
Set up Google Search Console and submit a sitemap. This is how Google finds you efficiently. Verify your site at Search Console, submit your sitemap, and check it’s valid with our Sitemap Checker. Our guide on what a sitemap is covers the details, and if pages don’t appear after a while, why your website isn’t showing up on Google walks through the causes.
Check your page titles and descriptions. These are what people read in search results, and defaults are usually poor. Our Meta Tag Checker shows what you’re currently serving.
Run a speed test and fix the obvious. Use our Website Speed Checker and Google’s PageSpeed Insights. You don’t need a perfect score — compress your images and enable caching and you’ve done most of it. Our guides on why WordPress sites are slow and why mobile is slower than desktop cover the rest.
Lock down your login. New sites get probed by bots within days. Turn on two-factor authentication and use a strong unique password — our guide to web hosting security covers the wider picture.
Set up uptime monitoring. So you find out your site is down before a customer tells you — see what website monitoring is.
What people forget, and regret
Three things that are easy on day one and genuinely painful later.
Your URL structure. Changing page addresses after launch means setting up redirects for every one, and any that you miss becomes a broken link. Settle on a permalink structure before you have content and links pointing at it.
Access to your own domain. If someone else registered it for you, get the login credentials now, while everyone’s on good terms. People discover they can’t access their own domain at the worst possible moment, and it can be slow or impossible to resolve. Our guide on choosing a domain name covers what to get right at the start.
A way to test changes safely. Once your site is live and earning, you don’t want to experiment on it. Setting up a staging site takes twenty minutes and saves a bad afternoon eventually.
What can genuinely wait
Because a checklist that never ends is a checklist nobody finishes.
Your favicon is worth adding but nobody left a site over a missing tab icon. Chasing a perfect speed score is mostly diminishing returns once the basics are done. Advanced schema markup, a custom 404 page, social preview images, analytics dashboards — all good, none urgent. And rewriting your homepage copy for the fifth time is usually procrastination wearing a productive hat.
Launch, then improve with real visitor behaviour telling you what to fix.
One expectation to set before you go live
Publishing doesn’t make you findable. Google needs time to discover and index a new site, and ranking for anything competitive takes months — our honest guide on how long it takes a new website to rank lays out realistic timelines. Knowing that in advance saves a lot of week-two panic about a site that’s working exactly as expected.
Get the pre-launch items right, work through the first-week list when you have a quiet hour, and let the rest follow. If something on the list looks like a problem you’d rather not untangle alone — SSL not applying, email not sending, pages not indexing — our support team is happy to take a look.
