Pointing your domain at the new site

If you already own a domain (eg. yourbusiness.co.uk), pointing it at the new VerySEOly site is a 5-minute DNS edit. You do not need to transfer the domain, keep it wherever it is registered.

What you need

• Login to your domain registrar (whoever you renew the domain with, such as Cloudflare, GoDaddy, 123-reg, Namecheap, IONOS, etc.)
• Five minutes
• The DNS values I will send you when the new site is ready to flip

The two records

The new site is hosted on Vercel (London region). To point your domain at it you set two DNS records:

Type    Name    Value                       TTL
────    ────    ─────────────────────       ─────
A       @       76.76.21.21                 300
CNAME   www     cname.vercel-dns.com.       300

• @ (the apex / root) gets an A record pointing to Vercel’s anycast IP.
• www gets a CNAME to Vercel’s DNS pool.
• TTL of 300 (5 minutes) means the change propagates fast.

Some registrars label @ as “blank”, “root”, or your full domain name, they all mean the same thing.

Step by step (generic)

1. Log into your registrar’s DNS panel.
2. Find the current A record on @ and edit it to the value above (or delete it and add a new one).
3. Find the current CNAME on www and edit it to cname.vercel-dns.com. (or delete and add).
4. Save.
5. Email me, I add the domain to Vercel and Vercel issues the SSL certificate within 60 seconds.

What about email?

DNS records for email (MX, TXT/SPF, DKIM, DMARC) live alongside the A and CNAME records. Do not delete them. Only touch the A on @ and the CNAME on www.

If you currently use Google Workspace or Microsoft 365 for email, your MX records keep working unchanged. The website change does not touch email.

If you want to set up email forwarding or a real mailbox alongside the new site, see setting up email.

Downtime

Zero. The old site keeps serving traffic until DNS resolves to the new one, then the new site serves. There is a window where some visitors see the old site and some see the new one (usually 5 to 60 minutes depending on their resolver’s cache). No 404 page in between.

After the flip

I verify the new site is live with the correct SSL certificate, run a Lighthouse audit, and email you a screenshot of the green padlock plus the Lighthouse score. Job done.

If something looks wrong from your end (eg. you see the old site from your phone for an hour after the flip, that is your phone’s DNS cache, not a problem with the new site), let me know and I will walk you through clearing it.