Your homepage loads and everything looks normal. As far as you can tell, the website is working.

But has anyone checked what happens when a customer submits an enquiry? Does the message reach your team? Can they reply? If you sell online, can a customer complete an order and can your team see it?

A website can appear to work while something behind the scenes is affecting those actions. Email may be going to the wrong place. A form may display a confirmation even though the enquiry never reaches the intended inbox. Your team may be unable to upload images or update pages while visitors can still browse the site.

These challenges can affect leads and day-to-day operations without making the homepage disappear. That is why website reliability needs to be assessed from the customer’s first visit through to the business receiving and handling their request.

Why migration checks go beyond the homepage

During a recent server migration, I had to check more than whether the websites loaded. Email routing and the server configuration needed to run WordPress also required attention.

During separate follow-up work, one site reached the storage limit of its hosting package. An automatic WordPress update then failed, leaving incomplete WordPress files and taking the website offline. The previous site remained intact on the old server, providing a rollback option by pointing the domain back. The storage limitation affected that particular hosting package, rather than the server’s overall capacity.

These were different challenges at different stages, and each required its own checks.

A website move is only complete once the services the business relies on have been checked. Seeing the homepage on the new server is a useful first step. Email, enquiries and routine website administration still need to be tested.

What a working website means for a business

For a service business, the website should help a prospective customer find the right information and make contact. The enquiry then needs to reach someone who can respond.

For an online shop, the customer needs to be able to place an order. The business also needs the order details so it can fulfil that purchase.

Your team needs to be able to maintain the site too. If they cannot update a service, upload an image or complete routine maintenance, the website has an operational limitation even if its existing pages still load.

There are three useful questions to ask:

• Can customers reach the pages they need?
• Can they complete the enquiry, booking or purchase?
• Does the business receive what it needs to take the next step?

A basic uptime check can tell you whether a page responds. It does not answer all three questions.

Where the hidden challenges can arise

The website works but email does not

Your domain has settings that direct visitors to the website and other settings that direct email to the mail service. These settings are part of DNS, the system that tells other computers where to find your services.

During a hosting migration, the website may be moved while email stays with its existing provider. That can work well, provided the correct settings are preserved.

A nameserver change needs care because it changes where the domain’s DNS settings are managed. The new setup must include the records needed for email and any other services that are staying in place.

Ask your technical team to confirm which services are moving and which are staying. Then test website access and email separately. If one is working, it does not prove the other is working.

DNS caching means people may see different results for a while after a change. Your technical team should check the actual settings rather than assuming every unresolved issue will disappear once the DNS changes have had time to propagate.

The form says thank you but the team receives nothing

A customer submits a form and sees a confirmation. From their perspective, they have contacted you and are waiting for a reply.

The business still needs to confirm that the enquiry arrived. WordPress’s own documentation explains that a successful email request does not automatically mean the recipient received the message.

Test the form by submitting a clearly labelled enquiry and checking the intended inbox. If the form sends details to a CRM or another system, check that destination as well. Finally, reply to the test enquiry.

Some forms also save submissions on the website. Where that is configured, a saved entry may help you recover an enquiry if the email notification fails. Do not assume your form does this without checking.

Pages load but certain website functions fail

WordPress needs more than a selected PHP version to run correctly. PHP is the software that runs much of WordPress, and it uses additional modules for particular tasks. The modules the site needs must be available, and the theme and plugins must work with the chosen configuration.

A site using cached copies of pages may still display those pages while another function fails. For example, an existing page may load even though an image upload encounters an error.

This is why the actual website functions need testing. Can your team edit a page and upload an image? Can a customer submit a form or complete a purchase?

The technical configuration matters because of what it allows the business and its customers to do.

Storage limitations or missing files interrupt maintenance

WordPress needs sufficient free storage within its hosting package to complete updates. A site can reach the limit of its own package even when the server still has storage available. If the site has too little space, or files cannot be copied successfully, an update may fail to complete.

After a migration or restoration, your technical team should also check that the required website files and database content are present. Loading the homepage alone will not confirm that the transfer was complete.

WordPress provides tools for checking its core files against the official versions. That is one useful check, but forms, uploads, plugins and other business functions still need their own tests.

Search engines or advertising systems cannot reach the right pages

A page loading on your computer does not prove that Google’s systems can reach it. Access restrictions, server errors or a problem affecting a particular page may produce a different result.

Google explains that server errors can slow its crawling. Pages that keep returning server errors may eventually be removed from the search index. A short interruption does not automatically mean a lasting loss of rankings.

Google Ads also requires accessible landing pages. DNS errors, timeouts or error responses can lead to an advert being disapproved under its destination requirements.

A working landing page with a failed enquiry form creates a different concern. Someone may reach the offer and try to contact you, but your team receives no enquiry. That does not automatically mean Google will disapprove the advert.

Our article on why Google Ads landing pages matter looks at the wider experience after the click. Checking whether an enquiry reaches the business is part of making that experience useful.

What to check after a website or hosting change

You do not need to understand every server setting. You do need to know that the important business functions have been tested.

After a migration, DNS change, major update or recovery, ask your technical team to check the following:

• Important pages: open the service and campaign pages customers use, including on mobile.
• Enquiries: submit a test form and confirm the details reach the intended inbox and any connected system.
• Email: test incoming and outgoing business email, and reply to the form enquiry.
• Bookings or purchases: use an agreed test method and confirm the result appears where your team handles it.
• Administration: check that your team can edit content, upload images and carry out routine maintenance.
• Technical setup: confirm the DNS settings, server configuration, available storage and website files have been checked.
• Search and advertising: investigate new access errors, crawl issues or advert disapprovals.

Ask for a short summary of what passed, what still needs attention and who will resolve it. Technical logs may help the people investigating a fault, but the business owner also needs an understandable answer.

Repeat the important customer tests periodically during normal operation. Agree how often they will be done and who is responsible. A successful test confirms what worked at that time; monitoring and later tests help identify subsequent changes.

If enquiries drop check before drawing conclusions

Fewer enquiries do not automatically mean there is a hosting problem. Demand, traffic quality, the offer, website content and the way enquiries are handled can all play a part.

Start by checking where the gap appears. Are people reaching the relevant pages? Are form submissions being recorded? Do those enquiries reach the team, and are they being answered?

A test enquiry with a recognisable reference helps you follow the process. It also gives the technical team a specific time and example to investigate if something fails.

Analytics may record a form interaction without proving that the enquiry reached the business. Compare the tracking information with actual submissions and received messages where those records are available.

If the enquiry process works, continue reviewing the marketing and sales process. The aim is to establish what needs attention before changing budgets or deciding which service is responsible.

Ask what was tested

When someone says the website is working, ask what that assessment includes.

Were the important pages checked? Did a test enquiry reach the intended person? Does email work in both directions? Can your team maintain the website?

It should also be clear who handles a challenge that involves more than one service. Hosting, website maintenance, email and marketing may have different responsibilities, but the business still needs someone to coordinate the investigation.

A reliable website supports the complete task: the customer can take the intended action, the business receives the result and the team can keep the site running.

If you are unsure how your website, hosting and enquiry process fit together, speak to us about reviewing the setup and agreeing the checks your business needs.