Web Development

The website launch checklist

A pre-launch, launch-day and first-30-days website checklist where every non-obvious item carries its reason and its source, from noindex to DNS.

Duraan AliUpdated 17 min read
A printed checklist on a clipboard with most boxes ticked, next to a laptop and a fresh coffee

Three mistakes cause most launch-day disasters: the new site goes live with search engines still blocked, the old URLs have nowhere to go, and company email stops arriving during the DNS change. Everything else on this list matters, but those three turn a good week into a bad month, and each one takes under five minutes to check.

This list is written to be used, not read once. Copy the sections into a shared document, put a name and a date next to each line, and do not launch until every line has an owner who has looked at it. Where an item is not obvious I have written down why it is there, and where it rests on a published rule, whose rule it is and when I read it. The sections are in the order I actually work through them.

What are the three items that get missed most?

Mistake What it looks like How to catch it
noindex left on The site looks perfect and gets no organic traffic. Panic sets in around week three View source on the live home page and search for noindex. Then open yoursite.com/robots.txt and confirm it does not say Disallow: /. These are two separate checks, for the reason below
No redirect map Old links from Google, Facebook, directories and email signatures land on 404 pages Export every URL from the old site before launch. Every one needs a destination on the new site
Broken company email Staff stop receiving mail a few hours after cutover and nobody connects it to the website Export the entire DNS zone and recreate MX, SPF, DKIM and DMARC at the new host before you change nameservers

The noindex check is two checks because of how Google works. Its Search Central documentation, read in November 2026, says noindex is a rule set with a meta tag or an HTTP header, that putting it in robots.txt is not supported, and that it only works if the crawler can reach the page. A page blocked by robots.txt can still appear in search results, because Googlebot never sees the noindex on it. A launched site still blocked in robots.txt can end up half-indexed from old links with no way for Google to read your instructions. Check both.

The email one is the most damaging because the cause is invisible. Nobody thinks a new website could stop mail from reaching the front desk. It happens when someone points the domain’s nameservers at a new host and the new host’s blank DNS zone replaces the old records wholesale.

