A website go-live checklist helps agencies and business owners review domains, hosting, DNS records, emails, SSL, WordPress settings, redirects, SEO basics, forms and final QA before a website is published. A website may look ready on the front end, but launch problems usually happen in the hidden areas: name servers, MX records, SSL certificates, noindex settings, broken forms, missing analytics, wrong contact details or email routing mistakes. This guide explains what to check before launch, what clients should prepare, and how agencies can avoid last-minute issues that delay the website or damage trust.
Key Insights
- A website should not go live until domain, hosting, DNS, SSL, email routing, forms, redirects and mobile layout are checked.
- DNS and MX record mistakes can break emails even when the website itself looks fine.
- WordPress launch checks should include permalink settings, noindex removal, plugin updates, backups, security and admin access.
- Search engines need crawlable pages, clean URLs, internal links, indexable content and accurate metadata after launch.
- A written launch checklist reduces confusion between the client, developer, hosting provider, IT team and marketing team.
- Post-launch monitoring is part of the launch process, not something to think about weeks later.
What Is a Website Go-Live Checklist?
A website go-live checklist is a step-by-step review of everything that must work before a website is made public on its final domain. It covers technical setup, content, SEO, security, tracking, emails, forms, mobile performance and final client approval.
For business owners, the checklist prevents launch-day surprises. For agencies, it creates accountability between the project manager, developer, designer, SEO team, content team, hosting provider and client.
A website launch is not just a design milestone. It is a technical handover, SEO event, customer experience event and business communication event at the same time.
Why Website Launches Fail After Design Approval
Many websites fail at launch because the team assumes design approval means the project is finished.
Design approval only confirms that the website looks acceptable. It does not confirm that the website is technically ready.
A website can look polished and still have serious launch issues:
- the domain may not point to the correct server
- the SSL certificate may not be active
- business emails may stop receiving messages
- forms may submit to the wrong inbox
- pages may still be blocked from indexing
- old URLs may not redirect properly
- mobile menus may break
- analytics may not be tracking
- contact details may be wrong
- WordPress admin access may not be handed over
- Google may not be able to crawl key pages
This is why agencies should separate three stages:
- Design approval
- Technical go-live
- Post-launch monitoring
A website is only truly launched when all three are complete.
Domain Checks Before Website Launch
The domain is the website’s public address. Before launch, confirm who owns it, where it is registered, and who has access.
Check Domain Ownership
The client or agency should confirm:
- domain registrar
- domain owner
- admin email
- renewal date
- payment method
- login access
- two-factor authentication
- domain lock status
The domain should ideally be registered under the client’s ownership, even if the agency manages it. This protects the client from losing control of the business domain later.
Confirm the Final Domain Format
Decide whether the website will use:
https://example.comhttps://www.example.com
Both can work, but only one should be the primary version. The other should redirect cleanly to the chosen version.
Check Domain Renewal
A website can be perfectly built and still go offline if the domain expires.
Before launch, check:
- renewal date
- auto-renewal status
- billing email
- registrar notification email
- backup payment method
Domain renewal is simple, but forgetting it can create major business disruption.
Hosting and Server Checks
Hosting controls where the website files live. Before launch, confirm whether the website will go live on the client’s hosting, agency hosting or a new hosting environment.
Confirm the Hosting Environment
Check:
- hosting provider
- hosting plan
- server location
- PHP version
- database version
- storage limit
- bandwidth limit
- staging environment
- production environment
- backup availability
- support access
For WordPress websites, the server should support the current WordPress requirements and expected traffic level.
Check Server Access
The team should know who has access to:
- hosting dashboard
- cPanel or control panel
- FTP/SFTP
- database
- WordPress admin
- DNS zone editor
- backup system
Do not wait until launch day to request access. Access issues can delay a launch even when the website is ready.
Confirm Staging vs Live Environment
A staging website is used for development and review. The live website is the public version.
Before launch, make sure:
- the staging site is not indexed
- the live site is indexable
- the correct database is connected
- the correct domain is mapped
- test URLs are not visible on the live site
- staging links are replaced with live URLs
One common mistake is launching a website that still contains staging links, demo images or test content.
DNS and Name Server Checks
DNS controls how a domain connects to website hosting, email services and other systems.
DNS mistakes are one of the biggest reasons website launches become stressful.
Understand Name Servers
Name servers tell the internet where the domain’s DNS records are managed. If the name servers change, all DNS records must be reviewed carefully.
Before changing name servers, confirm:
- current name servers
- new name servers
- existing DNS records
- email records
- subdomain records
- third-party verification records
- old website records
- TTL settings
Never change name servers without first checking email records.
Check DNS Records
Important DNS records may include:
- A record
- CNAME record
- MX record
- TXT record
- SPF record
- DKIM record
- DMARC record
- verification records
- subdomain records
A website launch often only needs the A record or CNAME updated, but emails, analytics, security tools and third-party platforms may depend on other records.
Reduce DNS Risk Before Launch
Before changing DNS:
- export or screenshot existing DNS records
- identify which records are for email
- identify which records are for the website
- lower TTL if needed before migration
- schedule launch during working hours
- avoid launching late Friday if support is limited
- keep registrar, hosting and IT contacts ready
DNS can take time to propagate. Plan the launch window accordingly.
Email and MX Record Checks
Email setup is one of the most overlooked parts of website launch.
A website can go live successfully while business emails silently stop working.
What Are MX Records?
MX records tell the domain where to deliver emails. If MX records are changed incorrectly, emails may bounce or disappear.
Before launch, confirm whether the business uses:
- Google Workspace
- Microsoft 365
- webmail
- Zoho Mail
- cPanel email
- another email provider
Check Email Routing Before DNS Changes
Before editing DNS, record the existing MX settings.
Also check:
- SPF records
- DKIM records
- DMARC records
- email aliases
- contact form recipient emails
- sales inbox
- support inbox
- admin email
- notification email
- billing email
If the website uses forms, order notifications, appointment requests or quote requests, test every email path.
Test Email After Launch
After DNS changes, send test emails:
- from Gmail
- from Outlook
- from a business domain
- through website forms
- through WordPress notifications
- through WooCommerce or Shopify if relevant
Check inbox, spam folder and email logs.
Do not assume emails are working just because the website loads.
SSL and HTTPS Checks
SSL protects the connection between the user and the website. Without HTTPS, browsers may show security warnings and users may lose trust.
Before launch, check:
- SSL certificate is installed
- SSL certificate is active
- HTTPS version loads correctly
- HTTP redirects to HTTPS
- mixed content issues are fixed
- images and scripts load over HTTPS
- canonical URLs use HTTPS
- sitemap URLs use HTTPS
Fix Mixed Content
Mixed content happens when an HTTPS page loads some files over HTTP.
This can affect:
- images
- fonts
- scripts
- stylesheets
- embedded media
Use a mixed content scan or browser console check before launch.
WordPress Go-Live Checklist
For WordPress websites, the go-live process should include both front-end and backend checks.
WordPress Settings
Check:
- site title
- tagline
- timezone
- admin email
- permalink structure
- homepage setting
- blog page setting
- comment settings
- user roles
- media settings
- privacy settings
Remove Noindex From Live Site
During development, websites are often blocked from search engines.
Before launch, check:
- WordPress “Discourage search engines” setting
- SEO plugin index settings
- robots.txt
- page-level noindex tags
- staging protection
- password protection
- server-level restrictions
A common launch mistake is making the website public but accidentally keeping it hidden from search engines.
Update Plugins and Theme
Before launch:
- update safe plugins
- update theme if stable
- remove unused plugins
- remove inactive themes
- check plugin conflicts
- test forms after updates
- test checkout if eCommerce
- test booking systems if service-based
Do not update everything blindly on launch day without backup.
Create a Backup Before Launch
Before going live, create a full backup:
- website files
- database
- media library
- theme files
- plugin settings
- DNS record screenshots
A backup gives the team a recovery point if something breaks.
SEO Checks Before Going Live
SEO should be checked before launch, not after the website has already been published.
Check Page Titles and Meta Descriptions
Every important page should have:
- unique SEO title
- clear meta description
- primary keyword focus
- natural language
- service or topic relevance
- location modifier if relevant
- no duplicate metadata across key pages
Do not write titles only for search engines. Titles should also help users understand the page quickly.
Check Heading Structure
Each page should have one clear H1.
Use H2s and H3s to organize content logically.
Avoid:
- multiple random H1s
- vague headings
- keyword stuffing
- headings used only for visual styling
- missing H1s on important pages
A strong heading structure helps both users and search systems understand the page.
Check URL Structure
Before launch, review URLs.
Good URLs are:
- short
- readable
- lowercase
- separated by hyphens
- relevant to the page topic
- free from unnecessary dates or IDs
- consistent across the site
If the website is a redesign, map old URLs to new URLs before launch.
Check Internal Links
Review internal links across:
- menu
- footer
- service pages
- blog posts
- buttons
- breadcrumbs
- related pages
- homepage sections
Internal links help users navigate and help search engines discover pages.
Submit XML Sitemap
The XML sitemap should include important indexable pages.
Check that the sitemap does not include:
- staging URLs
- noindex pages
- thank-you pages
- admin pages
- duplicate URLs
- old demo pages
- irrelevant archives
After launch, submit the sitemap in Google Search Console.
Check Robots.txt
Robots.txt should not block important website sections.
Review it for accidental blocks such as:
- blocking the entire site
- blocking CSS or JavaScript
- blocking service pages
- blocking product pages
- blocking important blog sections
Robots.txt should be intentional, not copied from staging without review.
Forms, Buttons and Conversion Checks
A website launch is not successful if users cannot contact the business.
Before launch, test:
- contact forms
- quote forms
- booking forms
- newsletter forms
- appointment buttons
- WhatsApp links
- phone links
- email links
- payment buttons
- checkout flow
- login forms
- download buttons
Test Forms Properly
Do not only check whether the form looks correct.
Submit test entries and confirm:
- the form submits successfully
- confirmation message appears
- email notification is received
- CRM integration works
- spreadsheet integration works
- autoresponder works
- spam protection works
- the correct team receives the lead
A broken form can make a business think marketing is not working when the real problem is lead capture.
Mobile, Speed and Page Experience Checks
Most users will experience the website on mobile before desktop.
Before launch, test:
- mobile menu
- tap targets
- sticky header
- contact buttons
- form fields
- image sizes
- font readability
- spacing
- popups
- page load speed
- layout shifts
- embedded videos
- maps
- sliders
Check Core Web Vitals
Core Web Vitals are performance metrics that help evaluate real user experience.
The website should be reviewed for:
- loading performance
- layout stability
- interaction responsiveness
Do not optimize only for a score. Optimize for actual users.
Compress Images
Large images are one of the easiest ways to slow a website.
Before launch:
- resize oversized images
- compress images
- use modern image formats where appropriate
- add descriptive alt text
- avoid uploading huge hero images
- lazy-load non-critical images where suitable
Test Across Devices and Browsers
Check the website on:
- iPhone
- Android
- desktop Chrome
- Safari
- Edge
- tablet if relevant
Do not assume one browser test is enough.
Tracking, Analytics and Search Console Checks
A website should not launch without measurement.
Before or immediately after launch, set up:
- Google Analytics
- Google Search Console
- Google Tag Manager if used
- Meta Pixel if running ads
- Google Ads conversion tracking if needed
- call tracking if relevant
- form conversion tracking
- thank-you page tracking
- eCommerce tracking if applicable
Verify Google Search Console
Search Console helps monitor indexing, performance, sitemap submission and search issues.
After launch:
- verify the domain property
- submit XML sitemap
- inspect important URLs
- check indexing status
- monitor page experience
- monitor crawl issues
- check enhancements and structured data
- review search performance over time
Test Conversion Events
If the website will run ads, test conversion tracking before campaigns start.
Check:
- form submissions
- phone clicks
- WhatsApp clicks
- booking completions
- purchases
- add-to-cart events
- lead form events
- thank-you page events
Without tracking, paid ads and SEO performance become harder to judge.
Security, Backup and Access Checks
Security should be part of launch, not an afterthought.
Before launch:
- remove unused admin users
- use strong passwords
- enable two-factor authentication where possible
- limit admin access
- install security plugin if appropriate
- confirm backup schedule
- check malware scan
- update plugins carefully
- secure wp-admin if needed
- disable directory browsing
- confirm SSL works
Handoff Access Properly
Document who has access to:
- domain registrar
- hosting
- WordPress
- Google Analytics
- Google Search Console
- Google Tag Manager
- email provider
- CRM
- booking system
- payment gateway
- CDN
- backup system
Access should be clear before the project is closed.
Launch-Day Checklist
On launch day, complete these steps in order.
Before DNS Change
- final backup completed
- client approval received
- DNS records exported
- email records confirmed
- SSL ready
- live server prepared
- staging site reviewed
- launch team available
- rollback plan ready
During Launch
- update DNS or name servers
- map domain to hosting
- activate SSL
- force HTTPS
- test homepage
- test key pages
- test forms
- test emails
- check mobile menu
- check redirects
- check sitemap
- check robots.txt
After Launch
- inspect website in Search Console
- submit sitemap
- test analytics
- test conversion events
- check email delivery
- check page speed
- check contact details
- check broken links
- monitor uptime
- inform the client
The launch should not end when the site loads. It ends when the site works.
Post-Launch Monitoring Checklist
Monitor the website for at least the first few days after launch.
Check:
- uptime
- page errors
- form submissions
- email delivery
- search indexing
- crawl errors
- broken redirects
- mobile usability
- analytics data
- server errors
- plugin issues
- customer complaints
- conversion tracking
For redesigns, continue monitoring old URLs and traffic patterns for several weeks.
Common Website Go-Live Mistakes
Launching Without Email Testing
This is one of the most damaging mistakes. The website may work, but sales inquiries may not reach the business.
Forgetting to Remove Noindex
If a staging noindex setting remains active, search engines may not index the live website properly.
Not Mapping Redirects
For redesigns, old URLs should redirect to the most relevant new pages. Missing redirects can hurt user experience and search visibility.
Not Testing Forms
A contact form that “looks fine” may still fail to send notifications.
Launching With Placeholder Content
Placeholder content damages trust. Remove dummy text, demo images and test blog posts.
Ignoring Mobile
A desktop-approved website can still fail on mobile. Always test the mobile journey.
Not Installing Analytics
If tracking starts late, the first launch data is lost.
Changing DNS Without Checking MX Records
This can break business email delivery.
What Clients Should Prepare Before Launch
Clients can speed up the launch by preparing:
- domain login access
- hosting access
- email provider details
- final business name
- final phone numbers
- final email addresses
- final office address
- social media links
- service details
- product details
- team bios
- legal pages
- images
- brand assets
- approval on final content
- preferred launch date
The more complete the client’s inputs are, the smoother the launch becomes.
What Agencies Should Document Before Handoff
Agencies should document:
- final website URL
- CMS login instructions
- hosting details
- domain details
- DNS changes made
- email configuration
- plugin list
- backup process
- analytics access
- Search Console access
- maintenance recommendations
- known limitations
- post-launch support period
- emergency contact process
A good handoff reduces future confusion and protects the agency-client relationship.
Questions This Article Answers
What should be included in a website go-live checklist?
A website go-live checklist should include domain access, hosting setup, DNS records, SSL, email routing, WordPress settings, SEO metadata, redirects, forms, mobile layout, analytics, backups, security and final client approval. Agencies should check these items before launch day to avoid broken emails, missing pages, tracking gaps and delayed publishing.
Why do website launches get delayed?
Website launches often get delayed because domain access, hosting access, DNS records, email routing, content approval, final images, form testing or client sign-off are not ready. Many delays happen outside the visible website design, which is why technical and administrative checks should begin before the final launch date.
What can break when changing name servers?
Changing name servers can affect website routing, email delivery, subdomains, verification records, CRM integrations, Google Workspace, Microsoft 365, SPF, DKIM and DMARC records. Before changing name servers, the existing DNS zone should be reviewed and backed up so important records are not lost.
Why are MX records important during a website launch?
MX records control where emails for a domain are delivered. If MX records are removed or changed incorrectly during website launch, the website may load but business emails may stop working. Always confirm email provider settings before editing DNS.
What should be checked before making a WordPress website live?
Before making a WordPress website live, check permalink settings, SSL, admin email, noindex settings, plugins, theme updates, forms, backups, page titles, meta descriptions, sitemap, robots.txt, user roles, mobile layout and analytics. Also remove staging URLs, demo content and temporary login restrictions.
When should Google Search Console be set up?
Google Search Console should be set up before or immediately after launch. It helps confirm whether Google can crawl and index the website, submit the sitemap, inspect important URLs, monitor errors and review search performance after launch.
How long should a website be monitored after launch?
A website should be monitored closely for the first few days after launch and reviewed again over the next few weeks. Redesigns and migrations need longer monitoring because redirects, indexing changes, ranking fluctuations and old URLs may create issues after launch.
Who should control the domain after a website launch?
The client should usually own the domain, even if the agency manages it. The agency can help configure DNS, hosting and launch settings, but domain ownership should remain clear to avoid future disputes, renewal problems or access issues.
Final Website Go-Live Checklist
Use this checklist before publishing the website.
Domain
- Domain owner confirmed
- Registrar access available
- Renewal date checked
- Primary domain version selected
- WWW or non-WWW decided
- Domain lock status checked
- Admin email confirmed
Hosting
- Hosting plan confirmed
- Server access available
- WordPress installed or migrated
- PHP and database versions checked
- Backup created
- Staging and live environments separated
DNS
- Existing DNS records backed up
- Name servers confirmed
- A records checked
- CNAME records checked
- TXT records checked
- MX records checked
- SPF, DKIM and DMARC reviewed
- DNS propagation planned
- Email provider confirmed
- MX records preserved
- Test emails sent
- Contact form emails tested
- Admin email updated
- Sales/support inboxes checked
SSL
- SSL certificate active
- HTTPS working
- HTTP redirects to HTTPS
- Mixed content fixed
- Sitemap uses HTTPS
- Canonicals use HTTPS
WordPress
- Site title checked
- Timezone checked
- Permalinks set
- Noindex removed
- Plugins reviewed
- Theme checked
- Admin users reviewed
- Backup completed
- Security settings active
SEO
- SEO titles written
- Meta descriptions added
- H1s checked
- URL structure reviewed
- Internal links tested
- XML sitemap generated
- Robots.txt reviewed
- Redirects mapped
- Image alt text added
- Schema added where relevant
User Experience
- Mobile menu works
- Buttons work
- Forms work
- Phone links work
- WhatsApp links work
- Email links work
- Booking links work
- Checkout works if applicable
- Images optimized
- Pages load properly
Tracking
- Google Analytics installed
- Search Console verified
- Sitemap submitted
- Conversion events tested
- Meta Pixel added if needed
- Google Ads tracking added if needed
- Uptime monitoring enabled
Handoff
- Client approval received
- Login details documented
- Maintenance plan explained
- Backup process explained
- Post-launch support period confirmed
- Emergency contact process shared
How Rozzario Can Help
A website launch should not feel like guesswork. It needs proper planning across domain, hosting, DNS, email, WordPress, SEO, tracking, security and final QA.
Rozzario helps businesses plan, design, develop, launch and maintain websites with the technical and marketing details connected from the beginning. Whether you need a new website, a WordPress redesign, an eCommerce launch, SEO structure, website maintenance or post-launch support, the goal is simple: make the website work properly before real customers start using it.
If your website is close to launch and you want fewer technical surprises, Rozzario can help review the launch setup, fix missing items and prepare the website for a smoother go-live.
