Pricing & Process6 min read

Website launch checklist for 2026: before you pay for ads

Eleven things to verify before a new website gets its first paid visitor: domain, email, speed, redirects, lead tracking, consent, accessibility and AI visibility.

Most launch checklists are a list of things a developer should have done. This one is in the order the money is at risk. Every item is something we have seen missing on a live site, usually found after the advertising had already started.

The rule that ties it together: advertising goes last. Paid traffic multiplies whatever the site does. If the form drops messages, ads buy you dropped messages faster.

1. Own the domain and the DNS

The domain should be registered in an account the company controls, under a company email address, with two people able to log in. Not the agency's account. Not the personal account of a developer who left.

The same goes for DNS. We have watched a company's email stop because the DNS moved to the new host and nobody copied the mail records across. The website was fine. Nobody could write to the people who owned it.

Check: before any DNS change, export every existing record. After it, compare.

2. Make email arrive

A contact form that sends mail from your domain needs SPF, DKIM and DMARC records, or its messages go to spam. That includes the copy sent to your own sales inbox. Google and Yahoo have required authentication from bulk senders since 2024, and filtering has tightened for everyone else too.

Check: submit the form, then look at the headers of the email that arrives. All three should say pass.

3. Choose hosting for the people who will maintain it

The best host is the one your team can operate at two in the morning. A managed platform costs more per month and less per incident. A private server is cheaper until the person who set it up is on holiday.

Ask what happens when it breaks: who is alerted, where the backups are, and when a restore was last tested. A backup nobody has restored from is a hope.

Check: restore last night's backup to a scratch environment before launch, once.

4. Measure speed on a phone, not on your laptop

Google's Core Web Vitals set the bar: the main content visible within 2.5 seconds, a response to a tap within 200 milliseconds, layout shift under 0.1, for three quarters of real visits.

The usual causes of failure are not exotic. Too many font files. A hero image loaded at low priority. A chat widget and three trackers on every page.

Check: run the test on a mid-range phone profile, on an inner page, not only the home page.

5. Redirect every old address

If the new site replaces an old one, every old URL needs somewhere to go. Rankings and inbound links are attached to addresses, not to the brand.

Do it by script. Take the old sitemap, request every URL against the new site and list what does not answer with a redirect or a page. On a site with a few thousand pages the first run always finds some, and translated sections are the ones most often forgotten.

Check: zero old URLs returning 404, in every language.

6. Make missing pages say so

A page that does not exist must return a 404 status. It sounds too obvious to list. We have seen a loading component turn every missing page on a site into a 200, which tells a search engine that thousands of empty pages are real. It is one of several failures that report success while doing nothing.

Check: request an address that cannot exist and read the status code, not the page.

7. Count leads, not button presses

Before launch, decide what a conversion is and prove the site reports it. The default in Google Analytics counts a form submission on every attempt, including the failed ones, so the number looks healthy while the inbox stays empty. We wrote up how to count only accepted leads.

Check: ask where the conversion event is sent from: before the server accepts the message, or after. If the answer is "before", or nobody knows, fix that ahead of anything else on this list that costs money.

8. Ask before you track

Visitors from the EU, the UK and Switzerland have to agree before analytics cookies or session recording start. A banner is not enough: the trackers have to wait for the answer, and "Reject" has to be as easy as "Accept". The details of doing that on a fast site are in our write-up of a consent layer for Next.js.

Check: open the network tab, press Reject, and confirm nothing is sent to an analytics host.

9. Meet the accessibility baseline

This stopped being optional. The European Accessibility Act has applied to online shops and many other consumer services in the EU since June 2025, and in the United States ADA claims over websites are routine and mostly aimed at small and mid-sized businesses.

The common failures are cheap to fix before launch and expensive after: contrast, form labels, keyboard access, alternative text.

Check: complete the main task of the site, buying or enquiring, using only the keyboard.

10. Let the machines read it

A growing share of first impressions happens inside an assistant. Someone asks which companies do what you do, and the assistant reads the sites it can reach.

Two things decide whether yours is among them. It has to be fetchable, and bot protection often blocks assistants without anyone choosing that. And it has to say plainly, in text on the page, what the company is, where it is and what it sells. Not in an image. Not behind a script.

Check: request the home page with a plain HTTP client and read what comes back. That is your site, as a machine sees it.

11. Close the obvious doors

Nobody expects a launch-day penetration test. Three things are worth an hour.

No secret keys in the front-end bundle, which is easier to get wrong than it looks. Every dependency and the server runtime on a patched version, which in 2026 matters more than it used to. And a rate limit on every form, so the first bot that finds it cannot send you ten thousand messages.

Check: search the built JavaScript for the first characters of each key you hold.

Then, advertising

Only now. Send one test lead through the same path a paid visitor will take: the ad's landing page, the form, the CRM, the sales inbox, the conversion in the ad platform. If it appears at every step, switch the campaign on.

If one step is missing, you have just found it for the price of one test instead of a month of budget.

What this looks like as a service

Every item here is a check with a pass or a fail, which is why it works as a fixed piece of work. Our website audit runs this list and the deeper version behind each item against a live or nearly live site, and returns ranked findings with the steps to reproduce each one.

If you are about to launch, or about to start paying for traffic to a site nobody has checked this way, tell us what you are launching.