DNS records explained: A, CNAME, MX, TXT and more
What DNS is, what each common record type does, how changes propagate and how to update DNS safely when moving websites or email.
A comprehensive pre-launch checklist covering content, design, functionality, SEO, performance, accessibility, security, analytics and the launch itself.
Before launching a website, check content accuracy, design on every device, forms and integrations, SEO settings and redirects, speed, accessibility, security, analytics and legal pages. Remove staging blocks that hide the site from search engines, plan DNS changes carefully, and keep a rollback plan. After launch, monitor errors, forms, search indexing and performance closely for the first few weeks.
Launch day is exciting and nerve-wracking. A missed detail, like a form sending emails nowhere or a setting blocking search engines, can undo months of work. Use this checklist in the week before launch.
Agree in advance who approves the launch: usually a business owner for content, a developer for technical checks and someone responsible for legal and privacy pages. A short sign-off meeting the day before launch catches last-minute issues and makes sure everyone knows the plan, the timing and who to contact if something goes wrong.
Decide in advance what would make you roll back, such as broken checkout or forms, and how you'd do it. Keep the previous version deployable and DNS changes documented so you can revert quickly if needed.
Record what was launched, settings changed, accounts and access, and known issues. It's invaluable for future updates and troubleshooting.
Some sites need extra checks. A SaaS marketing site should confirm sign-up flows and trial emails work end to end; see our guide to SaaS website design. A charity site should test donation journeys, receipts and recurring giving; our nonprofit website guide covers those details. Online stores need full checkout, tax and shipping tests.
Turn this list into a shared document or project board, assign an owner to each item and tick items off together in a pre-launch meeting. A shared checklist stops tasks falling between people.
Every site our web development team launches goes through a checklist like this. Our CMS development team makes sure editors are trained before launch, and our maintenance plans provide monitoring and support afterwards.
Leaving a noindex setting from staging, which hides the site from search engines. Forms not delivering email is a close second.
During a quiet period early in the week, when the team is available to fix problems.
At least two to four weeks, checking forms, errors, indexing and performance.
This guide is general information, not legal, tax or financial advice, and details such as prices, features and rules can change. Product and company names mentioned are trademarks of their respective owners and are used only to identify those products; UK Technology Hub is not affiliated with or endorsed by them.
Tell us about your project and get a free, fixed quote.
Get a free quoteWhat DNS is, what each common record type does, how changes propagate and how to update DNS safely when moving websites or email.
How privacy-focused analytics tools differ from traditional analytics, what you gain and lose, and how to choose an approach that fits your legal and business needs.
What the Jamstack approach is, how pre-built pages and APIs make sites faster and more secure, and when it's the right choice for a business website.