Website Launch Checklist for Small Businesses

The short answer

Run it the day before launch and again the morning after, because DNS changes and caches make the first hours behave differently from the staging site.

Forms, emails and notifications

Forms are the most common launch failure because they work on staging, where the developer's address is the recipient, and break in production, where email is sent from a new domain that no mail server trusts. Test with a real submission from a phone, not from the admin account.

Every form: submit, receive the notification, receive the auto-reply if there is one, and check the message lands in the inbox rather than spam.
Sender domain: SPF, DKIM and DMARC records exist for the domain the site sends from. Without them, Gmail and Microsoft will quietly drop your enquiries.
Recipients: notifications go to a shared address that is monitored during holidays, not to one person.
Booking or chat widgets: make a test booking and confirm it appears in the calendar you actually use.
Thank-you page or state: exists, is not indexed, and is the page your conversion tracking listens for.

Redirects from old URLs

If you are replacing an existing site, its old addresses carry rankings, links from other sites and bookmarks. Every one of them that returns a not-found page after launch loses that value and shows an error to whoever clicks. Export the old site's URLs from Search Console or a crawl, map each to the best new equivalent, and set permanent redirects before the switch.

Old page type	Redirect to	Not to
Service page that still exists	The matching new service page	The homepage
Service you no longer offer	The closest category or the services overview	A not-found page
Blog post kept	Same post at its new address	The blog hub
Old contact, about, pricing	The new page with the same role	A page with a different purpose

Redirecting everything to the homepage is treated as a soft error by search engines and confuses visitors; redirect to the closest match or accept a genuine not-found.

Tracking and consent

Tracking breaks at launch in two opposite ways: tags that were on the old site are forgotten, or tags are installed twice, once in the theme and once in Tag Manager, and every visit counts double. Open the site in a private window with the browser's network panel, accept the banner, and watch what fires. Then reject the banner and confirm nothing non-essential fires at all; how to get that right is in our guide to cookie banner rules in Sweden.

One analytics property, one tag, the correct measurement ID, and a test event visible in real time.
Key events defined for the actions that matter: form sent, call clicked, booking made. Our GA4 setup guide covers the settings.
Search Console verified for the new site, sitemap submitted, and the old property kept so you can compare.
Staging site blocked from indexing and the production site not blocked, which is the single most common mix-up on launch day.

Legal pages and company details

A Swedish company website must state the company's registered name, organisation number, address and contact details, and, if VAT-registered, the VAT number. Web shops have further duties before purchase under the Distance Contracts Act. Beyond that, a privacy policy that matches what the site actually does, a cookie policy, and terms if you sell or book online. The launch is also when old text slips through: a previous company form, a closed office, a colleague who left. Read the footer, the contact page and the about page aloud once.

Accessibility deserves a line here too. Alt text on meaningful images, visible focus states, form labels that are real labels and colour contrast that passes are cheap at launch and expensive to retrofit.

Speed and mobile checks

Test on a real phone over mobile data, not on the office Wi-Fi, and open every page type: home, a service page, the contact page, the blog. The things that fail are predictable. Images uploaded straight from a camera at full size. A hero video that autoplays. Fonts loaded from three sources. A cookie banner that covers the whole screen and cannot be dismissed with a thumb. Fix those four and most sites pass Core Web Vitals without further work.

When you do not need this checklist, or us: a single-page site built on a hosted platform with one form and no previous site has perhaps five items to check, and your platform's own launch guide covers them. If you are replacing a site with rankings, forms and a booking flow, the cost of a missed item is real enquiries. That is when a professional website launch at a fixed price, or an hour of review before you press go, is worth it. See the pricing page or book a call and we will walk the list with you.

Frequently asked questions

When should we launch: which day and time?

A weekday morning, early in the week, when the developer and you are both available for the rest of the day. Never a Friday afternoon. DNS changes can take hours to propagate, so plan for the old and new site to coexist briefly and keep the old hosting live for at least a week.

How long do redirects need to stay in place?

Indefinitely, in practice. Search engines update within weeks, but links from other sites, printed materials and bookmarks never do. Keep the redirect map as part of the site and add to it rather than removing entries.

Should we announce the new site before it is fully checked?

No. Launch quietly, run the morning-after checks, fix what you find, then announce. An announcement drives your most engaged customers to the site on the day it is most likely to have a broken form.

What if we find problems after launch?

Expect a few. Keep a shared list, fix forms and redirects first because they lose enquiries, then tracking, then cosmetics. Most agreements include a correction period after acceptance; agree its length and scope before launch rather than after.