Every developer knows the feeling. The site is built, the client is happy with the designs, and launch day is almost here. That’s usually when the small things slip through: a form still sending to a test inbox, a favicon nobody added, a console full of red errors and forgotten test messages.
This is the checklist we run before every go-live. It’s in the order we actually do things, with a quick note on why each step matters.
1. Record speed test results
Before touching any optimisation, run the site through PageSpeed Insights and record the results for both mobile and desktop. Save the scores, the Core Web Vitals (LCP, CLS and INP) and the total page weight, and test the homepage plus at least one inner page and one single template. This is your “before” snapshot. Without it, you can’t show how much difference your optimisation work made, and clients love seeing that difference in numbers.
2. Review files
Make sure your code doesn’t contain blocks that aren’t being used on the site. Check for header, footer, blog or single blog files that never get called, and for CSS or JS files that have been uploaded more than once. Think of it as spring cleaning, only with fewer dust sheets.
3. Review links on main pages
Go through the header, footer and main content areas and click everything. The header logo should take visitors to the homepage, and every menu item, button and call to action should point to the correct destination. Watch for links still pointing at the staging domain, links that open in the wrong tab, and placeholder # links that were never replaced. It’s tedious work, but a broken link on a main page is one of the first things a client will spot.
4. Are forms correctly connected and set up?
Submit every form on the site with real test data and confirm the notification arrives at the correct email address, not your own inbox or a placeholder. Check the confirmation message or redirect, the auto-responder if there is one, and that spam protection such as reCAPTCHA or a honeypot is working. Also look at where the submissions are stored, and whether any CRM or mailing list integrations are receiving the data. Forms are how many clients get their enquiries, so a silent failure here costs real business.
5. Booking mask
If the site has a booking mask, test the full journey from the front end to the booking engine. Check that it’s connected to the correct property or account, that the date picker shows the right dates and blocks out the past, and that the selected dates, guest numbers and language are passed through to the booking page correctly. Test it on mobile as well, because date pickers are notorious for behaving differently on smaller screens.
6. Conversion tools
Test every conversion tool and make sure each one is styled in tune with the rest of the design and works properly.
7. Language switcher
If the site is multilingual, check that the language switcher takes visitors to the equivalent page in the other language, not just the homepage. Dropping someone on the homepage after they’ve switched language is the digital equivalent of being sent back to the start of a queue.
8. Check videos are playing correctly
Test every video on desktop and mobile. Check that autoplay behaves as intended (browsers usually require videos to be muted), that looping and controls work, and that a poster image appears while loading. Keep an eye on file size too, because a huge background video will undo a lot of good work on performance.
9. Google Maps API and Instagram
Confirm that the Google Maps API key is in place, restricted to the correct domain, and that billing is set up on the Google Cloud account. Without billing, maps often load with a “for development purposes only” watermark or fail entirely. Remember that the Places API, Geocoding API and Maps JavaScript API all need to be enabled too. Do the same for Instagram: check that the feed or social links are connected and that the content displays properly.
10. Google Maps JSON style and pins
Apply the custom map style from the JSON file so the map matches the site’s branding. Check that the custom pins appear in the right places with the right icon, that any info windows or click behaviour work, and that the map is usable on mobile without trapping the user’s scroll. As a nice extra, add a short message on the editor side, because the map won’t render there and it helps people see that the block will show a map on the live site.
11. Terms and Conditions, Privacy Policy and Cookie Policy
Check that all the links in the copyright footer go to the correct pages, and that those pages contain final content rather than placeholders. Then test the cookie banner: it should appear on first visit, respect the visitor’s choice, and genuinely block non-essential scripts until consent is given. Depending on your client’s market, these pages are a legal requirement, so they need to be right from day one.
12. Check the 404 page
Visit a URL that doesn’t exist and see what happens. The page should be styled to match the site, show the correct header and footer, and give visitors a clear way back, such as a link to the homepage, a search box or links to popular pages. Also confirm it returns a genuine 404 status code.
13. No console errors
Open the browser developer tools on the key pages and check the console. Fix any JavaScript errors, failed network requests, 404s for missing files and warnings about deprecated features. Also remove every test message you added during development and then forgot about. A clean console is a good sign that the code is in good shape, and it saves you from a client opening it out of curiosity and finding “TEST 2 why isn’t this working”.
14. No assets loaded twice
This usually happens when a theme and a plugin both enqueue the same library, such as jQuery, a CSS file or a slider script, or when a font is loaded from both Google Fonts and the theme. Duplicates add unnecessary weight, slow the page down and can cause conflicts, so dequeue what you don’t need.
15. Responsive and cross-browser testing
Ideally you’ll have done this before reaching this stage, but it’s worth one last look. Test on current versions of Chrome, Safari, Firefox and Edge at the very least. Check a range of breakpoints, including tablets and large desktop screens, not just a typical phone and laptop. Safari, in particular, likes to do its own thing.
16. Accessibility basics
Run through the essentials: descriptive alt text on meaningful images, sufficient colour contrast, a logical heading structure, labels on form fields, keyboard navigation and visible focus states. An automated tool like Lighthouse or WAVE will catch a lot, but also try tabbing through the page yourself. These are quick wins that make the site better for everyone and reduce legal and reputational risk.
17. Add favicon
Make sure the favicon is added in all the required sizes so it displays properly in browser tabs, bookmarks, search results and on mobile home screens. It’s a small detail, but a missing favicon makes a site look unfinished the moment someone opens the tab.
18. Manifest.json
Check that the web app manifest exists, is linked in the head of the site, and has the correct name, short name, icons and theme colour. It controls how the site appears when saved to a phone’s home screen and how the browser interface is tinted. Validate it in the browser’s application panel, and make sure the icon paths actually resolve.
19. Screenshot theme file
Add the theme’s screenshot.png so the site is easy to identify in the WordPress dashboard. It’s a small touch that matters more than you might expect on a multisite network, where you may be managing a number of similar-looking themes, and it shows the project has been properly finished off.
20. Analytics and tracking
Confirm that Google Analytics, Tag Manager and any marketing pixels are installed, firing correctly and respecting the visitor’s cookie consent choices. Use the real-time reports or the browser’s tag debugging tools to check that page views and key events, such as form submissions and booking clicks, are being recorded. Everything should be added through our cookie plugin or, in some cases, a third-party cookie plugin. It’s much easier to fix tracking before launch than to explain missing data a month later.
21. Delete unused plugins and themes
Remove any plugins and themes you aren’t using. Fewer plugins means a lighter site, a smaller attack surface and less to update later.
22. Install WP Rocket and set up
Once everything else is done, install WP Rocket and configure it: page caching, file minification and combination, lazy loading for images and iframes, preloading and database cleanup. We do this last on purpose, because debugging functionality through a cache is frustrating and can hide the real cause of a problem. Take your time with the settings rather than switching everything on at once.
23. Re-check the site after WP Rocket
Minification, combining files and delayed JavaScript are brilliant for performance, but they can also break sliders, forms, maps, menus and third-party scripts. Retest the key features, from the forms and booking mask to the language switcher and videos, and check the console again. If something has broken, exclude the relevant script or file from the optimisation rather than switching the whole feature off.
24. Record speed test results
Run the same tests you ran at the start, on the same pages, under the same conditions, and compare the results with your baseline. Record the final scores and the improvement in load time, page weight and Core Web Vitals. Share the before and after with the client, because numbers make the case for your work better than any explanation could, and they give you something to refer back to if performance slips later.
Final thought
None of these checks are complicated, but missing even one can be embarrassing after launch. The value of a checklist is that it takes the memory out of the process, so you aren’t relying on remembering everything at the end of a long project. Keep the list, tick it off every time, and add to it whenever a project teaches you something new.