What Your URL Says Before You Do: A Domain Check for UK Launch Week

There is a moment in every launch week when a founder opens the domain registrar and thinks: right, what did I actually buy here? It is usually the same week the landing page goes live, the first invoice template gets dusted off, and someone asks whether the email address on the site matches the one on the bank account. The domain felt like a five-minute purchase back in the spring. Now it is the first thing every visitor touches, and the last thing anyone checked.

That is worth fixing before launch day, not after. In 2026, the address bar is still the quietest trust signal a UK startup has. It does not get a slide in the pitch deck. It does not appear in the demo. But it is doing work every time someone types your name, clicks a link or forwards your page to a colleague with the message: have a look at these people.

The address bar is a trust signal, not a logo

For a lot of UK buyers, especially small firms, public sector teams and local service businesses, a .co.uk still does quiet work. It says you are here, registered here, and likely to understand the paperwork. It is not a rule, and it is not a guarantee of quality. Plenty of excellent companies run on .com. But a .com can read as somewhere else — not wrong, just less local until proven otherwise.

That matters most when the buyer has never heard of you. A .co.uk beside a Companies House number and a real address reduces the number of tiny doubts. A .com with no location anywhere on the page can make a UK buyer pause, even if the team is in Manchester and the coffee is from a roaster two streets away.

So read your own site the way a cautious buyer would. Does the domain ending match the story you are telling? If you are using .com, is your UK base obvious within the first screen? If you are using .co.uk, is it clear you are not pretending to be a much larger organisation? The domain is not the whole handshake. It is the first half-second of it.

Buy the obvious mistakes before launch week

You do not need a defensive domain portfolio that costs more than your first hire. You do need the variants a hurried customer will actually type. That usually means the plural, the common misspelling, the hyphenated version if people instinctively add one, and the .uk twin of your .co.uk.

The .uk ending is separate from .co.uk and is administered by Nominet. If someone else owns the .uk version of your name, that is not automatically a disaster. But it is worth knowing before a customer lands on a parked page and assumes you have gone under. The same goes for plurals. If your brand is singular, buy the plural and redirect it. If your brand is plural, buy the singular. It is cheaper than explaining the difference in every sales call.

A founder in Leeds once told me they spent launch week buying three misspellings after a prospect emailed the wrong address twice. That is a reactive way to do it. A better use of an hour is to sit with the registrar, search the obvious variants, and redirect the ones that matter. Do not buy every combination under the sun. Buy the ones a real person might type with cold fingers on a train.

DNS, TTL and the switch that stalls at 9am

The domain is not just the name. It is the plumbing. If you are moving from a landing page builder to a proper site, or from an agency to an in-house setup, the switchover is DNS. That is where launch mornings go wrong.

Lower your TTL 24 to 48 hours before the change, not five minutes before. Check the records you actually need: A and AAAA for the site, CNAME for any subdomains, MX for email, and TXT records for verification and email authentication. Make sure the registrar lock is on when you are not making changes, and off when you are. Keep the transfer authorisation code somewhere a second person can find it. Confirm that the admin email on the account is one you can still access. It sounds basic because it is basic, and it is still the thing that catches founders out at 08:55 on launch day.

Then test from outside your own network. Ask someone on a different provider to load the site. Check the www and non-www versions. Check the old domain redirects if you have one. A launch page that only works on the office Wi-Fi is not a launch page. It is a rehearsal.

The invoice test: one domain, one promise

Here is the check that gets skipped most often. Your landing page says [email protected]. Your invoices go out from [email protected]. A customer replies to the invoice, and the message bounces. Or it lands in an inbox nobody checks. Or it arrives looking just different enough to feel like a phishing attempt.

Align the domains that customers see. If the site uses one domain, the invoice, the reply-to address and the footer should not quietly use another. Set clear reply-to addresses. Check your SPF, DKIM and DMARC records, even if you are not running a big outbound campaign yet. Send a test message from Gmail, Outlook and a work account, then reply to it from each one. If you use a catch-all address, decide who reads it and how quickly.

That is not glamorous launch work. It is the difference between a customer thinking you are small and responsive, and a customer thinking you are small and unreachable. In the first weeks, the second impression is expensive.

A short drill for launch week

Two weeks out, list every domain you own and every one you use in public. One week out, lower the TTL and confirm registrar access. Forty-eight hours out, test the site from outside and check the email records. The day before launch, send an invoice-style email to a friend and ask them to reply. On launch morning, load the page on mobile data, not office Wi-Fi. After the dust settles, put the TTL back to a sensible level and write down what you changed.

The domain is not the loud part of a launch. It is the boring bit that protects the loud part. Get it right, and nobody notices. Get it wrong, and the first thing a UK buyer learns about you is that the handshake did not quite land.