Pre-launch: content and proofing

  • Read every page out loud once. Typos survive silent reading.
  • Phone number identical on every page, including the footer and the contact page, and identical to your Google Business Profile.
  • Address formatted the same way it appears on your Business Profile. Google matches these.
  • Business hours and staff names current.
  • No placeholder text anywhere. Search the site for “Lorem”, “TBD”, “coming soon” and “[insert”.
  • All images real, licensed and relevant. Keep the license list; it belongs in your handover package, which the ownership guide lays out.
  • A 404 page exists, matches the design, and links back to the main sections.

Pre-launch: design and devices

Google’s mobile-first indexing documentation, read in November 2026, says Google “uses the mobile version of a site’s content, crawled with the smartphone agent, for indexing and ranking.” The phone view is not a secondary view. It is the one Google reads.

  • Home page, one service page and the contact page checked on a real phone, on cell data, not a browser resize.
  • Checked on iOS Safari and Android Chrome at minimum. They break differently.
  • No horizontal scroll on any page at 375 pixels wide, and no stretched layouts at 1920.
  • Favicon set. A default globe icon in the tab looks unfinished, and Google shows your favicon in mobile results.
  • Social share image set, and tested by pasting a link into a private message.
  • Print stylesheet acceptable if people print your schedules or forms. Schools and clinics still do.

Pre-launch: forms and anything that sends email

This section matters more than it did two years ago. Since February 1, 2024, Google’s email sender guidelines, read in November 2026, require every sender to Gmail addresses to authenticate with SPF or DKIM, to have valid forward and reverse DNS, to send over TLS, and to keep the spam rate reported in Postmaster Tools under 0.3 percent. Senders of more than 5,000 messages a day need SPF, DKIM and DMARC. A contact form that emails “from” an unauthenticated address, or from the visitor’s own address, now fails those checks and is junked with no error shown to anyone.

  • Every form submitted as a real test from a phone, on cell data.
  • The notification email arrives at the right inbox and is not in spam. Check the spam folder, not just the inbox.
  • Form email is sent from an address at your own domain, with the visitor’s address in Reply-To, through a sender that signs with your domain’s DKIM key. The cheap pattern of sending “from” the visitor is what gets junked.
  • The confirmation message or thank-you page appears after submitting.
  • Required fields, error states and success states all behave.
  • Spam protection active. A honeypot field or a rate limit stops most bots without a puzzle for real visitors.
  • Every navigation link and every button clicked once. A link checker catches the rest.
  • Search works if you have it, including a query that returns nothing.
  • Payment, donation or booking flows tested end to end in live mode with a real transaction you then refund. Test-mode success proves nothing about live keys.
  • Third-party embeds load on the live domain: maps, calendars, donation widgets, scheduling tools. Several of these are locked to a list of allowed domains, and the staging domain was the one on the list.
  • Unique title tag on every page, roughly 50 to 60 characters, most important words first.
  • Unique meta description on every page, 120 to 155 characters.
  • One H1 per page that matches what the page is about.
  • noindex removed. Check the live site, not staging.
  • robots.txt allows crawling and points to the sitemap. Google’s robots.txt documentation says the file is “not a mechanism for keeping a web page out of Google”; it exists to manage crawl load. Hide a page with noindex or a password, never with robots.txt.
  • XML sitemap generated and reachable. Google’s sitemap documentation caps one file at 50 MB or 50,000 URLs, ignores priority and changefreq entirely, and uses lastmod only when it is “consistently and verifiably” accurate. Do not let a plugin stamp today’s date on every URL.
  • Canonical tags point at the live URL, not the staging domain.
  • Redirect map complete. Every old URL maps to its closest new equivalent with a server-side 301 or 308. Google’s redirects documentation treats an instant meta refresh as permanent too, but says a server-side redirect “has the highest chance of being interpreted correctly,” and that JavaScript redirects are a last resort. Its site-move guide says to avoid redirecting many old pages to the home page, to keep any unavoidable chain to no more than three hops, and to leave redirects in place for at least a year.
  • Redirects tested by hand on the ten highest-traffic old URLs.
  • Google Search Console verified for the live domain and the sitemap submitted. Use the Change of Address tool only if the domain itself is changing; Google says it is not for HTTP to HTTPS, www changes or path changes.
  • Indexing requested for the top pages. Google’s URL Inspection documentation says the request “does not guarantee that the page will appear,” that there is a daily limit, and that indexing “can take up to a week or two.”
  • Analytics installed and confirmed recording a session from your own visit.
  • Structured data for the organization or local business, with the same name, address and phone as the Business Profile. Do not bother with FAQ markup for the sake of a rich result: Google’s FAQPage documentation says that feature stopped appearing in Google Search on May 7, 2026.
  • IndexNow turned on if your platform offers it. It notifies Bing, Naver, Seznam, Yandex and Yep of changes; Google is not among the participants listed on indexnow.org as of November 2026, so it is a cheap extra, not a substitute.

If the site is moving platforms as well as designs, read our guide to moving a website without losing rankings before launch week, not during it. The website redesign checklist covers the baseline exports you should have taken before any of this started.

Pre-launch: speed

The thresholds are published. Google’s web.dev, read in November 2026, defines a good page as one where Largest Contentful Paint happens within 2.5 seconds, Interaction to Next Paint is 200 milliseconds or less, and Cumulative Layout Shift is 0.1 or less, measured at the 75th percentile of real page loads, mobile and desktop separately. Run the home page and one inner page through PageSpeed Insights before launch and keep the report.

  • Images compressed and served in a modern format. Nothing on the page should be a 4 MB photo.
  • Images sized to their display size, so a 400-pixel thumbnail is not a 2,400-pixel file scaled down. This is the usual LCP fix.
  • Width and height set on images and embeds so the layout does not jump while loading. This is the usual CLS fix.
  • Unused plugins, fonts and tracking scripts removed. Third-party scripts are the usual INP problem.
  • Caching and compression enabled at the host or CDN.

If a page is still sluggish after this list, why your website is slow walks through the causes in order of how much they cost you.

Pre-launch: accessibility

WCAG 2.1 AA is the standard, and the first items below are its rules. The 2026 WebAIM Million report, which tested one million home pages in February 2026, found detectable WCAG 2 failures on 95.9 percent of them, an average of 56.1 errors per page, with low-contrast text on 83.9 percent of pages, missing image alt text on 53.1 percent, missing form labels on 51 percent and empty links on 46.3 percent. Assume your new site has some of these until you have checked.

  • Every image has alt text, or empty alt if it is decorative (WCAG 1.1.1).
  • Body text contrast of at least 4.5 to 1 against its background, and 3 to 1 for large text (WCAG 1.4.3).
  • The whole site usable with the Tab key alone, and focus visible as it moves (WCAG 2.4.7).
  • Headings in order, H1 then H2 then H3, not used just to make text big.
  • Form inputs with real labels, not placeholder text alone.
  • Captions on prerecorded video (WCAG 1.2.2).
  • An automated scan with a free tool, then a manual keyboard pass. Automated checks catch a minority of real problems.

If you are a public entity, this section has a deadline. The ADA Title II web rule requires WCAG 2.1 AA by April 26, 2027 for entities serving 50,000 or more people and by April 26, 2028 for smaller entities and special districts, after the April 2026 interim final rule. If you serve people with disabilities directly, as a disability services provider, a clinic or a school, the section is not optional either way. Our accessibility guide for small organizations explains which fixes carry the most weight.

  • TLS certificate installed and renewing automatically. Let’s Encrypt certificates last 90 days (its FAQ, read November 2026), and the CA/Browser Forum’s ballot SC-081, approved April 2025, caps every public certificate at 200 days from March 15, 2026, 100 days from March 2027 and 47 days from March 2029. Manual renewal is no longer a plan.
  • All http:// URLs forced to https://, with no mixed-content warnings.
  • HSTS header on, if you understand it. Do not submit the domain to the browser preload list on launch day. hstspreload.org requires a one-year max-age, includeSubDomains and preload, and warns that inclusion “cannot easily be undone” and takes months to reverse. Any subdomain that is not HTTPS forever will break.
  • Admin passwords unique and strong, two-factor on for every admin account.
  • Old contributor and developer accounts removed.
  • Software, theme and plugins updated the day before launch, not the day of.
  • Registrar lock on and auto-renew on at the registrar, in an account your organization controls. If you are unsure whose account that is, check who owns your website before launch, not after.
  • Privacy policy published if you use forms, email signup or analytics. Minnesota’s Consumer Data Privacy Act has been in force since July 31, 2025; by Lathrop GPM’s July 2025 summary it applies at 100,000 Minnesotans a year, or 25,000 if more than 25 percent of revenue comes from selling data, exempts small businesses by the SBA definition, and has no broad exemption for nonprofits. Most readers are under those thresholds, and a plain-language policy is still the floor. Clinics, home care agencies, therapists and schools have HIPAA or FERPA obligations on top, so have counsel read theirs.
  • Cookie notice if you run non-essential tracking and serve visitors who require one.
  • Terms of service if you sell online.
  • Copyright year in the footer set to update automatically.

Launch day: DNS and email, in this order

Every DNS record carries a time to live, a number of seconds that tells resolvers how long to cache it. If your A record’s TTL is 86,400, some visitors keep reaching the old server for up to a day after you change it. Lowering the TTL shortens that window, but only once the old, longer TTL has expired everywhere, which is why the change has to happen at least 48 hours before cutover, not that morning.

  • Screenshot or export the entire current DNS zone before changing anything.
  • Lower the TTL on the A and CNAME records to 300 seconds at least 48 hours before cutover.
  • Recreate every existing record at the new DNS host first: MX, SPF, DKIM, DMARC, and any verification TXT records for Google Workspace, Microsoft 365, your CRM or your form tool.
  • Confirm you can log in to the registrar yourself, today, with an account recovery email your organization controls.
  • Change the A record or the nameservers.
  • Send a test email to and from a company address within 15 minutes of cutover.
  • Submit every form again from the live domain.
  • Send a second email test the next morning, after propagation.
  • Raise the TTL back to normal after 48 stable hours.

Launch day: backups and rollback

  • Full backup of the old site, files and database, stored somewhere you control, not only on the old host.
  • Backup of the new site taken immediately after launch, and automatic backups scheduled with one restore actually tested.
  • A written rollback plan. Usually it is “point the A record back,” which is why you keep the old server running for two weeks.

What should launch day look like hour by hour?

Launch Tuesday, Wednesday or Thursday morning. Not Friday afternoon, not the day before a holiday, not a week when the person who built the site is traveling. Most problems surface in the first few hours, and you want everyone awake and at a desk.

When What
Day before Content freeze, backup taken, TTL already lowered, updates applied
Launch hour DNS change, certificate confirmed, noindex removed, robots.txt checked, email test sent
First hour after Ten redirect spot-checks, every form submitted from the live domain, analytics confirmed recording
Same afternoon Sitemap submitted in Search Console, indexing requested for the top pages
Same day Website link updated on your Google Business Profile, social profiles and email signatures

What usually goes wrong in week one?

These are the things I end up fixing in the first week, and none of them shows up in a browser on launch morning.

The form works and nobody gets the email. The notification lands in spam because the new sender was never added to the SPF record or signed with DKIM. The site owner concludes the form is broken; the form is fine.

An embed goes blank. A calendar, map, payment or scheduling widget was allowed only on the staging domain and nobody added the live one.

Some people see the old site for a day. The TTL was not lowered early enough, or a proxy in front of the old host is still caching. Both expire; both generate worried messages in the meantime.

The Business Profile still points at an old URL. Google reviews profile edits before publishing them, so the update you make on launch day may not show for a while. Make it on launch day anyway.

The first staff edit breaks a page. Someone pastes from Word, uploads a phone photo at full resolution to the home page, or edits the template instead of the page. That is a training issue, and it is why the handoff below exists. Password the staging site the same day, or staff will keep editing the bookmark they already have.

What do you watch for 72 hours and for 30 days?

For 72 hours, check daily: form notifications arriving, Search Console for crawl errors and a spike in 404s, analytics recording sessions, email flowing both directions. Ask two people outside the organization to open the site on their phones and tell you what breaks.

For 30 days, check weekly: Search Console coverage and the 404 report, because Google recrawls a site over weeks, not days. Google’s site-move guide says a small to medium site “can take a few weeks for most pages to move” and that ranking fluctuations in that period are normal. Compare against your baseline at 30, 60 and 90 days rather than reacting in week one. If organic traffic has not returned by day 60, why a site is not showing up on Google covers the diagnosis in order.

Two settings decide whether you can make that comparison. Search Console keeps 16 months of performance data (Google’s help pages, read November 2026), and standard Google Analytics 4 properties keep event-level data for 2 or 14 months depending on a setting that defaults to the shorter one. Set it to 14 the day you launch, and own both properties yourself.

Also update the things that live outside your site: your Google Business Profile, directory listings, and any printed material with the old URL structure on it.

Do you need to pay someone to run this checklist?

Often, no. If your site is five to ten pages on Squarespace or Wix, you are keeping the same domain and no URLs are changing, you can work through this list yourself in an afternoon. The platform handles the certificate, the sitemap and the hosting. Paying an agency by the hour to tick boxes you could tick is a poor use of money; for reference, agencies on Clutch’s 2026 pricing page list $100 to $149 an hour, and Codeable’s WordPress freelancers list $80 to $120 an hour plus a 17.5 percent fee, both read in October 2026. I would rather you spend that on photography or a month of content.

Bring in help when the launch has real risk attached: hundreds of URLs to map, a platform migration, a custom application, an online store, or a domain whose DNS carries the email for 30 staff. And if you have already paid for the site, the launch checklist should be part of the project, not an extra line. At TayoPro it is inside the fixed price quoted against the written scope, and the completed list, with names and dates, is part of what you receive.

Launch is when maintenance starts

The most common mistake after launch day is treating it as the finish line. The certificate will need renewing within months, the plugins within weeks, the content before anyone notices it is stale. Before you go live, write down who owns each of these:

  • Applying software, theme and plugin updates, and checking the site afterwards
  • Submitting every form once a month and confirming the email arrives
  • Renewing the domain and watching the certificate, with the dates in a shared calendar
  • Reading Search Console once a month for new 404s, manual actions and security issues
  • Posting the content that changes: hours, staff, events, board minutes, Ramadan times, the careers page

That list is the care plan, whether you run it yourself or pay someone. Our website maintenance checklist is the monthly version, and how much website maintenance costs shows what the Twin Cities market charges for it, with sources. Whoever built the site should also hand you the full handover package: registrar and hosting logins in your name, an admin account, a backup, the source files and the license list. A studio that cannot produce a completed launch checklist and a handover package when asked is telling you something before you sign; it is one of the questions worth asking before you hire.

What to do next

Export the old site’s URLs, screenshot the DNS zone, and find out today whether you can log in to the registrar. Those three things take an hour and prevent the three disasters at the top of this page. Then work down the list with a name next to each line.

If you want a second pair of eyes on the redirect map or the DNS plan, tell us what you are launching. TayoPro designs and builds websites and keeps them maintained month to month, both at a fixed price quoted in writing, and we will tell you plainly if you do not need either one.

FAQ

Questions people ask about this

What is the most common website launch mistake?

Going live with search engines still blocked. Staging sites carry a noindex tag or a robots.txt disallow rule, and both are easy to forget. Google's documentation says noindex only works when Googlebot can reach the page, and that noindex in robots.txt is not supported at all, so you have to check two things: view source on the live home page and search for noindex, then open yoursite.com/robots.txt and confirm it does not say Disallow: /.

Will my email stop working when I launch a new website?

It can, and it is the launch failure that hurts most because nobody connects the two. Email routing lives in your DNS zone as MX records, alongside the SPF, DKIM and DMARC records that prove your mail is genuine. If you point the domain at a new host whose DNS zone is blank, those records vanish and mail stops being delivered or starts landing in spam. Export the whole zone first and recreate every record at the new host before you change nameservers.

How long does it take for Google to index a new site?

Days for a few pages, weeks for the whole site. Google's URL Inspection documentation says a request for indexing does not guarantee anything, has a daily limit, and can take up to a week or two. Its site-move guide says a small to medium site can take a few weeks for most pages to move to the new URLs, with ranking fluctuations along the way. If you kept your domain and redirected every old URL properly, most rankings carry over in that window. A brand new domain with no history takes longer.

What day of the week should I launch a website?

Tuesday, Wednesday or Thursday morning, in my experience. Avoid Friday afternoon, the day before a holiday, and any week your main contact or the developer is traveling. Most launch problems surface in the first few hours, and you want the people who built the site at their desks for the rest of the day rather than on Monday.

Do I need a privacy policy on a small business website?

Yes, if the site has a contact form, an email signup or analytics, because you are collecting personal data and the policy says what you collect and why. Minnesota's consumer privacy law, in force since July 31, 2025, applies at 100,000 consumers a year or at 25,000 if more than a quarter of revenue comes from selling data, and exempts small businesses by the SBA definition, so most readers of this post are under its thresholds. A plain-language policy is still the floor, and clinics, home care agencies, therapists and schools have HIPAA or FERPA obligations that a generator will not cover.

What should I check in the first week after launch?

Daily for three days: that every form notification arrives and is not in spam, that Search Console shows no spike in 404s or crawl errors, that analytics is recording sessions, and that email flows in both directions. Then weekly for a month: Search Console coverage and the 404 report, because Google takes weeks to recrawl a site of any size. Also update the website link on your Google Business Profile, which Google reviews before publishing, and in your email signatures and directory listings.

Keep reading

Start a project

Ready to take your business to the next level?

Let's work together to create solutions that make a real impact. Tell us about your project and we'll come back with a clear plan.

(612) 293-0636info@tayopro.com