Developer gone? Liverpool WordPress maintenance next
When a Liverpool business loses contact with the person who built its WordPress site, the problem usually isn’t that WordPress has become impossible to understand. The real mess is access. Hosting, domain control, plugin licences, backups, admin users and old fixes are often spread across inboxes, personal accounts and half-remembered logins. That is where the fun starts.
A WordPress site can usually be taken over safely by another competent provider once ownership, administrator access, hosting, domain settings, licences, backups and existing faults are documented. The first job is not redesigning the website or blaming the old developer. It is establishing control, checking what is currently working, creating a restore point and setting a maintenance baseline before routine changes make the situation worse.
The false assumption: only the original developer can maintain it
Not ideal, but also not true.
The original developer may know why certain choices were made. That can help. But WordPress sites are not sacred artefacts that only one person can touch. A capable WordPress maintenance provider can usually work out the build, dependencies and risks if the business can prove ownership and provide enough access.
The real issue is power. If your first serious fault arrives before you control the hosting, domain and licences, you are negotiating from a weak position. A contact form failure, PHP version change, expired licence or malware warning suddenly becomes urgent. Urgent handovers are expensive in time, attention and stress, even when the technical fix is fairly ordinary.
Decision one: do you actually own the essentials?
Start with ownership, not loyalty. Website maintenance starts with control of the website, not with the person who originally built it.
For a Liverpool company, a common scenario is this: you have WordPress admin access, so you assume you are fine. Then you discover the old freelancer controls the hosting account, several premium plugin licences, the theme licence and maybe the backup storage. You can edit a page, but you cannot properly protect, move or recover the site.
| Area | What to check | Why it matters |
|---|---|---|
| Domain | Registrar login, DNS access and renewal contact | Without it, email, hosting moves and redirects can become awkward fast |
| Hosting | Account owner, server access, PHP version and backup tools | Admin access inside WordPress is not the same as server control |
| WordPress users | Administrator accounts, unknown users and old supplier logins | Too many admin users creates avoidable risk |
| Licences | Theme, page builder, forms, security, backups and WooCommerce extensions | Expired licences can block updates or support |
| Backups | Where backups live, how often they run and whether one restores | A backup nobody has tested is a nice thought, not a recovery plan |
Decision two: repair first or maintenance first?
Pick the route based on the state of the website, not your frustration with the old supplier.
If the site is stable, start with a takeover baseline
If pages load, forms work and there are no active errors, do not start changing plugins just to feel productive. Stop changing things until you know what changed first.
A proper baseline should include:
- A fresh off-site backup and a note of where it is stored
- A list of active plugins, theme, WordPress version and PHP version
- A review of admin users and email addresses attached to the site
- A check of contact forms, SMTP settings and delivery inboxes
- A record of visible faults, console errors or broken layouts
- A licence list showing what renews under whose account
One boring detail that catches businesses out: the form can show a success message while delivery fails. If the form sends through an old Gmail account, a dead Microsoft mailbox or no authenticated SMTP at all, enquiries may vanish without the website looking broken. A form that says thanks but sends nothing is not working. It is just being polite about failing.
If the site is already broken, contain the fault first
If the checkout is failing, forms are dead, the homepage is down or the admin area is throwing errors, treat it as website repair before ongoing maintenance. Do not bulk update everything on a live site during business hours and hope for the best. The plugin might be guilty. It might also just be standing closest to the scene of the crime.
In that case, get a restore point, document the current symptoms and follow a controlled fix route. For active faults in Liverpool, Liverpool website repair and recovery support is the more sensible starting point than a monthly maintenance plan pretending nothing is on fire.
Decision three: keep old licences or move them into business control?
Premium WordPress licences are often the awkward bit. Elementor Pro, Gravity Forms, WP Rocket, security tools, backup services, booking plugins, WooCommerce extensions and themes can all sit inside a developer’s account.
You have three realistic choices:
- Transfer the licence if the supplier is responsive and the product allows it
- Buy a new licence under the business if the old one cannot be transferred cleanly
- Replace the dependency if the plugin is poor, abandoned or unnecessary
Do not remove premium plugins blindly. Some will keep working for a while without a valid licence, but updates, templates, form integrations or support may stop. That becomes a maintenance issue later, usually on a day when nobody has time for it.
Decision four: who holds the keys after takeover?
The business should own the domain, hosting relationship, primary licences and recovery route. Your maintenance provider can manage them, but the company should not be locked out of its own commercial asset.
A clean setup usually means:
- The domain sits in an account owned by the business
- Hosting billing and account recovery go to a company-controlled email
- At least two trusted admin users exist, with sensible access control
- Backups are stored somewhere separate from the hosting
- Licences are documented with renewal dates and account owners
- Maintenance actions are logged, especially updates and repairs
This is exactly where ongoing WordPress maintenance in Liverpool should begin: not with a vague promise to keep things updated, but with a takeover checklist that gives the business control, visibility and a practical maintenance routine.
A sensible takeover sequence
Use this order. It avoids the usual panic shuffle.
- Confirm ownership. Domain, hosting, WordPress, licences and key email accounts.
- Create a current backup. Store it somewhere separate and record the method.
- Audit access. Remove unknown admin users only after you understand what they do.
- Document dependencies. Plugins, theme, custom code, integrations, forms, payment tools and tracking.
- Test lead routes. Forms, phone links, WhatsApp links, booking buttons and email delivery.
- Record existing faults. Separate old issues from anything caused during takeover.
- Set the first maintenance baseline. Update plan, backup schedule, licence plan and repair priorities.
The smallest sensible next action is simple: make a list of what you can access today and what still sits with the old supplier. Do that before rebuilding your website, before paying for ads and before another plugin update breaks something.
FAQs
Can another developer take over my Liverpool WordPress website?
Usually, yes. Another competent WordPress provider can normally take over if they have administrator access, hosting access, domain information, licence details and a clear list of known faults. The harder part is often proving ownership and collecting credentials, not understanding the WordPress build itself.
What if I only have WordPress admin access?
WordPress admin access is useful, but it is not full control. You may still need hosting access, database access, domain DNS control, backup storage access and premium plugin licence details. Without those, maintenance is limited and recovery can become harder if the site breaks.
Should I contact the old developer before moving the website?
If the relationship is still workable, yes. Ask for hosting details, domain registrar information, licence ownership, backup locations and notes on custom code. Keep it factual. You are not asking for a debate. You are collecting business-critical information so the site can be maintained properly.
Can WordPress maintenance fix old website faults?
Maintenance can include troubleshooting, but active faults should be identified clearly before routine updates begin. Broken forms, layout issues, checkout errors or server problems may need repair work first. Once the site is stable, maintenance can reduce avoidable disruption, though it cannot guarantee nothing will ever fail.
What should a Liverpool business collect before a WordPress takeover?
Collect domain login, hosting login, WordPress admin access, backup details, licence information, form delivery settings, key integrations and a list of known problems. Include boring things like the email address used for SMTP and renewals. Boring is excellent when something goes wrong.
Get control before the fault arrives
A disappeared developer is irritating. A disappeared developer plus no hosting access, no licence records and no tested backup is worse.
Email Standish Services if you want a practical takeover review for a Liverpool WordPress site. Collect the access and ownership information before the next fault turns the handover into an emergency.