Your new website looks great. The homepage is finished, the images are in place and the contact page is ready.
But is the website actually ready to go live?
Launching a website involves more than making it publicly accessible. A website can look perfect during development while still containing broken links, forms that do not send emails, mobile layout problems, indexing restrictions or missing analytics tracking.
These problems can affect customer enquiries, website performance and search engine visibility from the moment the website launches.
For businesses investing in a new website, proper testing is an important part of protecting that investment.
At Web Anatomy, we believe website testing should consider the complete experience, from the first page a visitor opens to the moment they submit an enquiry or complete a purchase.
This guide explains how to test a website before launch, covering design, functionality, mobile compatibility, performance, security, technical SEO, Google Search Console, GA4 and Google Tag Manager.
It also includes a practical launch checklist for WordPress, Elementor, WooCommerce and custom-developed websites.
Why Is Website Testing Important Before Launch?
Website testing helps identify problems before customers encounter them.
A website may display correctly on the developer’s computer but behave differently on mobile devices. A form may work in a test environment but fail when moved to production hosting.
Search engines may also encounter technical restrictions that were appropriate during development but should have been removed before launch.
For example, a WordPress staging website may use a noindex directive to discourage search engines from indexing unfinished content.
If that setting remains active after launch, important pages may be excluded from Google Search.
Website testing reduces the likelihood of these problems going unnoticed.
It also helps establish whether the website is ready to support its intended business activities.
Website Testing vs Website Launching
Website testing and website launching are related but separate activities.
Testing involves checking the website’s functionality, design, performance, security and technical configuration.
Launching involves making the production website publicly accessible, updating relevant DNS or hosting settings and confirming that the live environment works correctly.
A website should be tested before launch and checked again afterwards.
This is important because production hosting, domain configuration, caching, email delivery and external integrations may behave differently from the development environment.
1. Check Every Important Website Page
Begin by reviewing the website’s main pages.
These may include the homepage, about page, services, product pages, contact page, blog and relevant landing pages.
Open each page and inspect its content.
Look for missing images, incomplete sections, placeholder text, formatting errors and incorrect links.
Make sure headings are meaningful and that the information presented is accurate.
Pay particular attention to important commercial pages.
If customers cannot understand what your business offers or how to make an enquiry, the website may struggle to generate leads even when its technical configuration is correct.
What to Check
- Page titles and headings are correct.
- Images load successfully.
- Content is complete and accurate.
- Contact information is correct.
- Important buttons lead to the intended destination.
- No placeholder content remains.
- Navigation and footer links work.
2. Test the Website on Mobile Devices
Mobile testing is essential because visitors use different screen sizes and devices.
A website that looks correct on a desktop monitor may have problems on smaller screens.
Text may become difficult to read, buttons may overlap and images may extend beyond the visible page.
Test the website on real mobile devices where possible.
Browser developer tools can help simulate different screen sizes, but they do not replace testing on actual devices.
For Elementor websites, review responsive settings carefully.
A layout may use different spacing, typography or visibility settings across desktop, tablet and mobile views.
Check whether menus open correctly and whether important buttons are easy to select.
3. Check Browser Compatibility
Modern websites should work across the browsers used by their intended audience.
Test important pages and functionality in commonly used browsers such as Chrome, Safari, Firefox and Edge.
Not every minor visual difference represents a problem.
However, important functionality should remain accessible and usable.
Check forms, menus, interactive elements and checkout processes.
For custom-developed websites, browser compatibility testing may be especially important when using newer JavaScript or CSS features.
4. Test Website Navigation and Internal Links
Navigation helps visitors move between important pages.
Test the main menu, footer navigation, buttons and relevant internal links.
Look for links pointing to old development URLs, deleted pages or incorrect destinations.
If the website is replacing an existing site, review the previous URL structure.
Pages that have moved may require permanent redirects.
For example, an old services URL should redirect to the appropriate new page when its content has moved.
Avoid redirecting every old URL to the homepage without considering relevance.
A clear internal linking structure also helps search engines discover website content.
5. Test Contact Forms and Email Delivery
Contact forms are among the most important features to test.
A form may appear to submit successfully without actually delivering the enquiry to the business.
Complete each important form using appropriate test information.
Confirm that required fields work, validation messages appear and the success confirmation displays correctly.
Then check whether the enquiry reaches the intended recipient.
Where relevant, verify that notifications do not consistently land in spam folders.
Email delivery may depend on SMTP configuration, domain authentication and the hosting environment.
For WordPress websites, form plugins such as Elementor Forms, Gravity Forms and Contact Form 7 may require different configurations.
A successful form display does not guarantee reliable email delivery.
6. Test Telephone, WhatsApp and Email Links
Business websites often provide several ways for customers to make contact.
Test clickable telephone numbers, WhatsApp buttons and email links.
Make sure telephone links use the correct number and WhatsApp links open the intended destination.
Check that email links use the correct address.
For mobile users, these interactions should be easy to access.
If these actions are being tracked through Google Tag Manager, verify that the corresponding analytics events also work.
7. Test Website Speed and Performance
Website speed affects the user experience.
Slow-loading pages can frustrate visitors and make it harder to browse products, read content or submit enquiries.
Use tools such as Google PageSpeed Insights to review important pages.
Pay attention to large images, inefficient JavaScript, caching, server response times and unnecessary plugins.
Google’s Core Web Vitals provide useful performance measurements.
| Metric | Good threshold |
|---|---|
| Largest Contentful Paint (LCP) | 2.5 seconds or less |
| Interaction to Next Paint (INP) | 200 milliseconds or less |
| Cumulative Layout Shift (CLS) | 0.1 or less |
These thresholds help assess loading, responsiveness and visual stability.
However, a high performance score does not guarantee search rankings or business conversions.
Test representative page types rather than only the homepage.
A product page or service landing page may perform differently because it uses different images, scripts or functionality.
8. Check SSL and HTTPS
A production website should use HTTPS with a valid TLS certificate.
Open the website using its intended domain and confirm that the browser establishes a secure connection.
Check that HTTP requests redirect appropriately to HTTPS.
Look for mixed-content problems where secure pages attempt to load resources over insecure HTTP connections.
Also verify that internal links, canonical URLs and sitemap references use the correct production URLs.
A valid certificate helps protect information transmitted between visitors and the website.
It does not, by itself, establish that the website is fully secure.
9. Review WordPress Security Settings
Before launching a WordPress website, review administrator access and installed software.
Remove unnecessary test accounts and unused plugins where appropriate.
Confirm that WordPress core, themes and plugins are using suitable supported versions.
Use strong authentication and appropriate user permissions.
Review backup arrangements and ensure that recovery procedures are understood.
Where relevant, confirm that security monitoring and access restrictions are configured.
A launch checklist should also establish who will be responsible for ongoing website maintenance after the website goes live.
10. Check Technical SEO Before Launch
Technical SEO should be reviewed before the website becomes publicly available.
A website may contain excellent content but still experience problems if search engines cannot access or index important pages.
Start by reviewing the production URL structure.
Check that important pages return appropriate HTTP responses and that internal links use crawlable URLs.
Then examine indexing directives, canonical tags and sitemap configuration.
Check for Noindex Directives
Development websites sometimes use noindex directives to discourage indexing.
These should be reviewed carefully before launch.
Important public pages generally should not contain unintended noindex instructions.
However, some pages may intentionally remain excluded from indexing.
The correct configuration depends on the website.
Review Robots.txt
Robots.txt can control crawling access for compliant search engine crawlers.
Check that important public sections are not accidentally blocked.
Remember that robots.txt is not a reliable method for keeping confidential content private.
Sensitive environments should use appropriate access controls.
Review Canonical URLs
Canonical tags help indicate the preferred URL when duplicate or substantially similar pages exist.
Check that canonical URLs reference the intended production pages.
Avoid leaving canonical references pointing to staging domains.
Review XML Sitemaps
An XML sitemap can help search engines discover important URLs.
For WordPress websites, a sitemap may be generated by WordPress itself or an SEO plugin.
Check that the sitemap is accessible and contains appropriate production URLs.
An XML sitemap is useful, but it is not a requirement for every page to be indexed.
Test JavaScript-Rendered Content
Custom websites and single-page applications may depend on JavaScript to display content.
Check whether important information and navigation links are accessible to search engines.
Depending on the application architecture, server-side rendering, prerendering or other implementation approaches may be appropriate.
Google can render JavaScript, but rendering introduces additional considerations.
WordPress and custom-developed websites must both provide accessible, indexable content.
Google does not automatically prefer one development platform over another.
11. Check Google Search Console
Google Search Console helps website owners monitor how Google interacts with their websites.
Before or shortly after launch, confirm that the correct website property is available.
For a new domain, domain-property verification may be appropriate.
Review relevant indexing settings and submit the XML sitemap if one is available.
After launch, use URL Inspection to check representative important pages.
Search Console can help identify problems involving crawling, indexing and other search-related issues.
However, submitting a sitemap or requesting indexing does not guarantee that Google will index a page immediately—or at all.
12. Test Google Analytics 4 and Google Tag Manager
Analytics should be tested before launch so the business can begin measuring website activity.
Confirm that the correct GA4 property and Google Tag Manager container are installed.
Use Tag Assistant to check whether tags run as intended.
Review GA4 Realtime and DebugView where appropriate.
If the website uses lead tracking, test contact form submissions, telephone clicks, WhatsApp buttons and other important events.
Be particularly careful with duplicate tracking.
Installing GA4 through a WordPress plugin and Google Tag Manager without reviewing the setup may cause duplicate events.
For a complete implementation guide, read How to Track Website Leads with GA4 and Google Tag Manager.
13. Check Cookie Consent and Privacy Requirements
Websites collecting personal information should consider applicable privacy and data protection requirements.
For South African businesses, the Protection of Personal Information Act (POPIA) may be relevant.
Depending on the website and its audience, other legal requirements may also apply.
Review the privacy policy, contact forms, tracking technologies and any consent management implementation.
Make sure the website accurately explains relevant data collection practices.
A cookie banner alone does not automatically establish legal compliance.
Where necessary, obtain appropriate legal advice.
14. Test WooCommerce Checkout and Payments
Online stores require additional launch testing.
A WooCommerce website may appear functional while its checkout or payment gateway is incorrectly configured.
Complete test transactions using the payment provider’s supported testing process.
Verify that products can be added to the cart and that checkout calculations work correctly.
Check shipping options, taxes, order confirmations and payment status handling.
WooCommerce Launch Checks
- Products display correctly.
- Prices and stock information are accurate.
- Cart functionality works.
- Shipping methods are configured correctly.
- Payment gateways process supported test transactions.
- Orders appear in WooCommerce.
- Confirmation emails are generated.
- Failed payments are handled appropriately.
- Refund and cancellation processes are understood.
Where possible, test both successful and unsuccessful payment scenarios.
Do not assume that a payment button working in a test environment means the live payment configuration is correct.
15. Check Website Backups Before Launch
A reliable backup should be available before significant launch changes.
This is especially important when replacing an existing website.
The backup should include the necessary files and database information.
Check where the backup is stored and whether the recovery process is understood.
For migrations, a rollback plan should be prepared in case the launch encounters unexpected problems.
A backup that cannot be restored is of limited practical value.
16. Test Hosting and Server Configuration
The production hosting environment should be reviewed before launch.
Check that the website uses compatible PHP and database versions where applicable.
Review storage capacity, server resources, caching and any relevant application requirements.
Confirm that the production domain points to the correct hosting environment.
If the website is being migrated, consider whether DNS changes, email services or other records may be affected.
For higher-traffic websites, capacity and load testing may be necessary.
Hosting requirements should reflect the website’s expected usage rather than relying on a generic package description.
17. Check Website Accessibility
Website accessibility helps make digital content usable by people with different abilities and assistive technologies.
Review keyboard navigation, form labels, colour contrast and meaningful alternative text for relevant images.
Check that important controls can be operated without a mouse.
Headings should follow a meaningful structure, and error messages should be understandable.
The Web Content Accessibility Guidelines (WCAG) provide a recognised framework for accessibility.
Automated accessibility tools can identify some problems, but they cannot replace manual testing.
18. Review SEO Titles and Meta Descriptions
Before launch, review the website’s important page titles and meta descriptions.
Each major page should have a clear title describing its subject.
Avoid duplicate or generic titles across unrelated pages.
Meta descriptions should accurately summarise the content and encourage relevant visitors to explore the page.
Google may generate different search snippets based on the search query.
Titles and descriptions should be written for clarity rather than keyword repetition.
19. Check Structured Data
Structured data can help search engines understand certain types of website content.
Depending on the website, relevant schema types may include Organization, LocalBusiness, Product, BreadcrumbList and Article.
Check that structured data accurately reflects the visible content and follows Google’s applicable requirements.
Use Google’s Rich Results Test for supported rich-result types.
Valid structured data does not guarantee a rich result or improved rankings.
Avoid adding schema types that do not accurately describe the page.
20. Check Images and Media
Images should load correctly and support the website’s content.
Review image sizes, responsive behaviour and appropriate alternative text.
Large images can contribute to slower loading, particularly on mobile devices.
Videos and embedded media should also be tested.
Check that media players function and do not interfere with important page content.
21. Test Redirects When Replacing an Existing Website
A website redesign or migration can change URLs.
If existing pages are removed or moved, relevant redirects may be necessary.
Prepare a mapping between old and new URLs before launch.
Use appropriate permanent redirects when content has moved permanently.
Test redirects after the production website goes live.
Avoid redirect chains and unnecessary redirects to unrelated pages.
Preserving useful URLs where possible can reduce migration complexity.
22. Check the Website’s 404 Page
A 404 page appears when a requested URL cannot be found.
Test how the website responds to an invalid URL.
The page should clearly explain that the requested content is unavailable and provide useful navigation options.
The server should also return an appropriate 404 HTTP status for genuinely missing pages.
Displaying a friendly error message while returning HTTP 200 can create technical problems.
23. Review Website Content for Accuracy
Technical testing is important, but content accuracy matters just as much.
Check business names, telephone numbers, addresses, email addresses and service descriptions.
Remove unfinished text and development notes.
Verify that pricing, product information and promotional claims are correct.
A professional-looking website can lose credibility quickly if customers encounter incorrect information.
24. Test the Live Website After Launch
Testing should continue after the website becomes publicly available.
Production hosting may behave differently from the staging environment.
After launch, repeat the most important checks.
Confirm that the homepage loads, contact forms work, navigation is correct and analytics events are being collected.
For WooCommerce stores, verify that the live payment configuration is operating as intended.
Check HTTPS, redirects, canonical URLs and indexing directives.
This final review helps identify problems introduced during deployment.
25. Establish an Ongoing Maintenance Plan
Website testing does not end permanently after launch.
WordPress, plugins, hosting systems and integrations continue changing.
A maintenance plan should define who is responsible for updates, backups, monitoring, security and technical support.
Businesses should also consider how they will monitor enquiries, website performance and Google Search visibility.
Ongoing maintenance helps protect the website after the initial launch.
Complete Website Launch Checklist
| Area | Launch requirement | Status |
|---|---|---|
| Content | Main pages reviewed and approved | ☐ |
| Mobile | Responsive layouts tested | ☐ |
| Browsers | Important browsers tested | ☐ |
| Navigation | Menus and internal links checked | ☐ |
| Forms | Successful submission and email delivery tested | ☐ |
| Contact | Phone, WhatsApp and email links checked | ☐ |
| Performance | Key pages reviewed for speed | ☐ |
| Security | HTTPS and access settings checked | ☐ |
| Backups | Backup and recovery plan confirmed | ☐ |
| Technical SEO | Noindex, robots.txt and canonicals reviewed | ☐ |
| Sitemap | Production XML sitemap checked | ☐ |
| Search Console | Property verification prepared or completed | ☐ |
| Analytics | GA4 and GTM tested | ☐ |
| Privacy | Relevant notices and consent setup reviewed | ☐ |
| E-commerce | Checkout and payments tested, if applicable | ☐ |
| Hosting | Production environment verified | ☐ |
| Accessibility | Key accessibility checks completed | ☐ |
| Metadata | Titles and descriptions reviewed | ☐ |
| Structured data | Relevant schema validated | ☐ |
| Media | Images and videos tested | ☐ |
| Redirects | Old-to-new URL mapping tested | ☐ |
| Error handling | Missing pages return appropriate status | ☐ |
| Business details | Contact information and content verified | ☐ |
| Post-launch | Live website checked after deployment | ☐ |
| Maintenance | Ongoing support responsibilities agreed | ☐ |
Frequently Asked Questions
How Do I Test a Website Before Launching It?
Review content, navigation, forms, mobile layouts, browser compatibility, performance, security, technical SEO and analytics. Test the live website again after deployment.
What Is a Website Launch Checklist?
A website launch checklist is a structured list of tests and requirements used to confirm that a website is ready for public use.
Should I Test My Website on Mobile?
Yes. Mobile testing helps identify layout, navigation and functionality problems that may not appear on desktop devices.
How Do I Know Whether Google Can Index My Website?
Review robots.txt, noindex directives, canonical tags and important page responses. After launch, Google Search Console can provide additional information about crawling and indexing.
Does Submitting a Sitemap Guarantee Google Indexing?
No. A sitemap helps Google discover URLs, but it does not guarantee indexing.
Should GA4 Be Installed Before Launch?
Ideally, yes. Testing GA4 and important events before launch helps ensure useful measurement is available when the website becomes public.
What Should I Test on a WooCommerce Website?
Test products, carts, checkout, payment gateways, shipping, taxes, order confirmations and failed-payment handling.
Do I Need a Backup Before Launch?
A suitable backup and recovery plan is strongly recommended, especially when replacing or migrating an existing website.
Can I Launch a Website Without Completing Every Test?
The decision depends on the website and the severity of outstanding issues. Critical problems involving payments, security, forms or public accessibility should generally be resolved before launch.
Should I Test My Website Again After Launch?
Yes. DNS, hosting, caching, integrations and production settings can introduce problems that were not present in development.
Launch Your Website With Confidence
A successful website launch involves much more than publishing a homepage.
The website needs to work correctly for visitors, provide a reliable way for customers to contact the business and be technically accessible to search engines.
Testing forms, navigation, mobile layouts, security, performance, technical SEO and analytics helps reduce avoidable launch problems.
At Web Anatomy, we help businesses with website development, WordPress management, hosting, technical SEO and website tracking.
Whether you are launching a new WordPress website, redesigning an existing site or moving a custom application to a new hosting environment, a structured testing process can help make the transition more reliable.
Preparing to launch a new website?
Contact Web Anatomy to discuss a pre-launch website audit, technical testing or website development requirements.
Last updated: 10 November 2026.
