The South African Business Website Launch Checklist: 15 Tests Before Going Live

A polished homepage is only one part of a successful launch. This website launch checklist for South Africa focuses on the issues that tend to appear after a redesign: missed enquiries, broken redirects, mobile layout failures and tracking that was never tested.

Create a spreadsheet with each check, a responsible person, a test date and a pass/fail result. Run it on a staging site where possible. The goal is a repeatable release process rather than a final inspection performed five minutes before launch.

1–5: Check the customer experience

1. Confirm the primary message. A first-time visitor should understand what you sell, where you serve customers and what to do next. Test the homepage with someone who has not seen the project.

2. Test the menu on a phone. Open and close the mobile menu, tap submenus and ensure no content disappears under a sticky header. Include a small Android device, not only a large desktop preview.

3. Check every main call to action. Buttons labelled “Get a Quote” must go to the correct form or contact route. Avoid links that unexpectedly open unrelated pages.

4. Review text legibility. Body text should not need pinch-zooming. Ensure sufficient contrast, descriptive link labels and visible keyboard focus states.

5. Optimise images. Give each useful image a relevant alternative description, choose sensible dimensions and test image-heavy pages on a slower connection.

6–10: Protect your search visibility

6. Inventory the old URLs. Export existing pages, posts and their indexed addresses before replacing the site. A redesign is not a reason to casually delete URLs that receive traffic.

7. Map redirects. Set permanent redirects for retired pages to the closest matching replacement, not indiscriminately to the homepage. Test a sample with real requests.

8. Review page titles and headings. Each important page needs a clear title and one meaningful primary heading. Avoid copying the same service paragraph onto every city page.

9. Confirm indexability. In WordPress, check Settings → Reading for the search-engine visibility option. Inspect important pages for noindex, canonical mistakes and staging-domain URLs.

10. Confirm the XML sitemap. Verify that the sitemap is accessible and contains your intended indexable pages. Rank Math can manage the sitemap, but Google Search Console still needs configuration and ongoing review.

Google’s Search Essentials explain the basic requirements for appearing in Search; passing a checklist does not guarantee immediate indexing.

11–15: Make sure the business can use the site

11. Submit every form. Enter a genuine test name, email and telephone number. Confirm the correct mailbox receives it, validation is clear, and a helpful confirmation appears. WordPress email delivery often requires authenticated SMTP or another transactional mail service.

12. Test click-to-call and WhatsApp. Mobile telephone links should use the correct number, and WhatsApp links must open a valid conversation. Confirm the international prefix where required.

13. Confirm analytics events. In GA4, check the realtime or debug view for test enquiry submissions. Do not count mere visits to the contact page as qualified leads unless that is intentional.

14. Test privacy and trust pages. Publish a privacy notice relevant to the information you collect. For South African businesses, review POPIA implications with appropriate legal guidance, especially for lead forms and marketing follow-up.

15. Test backups and recovery. Confirm an independent backup exists and that your team knows how to restore it. Capture access details and a rollback procedure before changing DNS or activating the new theme.

A practical sign-off method

Assign the business owner to approve messaging, prices and contact details; the designer to approve responsive layouts and accessibility; and the developer or SEO lead to approve redirects, technical SEO, analytics and forms. One person can hold multiple roles, but each decision needs an owner.

Do two passes: the first on staging, the second after the public domain is live. DNS, CDN caching, email authentication and browser behaviour can differ after deployment.

Frequently asked questions

What is the biggest mistake during a WordPress redesign?

Changing established URLs without an inventory and redirect plan is a common preventable risk. Another is publishing a working design whose forms send no email. Both deserve explicit tests.

Should I publish every drafted article on launch day?

Not automatically. Review each article for factual accuracy, topical fit, authorship, internal links and duplication. A smaller set of complete, helpful pages is more useful than an unreviewed bulk upload.

Use the checklist before the switch

Save this page as a test script and ask your supplier to report the results in writing. If you need support planning a website redesign, request a launch checklist and redirect map as contractual deliverables.