Something has stopped working on your WordPress website. Perhaps a page is showing an error, a form has stopped sending enquiries, or you cannot log in to the dashboard.
You know you need help, but it is not always clear who to ask. Should you contact your hosting provider, the developer of a plugin, a WordPress support forum or someone who can investigate the whole website?
The answer depends on what has gone wrong and how urgently it needs attention.
This guide explains what to check first, where to find WordPress support, how to describe a problem clearly and when it makes sense to get professional help.
First, work out how serious the problem is
Before changing anything, consider what the issue means for your website and its visitors.
A small layout problem on a rarely visited page is different from a checkout that has stopped taking orders. A suspicious redirect or unexpected administrator account may also require a different response from a routine technical error.
Ask yourself:
- Is the entire website unavailable, or is only one page or feature affected?
- Can customers still place orders, make bookings or send enquiries?
- Is the issue affecting every visitor or only certain users?
- Are there signs of a security incident, such as malware warnings or unexpected changes?
- Did the problem begin after a particular update, edit or hosting change?
If the issue is causing significant business disruption, treat it as urgent and contact the provider or support team responsible for the affected service.
For a WordPress problem that needs urgent attention, you can also use our emergency WordPress support page to explain what has happened and find the appropriate support route.
Newt Labs does not provide guaranteed instant or 24/7 emergency support. Urgent enquiries are reviewed during our available support coverage.
If you suspect your website has been compromised, avoid experimenting with random fixes. Preserve useful evidence, contact your hosting or security provider and arrange appropriate security assistance.
What can you check before asking for help?
You do not need to diagnose the problem yourself. A few simple observations, however, can help you explain what is happening and avoid unnecessary changes.
Check whether the problem is repeatable
Open the affected page again and note exactly what happens.
If appropriate, check it in another browser or a private browsing window. This can help establish whether the issue might be related to your current browser session, but it does not establish the underlying cause.
If a customer reported the problem, ask which page or action was affected. Do not assume that everything works simply because you cannot reproduce the issue yourself.
Check for a recent change
Think about what happened shortly before the problem appeared.
Was WordPress updated? Did someone install a plugin, edit the theme, change a setting or move the website to another host?
A recent change is a useful clue, not proof of what caused the problem.
Make a note of it rather than immediately reversing changes on a live website.
Look for a clear error message
If WordPress displays an error, copy the exact wording or take a screenshot.
A message such as “Error establishing a database connection” provides a more useful starting point than saying that the website is broken.
If your dashboard is accessible, Tools → Site Health may also highlight issues worth investigating. Its information screen contains technical details that can help a support provider understand your setup.
Review anything you share from the dashboard and remove sensitive information before posting it publicly.
Avoid making the issue worse
Do not repeatedly update, reinstall or deactivate software just to see what happens.
In particular, switching themes or deactivating all plugins on a live business website can interrupt its appearance or essential functionality.
Plugin and theme conflict testing is better performed on a staging copy or through an appropriate troubleshooting method that does not change the experience of ordinary visitors.
Make sure there is a suitable backup and recovery plan before carrying out potentially disruptive work.
Our WordPress backup and recovery guide explains what a usable backup should include and why restoration matters.
Where can you get WordPress support?
WordPress problems do not all belong with the same provider. Start with whoever is responsible for the affected part of your website.
1. Your website hosting provider
Your hosting provider is a sensible first contact if the website is completely unavailable or the issue appears to involve the server or hosting account.
Examples include:
- Hosting control-panel or server-access problems.
- Server resource limits or hosting outages.
- Database-server availability.
- Hosting-managed backups and restorations.
- SSL or domain settings managed by the host.
A hosting provider may also help you identify whether a problem is occurring at server level.
However, hosting support does not necessarily include fixing plugin conflicts, editing a theme or repairing custom WordPress code.
Check what your hosting package actually covers rather than assuming every WordPress problem is included.
If your domain, DNS or email is managed by a different company, that provider may be the appropriate contact for issues affecting those services.
2. Your plugin or theme developer
If a problem appears limited to a particular plugin or theme, check its official documentation and support channel.
For a plugin downloaded from WordPress.org, you can usually find its support forum through the plugin’s directory page.
If you purchased a commercial plugin or theme, use the developer’s own customer-support service. The WordPress.org forums direct commercial-product support questions to the product provider.
When contacting a developer, explain which feature is failing, which version you are using and whether the problem followed an update.
Avoid assuming that a plugin is responsible simply because its name appears in an error message. More than one component may be involved.
3. WordPress documentation and community forums
The official WordPress documentation can help you understand WordPress features and investigate common issues.
The WordPress.org support forums offer community help for self-hosted WordPress websites, with dedicated areas for plugins and themes.
Search for the exact error message or describe your issue in an appropriate forum.
Remember that these are volunteer-supported resources. A reply, response time or successful fix is not guaranteed.
Do not post passwords, login details, private customer information or confidential website data in a public support topic.
If your site is hosted on WordPress.com, use its own support resources and the support options available with your plan. WordPress.com and a self-hosted WordPress installation can have different support arrangements.
4. A professional WordPress support provider
Some issues cross several parts of a website.
A broken checkout, for example, could involve a plugin, payment integration, theme, hosting configuration or more than one of these.
If you cannot identify who is responsible, need someone to investigate safely or simply do not have time to troubleshoot, a WordPress support provider can help assess the problem.
Professional assistance is also worth considering when a failure affects important business functions or the website needs changes beyond the scope of hosting support.
You do not necessarily need an ongoing contract for a defined problem.
Newt Labs offers one-off WordPress services for issues, repairs, website changes and other specific tasks. If you are unsure which service applies, you can describe the problem in a one-off support enquiry and have the appropriate next step reviewed.
How to write a WordPress support request
A clear support request helps the person investigating understand the problem without guessing or repeatedly asking for basic details.
You do not need to use technical language. Explain what you are seeing and what you expected to happen.
Include the following information where it is relevant and safe to share.
Your website and the affected page
Provide your website address and a link to the specific page where the issue occurs.
If the problem is in an area that is not publicly accessible, identify the page or feature without sharing private access details.
What is happening
Describe the symptoms as precisely as you can.
For example, “The contact form shows a success message, but no enquiry arrives in our inbox” is more useful than “The form is broken”.
Include the exact error message if one appears.
What should happen instead
Explain the expected result.
For a checkout issue, that might be: “A customer should be able to complete payment and receive an order confirmation.”
This helps support distinguish the intended behaviour from the actual result.
When the problem started
Give the approximate date and time, including your time zone if relevant.
If you know that the issue started after an update or other change, mention it. If you are unsure, say so.
How to reproduce it
Describe the steps that trigger the problem, if you can reproduce it safely.
For example:
- Open the contact page.
- Complete the form.
- Select Submit.
- A success message appears, but the enquiry does not arrive.
Do not keep submitting real payments or customer orders just to demonstrate a problem.
What you have already checked
Mention any simple checks you performed and their results.
This could include testing another browser, checking the hosting provider’s status page or reviewing a recent change.
Do not claim to have ruled out a cause unless you have actually tested it.
How the issue affects your business
Explain whether the problem is cosmetic, affects one feature or prevents customers from using the website.
If checkout, bookings, logins or enquiries are affected, make that clear.
This gives the support provider the context needed to assess the request.
Screenshots and technical details
A screenshot can be useful when the problem is visual or an error message is difficult to describe.
WordPress version, plugin or theme details may also help, particularly for a compatibility issue.
You can find information about your installation under Tools → Site Health → Info, if your dashboard is accessible.
Before sharing screenshots, logs or technical details, check for passwords, access tokens, customer data and other confidential information.
Do not send passwords through a public forum or an ordinary enquiry form.
A simple example of a useful support request
Subject: Contact form enquiries stopped arriving
“Hello, our contact form at example.com/contact/ shows a success message after submission, but we have not received enquiries since yesterday afternoon.
The problem affects our main enquiry form, so potential customer messages may be getting lost.
I tested the form once in another browser and saw the same result. We updated a form plugin yesterday morning, although I do not know whether that caused the issue.
Could you investigate and let us know what you need from us?”
This gives the support provider a clear symptom, the affected page, business impact and a relevant recent change without requiring the website owner to diagnose the fault.
If you have several unrelated issues, separate requests can make them easier to track. Keep related symptoms together when they may be part of the same incident.
How should you give a support provider access?
A support provider may need access to WordPress or your hosting account to investigate and fix an issue.
Only provide access after confirming who you are dealing with and what they need.
Where possible, create a separate account for the person or team helping you. Give it only the permissions required for the agreed work.
Use a secure access-sharing method rather than emailing passwords or posting credentials in a support thread.
If access is temporary, review and remove it when the work is finished. Keep your own administrator access and ensure that your website has an appropriate backup before significant changes begin.
For a suspected security incident, discuss the safest access and recovery process with the provider rather than making uncoordinated changes.
Should you get a one-off fix or ongoing WordPress support?
The right arrangement depends on whether you have one defined task or need regular help looking after the website.
One-off help is a practical starting point when a page is broken, a form needs fixing, a plugin conflict needs investigation or you have a specific website change to make.
Ongoing care is intended for recurring responsibilities such as updates, monitoring, backups and support over time, with the exact coverage depending on the plan.
You can start with a one-off service without committing to a monthly plan.
If the same problems keep recurring or routine upkeep is being postponed, it may be useful to review your wider maintenance arrangements.
Our guide to signs you may need WordPress maintenance support explores that decision in more detail.
If you already know you want ongoing support, compare the available options on our WordPress Care Plans page. Maintenance provides the foundation, with Security and Performance adding broader levels of care.
Get help with your WordPress website
You do not need to know the exact cause of a WordPress problem before asking for help.
Start by noting what is affected, how serious it is and whether anything changed recently. Choose the support channel responsible for the issue, then share a clear description without exposing sensitive information.
If you need help with a specific problem or change, explore our one-off WordPress services.
Not sure which service fits? Tell us what is happening and we will review your enquiry and help identify the appropriate next step.
For businesses looking for regular website upkeep and support, you can also compare our Care Plans.
