01
Business information
Verify company name, services, locations, hours, phone numbers, email addresses, legal details and other visible business facts.
Website go-live checklist
A website is ready to launch when the content, customer journey, mobile experience, technical SEO, forms, tracking and recovery plan have all been checked on the final production setup—not just in a design preview.
Use this checklist for a new small-business website or a redesign. It is designed to catch the mistakes that can create broken enquiries, lost URLs, indexing problems or a poor first experience after go-live.
Check final content and business details, navigation, forms, calls to action, mobile layouts, accessibility basics, page titles and headings, indexability, canonicals, redirects, internal links, XML sitemap, analytics, Search Console, SSL, DNS, backups and post-launch monitoring. For a redesign, also map old URLs before launch so useful pages are not lost during migration.
Before the website goes live
A design can look finished while the live website still has launch risks. Forms may route differently, analytics may not fire, redirects may be missing and staging settings can accidentally carry over to production.
Assign an owner to each launch area and record whether the item is ready, blocked or requires a post-launch follow-up.
Website launch checklist
These checks cover the most common launch risks without turning the process into a generic list of design preferences.
Verify company name, services, locations, hours, phone numbers, email addresses, legal details and other visible business facts.
Confirm each important page has a clear purpose, accurate copy, useful headings and no placeholder or duplicate content.
Check menus, breadcrumbs where used, footer links and contextual links so important pages are reachable without dead ends.
Submit forms, test phone and email links, verify notifications and confirm booking, checkout or CRM routing where relevant.
Review headings, buttons, forms, tables, images, navigation and sticky elements on common mobile screen sizes.
Check keyboard access, visible focus, form labels, image alternatives where needed and readable contrast.
Confirm production pages intended for search are not blocked by noindex directives, login requirements or staging restrictions.
Use the correct canonical URLs and map changed or retired URLs to the closest relevant destinations.
Verify analytics, consent behavior where applicable and the events used to measure calls, forms, bookings or purchases.
Confirm the intended domain resolves correctly, HTTPS works and unwanted protocol or hostname variants redirect consistently.
Create a usable launch backup and know how to restore the previous stable version if a major problem appears.
Schedule checks for forms, crawl errors, indexing, redirects, analytics and high-value pages during the first days after launch.
New business website checklist
A technically perfect launch can still fail commercially if the website does not explain the business or make the next step obvious.
Buttons can link to old staging URLs, wrong forms or outdated pages even when they look correct. Test the complete action rather than only the click.
Do not launch with invented reviews, unverifiable results, fake local addresses or claims the business cannot support.
Make sure privacy, terms, refund, accessibility or other required notices reflect the actual business and website functionality.
Pre-launch SEO checklist
For a redesign, migration mistakes can erase useful URLs and internal links. For a new website, the goal is to make the intended pages easy to discover, crawl and understand from day one.
| SEO check | What to verify | Common launch mistake |
|---|---|---|
| Indexing | Important production pages can be crawled and are not accidentally noindexed | Staging noindex settings remain active after launch |
| Canonical URLs | Unique pages point to their preferred final URLs | Production pages still canonicalize to staging, old domains or the wrong page |
| Redirect map | Changed high-value URLs redirect to the closest relevant new destination | All retired URLs redirect to the homepage or remain 404s |
| Internal links | Navigation and body links point directly to the new final URLs | Internal links rely on redirects or still reference staging paths |
| Page titles / headings | Important pages have clear, distinct topics and heading hierarchy | Multiple pages compete for the same search intent |
| XML sitemap | The sitemap contains preferred indexable production URLs | Old, staging, redirected or noindex URLs remain in the sitemap |
| Search Console | The correct production property is available for monitoring | Launch problems are discovered late because nobody is watching indexing and crawl data |
Website go-live checklist
Domain, SSL and server changes can affect more than the homepage. Test the actual live environment after DNS and deployment changes are complete.
Go-live is the point where live-system QA starts. Re-test the homepage, high-value service pages, forms, redirects, analytics and mobile behavior after the final domain is serving the site.
Lead and analytics QA
A website can appear to launch successfully while leads are disappearing. Test the full path from visitor action to business notification or CRM record.
Do not assume a form works because the button changes state. Confirm the submission reaches the inbox, CRM, booking system or ecommerce workflow.
Track the actions that matter—qualified forms, calls, bookings or purchases—rather than relying only on page views.
For deeper journey work, review conversion-focused design.
Mobile and usability QA
Review the full customer journey on smaller screens, not just screenshots of the homepage.
Systemic mobile problems are easier to correct before the site is live. Review responsive web design if the layout system itself needs work.
Launch QA should catch obvious barriers, but accessibility should continue to be considered as pages, forms and components change.
Launch-day sequence
The exact steps vary by platform, but the sequence should make it clear when the backup is taken, when production changes happen and when live QA begins.
After the small business website launch
Some issues appear only after real users and search crawlers interact with the site. Plan monitoring instead of assuming the project ends the moment the site becomes public.
Test forms, calls, priority pages, redirects, analytics, HTTPS and mobile behavior on the production domain.
Review crawl/indexing signals, redirect issues, form delivery, analytics anomalies and any customer-reported problems.
Check high-value pages again, watch Search Console and conversion data, resolve broken internal links and document items that move into ongoing maintenance.
Launch-checklist search intent
This article should own the broad informational intent for small business website launch checklist, website launch checklist, pre-launch SEO checklist and website go-live checklist.
If an existing FAQ or article repeats the same full checklist, merge or 301 it to this page. If it remains live, rewrite it around a materially narrower question rather than competing for the same head terms.
Content, conversion, mobile QA, technical SEO, redirects, analytics, backups, go-live and post-launch monitoring.
Responsive design, local SEO, maintenance, development and conversion service pages should explain their own deliverables rather than repeat this full checklist.
If `/faq/website-launch-checklist/` substantially duplicates this topic, consolidate it here. Otherwise give it a truly narrower question and link to this guide for the complete checklist.
Related launch resources
The checklist identifies risks. The related service pages should handle the implementation work without duplicating the checklist intent.
Website launch checklist FAQ
These answers stay focused on launch readiness so service pages can keep separate commercial intent.
Check final content, navigation, forms, mobile layouts, business details, page titles and headings, indexability, canonicals, redirects, analytics, Search Console, XML sitemap, backups, SSL, DNS, contact actions and the post-launch monitoring plan.
A pre-launch SEO checklist verifies that important pages have a clear search intent, are crawlable and indexable, use the correct canonical URL, have working internal links, preserve valuable old URLs through redirects when needed, and appear in the XML sitemap.
Staging or development environments are commonly kept out of search results, but production pages intended for search must not accidentally retain noindex directives or access restrictions after launch. Review indexing controls before going live.
Redirect old URLs only when they are changing or being retired. Map each valuable old URL to the closest relevant new destination rather than sending every retired page to the homepage.
Test tracking before launch and again on the live site. Verify important form submissions, calls, bookings, purchases or other conversion events so the business can measure whether the new site is working.
Review the site immediately after launch, again within the first day, and continue monitoring during the first week. Focus on forms, indexing, redirects, crawl errors, analytics, mobile behavior and any pages changed during migration.
No. A simple brochure website has fewer launch risks than ecommerce, booking, multilingual or heavily integrated sites. Keep the core QA items, then add checks based on the website's actual features and business risk.
Yes. Before major changes go live, keep a usable backup and understand how the previous stable version can be restored if the launch introduces a serious problem.
Launch with fewer avoidable surprises
Share the current build, target launch date, old website if there is one, and the customer actions that must work on day one. The launch plan should focus on the risks that actually matter to the business.
