.png)
.png)
.png)
How to Test a New Trade Website Before Launch
By Blackbird Marketing
A new trade website should not go live simply because the pages look finished. Before launch, test the actions that generate work, the technical settings that help search engines understand the site, and the details that affect whether a potential customer trusts it enough to make contact.
The most important checks are straightforward: submit every enquiry form, call the numbers shown on the site, test it on a mobile, check every important redirect, confirm tracking works and make sure the new site is not accidentally hidden from search engines. Record the results rather than relying on memory.
In short: Treat the launch as a controlled change, not just a design handover. Test the customer journey first, then check redirects, indexing, analytics and business details before pointing the old domain at the new website.
Start with the enquiries a trade website must protect
The first test is not a technical one. It is whether a customer can quickly understand what you do and contact you without hesitation. A plumber, electrician, builder or other trade business should test the journeys for someone who is ready to request work, someone comparing options and someone looking for basic reassurance.
Test every contact route
Work through the site as a customer and test each route separately. Do not assume that one successful form submission proves the other forms, buttons and phone links work.
Submit every enquiry form using a real test address and a clear test message.
Check that the confirmation message is understandable and that the email reaches the intended inbox.
Reply to the test email to confirm that replies go to a monitored address.
Click every telephone link on a mobile device and check that the number is correct.
Test email links, quote buttons, booking links and any links to messaging services.
Check whether required fields, error messages and consent options work as expected.
Make sure form failures are visible. A form that appears to submit successfully but sends nothing is more damaging than a clear error message, because the lost enquiry may never be noticed.
Follow the customer journey without internal knowledge
Ask someone who was not involved in building the site to find a service, understand the next step and make contact. They may notice unclear wording, a buried phone number or a menu label that makes sense to the project team but not to a customer.
Check the journey from at least three starting points: the home page, a service page and a search result landing page. A visitor may not arrive through the front door, so every important page should explain what the business does and what the reader can do next.
For a more focused navigation check, see How Trade Businesses Can Check Website Navigation Against Customer Search Journeys. The title itself reflects an important point: navigation should be checked against the way customers look for work, not just against the site's internal page structure.
Check the content that affects trust and conversion
Before launch, read each important page as a potential customer would. A new design cannot compensate for missing service information, contradictory details or vague calls to action.
Confirm the business details are consistent
Compare the new website with the details the business actually uses. Check the trading name, phone number, email address, opening information, service descriptions and any stated locations. Correct inconsistencies before launch rather than expecting customers to work out which detail is current.
Do not add a wider service area, emergency availability, qualification, guarantee or specialist service just because it sounds useful. If a claim cannot be confirmed by the business, leave it out or ask for approval before publication.
Review service pages for decision-making information
Each main service page should make clear what the service involves, who it is for and how the reader should enquire. It should also avoid promising an outcome or method that the business has not agreed to provide.
Look for practical gaps such as:
unclear differences between related services;
no explanation of the type of work accepted;
missing information about what the customer should include in an enquiry;
calls to action that use vague wording such as submit or click here;
old prices, phone numbers, staff names or references to a previous website.
Check headings, page titles and introductory paragraphs as well. They should describe the actual service on that page rather than forcing several unrelated keywords into the copy.
Check images, documents and legal pages
Open every image and downloadable document. Replace broken images, remove duplicate or irrelevant files, check that images have useful alternative text where needed, and confirm that PDFs do not contain outdated contact details.
Also check the privacy notice, cookie information, terms and any consent controls. The exact requirements depend on how the site collects data and which tools it uses, so obtain suitable legal advice where necessary rather than copying a generic policy without checking it.
Test the technical SEO before the site is public
A website can be attractive and still be difficult for search engines to crawl. The key pre-launch task is to identify what will change from the old site and make sure important pages remain accessible through the correct addresses.
Prepare a page and URL comparison
Make a simple list of the old site's important URLs and match each one to its replacement. Include the home page, service pages, location pages, contact page, useful guides and any pages that receive links or search visits.
For each old URL, decide whether it should:
remain at the same address;
redirect permanently to a closely matching new page;
be replaced by a relevant parent page; or
return a deliberate not-found response because the content has genuinely been removed.
Do not redirect every old address to the home page. That can leave visitors without the information they expected and gives search engines a poor match between the old and new content.
Check redirects, canonicals and index settings
Test redirects from the old domain, the www and non-www versions, HTTP and HTTPS versions, and important old page addresses. Each should reach the intended final URL without a chain of unnecessary redirects or a loop.
On the new site, check that important pages are not marked noindex, that canonical tags point to the correct preferred URL, and that the robots.txt file is not blocking the whole site or an important section. A common launch error is leaving a staging site's noindex setting in place.
Review the XML sitemap after launch preparation. It should contain the preferred, working URLs that the business wants search engines to discover, not test pages, duplicate addresses or old URLs.
Review titles, headings and internal links
Every important page should have a distinctive title and a clear main heading that match its subject. Check that service pages link to the contact route and to other relevant pages, while old internal links do not point to removed URLs.
Use a crawl of the staging site or a manual sample of important pages to find broken links, missing titles, duplicate titles and pages that cannot be reached through normal navigation. The exact tools can vary; the important point is to test the site as both a visitor and a crawler.
Test mobile use, speed and accessibility
Trade customers may visit from a phone while travelling between jobs or comparing businesses. Do not assume a responsive design has solved every mobile problem. Use several screen sizes and check the actual tasks a visitor needs to complete.
Can the main service be understood without excessive scrolling?
Is the phone button easy to find and tap?
Do menus open, close and remain usable on a small screen?
Are text, buttons and form fields large enough to use accurately?
Do banners, pop-ups or cookie controls cover the contact action?
Do images, videos and embedded maps load without pushing content around?
Run performance checks on representative pages, not just the home page. Large images, unnecessary scripts, chat tools, tracking tags and poorly configured fonts can slow down a site, particularly on a weaker mobile connection. Fix the largest practical problems first instead of chasing a score without considering usability.
Accessibility checks should include keyboard navigation, visible focus states, sensible heading order, sufficient contrast, labels for form fields and useful alternative text. These checks improve usability for people with different needs and can expose problems that affect every visitor.
Confirm analytics, calls and other measurement work
A launch is harder to manage if the business cannot tell whether an enquiry was completed or where visitors dropped out. Before launch, list the actions that matter and test whether each is recorded once, accurately and in the right account.
Depending on the website, this may include:
form submissions and confirmation pages;
telephone link clicks;
email or messaging link clicks;
quote or booking completions;
clicks to an external booking or payment system;
organic landing pages and search performance data.
Check that test activity is distinguishable from genuine enquiries and that duplicate tags are not counting one action several times. Confirm who has access to the analytics, tag management and search accounts; a site should not depend on one individual's personal login.
Also check any call tracking or advertising conversion setup separately. A phone call can be the main commercial action for a trade business, but it will not appear in form data unless the relevant tracking arrangement has been configured and tested.
Plan the launch as a controlled change
Use a written launch sheet with an owner beside each task. It should record the current site details, the new hosting or platform information, domain access, backups, redirect file, tracking IDs, form recipients and the rollback plan.
Before changing the live site, take a backup of the existing files and database where applicable. Keep a copy of the old URL list and important content. If a serious problem appears, the team needs a known recovery option rather than having to reconstruct the previous site under pressure.
Decide who will carry out the final checks and who will approve the switch. The website developer, business owner and person responsible for enquiries may each notice different problems, so do not leave the launch review entirely to the person who built the pages.
Blackbird Marketing describes its website work as moving through review, plan, build and launch or improvement stages. That published process is a useful model for treating launch as part of the work rather than as the moment the design is handed over. Its resources page also lists a New Website Launch Checklist; refer to the exact published resource rather than assuming every listed resource is available as a download.
What to check immediately after launch
Repeat the highest-risk tests on the live domain. Staging can hide problems caused by hosting, DNS, HTTPS certificates, live email settings, caching or third-party integrations.
Open the home page, key service pages and contact page from different devices.
Submit a live test enquiry and confirm delivery, notification and reply handling.
Call or test the displayed number and check that it reaches the intended destination.
Test old important URLs and confirm that redirects reach the right new pages.
Check the live source or settings for noindex, robots.txt, canonical and sitemap errors.
Confirm analytics and conversion records appear without duplicate counts.
Look for visible errors, missing images, broken menus and mixed-content warnings.
Monitor enquiries and search data for unexpected changes, then record and fix issues promptly.
Search visibility does not depend on one launch-day check. A new site may need further review when pages, redirects, tracking or content are changed. Keep the old URL list and launch notes so future updates can be tested against the same baseline.
When to get outside help
For a small site with no URL changes, a careful owner-led test may be enough. Outside help becomes more sensible when the website is replacing an established site, has many service or location pages, uses several lead systems, includes paid advertising, or has already suffered from lost enquiries or indexing problems.
Ask whoever is helping to explain what will be checked, which access they need, how redirects will be handled and how problems will be reported. If the work includes search or paid campaigns, confirm that tracking and landing pages are included in the discussion rather than treating the visual build as the whole launch.
Blackbird Marketing publishes services including web design, local and technical SEO, and digital marketing for tradespeople. If the site needs a planned build or a launch review alongside the marketing work, you can consider Blackbird Marketing's business website service and ask whether it suits the required website and testing work.
Ready to check the launch properly? Reduce the risk of missed enquiries by discussing the new site's customer journey, technical checks and handover requirements with Blackbird Marketing's business website team.
