It happens more than it should. You hired a developer, the project went reasonably well, the site launched, and then at some point you needed something and the developer stopped responding. Maybe it was gradual: slower replies, then very slow replies, then nothing. Maybe it was sudden: you sent an email and it just never came back. Either way, you are now in possession of a website and not in possession of a developer who knows how it works.
This is one of the more stressful situations a business owner can find themselves in, particularly if the site has any complexity to it or if something has gone wrong and you need help. So let me walk through how to handle it.
First: Figure Out What You Actually Have Access To
Before you do anything else, take stock of what you control. This is the most important first step and it will shape everything that follows.
Do you have admin access to your WordPress dashboard? Log in and confirm it works. If the developer set up the site under their own account and made you a lesser role, that is a problem you need to address.
Do you control the domain? Log in to your domain registrar and confirm the domain is registered to you or your business, not to the developer. If a developer registered your domain under their account, that is a serious situation that may require some effort to resolve, but it is resolvable.
Do you control the hosting? Log in to your hosting account and confirm access. If the developer set up hosting under their own account and you have been paying them for it, you may not have direct access. That is worth addressing quickly.
Do you have the login credentials for any third-party services connected to your site? Email marketing platforms, CRM integrations, payment gateways, analytics accounts. Make a list of what is connected and whether you have direct access to each one.
If you have all of the above, you are in a much better position than you might feel right now. The developer is gone but the assets are yours and you can move forward. If any of these are missing, prioritizing recovery of those assets is your first order of business.
Getting Your Credentials Back
If your domain or hosting is registered under the developer's account, start with a polite but direct email requesting transfer. Most developers, even ones who have gone quiet on support requests, will respond to a direct request for asset transfer because they understand it is the right thing to do and it closes out the relationship cleanly.
If that does not work, contact the registrar or hosting provider directly. Explain that you are the business owner and that the account was set up by a contractor. Most registrars have a process for resolving ownership disputes, and if you can demonstrate that the domain represents your business name and brand, they will generally work with you.
For hosting, the process varies by provider but the principle is the same. Document your ownership of the business and make the case that the account should be transferred to you.
Understanding What Was Built
Once you have access sorted out, spend some time understanding what you are working with. This does not require being technical, but it does require being thorough.
Log into your WordPress dashboard and look at the plugins list. Note what is installed and whether anything is showing update notices or alerts. Look at the theme. Is it a commercial theme with a license that needs to be renewed, or something custom? Are there any plugins that look like they require a subscription or license key that you may not have?
If the developer used any tools or services you are not familiar with, now is the time to investigate what they are, whether you are paying for them, and whether you have your own account or whether access was through the developer.
This audit is not about understanding how to maintain the site yourself. It is about understanding what you own and what dependencies exist, so that the next developer you bring in can get oriented quickly.
Inherited a WordPress site with no documentation?
We have taken over more orphaned sites than we can count. Honest assessment, fixed-price diagnostic, and a clear plan to stabilize what you have or rebuild what cannot be saved.
Finding Someone to Take Over
When you bring in a new developer to take over a site they did not build, the quality of the handoff documentation you can provide makes a real difference in how smoothly that goes. If you have nothing, that is fine. A good developer can work with what is there. It just takes more time at the start to understand the existing setup.
Be honest about what you know and what you do not. Tell the new developer what you know about how the site was built, what plugins are in use, what has been customized, and what has changed recently. Even incomplete information is useful.
Be realistic about expectations. Taking over someone else's code always takes longer than working from scratch, and sometimes the honest recommendation after a full review is that certain things need to be rebuilt rather than maintained. That is not a failure on anyone's part. It is just the reality of inheriting a codebase with no documentation and no handoff.
The Bigger Picture
Developer disappearances happen for all kinds of reasons. Health issues, burnout, business failure, a career change. In most cases it is not malicious, it is just disruptive. And the businesses that weather it best are the ones that maintained control of their own assets throughout the relationship.
If this experience has left you wanting a more stable arrangement going forward, that is a completely reasonable conclusion to reach. A developer or firm that has been around for a while, communicates clearly, and gives you full ownership of everything from day one is a different kind of relationship than the one that just ended.
If you need someone to assess what you have, sort out access issues, or take over maintenance and support of a site you inherited, that is work we do. We have seen this situation more times than I can count and we know how to get things stabilized quickly.
